Inbound Process with no Packing Information from Vendor

SAP Extended Warehouse Management (SAP EWM) Rapid-Deployment Solution V2

Inbound Process with no Packing Information from Vendor

Physical Activity

Step 1
A truck arrives at the
checkpoint and drives
to the door

System Activity

A truck arrives
The checkpoint clerk communicates the door
to the truck driver
The truck drives to the door

Step 2
Check the delivery note
and find or create an
inbound delivery (EWM)

Step 3
Unload the truck and
check the goods

The GR office clerk finds or creates an

inbound delivery note

A warehouse worker unloads the truck

A warehouse clerk checks the goods against

the delivery note

Step 4
Post the goods receipt and
create putaway WOs (EWM)
*Check also the process
Variant for this step

The GR office clerk checks the quantities and

posts the goods receipt

The system post GR , creates and prints WOs

Step 5
Truck Departure

Step 6
Put away the goods (EWM)

The truck leaves

A warehouse worker takes the WO printouts

and sticks one printout to the goods

A warehouse clerk confirms the WOs

The warehouse worker moves the goods to the

final bin or to the clarification zone
(exceptional case)

Step 7 exceptional case

Put away the goods from
the clarification zone (EWM)

A warehouse clerk creates the missing master

data and creates an ad hoc WO

The system prints the WO

A warehouse worker takes the WO printouts
and sticks one printout to the goods

The warehouse worker moves the goods from

the clarification zone to the final bin

The warehouse clerk confirms the WO

2011 SAP AG. All rights reserved.

Purpose

When the truck arrives, the checkpoint clerk directs the truck to a
door. The truck driver brings the delivery note to the goods receipt
office (GR office). If the vendor has sent an ASN to SAP ERP, the GR
office clerk finds the corresponding inbound delivery in SAP Extended
Warehouse Management (SAP EWM). If no inbound delivery yet exists
in the system, the GR office clerk creates an inbound delivery in SAP
EWM. A warehouse worker unloads the truck. A warehouse clerk
checks the goods against the delivery note and takes it with
annotations to the GR office. The GR office clerk posts the goods
receipt. Upon the goods receipt posting, the system creates and
prints warehouse orders(WOs) with reference to the inbound delivery
to move the goods into the warehouse. The truck leaves. A warehouse
worker moves the goods from the GR area into the warehouse. For
example, they are moved to two different storage types: a storage
type for small parts and a storage type for large parts. The storage
type for small parts is divided into two storage sections: one for slowmoving items, and one for fast-moving items. In the storage type for
small parts, the next empty storage bin is determined as the
destination storage bin. In the storage type for large parts, fixed
storage bins are used.

2011 SAP AG. All rights reserved.

Purpose

Products that have not yet been categorized as small or large parts or
that have no fixed bin assignment are first moved into a separate
storage type for clarification.
A variant of this process is to trigger the stock placement operations
before the Goods Receipt posting. In this case, the warehouse task
can be created manually, and the system posts the GR automatically.

2011 SAP AG. All rights reserved.

Prerequisites

You

have integrated SAP EWM with SAP ERP

You

have configured the warehouse structure and master data

You

have configured your systems for this process

Either

a purchasing document exists in SAP ERP, or no purchasing

document exists yet, but you have set up the automatic purchase
order creation in SAP ERP.

2011 SAP AG. All rights reserved.

Process step 1:

A truck arrives at the checkpoint and drives to the door

The truck drives to the door assigned by the checkpoint clerk.

In this process, this step is not realized in the system.

2011 SAP AG. All rights reserved.

Process step 2:

Check the delivery note, and find or create an inbound delivery (SAP EWM)
The truck driver brings the delivery note to the GR office, where the GR
office clerk checks it against the system data.
Variant A: The GR office clerk finds the inbound delivery by the ASN
number in the system. In this case, the vendor has sent an ASN, and the
inbound delivery is created in SAP ERP and is sent to SAP EWM
automatically.
Variant B: The GR office clerk finds an expected goods receipt by the
purchase order number in the system. In this case, he or she manually
creates an inbound delivery based on the expected goods receipt.
Variant C: The GR office clerk finds no inbound delivery and no
expected goods receipt in the system. In this case, he or she manually
creates an inbound delivery in SAP EWM System by entering the data
from the delivery note into the system.
Instead of creating inbound deliveries manually in SAP EWM, it is also
possible to create them in SAP ERP or to switch to SAP ERP from the
user interface in SAP EWM to create them.

2011 SAP AG. All rights reserved.

Process step 3:

Unload the truck and check the goods

A warehouse worker unloads the truck. A warehouse clerk checks the
information on the packages against the delivery note. The warehouse
clerk takes the delivery note with annotations to the GR office.
In this process, this step is not realized in the system.

2011 SAP AG. All rights reserved.

Process step 4- Part 1:

Post the goods receipt and create the putaway WOs (SAP EWM)
Before posting the GR, the GR office clerk can change the delivery
data in the system (for example, quantities) based on the delivery note
with annotations from the physical check.
The GR transaction offers scanning capabilities for identifying the
delivery items by product or EAN/UPC.
The GR office clerk posts the goods receipt. The system
communicates the goods receipt to SAP ERP. When the GR is posted,
the system automatically creates WTs. Using the palletization data
coming from the packaging specification, the system creates as many
WTs as physical units of the received quantity of the product exist.
The system creates one WO for each WT.
For products that are not yet categorized as small or large parts, or
that do not yet have a fixed bin assignment, the system determines a
destination bin in the clarification zone.
If the fixed bin or the destination storage type of a product is full, the
system also determines a destination bin in the clarification zone.

2011 SAP AG. All rights reserved.

Process step 4- Part 2:

Post the goods receipt and create the putaway WOs (SAP EWM)
The system automatically prints the putaway WOs upon creation twice on
a printer in the GR office. One printout is attached to the goods, the other
one is used for putaway execution and confirmation.

Process Variant : The warehouse task and warehouse orders for putaway
activities can be created manually before the goods receipt posting, if
required. Then, the GR posting is automatically performed during the
warehouse task confirmation step.

2011 SAP AG. All rights reserved.

10

Process step 5:

The truck departure

The truck leaves the door and the premises.

In this process, this step is not realized in the system

2011 SAP AG. All rights reserved.

11

Process step 6:

Putaway the goods (SAP EWM)

A warehouse worker takes both printouts of the WOs from the GR
office. Then, he or she goes to the GR area to identify the goods (by
the product short description on the WO, for example). He or she
attaches one WO printout to the goods. The worker moves the goods
to the destination bin. If the destination bin cannot be reached or if it
is full, he or she takes the goods to the clarification zone. At the end
of putaway execution, a warehouse clerk confirms the putaway WOs
in the system.

2011 SAP AG. All rights reserved.

12

Process step 7 (exceptional case):

Putaway the goods from the clarification zone (SAP EWM)

A warehouse clerk monitors the stock in the clarification zone. If stock
exists there, he or she clarifies the reason for the movement of that
stock to the clarification zone. If the warehouse-specific master data
is missing for the product, he or she maintains it. If the packaging
specification for the product is missing, the clerk creates it together
with the condition record. If the assigned fixed bin is full, he or she
assigns a new (suboptimal) fixed bin to the product. Finally, the clerk
creates an ad hoc WO to put away the product. The system prints the
ad hoc WO. After the physical move is processed by a warehouse
worker, he or she confirms the WO.

2011 SAP AG. All rights reserved.

13

Process Monitoring
Process
Step

Objects To Be
Monitored

Activities

GR workload list

Extended Warehouse Management Monitoring Goods Receipt

Workload

Open deliveries in
terms of GR

Extended Warehouse Management Monitoring Warehouse

Management Monitor Inbound Documents Inbound Delivery
Select inbound deliveries by Delivery Date and Goods Receipt Status

4 and 6

Open deliveries in
terms of warehouse
activity (WT not
created yet, WT not
confirmed yet)

Extended Warehouse Management Monitoring Warehouse

Management Monitor Inbound Documents Inbound Delivery
Select inbound deliveries by Delivery Date and Putaway Status or Putaway
Status (Plan).

Open putaway WOs

for the destination
activity areas

Extended Warehouse Management Monitoring Warehouse

Management Monitor Documents Warehouse Order

Open putaway WTs

for the GR area

Extended Warehouse Management Monitoring Warehouse

Management Monitor Documents Warehouse Task
Select Open WTs and From Data by source Storage Type

Current stock in the

clarification zone

Extended Warehouse Management Monitoring Warehouse

Management Monitor Stock and Bin Stock Overview
Select stock by Storage Type and Storage Bin.

All

2011 SAP AG. All rights reserved.

14

More Information

For more information, see SAP Library for SAP

Extended Warehouse Management on the SAP Help
Portal at http://help.sap.com.

2011 SAP AG. All rights reserved.

15

 2011 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, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,
z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,
PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,
OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,
Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered
trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated 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.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, 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 other
countries.

2011 SAP AG. All rights reserved.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase, Inc. Sybase is an SAP company.
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.

16