Skip to main content

EWM monitor: Parameters for method for del. qty adjustment automation

SET/GET parameters (user parameters) that you can maintain in transaction SU3 are available for both methods. You can use these parameters to prepopulate input values in the dialog boxes of the monitor methods. The respective dialog boxes then no longer appear.

There are the following SET/GET parameters:

/SCWM/MON_AQ_ACT -  For the method "Quantity Adjustment"

/SCWM/MON_AQOD_ACT - For the method "Create Quantity Adjustment and Outbound Delivery"

Both parameters can be filled according to the following logic. The parameter is set up as follows:

<first parameter part><second parameter part>

First parameter part (one-digit):

This specifies the selection in the first dialog box. The first dialog box provides the following three different options. The first character in the parameter specifies which selection is made. The dialog box then no longer appears. It can contain values from 1 to 3. This means the following:

"1": Adjust Quantity

"2" Adjust Quantity (create new delivery in EWM for difference)

"3" Adjust Quantity (use default process code from profile)

Second parameter part (four-digit):

This specifies the process code that you want to choose. The system usually displays a second dialog box after the first dialog box. Here you can choose between different valid process codes. If you want to select a specific process code here, this can be done using the second parameter part. Note that you can enter the second parameter part in the parameter only if the first parameter part has also been entered. The entered process code must match the first parameter part. Otherwise, the system displays an error message and the dialog box appears on the user interface (UI).

The second parameter part is optional.

Example 1:

You want to automate the monitor method "Quantity Adjustment" in such a way that the option "Adjust Quantity" is automatically chosen in the first dialog box and the process code "O001" is then chosen in the second dialog box.

For this, call transaction SU3, go to the "Parameters" tab page, enter the parameter ID "/SCWM/MON_AQ_ACT", and enter the parameter value "1O001".

If you now call the monitor method "Quantity Adjustment", the last confirmation prompt automatically appears and you no longer have to enter values.

Note that the system issues an error message if the chosen delivery items in your process profile do not have O001.

Example 2:

You want to automate the monitor method "Create Quantity Adjustment and Outbound Delivery" in such a way that the option "Adjust Quantity" is automatically chosen in the first dialog box. However, the process code selection should be made manually as before.

For this, call transaction SU3, go to the "Parameters" tab page, enter the parameter ID "/SCWM/MON_AQOD_ACT", and enter the parameter value "1".

If you now call the monitor method "Create Quantity Adjustment and Outbound Delivery", the dialog box automatically appears in which you can select the available process codes.

Comments

Post a Comment

Popular posts from this blog

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...
1 comment
Read more

[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.
Post a Comment
Read more

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...
1 comment
Read more