SAP Logistics

Whenever there is a new process setup by the SD team based on the business cases. It's a good practice to setup new document in EWM level as well.  Below are the config changes to be performed while creation of new document type :  Define Document Types for Outbound Delivery Process (copy from standard OUTB)  Map Document Types from ERP System to EWM  Control Message Processing Dependent on Recipient  Map Date Types from ERP System to EWM  Map Item Types from ERP System to EWM  Define Warehouse Process Type  Determine Storage Type Search Sequence for Stock Removal  Specify Storage Type Search Sequence Note : Always ensure that no process is controlled at the product master level i.e., item level. Some consultants use WPT indicator at product master data level as a parameter to control the business process. This is not good practice as this will have an impact when business try to use the same material for other processes as well.

 At times, business look for the personnel who did changes for a specific field in the product master. In this situation, SAP has given standard transaction code  '/SCWM/PROD_CD_READ' to view the change documents. Apart from the above transaction, the same can be access through warehouse monitor as well

 There are various ways to perform goods movement for a ODO in EWM : FM -  SCWM/PPF_POST_GM can be accomplish the requirement and this requires import parameters as ' DOCID' and 'DOCCAT' but the challenge for this FM is capturing the return messages. This FM will not return any message. To avoid the above situation, we have alternate way to handle this. Class /SCWM/CL_GOODS_MOVEMENT can be leveraged to accomplish the requirement as well by passing the same parameters as above in method /SCWM/IF_GM_DLV~POST_DLV. In general, this class will be called from the above mentioned FM

  In customizing, you can enable that an update is send to LE when warehouse activities are completed in EWM. Customizing path: SPRO -> SCWM Extended Warehouse Management -> Cross-Process Settings -> Delivery – Warehouse Request -> Process Management and Control -> Define Process Profile for Document Header Select the process profile and flag the checkbox “Ready for Shipping (Send Update to LE)”. When the EWM delivery is set to “Ready for Shipping”, the warehouse execution status is also updated in the LE delivery.

 Issue : Product has been posted goods issue (GI) from HU AAAA on storage bin BBBB. The GI reversal is stuck by error: /SCWM/GM034: You can only post to bin BBBB using a handling unit Root Cause : During GI cancellation the system tries to post the stock back into the same HU (which has been deleted in the meantime). If this HU no longer exists, it will try to post as unpacked stock to the same bin. However, this can be prevented by error /SCWM/GM034 in case of HUs are obligatory in that storage type and the GI happened by a product warehouse task (WT). Consider also it is not possible to cancel the goods movement and post the stock to a different HU. Solution Approach : In case the GI posting was done by a HU WT, then system re-creates automatically the HU posted for GI. In case the GI posting was done by a product WT there are two options: Option A) Change the storage type settings regarding HU requirement to value ' ' (HU allowed but not a requirement) and re-try the reverse

Below is the approach to be followed to fix the issue : Call transaction /SCWM/CHM_LOG. Choose "Ad-Hoc". On the following screen, choose "Stock and Bin" and enter the selection criteria by choosing the yellow arrow on the right (entry of warehouse number, storage type, and storage bin as required). From the checks available below this node, select "Available Quantity" and then select the line. As a result, the system should display the bulb icon on the left. At the level of the available stocks, you can optionally restrict your selection (arrow) to a transportation unit (TU), resource, or product. Make the selection using F8. The system now checks for inconsistencies. If there are any inconsistencies, they can be corrected by positioning the cursor on a line and right-clicking it, provided that the relevant function supports this. However, the selection criteria should be entered as specifically as possible. A selection that checks an entire storage type w

 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