[SAP EWM] Sample size WT determination technical analysis

At times, there will be a situation where sample warehouse task is not created.

The first step, we will check the configuration of the QM note of EWM

Define and Activate warehouse IOT settings. If the sample size config is maintained there. Then check if the inbound delivery document flow is determined with doc category 'Q01', this will give you the sample size.

System still unable to determine warehouse tasks then in that situation, from technical standpoint during debugging, keep a breakpoint at the below class and Methods to troubleshoot the issue. This is the place where inspection rules will be called.

CLASS - /SCWM/CL_QGR_CONTROL

METHOD - /SCWM/CL_QGR_CONTROL~SAMPLE_SPLIT_CHECK

CLASS - /SCWM/CL_GOODS_MOVEMENT

METHOD - /SCWM/CL_GOODS_MOVEMENT~CHECK_QGR_CONTROL

METHOD - PREPARE_DLV_DATA~CHECK_QGR_CONTROL

BADI : GGR_CONTROL ~ SET_GGR_CNTRL_BY_IRULE can be leveraged in case of if business have a requirement that deviates from the standard functionality

Function module - /SCWM/GM_CREATE creates two tasks one for the sample Quantity and other for the remaining quantity.

Comments

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...

SAP Logistics

Search This Blog