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

 Error Message Creating a return to vendor delivery on VL60 raises error: 'Unknown error has occurred in target system (Message No. /SCWM/DELIVERY_UI056)'. Root Cause RFC user is not configured as a dialog user. When creating a return delivery from EWM, the system attempts to call the RFC function /SPE/INB_CALL_TRX_VL60 using an RFC destination. This process involves executing the dialog transaction VL60, and the RFC destination relies on the RFC user for the call. Solution Approach Solution 1: Master data. Ensure that the RFC User master data is adapted to 'dialog'. Solution 2: BAdI implementation. Maintain a separate RFC destination for Return to Vendor scenario. Maintain a separate dialog user with restricted authorizations (e.g. only VL60). Assign the dialog user to the RFC destination. Change the RFC destination for calling the VL60 transaction from EWM, with BAdI '/SCWM/EX_DLV_ERP_CALL_CTRL->CALL_CTRL'. BAdI documentation extract: "Sample coding an...

The customizing flag for storage type "No GI" blocks only the posting goods issue for delivery documents, but in ad-hoc goods movement scrapping process (/SCWM/RGI_SCRAP), it is not evaluated.  On the selection screen of /SCWM/ADGI, if flag "Select Scrap Stock only" is set, the system will filter for stock with stock type S5 Scrapping from Putaway and/or S6 Scrapping from Warehouse.  In case it is needed additional checks on ADGI, customer-specific checks during unplanned goods issue can be implemented via BAdI /SCWM/EX_CORE_GM_STOCK.

If there is a requirement where system has to determine warehouse process type based on the storage location then in that situation we have to leverage exit /SCWM/EX_DLV_DET_PROCTYPE~CHANGE_PROCTYPE to accomplish the requirement. Logic should be written such that /SCWM/WHR_QUERY is used to fetch the delivery document details from EWM. REFDOC field in the IT_HEADER-REFDOC will contain the S4 delivery number.  This is passed into LIPS and fetch storage location and determine process type based on TVARVC or custom table

  This error has occurred due to standard behavior due to missing customizing/customizing restriction. Error /SCWM/UI_PACKING083 is raised because in /SPRO path below the Work Center you try to open is attributed to Storage Type &1, however Inbound Section (field I_SECTION) and Outbound Section (field O_SECTION) are empty. SCM Extended Warehouse Management Extended Warehouse Management Master Data Work Center Define Work Center If you try to fill them, they cannot hold any information due to error: "You can only use storage types with role B, C, E, I, H, or K. Message No. /SCWM/UI_PACKING059" This is raised because Storage Type &1 has a Storage Type Role different to any of those: B             Pick Point                                                C             Identification and P...

If business want to add a custom field to the /SCWM/PACK screen and the requirement is that once business enter value here system will check against the weight in the material master  Step 1 : Structure /SCWM/S_PACK_VIEW_HUHDR need to be appended with the new custom field Step 2 : Then use screen enhancement /SCWM/UI_PACKING /SCWM/EX_WRKC_CHECK_BFR_HU_CMP to include logic specific to validation and updation of the table

 Available stock - This stock is not allocated or reserved to any delivery and ready for use. Physical stock - System will display the stock that is available in the warehouse. means, this will display stock which is assigned to the delivery document or Production warehouse request. So always order management team should consider stock in the available stock node while placing the orders as this is the stock which is available to use. Note : Before physical inventory is initiated, try to close these open documents if possible. Else there is a chance of having an impact during goods issue in case of any stock changes

Issue : Although SAP does not recommend it, it may happen that you want to change the serial number profile of an existing material. If stock has ever existed for this material in the warehouse, the serial number profile is stored in table /SCWM/SERH, and it is no longer changeable despite any changes in the material master in ERP or in EWM . Solution Approach  As first step you have to remove all stock (including planned stock, which means rejection of all not yet goods receipted stock on existing inbound deliveries) for the material from the warehouse. Set the appropriate serial number profile for the material in ERP. Delete the entry from table /SCWM/SERH for the material. Then you can start using the material with the new serial number profile, when the new stock comes for the material the entry in /SCWM/SERH will be automatically recreated with the relevant data. Deletion of the entry from the table can be done through debug mode or through the implementing the code proposed b...

Rejection of the outbound delivery order can be done from /'SCWM/MON or /SCWM/PRDO. This post will show you the rejecting the delivery through /SCWM/PRDO Below is the process steps to reject the outbound delivery in SAP EWM : Launch transaction /SCWM/PRDO and enter the delivery number, execute Click on Process codes --> Adjust delivery Quantity     Select O001 and click on ok , Save Delivery will be rejected and EWM. If the delivery type is enabled with create OD automatically at cancel, then business need not click on 'Outbound delivery' button. If not, business has to click on this button to cancel the delivery in SAP S4. Thank you.

 At times, business will contact us to perform put away reversal due to various reasons like received wrong quantity or PO was wrongly entered. As per standard SAP, EWM will not allow you to perform GRN reversal after stock is received in the warehouse ( Putaway is done ) . For say, if the business has done goods received but not initiated the putaway process then system will allow business to perform GRN reversal if no HU movements are done. But however, if the warehouse tasks are confirmed then system will not allow business to reverse the goods receipt. But however in the SAP S4 HANA systems from 2023 came up with a functionality where system will allow to perform Putaway reversals even though putaway is completed provided HU's are not modified.

 /SAPAPO/PLANNER - Validate SNC planner /SAPAPO/LOC - Get location based on location ID or Vice versa /SAPAPO/MATLPL - Combination of Product, Location & Planner BAPI_PRDSRVAPS_SAVEMULTI2 - BAPI to update obsolete product in product master /SCMB/INBDLVDAT - This table is to check ASN's ( Pass ASN number and Supplier )

At times, there will be a requirement seeking mass assignments of products & BOD's. In order to accomplish this requirement, we have develop a BDC program on the transaction /SAPAPO/PRDO2BOD_M. Commonly used FM's & Tables related to BOD : /SAPAPO/CHECK_PROD_ON_BOD_LOC -  This is used to check whether material is present in all the locations of the BOD

At times, business wish to influence the destination bin determination based on their set of  custom parameters rather than following the standard puaway search strategy parameters. In this situation, we have to use EXIT - EXIT_SAPLL03A_001 to accomplish this requirement. Thank you

 SAP Note  1913028   recommends the below steps to be followed in case of this error : Option A Cancel all additional material documents with MVT 107,  except the first one . Use transaction MIGO with "A03 Cancellation" and "R02 Material Document". Remember the quantity posted. Post a subsequent delivery for the first material document number with MVT 107 for the quantity used in step 1. Use transaction MIGO with "A06 Subsequent Delivery" and "R02 Material Document". Release Goods Receipt for Inbound Delivery by movement ' 109 ' in transaction  VL32N . Now the error M7329 should be gone. Option B Please run the reports ZCORR_EKBE_ETENS from note  655427  and ZCORREKESGRRTV from note  536190  to fix/synchronize the fiels EKBE-ETENS and EKES-ETENS.

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

  Issue : If the delivery has two items, one of them is reference to the main item of the PO, another one is reference to the subitem whose EKPO-UPTYP is not blank. eg. EKPO-UPTYP = 8, that means the subitem is the 'Interchangeable Items (IBU: A&D)' of the main item. In general, the inbound delivery should only be posted for items which contain the actual material, but in the case of the error PO, inbound delivery was posted for both main item and subitem. This will cause the error when system reads confirmation data during GR posting. Solution Approach given by SAP : Only items refer the actual material in the PO should be created in the delivery. The queue cannot be processed. Reverse GR for the delivery in EWM and cancel the delivery then recreate the delivery. If the GR cannot be reversed due to DCO status is 9, use VL_COMPLETE to complete the ERP delivery then do physical inventory in EWM

Below is the solution approach to be followed in case of the error message Error "/SAPAPO/LOC040" during mass maintenance in /SCWM/MON : Entries for that Party Entitled to dispose (PED) should be present in tables /SAPAPO/LOC, /SAPAPO/LOCMAP,/SCMB/TOENTITYMP and /SCMB/TOENTITY.  If relevant entry for PED (Party Entitled to Dispose) is missing from any of above tables then system will through error "/SAPAPO/LOC040" during mass maintenance in /SCWM/MON To correct this, please execute below steps Go to SE38 tcode, Execute report /SCMB/CHECK_SCU  Give the affected SCU & Business Attribute. example "PLOC", "ZONE" Mark the check box "Make Corrections"& execute Report /SCMB/CHECK_SCU correct the inconsistencies and process ended with message "Program /SCMB/CHECK_SCU ended" (/SCMB/SCU206)