Master Data and

Basic Concepts
Supply Chain Execution
SCM 5.0

SAP AG 2005

SAP AG 1
 Warehouse Structure

SAP AG 2005

The warehouse number is the highest organization level in the warehouse structure. In EWM,
you can define an entire physical warehouse complex using a single warehouse number.
You can define the individual warehouse facilities or warehouses that make up the warehouse
complex, using their technical, spatial, and organizational characteristics as storage types.
Each storage type is divided into storage sections. All storage bins with specific common
attributes belong to one storage section, for example, storage bins for fast-moving items that are
close to the goods issue zone.
Each storage type and storage section consists of a selection of storage compartments, which in
EWM are called storage bins. The coordinates of the storage bin tell you the exact position in the
warehouse where you can store products.
The quant is the existence of a product in a bin.
The activity area is a logical grouping of storage bins. It can refer to a storage bin, or can
concatenate bins from several storage types. You can either assign storage bins manually to the
activity areas, or if there is a 1:1 relationship between storage type and activity area, you can
have the system generate the assignment.

SAP AG 2
 Warehouse Structure

Warehouse number

In EWM, you can manage an entire physical warehouse complex

using a single warehouse number.

Storage type

You can define the individual warehouse facilities or warehouses

that make up the warehouse complex, using their technical,
spatial, and organizational characteristics as storage types.

Storage section

Each storage type is divided into storage sections. All storage

bins with specific common attributes usually belong to one
storage section, for example, storage bins for fast-moving items
that are close to the goods issue zone.

SAP AG 2005

SAP AG 3
 Warehouse Structure

Storage bin

Each storage type and storage section consists of a selection of

storage compartments, that in EWM are called storage bins. The
coordinates of the storage bin tell you the exact position in the
warehouse, where goods can be stored.

Quant

The quant is used for inventory management of a product in a

storage bin.

SAP AG 2005

SAP AG 4
 Warehouse Structure Staging Areas

Staging area
assigned hierarchically to the warehouse number
used to organize the flow of goods in the warehouse

Staging areas are used for the interim storage of goods in the
warehouse. They are located in close proximity to the doors
assigned to them. You can define staging areas for different
purposes and even simultaneously for multiple purposes:

Goods receipt

Interim storage of unloaded goods until they are put away

Goods issue

Interim storage of picked goods until they are loaded

SAP AG 2005

SAP AG 5
 Warehouse Structure Staging Areas

SAP AG 2005

You can group together staging areas to form staging area groups which correspond to the
storage type.
Staging areas can be divided into multiple bins. Multiple bins are required if you want to define a
loading sequence.

SAP AG 6
 Warehouse Structure

Door:

location in the warehouse where the goods arrive at or leave the

warehouse. The door is assigned to the warehouse number.

Vehicles and their transportation units (TUs) drive up to the doors

of a warehouse to load or unload goods. The doors are in close
proximity to their relevant staging areas.

SAP AG 2005

To control putaway and stock removal processes in your warehouse, you can define doors and
staging areas within a warehouse number.
You can assign various functions to a door:
Inbound
Outbound
Inbound and outbound
In delivery processing, the system can use determination rules to determine the following for
each delivery item:
Staging area groups
Staging areas
Staging bays
Doors
The determination rules are influenced by the possible assignments between doors and staging
areas as well as between doors and staging area/door determination groups that you have
defined in customizing. The system updates the delivery at item level with the values that it finds.

SAP AG 7
 Warehouse Structure Activity Area

AA3 (AA3 = AA1 + AA2)

AA1 AA2

SType ST01 SType ST02

Activity Areas (AA) are logical groups of bins that can be used in different
activities like Picking, Put-away, Physical Inventory.

Activity Areas are used to determine how Warehouse Orders (WO) are created
through Warehouse Order Creation Rules (WOCR).

Activity Areas enables sorting sequences for Bins.

Activity Area is an influencing parameter in determining queues

SAP AG 2005

An Activity Area is a logical area of the warehouse where storage bins are grouped together with
regards to specific warehouse activities. Examples are picking, putaway and physical inventory.

SAP AG 8
 EWM Documents

Inbound delivery Notification

Inbound delivery

Outbound delivery request

Outbound delivery order

Outbound delivery

Warehouse request

Warehouse order

Warehouse Task

Shipment

Handling Unit

SAP AG 2005

SAP AG 9
 Warehouse Documents

Inbound Delivery Notification

The shipping notification from the supplier is saved in the

inbound delivery notification in EWM.

The inbound delivery notification is created automatically by

incoming messages and is converted manually/automatically into
an inbound delivery.

Inbound Delivery

The inbound delivery is a document containing all the data

required for triggering and monitoring the complete inbound
delivery process. This process starts on receipt of the goods in
the yard and ends on transferal of the goods at the final putaway,
production or outbound delivery

SAP AG 2005

SAP AG 10
 Warehouse Documents

Outbound Delivery Request

The outbound delivery request contains all the relevant logistics

data in the outbound delivery process right from the origin of the
outbound delivery process (sales order, for example).

The outbound delivery request is created automatically by

incoming messages and is converted manually/automatically into
an outbound delivery order.

Outbound delivery order (Warehouse Request)

The outbound delivery order contains all the data required for
triggering and monitoring the complete outbound delivery
process. This process starts with the first planning activities for
the outbound delivery and continues until the finished goods have
been loaded and sent.

SAP AG 2005

SAP AG 11
 Warehouse Documents

Outbound Delivery

The outbound delivery represents the goods to be delivered

together to a goods recipient. The outbound delivery is used as
the basis for printing the delivery note or for sending a shipping
notification.

You use this document in delivery processing when:

Posting a goods movement
Canceling a goods movement
Setting the status Leave Yard

You can save, process, delete and archive an outbound delivery

SAP AG 2005

SAP AG 12
 Warehouse Documents

Warehouse Request

The warehouse request is a document that enables the processing

of warehouse activities for a specific product. The warehouse
activities for a product include the following:

picking
put-away
posting change
stock transfer (within warehouse)
scrapping

SAP AG 2005

SAP AG 13
 Warehouse Documents

Warehouse Order

Groups together warehouse tasks into warehouse orders

according to your customizing settings to create optimum work
packages.

For warehouse order creation, you define rules with their relevant
criteria.

You assign warehouse orders to warehouse employees in

resource management

SAP AG 2005

SAP AG 14
 Warehouse Documents

Warehouse Task

Document used for executing goods movements that are logical or

physical, including pick, put-away, posting change, packing etc.

A warehouse task contains all the necessary information on a planned

goods movement:

What should be moved?

Which quantity should be moved?
From where (source storage bin) should the bin be moved, and to
where (destination storage bin)?

In EWM a distinction is made between Product Warehouse Tasks and HU

Warehouse Tasks.
PROD-Task

HU-Task HU-Task

SAP AG 2005

SAP AG 15
 Extended WM Process Terminology and Definitions

Shipment

Document containing all the goods that are consolidated by a

ship-from party and are then transported together from an issuing
location to a destination location. The shipment forms the basis
for planning, executing, and monitoring the transportation of
goods.

The shipment can be:

Inbound: Goods are transported from the supplier to the plant

Outbound: Goods are transported from the plant to the customer

SAP AG 2005

SAP AG 16
 Warehouse Structure
Handling Unit:
A physical unit consisting of packaging materials (load carriers/
packing material) and the goods contained on/in it. A handling unit is
always a combination of products and packaging materials. All the
information contained in the product items, for example, about
batches, is retained in the handling units and is always available.
Handling units can be nested, and you can create a new handling unit
from several other handling units as often as you want.
A handling unit has a unique, scannable identification number that
can be formed according to industry standards such as EAN 128 or
SSCC.

SAP AG 2005

The Handling Unit contains the following attributes: Identification Number, Dimension, Weight,
Volume, Status, Products and quantities, packaging materials, packaging specification.
A Handling Unit consists of a handling unit header and handling unit items. A handling unit has a
unique number used for identification purposes.
The Handling Unit is connected to general status management which allows you to document
the various physical status (such as planned or realized) and other attributes (such as weighed,
loaded, blocked, or posted GI). It is also possible to store a user schema for a packaging
material type and thus use your own statuses.
The items of a handling unit can consist of material items, auxiliary packaging materials, or other
handling units, which are displayed in an overview.

SAP AG 17
 EWM Interface to ERP

Classic decentral-WM interface based on delivery

Delivery Interface is extended for the possibility to have

delivery splits.

Direct postings in Materials Management for stock transfer

postings triggered in EWM.

Master Data (product level information) is populated using the

CIF integration.

SAP AG 2005

SAP AG 18
 The CIF interface > Create an Integration Model

SAP AG 2005

SAP AG 19
 The CIF interface > Distribute Integration Model to EWM

SAP AG 2005

SAP AG 20
 Copyright 2005 SAP AG. All Rights Reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

SAP AG 2005

SAP AG 21