SAP LP22 Replenishment Program Update
Uploaded by
fkamaliyahSAP LP22 Replenishment Program Update
Uploaded by
fkamaliyahCommon questions
Powered by AIAccording to user requirements, when handling stock with the same expiry date, the replenishment program should follow a precise sequence: stock should be taken from Less Full Pallet (LFP) first, then High Rack (HR), and finally Drive-In (DI). This ensures a logical order that aligns with storage efficiency and operational priorities. The current system doesn't support this sequence and instead removes stock based on default storage type order without considering this specified logic .
The SAP standard program RLLNACH2 faces challenges in following specific storage type sequences when replenishing. Vietnam business requirements demand that stock removal sequence starts from LFP, then HR, finally DI for same expiry date stocks, while the program currently can't manage this and defaults to a non-sequential removal. This can lead to inefficiencies and stock misalignment with the customer's logistical strategies .
The transactional codes (Tcodes) involved in the replenishment process are LP22, LB10, and LT04. LP22 is used for executing the replenishment to create a transfer requirement (TR) quantity. LB10 is used for displaying the transfer requirement, and LT04 is used to search and create the transfer order based on expiry date and available stock in storage types .
The field 'MLGT_NSMNG' in the replenishment process represents the defined quantity for an item number in the material master warehouse management view. It is crucial for calculating replenishment needs. For instance, if the outbound quantity is 2500, and the defined quantity (MLGT_NSMNG) is 600, this indicates a need for multiple replenishment operations. The system calculates that 4 replenishments are required (600 x 4 = 2400) to ensure stock availability. This calculated quantity guides the system to search and remove stock from LFP, HR, and DI as per the replenishment logic .
When multiple storage bins have the same expiry date, the program implements a strategy that employs the specific search sequence of Less Full Pallet (LFP), followed by High Rack (HR), and then Drive-In (DI), to manage the removal process efficiently. This strategy is designed to optimize the pick-face replenishment by prioritizing stock removal from LFP first, ensuring stock with the nearest expiry date is utilized, in alignment with the business's operational needs .
The SAP standard replenishment program uses a priority sequence for stock removal when stock items have the same expiry date. The system should prioritize stock removal from Less Full Pallet (LFP), followed by High Rack (HR), and then Drive-In (DI). This sequence ensures that stock is replenished from storage areas in a specific order when the expiry dates are identical. However, the current system configuration initially focuses on storage type removal without adhering strictly to this sequence, which the business requirement aims to address .
The primary limitation of the current replenishment program is its inability to follow the desired replenishment sequence (LFP, HR, DI) when multiple stock items have the same expiry date. Instead, it relies on the default storage type sequence for removal. To address this, the proposal recommends modifying the logic to ensure the system searches and removes stock based on the preferred sequence if the expiry date is the same .
In the SAP replenishment process, the transfer requirement (TR) is a precursor to the transfer order (TO). TR is created through the execution of Tcode LP22, which determines the needed quantity for replenishment. Subsequently, through Tcode LT04 (or visible in LB10), a transfer order is generated based on this TR, facilitating the actual transfer of stock within the warehouse as per the replenishment needs .
The FEFO (First Expiry First Out) logic is critical in the replenishment process as it prioritizes the removal of older stock with earlier expiration dates to minimize waste and ensure freshness. However, when stock items have the same expiry date, the FEFO logic becomes less effective. In these situations, the system should follow a specific sequence (LFP first, then HR, and DI) to optimize the replenishment process rather than reliant purely on expiry dates .
When the outbound delivery request exceeds the available stock at the pick face bin, the system calculates the shortage and then uses the defined replenishment quantity (MLGT_NSMNG) to multiply the number of replenishments needed. It then searches for available stock at LFP, HR, and DI based on the FEFO logic. If multiple stock items have the same expiry date, the system must search by storage type and prioritize removal based on the predefined sequence: LFP, HR, DI, to ensure effective replenishment .