SAP Logistics

 Issue  The system does not create the follow-up WT (Warehouse Task) in POSC (Process-Oriented Storage Control) despite Auto WT creation is enabled in the customizing for the concerned Storage Process Step. BAdI /SCWM/EX_WRKC_UI_AFTER_SAVE contain custom code and it is getting triggered in the process. Solution Approach In the EWM standard the follow-up WT is usually created by the fallback class that is assigned to BAdI /SCWM/CL_EI_WRKC_UI_AFTER_SAVE. If creating an own implementation for BAdI /SCWM/EX_WRKC_UI_AFTER_SAVE is needed, make sure that  either trigger the WT creation manually from you custom implementation, or that you call the respective method of /SCWM/CL_EI_WRKC_UI_AFTER_SAVE.

 Requirement  You manufacture a product integrated with Enhanced Warehouse Management (EWM) procedure. You expect the staging of the component to be triggered automatically upon the order release. However, after releasing the order, the staging request is not triggered and there is no new entry in app Process Posting Change Item. You have to trigger the staging manually in the order by going through "More/Functions/WM Material Staging/Execute". Solution Approach Since the "Posting Change Item" is a kind of "Delivery", if you want to trigger automatic EWM staging, you have to set the "WM Request" field of the Production Scheduling Profile as "2 - Transfer Reqmt, Transfer Order, and Delivery Upon Release". This configuration can be done by SSCUI 102508 "Define Production Scheduling Profile for Discrete Manufacturing".

 Requirement  While creating inbound delivery in ERP/S4 side you have added Incoterm data, but that field is not getting added in outbound queue to EWM. After LE Inbound Delivery distributed to EWM. Incoterm is always blank on EWM Inbound Delivery.  Root Cause  It's standard functionality to have Inco terms not transferred to EWM inbound delivery. The transfer of incoterm data (INCO1, INCO2) from ERP/S4 inbound deliveries to EWM inbound deliveries is not possible with the given interface FM /SCWM/INB_DLV_SAVEREPLICA. The FM does not contain this field in any parameter. The same holds vice versa in the other direction from EWM to ERP inbound deliveries. Incoterms can only be transferred for outbound deliveries.  You can find incoterm field in FM /SCWM/OUTB_DLV_SAVEREPLICA in parameter HEADER_DATA-INCOTERMS1 and HEADER_DATA-INCOTERMS2.

SET/GET parameters (user parameters) that you can maintain in transaction SU3 are available for both methods. You can use these parameters to prepopulate input values in the dialog boxes of the monitor methods. The respective dialog boxes then no longer appear. There are the following SET/GET parameters: /SCWM/MON_AQ_ACT -  For the method "Quantity Adjustment" /SCWM/MON_AQOD_ACT - For the method "Create Quantity Adjustment and Outbound Delivery" Both parameters can be filled according to the following logic. The parameter is set up as follows: <first parameter part><second parameter part> First parameter part (one-digit): This specifies the selection in the first dialog box. The first dialog box provides the following three different options. The first character in the parameter specifies which selection is made. The dialog box then no longer appears. It can contain values from 1 to 3. This means the following: "1": Adjust Quantity "2...

 Requirement  The issue involves performing a WBS-to-WBS transfer posting in the EWM site using a bulk upload program. Functional module /SCWM/CALL_POST was explored but did not enable the transfer posting functionality. The issue has caused delays in processing as each material must be handled individually. Solution Approach Functional module /SCWM/CALL_POST mainly calls transaction /SCWM/POST, but this is not a report and cannot be used in background mode. Perform the posting change in transaction /SCWM/POST. Use the mass change button within /SCWM/POST to update multiple lines with the same target data, if applicable. If the mass change button does not suffice, write a custom report that calls function module /SCWM/STOCK_CHANGE and pass all required data.

Requirement At times, we might require to change the WBS-element status for many WBS-elements. In this situation, as we cannot go one by one to change manually, SAP has provided different approaches to perform this activity depending on need. Solution Approach  Use transaction code CNMASSSTATUS or report RCNMASSSTATUS to change WBS-element status in batch. (CNMASSSTATUS can't be used to revoke DLFL status) Use BAPI_BUS2054_SET_STATUS to develop report to change WBS-element status by running a job in background. Use BADI: WORKBREAKDOWN_UPDATE to develop custom logic and update the WBS-status.