[SAP EWM] /SCWM/L1012: Storage bin cannot be deleted because it is not empty

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 SAP note 2333338 not applicable to your system release. Kindly follow the below steps.

Use the correction report ZRECALCULATE_CAPA given in the SAP Note 1532672 to correct the storage bin inconsistencies.
Then Storage bin can be deleted successfully through /SCWM/LS02 transaction.
Finally, you may need to decide, in IMG: EWM-> Master Data-> Define Storage Type, whether the indicator "No Capacity Update" should be set or not in your scenario

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