SAP Logistics

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. 

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.