SAP Logistics

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. 

 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

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.

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.

When business requirements necessitate additional validation for delivery creation—beyond standard schedule line confirmations and stock availability—you should implement custom logic within user exit EXIT_SAPLV50P_001 . This exit allows you to intercept the delivery creation process for specific sales order items and enforce unique parameters or business constraints before the document is generated. Technical Summary & Context In standard SAP, the delivery creation process primarily looks at the Material Availability Date and the Confirmed Quantity at the schedule line level. However, many organizations require "smarter" logic. Key Scenarios for EXIT_SAPLV50P_001: Credit/Block Checks: Preventing delivery if the customer has specific financial standing issues not caught by standard credit management. Item Grouping: Ensuring that Item B is never delivered unless Item A is also fully available  Custom Attribute Validation: Checking custom fields (Z-fields) in the Sales...

When business requirements dictate that shipment status or date calculations must bypass standard SAP protocols in favor of custom business rules, you should utilize the functional exit EXIT_SAPLV56F_011 . This exit provides the necessary hook to intercept shipment processing and inject your own logic to manipulate header or stage data before the document is finalized. Some of the sample requirements : Stage Level: Automatically update the shipment 'Planning' start and end dates at the stage level based on new delivery dates. Header Level: Once the shipment end date for the final stage is determined, that value must propagate to and update the shipment header.

 At times, business requires to add custom fields to the delivery list in transaction 'VL06' like addition of customer PO number, Freight order ....  To enhance the standard report, we need to leverage the customer exit 'EXIT_SAPLV50Q_001' and write logic related to fetching the data to accomplish this requirement. In this situation to get the Customer PO number, Pass VBGEL fetched from the LIPS into table VBKD to fetch the customer PO number 

 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.

Below are the useful parameter ID's in EWM    Parameter ID Description /SCWM/LGN Select the warehouse immediately /SCWM/MON Select immediately the correct Warehouse Monitor /SCWM/MON_NO_TREELAY Allow to disable saving of monitor tree /SCWM/MONNAV   Allow to select a hotspot in the Warehouse Monitor without opening a new modus /SCWM/MON_TECH Display Warehouse Monitor technical nodes /SCWM/RF_TECH_TITLE         Display the technical name of RF /SPE/IF_DEBUG_QRFC            This parameter has to be set on ERP side. It allows debugging qRFC from ERP to EWM /SCWM/IF_DEBUG_QRFC      This parameter has to be set on EWM side. It allows debugging qRFC from EWM to ERP ...

Issue When user is trying to enter the serial number manually in EWM, error message serial number already exist is getting displayed Analysis : Whenever serial number is assigned to the inbound delivery, as soon as inbound delivery is saved /SCWM/SERI table will be updated with serial number and inbound delivery combination. Now, when user try to use the same serial number for another inbound delivery by  mistake then system will validate against this table and restrict business user from saving the document. Below is the solution approach to be followed to fix this issue in this situation To check if the Serial Number is assigned to a different inbound delivery follow the steps below: Go to transaction code /SE16 and execute table /SCWM/SERI; Select the relevant Product and Serial Number; Execute the selection; You will see a line that contantains the DOCID which has the corresponding SN assigned; Copy the DOCID; Run table /SCDL/DB_PROCH_I; Enter the previously copied DOCID; The i...

At times, business want to control update of Country of Origin (COO) , Vendor and other details of batch master data based on certain conditions like for certain material types this has to be updated .... In this situation, we have to leverage the Exit 'EXIT_SAPLV01Z_013' to accomplish the requirement.

 In some cases, the capacity related data of the bin, stock or HU are calculated incorrectly. Or the master data is changed. The data must be corrected on database level. Common issues like Storage Bin cannot be deleted in transaction code /SCWM/LS02; Warehouse task cannot be confirmed due to storage bin inconsistency; Inconsistencies in the storage bins - number of HUs. Empty flag (field KZLER) is not set even if: No stocks (physical neither available) exist & no open/on hold WTs exist. Storage bin inconsistency is the root cause for all the above issues. To resolve this, please follow the below steps :  1. Go to transaction /SCWM/CHM_LOG --->  click on Ad-Hoc button; 2. Go to node Stock and Bin, click on 'Selection' button and insert a Warehouse number and storage bins: 3. Open the Capacity check node, 'Choose' Recalculate capacity, click on 'Selection' button and check either 'Update bin only' or 'HU counters + Empty bin flag' and execu...

Below is the solution approach for the following error messages : Batch Error VLA317 during Goods Receipt using Inbound Delivery  Error VLA317 'Inbound delivery batch cannot be changed to &1 here' is reported  Error VLA318 'Inbound delivery valuation type cannot be changed to &1 here' is reported  Error VLA319 Return delivery qty greater than previously GR-posted qty: &1/&2 when reversing a delivery GR is not happening with reference to Inbound Delivery Solution Approach Options for Resolution:  Approach 1 : Update the Inbound Delivery with the Batch Number (LIPS-CHARG)/Valuation Type (LIPS-BWTAR) prior to posting the Goods Receipt via MIGO transaction.  Approach 2 : Implement Note 2991640 and then the error VLA317/VLA318 can be customized as a warning. Please be aware that this may cause inconsistencies so review all the information provided in this note. Run transaction SPRO (or OVM1) and follow the path: Logistics Execution -> Shipping -...

 At times, we can see that post system upgrade some fields in the business partner will go missing, to fix this we need to re-generate the screens. Ensure to keep this is included in the post migration activity. Below is the approach need to be followed  Run T-code BUSP. Enter application object as BUPA. Select "All screens" in session "generate all screens or just selected screens". Then press "execute" button.

At times, there will be a situation where batch number need to be generated based on custom naming convention rather than through regular number series for example, having financial year as a prefix to the batch number like that. This is most common requirement in Pharma & FMCG industries. The solution for this cannot be achieved through standard functionality. So in order to accomplish this requirement, we need to write a custom logic in the exit ' EXIT_SAPLV01Z_002 ' to accomplish this requirement.