Shelf Life management
- Basics
- What are the BBD/SLED fields/Was sind die BBD/SLED-Felder?
- What are functions do we have with SLED?
- When it is calculated?
- What are the prerequisites?
- How can I avoid recalculation of the expiration date in the case of goods movements?
- Additional information
- 2190893 - Shelf Life Expiration fields not available in MIGO
- 2915951 - SLED/BBD check on batch during goods issue
- 2281693 - Remaining shelf life check problem (Goods receipt for purchase order)
- Enhancements
Basics
What are the BBD/SLED fields/Was sind die BBD/SLED-Felder?
The last goods receipt date (LWEDT) is set during the receipt of the goods from production orders or external purchase orders. If the system is set to plant level, the date is also set during the receipt of the goods for a stock transport order.
We can either maintain this date field in the batch master record manually or have it derived from the date of manufacture if a total shelf life has been entered in the master record of the batch material.
Depending on how it is defined, this field can be interpreted as the best-before date (minimum shelf life) or the shelf life expiration date (maximum shelf life).
If the batch was created in the process order or references a process order, the value of this field is the same as that of the BBD/SLED field in the process order.
- Batch record: Date of Manufacture (MCHA-HSDAT)
- Batch record: Best-Before Date (BBD) or Shelf Life Expiration Date (SLED)
Fields
- Batch record: Date from which the batch is available
- Batch record: Period Indicator for Shelf Life Expiration Date
- The period indicator specifies the unit of measurement for a period of time.
- Material master: Minimum Remaining Shelf Life
- Material master: Total Shelf Life
What are functions do we have with SLED?
- Purchase order: PO item level, Delivery tab contains a field Minimum Remaining Shelf Life (minimum amount of time for which the material must keep upon goods receipt).
- Automatic calculation and check of the SLED of a batch: If the total shelf life is specified in the material master record, the system calculates the SLED as follows: SLED = total shelf life + production date from GR document.
- Rounding off the SLED that has been calculated automatically: SLEDs that are specified manually are not rounded off.
- If the minimum remaining shelf life is specified in the material master record, the system calculates the remaining shelf life from the day of goods receipt to the SLED. The remaining shelf life must be greater than the minimum remaining shelf life for the batch to be accepted.
- Dynamic Date Determination* ( SPRO: Batch Valuation> Update Standard Characteristics; create the dependencies between the required characteristics yourself by creating a function and an object dependency)
- Dynamic Determination of Availability Date
- Dynamic Determination of a Different Date
- Dynamic Determination of SLED
When it is calculated?
- At goods receipt (GR)
- Upon automatic goods movements
What are the prerequisites?
You must activate the automatic calculation of the shelf life expiration date or the shelf life expiration date check Customizing for Batch Management. Movement type ( OMJ5 ).The shelf life is only checked if the following prerequisites are met
- The minimum remaining shelf life is maintained in the material master record or in the purchase order.
- The shelf life expiration date check is active for the plant and movement type in Customizing for Inventory Management.
How can I avoid recalculation of the expiration date in the case of goods movements?
- Start Transaction OCHS (Define properties of system messages) and change the category of message 005(12) from 'W' (Warning) to 'E' (Error).
Additional information
2190893 - Shelf Life Expiration fields not available in MIGO
- The customizing for the Expiration Date Check should to be set correctly against the relevant plant and the relevant movement type: SPRO -> SAP Reference IMG -> Materials Management -> Inventory Management and Physical Inventory -> Goods Receipt -> Set Expiration Date Check (transaction OMJ5). For the movement type, the 'Check SLExpDate' (KZMHD) setting needs to be set to '1 - Enter and Check' or '2 - Enter Only'.
- The field selection of Date of Manufacture and SLED/BBD for MIGO should be customised for Input: SPRO -> SAP Reference IMG -> Materials Management -> Inventory Management and Physical Inventory -> Settings for Enjoy Transactions -> Settings for Goods Movements (MIGO) -> Field Selection for MIGO (transaction OMJX).
2915951 - SLED/BBD check on batch during goods issue
Minimum remaining shelf life and total shelf life are relevant to goods receipt, they are not considered in goods issue.
- In OMCQ, set warning/message for M7667, then there will be a check on SLED/BBD in batch master and user local date(SY-DATLO), message will be issued if checks fail.
- If minimum remaining shelf life is required to be considered, implement customer check-in BAdI MB_CHECK_LINE_BADI.
2281693 - Remaining shelf life check problem (Goods receipt for purchase order)
If you maintain the remaining shelf life data in the purchase order in the Delivery tab, the system will ignore the shelf life data of the material master and will execute the shelf life check based on the data entered in the purchase order.
The minimum remaining shelf data can be maintained in the purchase order besides the material master record. The minimum remaining shelf data is the minimum number of days for which the material must keep for the receipt of the goods to be accepted by the system.
Notes
- If you use VL32N to post GR the shelf life expiration date (VFDAT) and date of manufacture (HSDAT) are taken from the inbound delivery. If LIPS-HSDAT and LIPS-VFDAT are filled in the inbound delivery these data are transferred to the MM-IM interface (MB_CREATE_GOODS_MOVEMENT) and the goods movement is posted with these data. Please note that prerequisite is that the SLED check is active on plant and also on the movement type level. You can check and set this in transaction OMJ5.
- If you use MIGO to post GR VFDAT and HSDAT are not taken from table LIPS. Instead, it gets the batch from the reference document and then reads its master data in VB_BATCH_GET_DETAIL. MIGO always copies the HSDAT and VFDAT from the batch master record (if this exists previously). If there is no previous batch master record, MIGO gets these fields empty. It is never copied from the inbound delivery.
- 33396 - Batch determination: Selection with remaining shelf life LOBM_RLZ
Enhancements
- Within customer exit EXIT_SAPLVBMD_001 (called in function module VB_MAINTAIN_MHD) you can control recalculation or expiration date using the indicators C_CALC (calculate) and C_CHECK (check). For more information refer to the documentation of function module VB_MAINTAIN_MHD.
- Using BadI method MAINTAIN_SLED_PARAMETERS of BAdI VB_SLED_MANAGEMENT (Notes 623203, 632741) you can override all relevant parameters of shelf life processing. For more information refer to the documentation of BAdI VB_SLED_MANAGEMENT.
Comments
Post a Comment