SAP Logistics

 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.

 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 > 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)

 At technical level, fixed bin will be determined based on the below logic : system will first check for the fixed bin field at the storage type level , if this is checked (  /scwm/t331 - fixbin = 'X' then system will call FM ' /SCWM/BINMAT_READ_MULTI' which will read the data maintained through the bins maintained in the /SCMW/BINMAT transaction at the front end level to fetch the bin data.

At times, we will struggle with stock being not picked from the source bin, in this situation to investigate from technical level for issue related to the source bin determination, try to keep breakpoint on the FM ' /SCWM/REM_BIN_DET_INT' which will give you some hint related to the root cause of the issue

In general, if business do not want source HU to be populated during the picking process then settings 'S ource L evel of Available Quantity of the Source Storage Type is on Bin Level' and  source storage type needs to be setup as a final storage type (Setting: Storage Control complete).

As per standard SAP functionality capacity check for /SCWM/ISU is deactivated. This transaction should be used for initial data transfer from old system to EWM (example). That means the stocks must be physical stocks already stored within the warehouse at storage bins. The same would happen if physical inventory will be performed and the user count more then allowed capacity. The system will post the differences without capacity check.  At /SCWM/ISU, and also in physical inventory counting (PI), not all checks against storage type, bin type customizing are performed, compared to 'normal' putaway. The reason for this: Both in initial stock upload, and PI counting, it must be possible to enter stock on a bin the way it physically exists there. Even if it is against the put away rules. 

  E WM stock is composed by the physical stocks plus the Difference Analyzer stocks. /SCWM/ERP_STOCKCHECK shows the total physical stock quantity of a given warehouse. The Physical Inventory difference was not yet posted on /SCWM/DIFF_ANALYZER, so the stocks still exist in the warehouse as a "difference" yet to be posted. While /SCWM/MON displays only available and physical stocks, not differences. The correct procedure is to run the /SCWM/DIFF_ANALYZER to clear this stock pending, so it will not be shown on /SCWM/ERP_STOCKCHECK as well. If  /SCWM/ERP_STOCKCHECK  has a different EWM quantity than the total physical stock, the difference can be found on the  Difference Analyzer , since the EWM stock is equal to the physical stock plus the Difference Analyzer stock.

  Issue After zero out EWM delivery, non-EWM relevant items in the ERP delivery are not zeroed out.\ Solution Approach Do not mix EWM relevant items and non-EWM relevant items into one single delivery. But you can add your own logic in method EXIT_SAPLV50I_004 of SMOD_V50B0001 to change the quantity of non-EWM relevant items to zero when the delivery is zeroed out in EWM.

 Issue  Delivery created from a sales order is distributed to the EWM system.  "Partial delivery at item level" is set to 'C' - Only complete delivery allowed Quantity is changed or Goods issue is complete in the EWM system.  Queue fails in the ERP system with error VL062 - "Full delivery is required" Solution Approach Maintain the following entries within your system using transaction OVM1 - if they already exist, adjust them accordingly: Application: 'L' - Shipping processing Call type 'D' - Confirm from external system Call type 'B' - Background processing, multiprocessing with Work phase 'B' Application Area = VL, Message no = 062, Type = I * Call type 'B' with Work phase 'A' is for background delivery creation.

 At times, we might need to overrule the existing capacity check of the bins and create a custom rule to determine capacity of the bin, in this situation we have leverage the below BADI to accomplish the requirement /SCWM/IF_EX_CORE_PTS_CAPACHECK~CUSTOM_CAPA_CHECK  Note : This BADI will be called for all types of transfers to the Bin due to that ensure to be careful while implementing this.

We use the transaction  /SCWM/VALUATION_SET    'Determine and Set Prices from ERP' to replicate the valuation data for products into the EWM system. For the non-valuated ERP products, not any data is created in the data base table /SCWM/T_VALUATE - Valuation Data for Physical Inventory. It is not possible in EWM to distinguish between just missing valuation data for a product( not replicated ), and non-valuated products.

Transaction /SCWM/CONV_BSKEY  can be used to change the business system key in all EWM tables. In addition, customer-specific tables that contain fields with domain SLD_BSKEY can be updated, if they are specified in the parameters of the transaction. The transaction does not update the tables /SCMB/TOWNBS and /SCMB/TBUSSYS. These tables must be manually maintained before executing the transaction. The transaction provides a test run, which checks the number of records per table to be updated. Both the test run results as well as the productive execution will write an application log.

Issue : In /SCWM/ISU, there is no option to fill stock items with AMOUNT_LC, External Amount in Local Currency. Analysis : This functionality is not available in the EWM standard until S/4HANA 2021 release. Before that, the EWM standard design did not foresee any price management. Every stock posting from EWM had to be done based on the existing price data on ERP side. Solution Approach : Before upgrading to a higher release, implement BAdI /SCWM/EX_ERP_GOODSMVT_EXT to update the price-related fields AMOUNT_LC and AMOUNT_SV in table CT_GOODSMVT_ITEM for every item to be posted. Note : This BADI will be called for any type of material document posting so this BADI can be used in general for multiple purposes.

  Stock Data Transfer with /SCWM/ISU: 974852  Stock data transfer using transaction /SCWM/ISU Uploading packaging specifications using /SCWM/IPU: 1726759 uploading packaging specifications using /SCWM/IPU Delivery: 1064376 Customer-specific determinations/validations of the delivery 1071644 BOPF: Manually implementing notes/importing Support Packages 1227714 FAQ: BC Sets and delivery Customizing in EWM 1276862 Generation of outbound delivery with quantity of zero Batches: 990638  Requirement for processes with batches in SCM-EWM 1272566 BAPI_OBJCL_CHANGE: Object for class type is not defined II (valid up to EWM 700) 1305698 Overview of communication/integration of batches ERP bet. EWM 1344366 FAQ: Batch Creation On ERP Side by Using Tx.: VL31N Handling Units (HUs): 1081145 Deleting empty unused handling units Inventory: 1166998 Settings for printing physical inventory documents Quality Management: 1278425 Connecting ERP QM to EWM Radio Frequency (RF): 1091765 En...

To reset the tolerance check (or approve this under/over tolerance violation), you can follow the steps bellow: Open /SCWM/PRDI transaction (for inbound deliveries) or /SCWM/PRDO transaction (for outbound deliveries); Open your delivery in the respective warehouse number; Select the delivery item blocked with the tolerance check error; Press the button "BBD/Tolerance" and then you have 2 options: Choose "Reset Tolerance Violation" to reset the current block and let the system available re-check the over/under tolerance. Choose "Approve Tolerance Violation" to approve the over/under tolerance and make the delivery item processable.

 Issue Transportation Unit is blocked with a red flag and you are not able to use it due to error message  "Delivery assignment to TU &1/&2 is inconsistent" (/SCWM/SHP_RCV177 ) Solution Approach To unblock your TU and synchronize the information again, Go to /SCWM/TU transaction, Select your TU, Push the Check button. Save the TU.

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.