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

 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

 Requirement The customer wants to block the picking Warehouse Tasks creation when a part of the items have insufficient stock. Solution approach Extended Warehoues Management Customizing Setting: Extended Warehouse Management->Cross-Process Settings->Warehouse Task->Define Warehoues Process Type. Select the desired warehouse process type, check the details. On the bottom section "Settings for Warehouse Requests", set the flag "Pick Completely", save it. Then when you create and save the picking WTs for an outbound delivery order with insufficient stock quantities, a window will pop up: Error messages occurred, save anyway? When you select No, it will show the below messages: Requested amount could not be supplied, Partial picking not defined for warehouse request XXXXXXX, XX.

We can use any of the below to fetch the physical stock of a material in EWM. CALL METHOD lo_stock->get_physical_stock                 EXPORTING                   it_matnr_r   = lt_matnr[]                   it_lgpla_r   = lt_lgpla[]                 IMPORTING                   et_stock_mon = DATA(lt_stock_mon). lo_mon_stock->get_physical_stock(       EXPORTING         iv_skip_resource = abap_true         iv_skip_tu       = abap_true         it_huident_r     = lt_huident_r         it_lgpla_r       = lt_lgpla_r       IMPORTING         et_stock_mon     = DAT...

Root cause Creation of inspection lot with origin 17 is controlled by EWM and during inspection planning EWM coding is triggered. Therefore, setting to prevent inspection lot creation in movement type customizing at ERP side (transaction OMJJ) is not considered. Solution Approach   In order to restrict inspection lot creation in EWM environment, following possibilities can be considered: A) Use EWM inspection rule to restrict the lot creation for certain document type, item type or other properties. In decentralized EWM landscape, inspection rules are used by default. In embedded EWM landscape, the setting to use inspection rules can be reached at following customizing: transaction SPRO ---> SCM Extended Warehouse Management ---> Extended Warehouse Management ---> Cross-Process Settings ---> Quality Management ---> Basic and Integration ---> Define and Activate Warehouse-Dependent IOTs. Inspection rules can be maintained in transaction /SCWM/QRSETUP. B) Check if B...

Below is the logic to fetch partner details based on the EWM delivery order Pass delivery document number into table Delivery header ( /SCDL/DB_PROCH_O) and fetch document ID Pass the document ID ( DOCID) into table (SCDL/DB_BPLOC) and fetch the partner number ( Party No) Pass the party number into KUNNR of KNA1 and fetch the customer details ***************************************************************************** Pass PARTNERTO_ID of table Delivery header ( /SCDL/DB_PROCH_O)  and pass it into CVI_CUST_LINK and fetch customer number Pass Customer number into table BUT020 to fetch the ADDRNUMBER Pass ADDRNUMBER into table ADRC to fetch address details  *******************************************************************************

 Below is the logic to fetch the supply chain unit (SCU) address : Pass the warehouse ID ( Location ID) from the /SCDL/DB_PROCH_O ( Delivery header ) into table /SCWM/T300_MD (Assignments: Warehouse Number/Business Partner) and fetch SCU  Pass the SCU into table BUT020 and fetch the ADDRNUMBER Pass the  ADDRNUMBER into table ADRC to fetch the address 

 SAP note “1606493 – SAP EWM deployment options best practices”.  The major differences between embedded EWM in SAP S/4HANA 2020 and a de-central EWM are described in SAP note “2938306 - SAP S/4HANA 2020: Release information and restrictions for EWM in SAP S/4HANA”  2938308 - Release information and restrictions of Decentralized EWM on S/4HANA 2020” Stock Room Management reuses major parts of LE-WM and can be used beyond 2025. For details about this solution see the SAP Note 2270211 - S4TWL - Warehouse Management (WM). 2808143 - Overview: Batch management for decentralized EWM SAP S/4HANA” for details about the limitations and supported processes.