Skip to main content

[SAP EWM] ERP Delivery date (LIKP-LFDAT) is overwritten by EWM GI message

 Requirement :

After PGI in EWM, the delivery date (LIKP-LFDAT) in ERP which is in the past is overwritten by the EWM system.

This issue can happen even if you've defined "Do Not Confirm Date/Time" in the EWM side customizing: SPRO -> Extended Warehouse Management -> Interfaces -> ERP Integration -> Delivery Processing -> Map Date Types from ERP System to EWM.

Cause

Standard behaviors :

Scenario 1: If the delivery date (LIKP-LFDAT) in ERP is in the past, the actual goods issue date from item will be taken over as the new delivery date and sent to ERP during PGI. 
Scenario 2: In EWM, multiple ODOs are assigned to a TU and posted GI together. To avoid unexpected TU split, all deliveries belonging to this TU will get their delivery date updated to the earliest delivery date of all deliveries.

Resolution

Scenario 1 : implement BAdI /SCWM/EX_ERP_MAPOUT_OD_CONFDEC to remove WSHDRLFDAT from CT_BAPI_HEADER_DEADLINES parameter table if you don't want LFDAT to be overwritten in ERP.

Scenario 1 & 2: implement the BAdI /SCWM/EX_ERP_MAPIN_OD_SAVEREPL and update CT_DLV_REQUEST-S_HEAD-T_DATE[]-DATE_INDICATOR to  /scdl/if_dl_data_c=>sc_ind_external, value 'E'.

Comments

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).
4 comments
Read more

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.
Post a Comment
Read more

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...
1 comment
Read more