Skip to main content

[SAP EWM] Analyzing and correcting inconsistencies in the available stocks or the warehouse order status

Below is the approach to be followed to fix the issue :

  1. Call transaction /SCWM/CHM_LOG.
  2. Choose "Ad-Hoc".
  3. 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).
  4. 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.
  5. At the level of the available stocks, you can optionally restrict your selection (arrow) to a transportation unit (TU), resource, or product.
  6. 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 with regard to the available stocks can be very time-consuming. In addition, you should not execute more comprehensive selections at a time where a large number of other activities is executed.

Comments

Post a Comment

Popular posts from this blog

[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

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

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