[SAP EWM] Error /SCWM/UI_PACKING083 is raised in /SCWM/PACK

This error has occurred due to standard behavior due to missing customizing/customizing restriction.

Error /SCWM/UI_PACKING083 is raised because in /SPRO path below the Work Center you try to open is attributed to Storage Type &1, however Inbound Section (field I_SECTION) and Outbound Section (field O_SECTION) are empty.

SCM Extended Warehouse Management

Extended Warehouse Management

Master Data

Work Center

Define Work Center

If you try to fill them, they cannot hold any information due to error:

"You can only use storage types with role B, C, E, I, H, or K.

Message No. /SCWM/UI_PACKING059"

This is raised because Storage Type &1 has a Storage Type Role different to any of those:

B Pick Point

C Identification and Pick Point

E Work Center

H Automatic Storage Retrieval (Material Flow Control)

I Work Center in Staging Areas Group

K Production Supply

Resolution

Without fields I_SECTION and O_SECTION maintained in customizing, the additional filtering from /SCWM/PACK must be used.

Otherwise, system would have to display all bins of a Storage Type in the /SCWM/PACK tree, which could cause performance issues depending on the size of the Storage Type.

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