[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

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).

Revenue Account Determination - SAP SD

Revenue account determination is one critical integration point between Sales & Distribution and Financial Module. Here on posting a billing document to account, based on this revenue account determination, system determines relevant G/L accounts for revenue posting. As like any other basic function configuration like pricing, its configuration also based on condition technique. The condition technique is used in account determination in order to allocate the correct GL account and account key assigned in the pricing procedure against condition types carries the condition values from SD to FI. IMG -> SD -> Basic Function -> Account Assignment -> Revenue account determination -> Check master data relevant for account assignment. Through check master data relevant for account assignment, one has the opportunity to create account assignment grouping criteria. This grouping criteria provides the system with an extra variable in determ

Determinations in SAP SD

Plant Determination in Sales Order 1st Preference: System fetches Delivering plant from Customer Material Info Record if Plant is not found at this level then system will look into 2nd Preference: Delivering plant from Customer Master data if Plant is not found at this level then system will look into 3rd Preference : the Delivering plant for Material Master data If business user overwrites Plant at sales document level then this will be given highest preference. Shipping Point Determination Delivering Plant (Based on above conditions) + Shipping Conditions ( Sales Document Type or Customer Master Data) + Loading Group ( Material Master ) Storage Location Determination Plant + Shipping Point + Storage Conditions ( Material Master ) ( MALA) Plant + Shipping Point + Situation ( RETA) Route Determination Departure Zone or Country of the Delivering Plant + Destination Zone or Country of the Ship to Party + Shipping Condition from the Customer Master + Transport

SAP Logistics

Search This Blog