SAP Logistics

  EWM 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.

Partial Picking configuration is set at two different areas within customising: SPRO -> Logistics Execution -> Warehouse Management -> Master Data -> Define Control Parameters for Warehouse Number SPRO -> Logistics Execution -> Warehouse Management -> Interfaces -> Shipping-> Define Shipping Control -> Shipping Control per Warehouse Number The above configuration is utilised by the system in two different ways: Define Control Parameters for Warehouse Number: This configuration setting is only considered in multiple processing when the user creates picking instructions for a delivery group with WM reference via VL06P or a group of TR’s created via LT41. If partial picking is not allowed, then the picking instructions created in background mode via LT42 will fail for the entire group if one or more line items is not completely fulfilled via a picking instruction, which will then require the user to step through each delivery in foreground mode to create the

 in SAP EWM, instead of using multiple tables to fetch the HU information. We can utilize standard FM '/SCWM/HU_READ' can be used to fetch the entire HU information. We are required to pass application 'WME' and HU GUID values to fetch the data

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     = DATA(lt_stock_mon)         ev_error         = DATA(lv_error) ).

3259682 - Error L3344 during creation of transfer order from transfer requirement Cause The function module checks to see if the action is allowable in background processing. Check in LT04 foreground for the Transfer Requirement which user input is required. For example, most commonly if there is a QM pop-up box, this can be the reason why background processing is not allowed. In that case it is not allowable by your QM-WM configuration Resolution Please check your QM-WM config (tcode SE16-> V_T325) if you have an entry there for warehouse.  The entry should be set to allow background processing in 'Foreground/Background control for inspection sample dialog' (T325-DUNKL).  In order for that configuration to be read during background processing of the TR, it can be paired with the 'storage type search' configuration.  Maintain that by going to transaction SE16 -> V_T334T. Here, you could edit the relevant entry and set the value for 'QM Control' (T334T-QMST

 2799378 - ATP result does not match the quantity available in MMBE / MD04 1725088 - Discrepancy between transactions Co09 & Co06

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 BAdI

 2332231 - EWM split deliveries with zero quantity not updated in the ERP original delivery 2565082 - ASN/BOL reference already exists in document xy 2844958 - Handling Unit or item quantity change is not sent from EWM to ECC immediately 2258386 - How to analyze: IBD shows open status in ECC but completed in EWM 2294597 - EWM Delivery Document Flow / Status Management and Quantity Offsetting Consulting Note 2594894 - EWM PDO document has GI completed but warehouse activity status is still open 3227904 - Limitations regarding returns inspection document distribution to ERP system 3371468 - EWM inspection document status remains QI02 QI10 3298981 - How to post Partial Usage Decision in Lot Origin 17 Inspection? 3300175 - How to see if decision is posted for lot origin 17 inspection? 3241873 - Inbound queue processing fails after UD is completed 3121479 - EWM-QM integration: issues with lot quantity/stock fields (QALS-LMENGE*) 3058435 - EWM Check Monitor 2754520 - Capacity check based on

 For any custom requirements in the packing specifications related to EWM BADI '/SCWM/EX_PS_CORE_VALIDATE' need to be leveraged.

  FM '/SCWM/TMAPSTLOC_READ_MULTI' is used to read multiple entries from /SCWM/TMAPSTLOC fetch Plant and EWM warehouse assignment details

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

BADI 'EXEC_METHODCALL_PPF ~ Execute'  can be leveraged for custom requirements during GI in EWM

 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 

 /SCDL/DB_DLVH_O - Outbound Delivery Header  /SCDL/DB_DLVI_O - Outbound Delivery Item /SCDL/DB_PROCH_O - Outbound Delivery Order Header /SCDL/DB_PROCI_O - Outbound Delivery Order Item /SCDL/DB_REFDOC - Reference /SCDL/DB_BPLOC - Partner/Location /SCDL/DB_PROCH_P - Production Material  Request  Header /SCDL/DB_PROCH_I -  Inbound Delivery: Header /SCDL/DB_PROCI_I -  Inbound Delivery: Item /SCWM/ORDIM_O - Warehouse Tasks Open /SCWM/ORDIM_C - Warehouse Tasks Confirmed /SCWM/DB_ITEMWT - Warehouse Tasks for Delivery Item PPFTTRIGG - PPF: Actions /SCWM/HUHDR - Handling unit header /SCWM/GMHUITM  - Handling Unit Item /SCWM/TU_DLV - Assignment of Deliveries and HUs to Transportation Units T307 - Storage Unit Types Below are the commonly used FM's /SCWM/PACK_UNPACK /SCWM/HUHDR_CREATE - Create HU Header /SCWM/DIFF_HUITM_CHANGE - LOCAL: Change HUs on Difference Analyzer /SCWM/PPF_POST_GM - Post PPF Goods Movement in BACKGROUND TASK

Most of the custom requirements at PO level can be handled through the  BADI ' ME_PROCESS_PO_CUST ' which contains various methods that gets called at different phases of the purchase orders