Skip to main content

[SAP EWM] Putaway Block is set to Storage Bin after picking

Requirement :

Upon Warehouse Task (WT) confirmation from a Source Storage Type with Bulk behavior, Putaway Block (PB) (field SKZUE) is set for the storage bin where the stock was picked from.

Root cause :

Customizing. On transaction /SPRO, following the path below you have set field 'Putaway Blocked' (field SENAU).

SCM Extended Warehouse Management
    Extended Warehouse Management
        Goods Receipt Process
            Strategies
                Putaway Rules
                    Storage Behavior: Bulk Storage
                        Storage Type Control for Bulk Storage

F1 documentation:

"Indicator: Blocked for Putaway After Stock Removal
Means that a block unit (row in bulk storage) is blocked for further putaway after the first stock removal has taken place.

Use
In this way, you can prevent a handling unit from being kept in the warehouse for an excessive number of days due to continuous stock placements. This block(age) is automatically deleted after the last handling unit has been removed from stock (picked from the row). You can also delete the block manually using a report after a specified time has elapsed."

The customizing table of this object is /SCWM/T331B and there the field 'SENAU' is checked.

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

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] Adding custom fields for /SCWM/PACK Screen

If business want to add a custom field to the /SCWM/PACK screen and the requirement is that once business enter value here system will check against the weight in the material master  Step 1 : Structure /SCWM/S_PACK_VIEW_HUHDR need to be appended with the new custom field Step 2 : Then use screen enhancement /SCWM/UI_PACKING /SCWM/EX_WRKC_CHECK_BFR_HU_CMP to include logic specific to validation and updation of the table
Post a Comment
Read more