SAP Logistics

 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. 

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

 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.

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.

 At times, business look for the personnel who did changes for a specific field in the product master. In this situation, SAP has given standard transaction code  '/SCWM/PROD_CD_READ' to view the change documents. Apart from the above transaction, the same can be access through warehouse monitor as well

 There are various ways to perform goods movement for a ODO in EWM : FM -  SCWM/PPF_POST_GM can be accomplish the requirement and this requires import parameters as ' DOCID' and 'DOCCAT' but the challenge for this FM is capturing the return messages. This FM will not return any message. To avoid the above situation, we have alternate way to handle this. Class /SCWM/CL_GOODS_MOVEMENT can be leveraged to accomplish the requirement as well by passing the same parameters as above in method /SCWM/IF_GM_DLV~POST_DLV. In general, this class will be called from the above mentioned FM

  In customizing, you can enable that an update is send to LE when warehouse activities are completed in EWM. Customizing path: SPRO -> SCWM Extended Warehouse Management -> Cross-Process Settings -> Delivery – Warehouse Request -> Process Management and Control -> Define Process Profile for Document Header Select the process profile and flag the checkbox “Ready for Shipping (Send Update to LE)”. When the EWM delivery is set to “Ready for Shipping”, the warehouse execution status is also updated in the LE delivery.

 Issue : Product has been posted goods issue (GI) from HU AAAA on storage bin BBBB. The GI reversal is stuck by error: /SCWM/GM034: You can only post to bin BBBB using a handling unit Root Cause : During GI cancellation the system tries to post the stock back into the same HU (which has been deleted in the meantime). If this HU no longer exists, it will try to post as unpacked stock to the same bin. However, this can be prevented by error /SCWM/GM034 in case of HUs are obligatory in that storage type and the GI happened by a product warehouse task (WT). Consider also it is not possible to cancel the goods movement and post the stock to a different HU. Solution Approach : In case the GI posting was done by a HU WT, then system re-creates automatically the HU posted for GI. In case the GI posting was done by a product WT there are two options: Option A) Change the storage type settings regarding HU requirement to value ' ' (HU allowed but not a requireme...

Below is the approach to be followed to fix the issue : Call transaction /SCWM/CHM_LOG. Choose "Ad-Hoc". On the following screen, choose "Stock and Bin" and enter the selection criteria by choosing the yellow arrow on the right (entry of warehouse number, storage type, and storage bin as required). From the checks available below this node, select "Available Quantity" and then select the line. As a result, the system should display the bulb icon on the left. At the level of the available stocks, you can optionally restrict your selection (arrow) to a transportation unit (TU), resource, or product. Make the selection using F8. The system now checks for inconsistencies. If there are any inconsistencies, they can be corrected by positioning the cursor on a line and right-clicking it, provided that the relevant function supports this. However, the selection criteria should be entered as specifically as possible. A selection that checks an entire storage type w...

 Requirement : After PGI in EWM, the delivery date (LIKP-LFDAT) in ERP  which is in the past  is overwritten by the EWM system. This issue can happen even if you've defined "Do Not Confirm Date/Time" in the EWM side customizing: SPRO -> Extended Warehouse Management -> Interfaces -> ERP Integration -> Delivery Processing -> Map Date Types from ERP System to EWM. Cause Standard behaviors : Scenario 1: If the delivery date (LIKP-LFDAT) in ERP is in the past, the actual goods issue date from item will be taken over as the new delivery date and sent to ERP during PGI.  Scenario 2: In EWM, multiple ODOs are assigned to a TU and posted GI together. To avoid unexpected TU split, all deliveries belonging to this TU will get their delivery date updated to the earliest delivery date of all deliveries. Resolution Scenario 1 : implement BAdI /SCWM/EX_ERP_MAPOUT_OD_CONFDEC to remove WSHDRLFDAT from CT_BAPI_HEADER_DEADLINES parameter table i...

Below BADI need to be leveraged to influence the dates received from EWM to ERP : If you would like to influence the dates sent from EWM to ERP side, For PDO related GI, you can use the BADI /SCWM/EX_ERP_MAPOUT_OD_CONFDEC method  /SCWM/IF_EX_MAPOUT_OD_CONFDEC~MAPOUT. The dates are passed in the CT_BAPI_HEADER_DEADLINES parameter table, where you can modify the GI date. the relevant date is WSHDRWADTI which is the actual goods issue date   (constant /SCWM/IF_MAPPING_CONSTANTS=>SC_TT_OBDLV_GI_ACT). For PDI related GR, use BAdI /SCWM/EX_ERP_MAPOUT_ID_CONFDEC. The time type of IDRECDOCK(constant /SCWM/IF_MAPPING_CONSTANTS=>SC_TT_IBDLV_REC_ON_DOCK) will be taken over by ERP as the posting date.

Cause Empty Indicator may not be set for the storage bin due to some inconsistencies and if there is any open warehouse tasks. Resolution CASE 1 :   Initially check whether the following note SAP note  2333338  has been implemented in your system, if not kindly implement the SAP Note  2333338   and follow the instructions below.  There should not be any open warehouse tasks for the storage bin which needs to be deleted. Check Whse Tasks tab in /SCWM/LS02 for the specific storage bin.  Goto transaction  /SCWM/CHM_LOG  --->  Ad-Hoc ---->  Stock and Bin   (enter the Warehouse number and Storage Bin)  ---->  Capacity   Check  -----> Recalculate Capacity  and execute.  Storage bin inconsistencies related to capacity & HU will be displayed and you can correct the same.  After that, Storage bin can be deleted successfully through /SCWM/LS02 transaction. CASE 2 :  If the...

 Solution Approach : If you want to correct the faulty queue entries with message M7 053 without debugging, you must activate user parameter DLV_POSTING_DATE. You have the following options for this: Call transaction SU01 and add the user parameter DLV_POSTING_DATE to the master data of the EWM qRFC user. To activate this value, set it to "X" or set an eight-digit posting date (YYYYMMTT). This user is used when executing in SMQ2 with F8. The users in question can maintain the parameter themselves using transaction SU3 and the menu option "System" -> "User Profile" - > "Own Data". However, to be able to use this, the qRFC user must be a dialog user. Furthermore, the ParameterID is valid only for debugging the EWM queue (F8). The set user parameter leads to the actual posting with the date according to the ParameterID only after the second posting in transaction SMQ2. If the system issues error message M7 053 at least once, an entry is create...

  There are two options available to get the queues in SMQ2 with status NOEXEC. Option A) Setting up a specific user parameter: it has to be done for the particular user, who is processing the deliveries in EWM or in ERP, not for the RFC user, the user parameter has to be set up in the menu System - User Profile - Own Data - tab Parameters or alternatively in transaction SU3, to stop the inbound queue in ERP side set the user parameter in EWM user master: parameter /SCWM/IF_DEBUG_QRFC, its value is X, to stop the inbound queue in EWM side set the user parameter in ERP user master: parameter /SPE/IF_DEBUG_QRFC, its value is X. Option B) Deregister the queue: It can be done in SMQR transaction. Use button „deregistration” then enter queue name in the popup. Here you can specify more queues or an exact one. Some examples: DLW* DLV* DLWSB6VCLNT001* DLWSB6VCLNT0011000001903 (exact ERP delivery coming from EWM) *1000001903 ...

 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.

Requirement : Upon Warehouse Task (WT) confirmation from a Source Storage Type with Bulk behavior, Putaway Block (PB) (field SKZUE) is set for the storage bin where the stock was picked from. Root cause : Customizing. On transaction /SPRO, following the path below you have set field 'Putaway Blocked' (field SENAU). SCM Extended Warehouse Management     Extended Warehouse Management         Goods Receipt Process             Strategies                 Putaway Rules                     Storage Behavior: Bulk Storage                          Storage Type Control for Bulk Storage F1 documentation: "Indicator: Blocked for Putaway After Stock Removal Means that a block unit (row in bulk storage) is blocked for further putaway after the first stock removal has taken place. Use I...

  The logs to identify the user who deleted/saved the queues from SMQ2 can be found in transaction SM21. In selection screen of SM21 enter the following values: From Date / Time = Enter the date/time the queue was deleted. Message ID = Q26 and Q2X. Transaction code = SMQ2.

Below is the approach to be followed to generate new spool request while printing documents : Go to transaction /SCWM/60000431, select warehouse number that is used in document and click "Spool Parameters" in the left window: If you'd like to just print immediately, the parameter 'Print immediately' should be set. In this case the system will also create new spool. If you'd like just to create new spool, the parameter 'New Spool Request' should be set.

Requirement :  The user wants to make the product field mandatory when entering transaction /SCWM/ADGI. Solution Approach : It is possible to implement the custom check via BAdI /SCWM/EX_CORE_GM_STOCK. If the fields are set to mandatory with the keyword "OBLIGATORY," the system will also make them mandatory for other GI processes such as Sampling and Consumption Posting.

  The user wants to reverse an unplanned goods issue in EWM using the below steps : Go to Tcode /SCWM/ADGI. Select GI process  Below is the process flow to be followed to perform the activity : User can reverse an unplanned goods issue with the help of transaction code /SCWM/ADGI. To do this, the user needs to select the "Cancel GI Document" option in the GI process.

  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     = DAT...

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