SAP Logistics

 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.

 At times, there will be a situation where sample warehouse task is not created.  The first step, we will check the configuration of the QM note of EWM  Define and Activate warehouse IOT settings. If the sample size config is maintained there. Then check if the inbound delivery document flow is determined with doc category 'Q01', this will give you the sample size. System still unable to determine warehouse tasks then in that situation, from technical standpoint during debugging, keep a breakpoint at the below class and Methods to troubleshoot the issue. This is the place where inspection rules will be called.  CLASS -  /SCWM/CL_QGR_CONTROL METHOD - /SCWM/CL_QGR_CONTROL~SAMPLE_SPLIT_CHECK CLASS - /SCWM/CL_GOODS_MOVEMENT METHOD - /SCWM/CL_GOODS_MOVEMENT~CHECK_QGR_CONTROL METHOD - PREPARE_DLV_DATA~CHECK_QGR_CONTROL BADI : GGR_CONTROL ~ SET_GGR_CNTRL_BY_IRULE can be leveraged in case of if business have a requirement that deviates from the standard functionality...

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button