SAP Knowledge Base Article - Public

3550366 - SLED Not Copied from Inbound Delivery to 'Post Goods Movement' app (MIGO) in SAP S/4HANA Cloud Public Edition

Symptom

  • By posting goods receipt (GR) in 'Change Inbound Delivery' app (VL32N) shelf life expiration date (VFDAT) and date of manufacture (HSDAT) are transferred from the inbound delivery.
  • By posting goods receipt (GR) in 'Post Goods Movement' app (MIGO) shelf life expiration date (VFDAT) and date of manufacture (HSDAT) are not transferred from the inbound delivery.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

If you use 'Change Inbound Delivery' app (VL32N) to post GR:

  1. Go to 'Change Inbound Delivery' app (VL32N) and enter the delivery number
  2. Push the button 'Post Goods Receipt' to book GR

If you use 'Post Goods Movement' app (MIGO) to post GR:

  1. Go to 'Post Goods Movement' app (MIGO) and enter the purchase order number
  2. Push enter to copy the data of purchase order
  3. VFDAT and HSDAT will be not completed

Resolution

This is the standard behavior and not an error.

If the 'Change Inbound Delivery' app (VL32N) is used 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 on movement type level. You can check and set this in Activity/SSCUI Set Expiration Date Check.

However, if the 'Post Goods Movement' app (MIGO) is used 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. 'Post Goods Movement' app (MIGO) always copies the HSDAT and VFDAT from the batch master record (if this exists previously). If there is no previous batch master record, 'Post Goods Movement' app (MIGO) gets these fields empty. It is never copied from the inbound delivery.

Keywords

SAP S/4HANA Cloud Public Edition, Inbound Delivery, MIGO transaction, date of manufacturing, Batch number, supplier batch, SLED date, LO-BM, Batch Management, SLED, not copied, IBD, MIGO, VL, inbound delivery, copy, displayed, missing, date of manufacturing , KBA , LE-SHP-DL-LA-2CL , Inbound Delivery (Public Cloud) , MM-IM-GR-MIGO-2CL , Goods Receipt from External Procurement (MIGO) (Public Cld) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions