Skip to main content

[SAP EWM] Storage type roles


 Standard Storage Type

A physical area in the warehouse where products are stored. SAP has pre-configured a number of standard storage types.

Identification Point

An area within a warehouse where goods are labelled, identified, and/or checked during the putaway process.

Pick Point

A physical area within the warehouse where goods are checked, labeled, inspected, and/or packed during the goods removal process.

Identification and Pick Point
An area within a warehouse where both identification (Identification Point) and picking (Pick Point) takes place.

Staging Area Group
A material staging area, or many material staging areas, in the warehouse.

Work Center
A physical area within the warehouse where processes such as deconsolidation, inspection, packing or value added service processing take place.

Doors
A door or many doors is a certain physical location within a warehouse, for example, the doors to the west of the warehouse.

Yard
A yard adjacent to the warehouse.

Automatic Storage Retrieval (Material Flow Control)

An area using automated storage and/or retrieval, for example, as a conveyor system.

Automatic Warehouse (Controlled by MFS)

An automated high-rack storage area with a stacker crane.

Work Center in Staging Areas Group

A work center within a material staging area.

Production Supply

An area where products for the production are staged, near the production line.

Comments

Popular posts from this blog

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.

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

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