[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

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1> VBAK-<Custom Field 2> VBAK-<Custom Field 3> ENDCHAIN. Thank you.

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

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...

SAP Logistics

Search This Blog