SAP Logistics

Below is the determination of Departure from Yard ( OUTYARD ) in the outbound delivery order : If there are several EGOODSISSUE dates (both on header and item level) on the delivery items, it takes the latest date from all the EGOODSISSUE dates. If there is no EGOODSISSUE date on the delivery items, it takes the value of the TDELIVERY date field. This date will be given highest priority during the wave creation for automatic process. If this value is blank, then system leverages planned goods issue date for wave creation

  Issue   When using DRFOUT and select replication mode "Changes", none of the changed BPs are sent to target system Solution Approach When Changes are selected in DRFOUT transaction, this requires Change pointers to be present in table MDGD_CP. For Change pointers to be present in this table, Business System that is associated to Replication Model selected & Outbound Implementation 986_3 should have Pooled Output. If DRFIMG is not Pooled output for the target system. Hence there are no change pointers saved. Change output mode to "P Pooled Output" in customizing below: T-code DRFIMG -> Define Custom Settings for Data Replication -> Define Technical Settings -> Define Technical Settings for Business Systems -> Define Bus. Systems,  BO

 Issue You are using SOA Web service for replicating BP master data to the decentralized EWM system and you encounter the following error within the receiver system 'No update is defined for BP role 000000' Solution Approach In source system, goto view V_TB003 by t-code SM30. Please make sure the role category field of role 000000 is blank.

  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.

 At times, we might require to update custom fields post confirmation of the warehouse task. In that scenario, BADI 'SCWM/IF_EX_CORE_CO_POST~POST' can be leveraged. Important tables to be considered : /SCWM/DB_ITEMWT - Warehouse Tasks for Delivery Item /SCWM/ORDIM_C - Warehouse Tasks Confirmed

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 End connection to SAPWebCo

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   System carries out an ATP check despite the ATP check is deactivated in the schedule line category of the sales order in transaction VOV6. Root Cause The ATP check for sales orders with immediate deliveries is controlled by the following settings: ATP check setting in the requirement class (transaction OVZG) ATP check setting in the schedule line category (transaction VOV6) ATP check setting in the item category of the delivery (transaction 0VLP) It is not sufficient to deactivate the ATP check only in the schedule line category when ATP check is activated at the other two mentioned customizing settings. In immediate deliveries the ATP check is carried out with checking rule B (Checking rule for deliveries). The setting in the item category of the delivery is also important in this case. Solution Approach If you would like to switch off ATP in immediate deliveries you have to either: Switch off ATP check in the requirement class (transaction OVZG)  OR Switch off ATP check BOT

 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.

 Issue : Business Partners are not getting replicated via Web Service (SOAP) after a change in BP transaction. Solution Approach : Call transaction CRMC_BUT_CALL_FU Click on 'Position' In Event, enter: BPOUT In Object, enter: BUPX In Item, enter: 5000001 Click on green tick button or press enter Set the call flag right next to function module MDG_BS_BP_OUTBOUND_DRF

 Issue : A queue triggered from EWM that does not contain any handling units or packing instructions gets stuck with error  "Delivery item is not or only partially packed"  (error no. VL615) in the ECC system. Solution Approach : Check the table  TVLP  for the corresponding item category of the inbound delivery item. Ensure that the value of field  packing control  (field name  PCKPF ) is space ("can be packed") instead of 'A' ("must be packed").  As a workaround to post the stuck queue from SMQ2, the field  LIPS-PCKPF  needs to be updated to space. Afterwards, re-attempt to process the queue from SMQ2.