SAP Logistics

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.