[SAP EWM] Posting from EWM due to closed posting period

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 created in table /SPE/COMM_DATA. This is then deleted with the actual adjustment posting. If you have have entered an invalid date for the user, the system, for example, issues error message FGV 004. The ParameterID must be entered in the form "YYYYMMTT" or for the current date "X" (for example, for January 2, 2013: 20130102).

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.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

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

SAP Logistics

Search This Blog