0% found this document useful (0 votes)
77 views13 pages

Example FS

This document provides a functional specification for enhancing the SAP Standard Replenishment program (Tcode LP22, Program RLLNACH2) for warehouse V10 (CG). The current program does not replenish stock with the same expiry date in the proper sequence from LFP, HR, and DI. The enhancement will modify the program to first replenish from LFP, then HR, then DI when stock has the same expiry date, fulfilling the required business process. It describes the business requirements, proposed solution including program inputs and outputs, and data processing rules to implement the necessary logic changes.

Uploaded by

fkamaliyah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
77 views13 pages

Example FS

This document provides a functional specification for enhancing the SAP Standard Replenishment program (Tcode LP22, Program RLLNACH2) for warehouse V10 (CG). The current program does not replenish stock with the same expiry date in the proper sequence from LFP, HR, and DI. The enhancement will modify the program to first replenish from LFP, then HR, then DI when stock has the same expiry date, fulfilling the required business process. It describes the business requirements, proposed solution including program inputs and outputs, and data processing rules to implement the necessary logic changes.

Uploaded by

fkamaliyah
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 13

Functional Specification

Enhancement
SAP Standard Replenishment program
Tcode; LP22
Program: RLLNACH2
Warehouse : V10 ( CG )
REVISION HISTORY
Version Amendment
Date Description Author
Number Number

OWNERSHIP
Process Owner
SAP Technical Owner
SAP Module
Type Of Development
Complexity
1 BUSINESS REQUIREMENTS ............................................................................ 4
1.1 DESCRIPTION ........................................................................................................................... 4
1.2 USER INTERFACE .....................................................................................................................4
1.3 PROCESS, PROCESS STEPS AND FLOWS................................................................................... 4
1.4 AUTHORIZATION REQUIREMENTS .............................................................................................. 4
1.5 OTHER REQUIREMENTS ............................................................................................................ 4
2 SOLUTION PROPOSAL ..................................................................................... 4
2.1 DESCRIPTION ........................................................................................................................... 4
2.2 PROGRAM INPUT ...................................................................................................................... 5
2.3 NAME OF SOURCE SYSTEM / LEGACY DATA .............................................................................. 6
2.4 MAPPING INFORMATION ............................................................................................................ 6
2.5 SOURCE RECORD LAYOUT ....................................................................................................... 6
2.6 SCREEN LAYOUT...................................................................................................................... 6
2.7 BADI / USER EXIT CRITERIA..................................................................................................... 6
3 DATA PROCESSING RULES, FORMULAE, CALCULATIONS ...................... 12
4 EXPECTED OUTPUT ....................................................................................... 12
4.1 OUTPUT REPORT AND/OR SCREEN LAYOUT............................................................................. 12
4.2 CRITERIA FOR UNIT TESTING .................................................................................................. 12
4.3 ERROR HANDLING REQUIREMENTS .......................................................................................... 13
4.4 IF NO OUTPUT IS REQUIRED, DESCRIPTION OF SUCCESSFUL COMPLETION OF PROGRAM ............ 13
1 BUSINESS REQUIREMENTS
1.1 DESCRIPTION

Need to develop new user exit for Replenishment for V10 (CG warehouse). For
replenishment Vietnam side execute the replenishment using In LP22 ( Program :
RLLNACH2) we create replenishment Transfer Requirement (TR) Quantity then go to
LB10 to create Transfer Order base on TR.
1.2 USER INTERFACE

Please refer to the attachment for the existing form.

1.3 PROCESS, PROCESS STEPS AND FLOWS

Currently the program RLLNACH2 able to create Transfer requirement from, Less Full
Pallet (LFP), High Rack (HR) and Drive in (DI) base on nearest expiry date (FEFO). The
limitation of this program it unable to replenish follow the sequence of stock removal
from LFP , HR and DI if the stock has same expiry date . This program currently
replenish the stock base on oldest quant which sitting at DI , HR and LFP, which subject
to user exit program for Putaway .

1.4 AUTHORIZATION REQUIREMENTS

N/A

1.5 OTHER REQUIREMENTS

N/A

2 SOLUTION PROPOSAL
2.1 DESCRIPTION

Warehouse
• CG : V10
• HEC : V20

Storage Type
• CG
o Pick Face : PF(Ambient Pick face) , PFA ( Air Con Pick Face )
o Less Than Full Pallet : LFP ( less full Pallet )
o High Rack : HR ( High Rack), HRA ( High Rack Air Con )
o Drive-In : DI, DIA
2.2 PROGRAM INPUT

Execution Type:
Required Execution Steps:
Variants (if applicable):
Navigational Criteria (if
applicable):

2.3 NAME OF SOURCE SYSTEM / LEGACY DATA

Transaction Code: LP22


SAP Programs:
SAP Forms:
SAP Package:

2.4 MAPPING INFORMATION

SAP Field External Target Target Field Mapping


Name System Field Length Format Description Rules/
Name Comments
Plant WERKS
Storage LGORT
Location
Warehouse LGNUM
Storage type LGTYP
Quant LQUA

2.5 PROGRAM INPUT

Execution Type:
Required Execution Steps:
Variants (if applicable):
Navigational Criteria (if
applicable):
2.6 NAME OF SOURCE SYSTEM / LEGACY DATA

Transaction Code: N/A


SAP Programs:

2.7 MAPPING INFORMATION

N/A
2.8 SOURCE RECORD LAYOUT

N/A

2.9 SCREEN LAYOUT

N/A

2.10 BADI / USER EXIT CRITERIA

Program Logic

B.REPLENISMENT

The Logic of replenishment is:

- First expiry date first out (FEFO) (first priority)

The second logic if same expiry date stock sitting in storage bin under
storage type LFP , HR ,DI or DIA ,HRA ,PFA then it should replenish :-
- Replenish from 1st search : LFP, 2nd search HR, 3rd search DI to PF
- Replenish from 1st search HRA , 2nd search DIA to PFA

Current situation

The replenishment Tcode LP22 unable to follow the replenishment sequence of LFP, HR , DI
if the stock has same expiry date

1. Replenishment:
The first priority is FEFO but now the system only focus on below logic:
Condition 1 ( No problem system able to determine )
Replenishment from Replenishment To

Follow FEFO Pick Face (PF )


Storage type ( HR , DI, LFP )

Condition 2 ( System unable to determine )


Replenishment from Replenishment To

Same Expiry date stock


available in DI , HR , LPF Pick Face (PF )
In this case replenish should start
from LFP , HR and DI

Current WMS configuration : -


Configuration for Replenishment search for Program RLLNACH2

Currently system manage to search the FEFO until “***”. But if have same expiry
date then system should remove for replenishment from LFP , HR , DI

User requires:

 The logic of replenishment focus on FEFO.


 If the expiry date is same but stock sitting in HR, LFP and DI then
the replenishment program should follow the sequence of LFP,
HR, and DI.
 Replenish from 1st search : LFP, 2nd search HR, 3rd search DI to
PF
 Replenish from 1st search HRA , 2nd search DIA to PFA

To fulfill the user requirement CSSC have propose to use Tcode: LP22 (Program:
RLLNACH2) in order to fulfil the requirement
:

The Field for Plant (WERKS) CG only plant VN08, storage location (LGORT): 1100,
Warehouse (LGNUM): V10 and Storage type (LGTYP): (PF)

Variant for the LP22 as shown below

Steps in executing the Tcode: LP22 (Program: RLLNACH2)

Steps : 1
To create the Transfer requirement need to execute the below screen (LP22 ). Here
the user will input : -The Field for Plant (WERKS) CG only plant VN08, storage
location (LGORT): 1100, Warehouse (LGNUM): V10 and Storage type (LGTYP): (PF)

Using this information the system will determine the delivery quantity base on
outbound quantity . For example if the outbound quantity is 2500 and the
replenishment qty which was define for the item number in material master (MM03) in
warehouse management view 2 is define 600 (field : MLGT_NSMNG ) and the stock
at Pick face Bin (filed : MLGT-LGPLA ) is 600 . In this case the available stock at pick
face is 600 therefore shortage of 1900 . Then system use the define 600 (field :
MLGT_NSMNG ) to multiply with 4 ( 600 qty define X need 4 time replenishment ) =
2400 .

Using is Qty = 2400 system will search the available stock at LFP, HR , DI base
FEFO in order to fulfil the qty .

But in search sequence if the stock has same expiry date (field : LQUA-VFDAT ) then
system should search the field : LQUA-LGTYP (storage type ) and sort it by storage
type LFP , HR DI at the same time It should remove the stock from XX-XX-01 to XX-
XX-05 for storage type DI .

Variant for LB10

The transfer Requirement can be display by using Tcode : LB10 as shown below .

Steps 2
The Transfer order can be create base on this TR number by click the button TO in
foreground or Background .

Transfer order is been create base on Tcode : LT04


In LT04 it will search base on expiry date . The above case same expiry date
7/10/2007 sitting in storage type DI , HR and LFP . Currently The replenishment
Transfer Order is created base on sequence storage type DI , HR and LFP . What
Vietnam business requirement is to create the TO base on LFP, HR , DI if the stock
has same expiry date .

This program will take into consideration the replenishment Qty base on: -

1. Open outbound delivery quantity

2. Total quantity available in Pick face


This replenishment program will read all the for the respective SKU and group it into
one TR

However the SAP standard program (RLLNACH2) unable to fulfill the conditions has
shown below :

Condition 2 ( System unable to determine )


Replenishment from Replenishment To

Same Expiry date stock


available in DI , HR , LPF Pick Face (PF )
In this case replenish should start
from LFP , HR and DI

• DATA PROCESSING RULES, FORMULAE, CALCULATIONS

Please refer to the Mapping Rules and Comments.

• EXPECTED OUTPUT
2.11 OUTPUT REPORT AND/OR SCREEN LAYOUT

N/A

2.12 CRITERIA FOR UNIT TESTING

N/A
2.13 ERROR HANDLING REQUIREMENTS

N/A

2.14 IF NO OUTPUT IS REQUIRED, DESCRIPTION OF SUCCESSFUL


COMPLETION OF PROGRAM

N/A

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy