Skip to main content

Posts

[SAP EWM] Return to Vendor Scenario

You have three primary methods for generating a return delivery to the vendor: 1. Creating the Return Delivery Option A: Directly in SAP EWM ( /SCWM/PRDI ) Open transaction /SCWM/PRDI ( Maintain Inbound Delivery ), select the relevant inbound delivery, and navigate to Inbound Delivery - Follow-on Function - Return to Vendor in the menu bar to generate the corresponding return delivery. Option B: In SAP ECC via Inbound Delivery Processing ( VL60 ) Access transaction VL60 ( Inbound Delivery Processing ) in the ECC system, locate your delivery, and select Quantity Differences - Return Quantities to trigger the return delivery. Option C: In SAP ECC via Goods Movement ( MIGO ) Launch transaction MIGO in ECC, set the action to Return Delivery , and select Material Document as the reference document (entering the original goods receipt material document number). Ensure that you also select the Via Delivery checkbox so the system generates a delivery rather than posting an imm...
Post a Comment
Read more
Recent posts

[SAP EWM] End of the day Carrier Manifestation

Requirement: Send an "End of Day Manifest" to carriers to sync shipment tracking data from EWM system. Architectural Approaches: Third-Party Systems: Use platforms like Kewill or Descartes to handle carrier API synchronization. Direct SAP Integration: Develop a custom SAP program to call the carrier’s manifest API directly. Mediated/Proxy Integration: Route data from SAP to a third-party system using a proxy  SI_CLOSE_CARRIER_OUT_SYNC , allowing the third-party system to interface with the carrier.
1 comment
Read more

How to reverse initial stock upload for EWM - SAP S/4HANA

Issue  In General, initial stock was posted into EWM via legacy migration or the Post Goods Movement app (MIGO) using movement type 561 . Due to data entry errors, a stock reversal or adjustment is now required to remove incorrectly posted items Solution Approach Approach 1. Create the physical inventory document and count the stock as "0", post the difference at difference analyzer. Movement type is 711. Approach 2. Do scrapping with APP Post Goods Issue - Unplanned (APP ID /SCWM/ADGI), select the GI process "Scrapping". Movement type is 711.
Post a Comment
Read more

[SAP EWM] ODO split is not supported in combination with TU assignment error Message No. /SCWM/DELIVERY_CONF050

Issue  System is not creating outbound delivery orders due to the error message /SCWM/DELIVERY_CONF050 ODO split is not supported in combination with TU assignment even though no TU relevancy exist for this document type Resolution Check if the PDO doctype has the flag 'Outbound SPlit' = 'O - ODO split'.  The ODO split is not allowed with TUs.  If you use TU please change the flag 'Outbound SPlit' to Default Logic.  If you don't use TUs please deactivate the DTU status. 
Post a Comment
Read more

[SAP SD] Delivery block after delivery creation

 At times, there will be a requirement where business want to block the delivery as soon as delivery is created based on certain parameters. As standard system doesnt block the delivery after the delivery creation to accomplish this requirement, custom logic need to be built.  From technical standpoint, Program 'MV50AFZ1' and User exit 'USEREXIT_MOVE_FIELD_TO_LIKP' need to be leveraged in this situation to accomplish this requirement
Post a Comment
Read more

[SAP SD] Custom storage location determination in delivery

At times, business requires to determine storage location through various parameters apart from the standard configuration setup. In this situation, as we cannot accomplish this requirement through standard SAP functionality so we need to leverage customer exit 'EXIT_SAPLV02V_002' to accomplish this. In parallel, from technical level we can achieve the same through BADI 'LE_SHP_DELIVERY_PROC~FILL_DELIVERY_ITEM' to accomplish this requirement.
Post a Comment
Read more

[SAP SD] Availability check exit

When SAP performs an ATP check, it follows standard rules (checking groups, checking sections, etc.). However, businesses often have "special sauce" requirements that the standard configuration can't handle.  In that situation, Exit 'EXIT_SAPLATPC_002' need to be leveraged to accomplish the custom requirement to build custom rules.
Post a Comment
Read more