Track2 Session8
Track2 Session8
Extended Warehouse
Management’s (EWM)
Inbound and Outbound
Processing Capabilities
Patti Gardner
SAP Labs
Landscape
Inbound Processing
Outbound Processing
Wrap-up
Roadmap WM: Enterprise Focus — Today
Architecture options:
Integrated or
Decentralized
© SAP AG 2006, 3
Landscape Overview — Decentralized WM (SAP ECC)
TRM
WM
WM TRA
TRA
Full SAP ECC
installation
IM
IM SD
SD PP
PP QM
QM PM
PM
Only Warehouse LE
LE
HR
HR FI
FI
Management Logistics
Logistics
configured
Cross
Cross Application
Application Objects
Objects (SAP
(SAP ABA)
ABA)
Web
Web Application
Application Server
Server (SAP
(SAP Web
Web AS)
AS)
Decentralized WM
© SAP AG 2006, 4
Enterprise, Service Parts Execution, and
Network Focus
SAP SAP
SAP Extended
ERP LES LES WM
SAP SCM
WM Dec WM = full SAP ECC system
© SAP AG 2006, 5
Roadmap WM: Service Parts Management
© SAP AG 2006, 6
Service Parts Management — Building Blocks
© SAP AG 2006, 7
Landscape Overview — Decentralized EWM
(SAP SCM 5.0)
SAP APO
Fully integrated
into SCM suite
SNP PP
PP
DP
DP TP/VS
TP/VS SNP gATP
gATP
DS
DS
Installation on a
separate server is
EWM
EWM SPP EM ICH
SPP EM ICH
Live
Live Cache
Cache
recommended
Cross
Cross Application
Application Objects
Objects (SAP
(SAP ABA
ABA 7.00)
7.00)
Web
Web Application
Application Server
Server (SAP
(SAP Web
Web AS
AS 7.00)
7.00)
© SAP AG 2006, 8
Key Capability: Service Parts Execution
This includes:
Procurement
Goods movement of new parts and returned parts
Quality Management, and
Warehouse and Storage Management
New Parts
Quality
Inspections
Warehouse
Management
Goods Movement
Returned Parts
Repair Services
Physical
Inventory
Cross-Docking
© SAP AG 2006, 9
Service Parts Execution
Parts
Inbound Parts Parts Quality Physical Parts Cross-
Warehousing
Processing Management Inventory Docking
and Storage
Historical data
Long
Long term
term
Faster order planning
planning
to delivery
cycles Mid
Mid term
term
planning
planning
Short
Short term
term Replenishment
Replenishment
planning
planning
Shorter
product life
cycles Sense and Respond
to Demand Customers
and
Consumers
Faster High
Warehouse Higher
product Warehouse Availability
Management Service
development Management
Levels As Needed
cycles Transportation
Transportation
Management
Management
All or portions
of your supply
chain may be West
outsourced
Returns
Adapting to
changes quickly
is no longer
an exception
process
© SAP AG 2006, 12
Success in a Supply Chain Network Requires Integrated
Planning and Execution by Design (Not After the Fact)
Respond Sense
Outbound Processing
Wrap-up
EWM Inbound Process
New New
Enhanced Enhanced
Putaway
New
Process Exceptions/Manage Work in Process
© SAP AG 2006, 15
EWM Inbound Process: New Processes
© SAP AG 2006, 16
EWM — Inbound Delivery Processing
© SAP AG 2006, 17
EWM — Inbound Delivery Processing (cont.)
Creation WT #1234
Inbound WT
Delivery Prompt Inbound #1233WT
1:1 Notification creation
#1235
delivery
8026 (ERP)
Whse 003
1:1 #25002(int.)
Whse 003 Confirmation
Messages: Response
ERP
Inbound Messages: Delivery Info
Delivery
EWM
© SAP AG 2006, 18
Complex Putaway Process with Internal Routing
Prod. WT
Mat. 1
Goods Receipt
SType: 9010 Deconsolidation Station: AP1
Bin: GR-ZONE SType: APDK
1 Sec: Sec: 0001
3 Step: IB02 AP1I Bin: AP1
Prod. WT
Mat. 2
Final Final
SType SType
JK01 JK04
AA: PT01 AA: PT04
C.Gr.: ICG01 C.Gr.: ICG04
© SAP AG 2006, 19
Multiple Materials on a Single Pallet
Material Material
1 2
SType SType
JK04 JK01
Consolidation Gr Consolidation Gr
ICG04 ICG01
© SAP AG 2006, 20
Storage Control
Process-Oriented:
Managing storage control based on the warehouse process
Layout-Oriented:
Managing storage control based on the warehouse layout
Combination:
EWM always executes the process-oriented storage control first.
The layout-oriented storage control then checks whether the
sequence of putaway process steps is possible in layout view,
and if required, adjusts the flow of the putaway or stock removal.
© SAP AG 2006, 21
Complex Putaway Procedures
© SAP AG 2006, 22
Layout-Oriented Storage Control
Example:
If you want to move a product pallet from storage bin A (goods
receiving area) to storage bin B (high rack storage area), the system
should execute a contour and weight check to ensure that the product
pallet can be put away in the high rack storage area safely. For this
activity, EWM splits the warehouse order into two: One from storage
bin A to identification point I, and a second from identification point
I to storage bin B.
© SAP AG 2006, 23
Layout-Oriented Storage Control for HU Movements
Handling Unit
Concept
Z Node
WT not active Î
A WT not active Î Z
Active WT Î WT active Î
B C
Active WT Î
From To Intermediate
A Z B
B Z C
© SAP AG 2006, 24
Direct Storage Control for Stock Removal
© SAP AG 2006, 25
Combined Storage Control for Stock Removal
© SAP AG 2006, 26
Updating the Outbound Delivery Order
EWM updates the Outbound Delivery order corresponding to the goods
issue activities for the following GI processes:
Unpacked Stock:
When the first product warehouse task is generated, EWM sets the
status Picking Planning in the outbound delivery order
On confirmation, EWM sets the status Picking in the outbound delivery
order. If the destination location in the product WT is a storage bin at the
door or a Transportation Unit (TU), EWM sets the status Unloading in the
outbound delivery order.
Packed Stock:
When the first product warehouse task is generated, EWM sets the status
Picking Planning in the outbound delivery order
On confirmation, EWM sets the status Picking in the outbound
delivery order
After packing, the related loading WT is generated. On confirmation of the
loading WT, EWM sets the status Loading in the outbound delivery order.
© SAP AG 2006, 27
Landscape
Inbound Processing
Outbound Processing
Wrap-up
EWM Outbound Process
Loading
Work and
Picking Packing Shipping Staging
Assignment Goods Issue
New
New
Process Exceptions/Manage Work in Process
© SAP AG 2006, 29
EWM — Outbound Delivery Processing
Outbound Delivery:
Represents the same data as ERP
checked delivery. Serves as
Unchecked Delivery
quantity reference for further
processing in EWM.
Outbound Delivery Order:
Warehouse Request; is comparable
with ERP Delivery. All further
picking is based on Outbound
Delivery Order.
Outbound Delivery:
Outbound Delivery Order Represents the physical GI
Quantities that are posted in EWM.
In Export cases this might be
Outbound Delivery created before the GI Posting in
EWM. In other cases it will
automatically be created with the
GI Posting for the Outbound
Delivery Order in EWM.
© SAP AG 2006, 30
Outbound Example
© SAP AG 2006, 31
Overview — Outbound Process
WHR
WHR11
WHR1
WHR1
WHR1
A list of Warehouse Requests is created
© SAP AG 2006, 32
EWM — Outbound Delivery Processing
ERP delivery
Outbound
Outbound contains 1
Delivery Immediate
creation/ delivery warehouse only
1:1 Request
deletion order
(read only) 1:1
ERP outbound
delivery
Messages: Delivery Info Delivery Processing
request WM processing
Messages: Final Delivery Info
SAP EWM
© SAP AG 2006, 33
Process-Oriented Storage Control
© SAP AG 2006, 34
Overview — Outbound Process
WO 1 WO 2 WO n
Internal Routing
Task
WHR1 Task
WHR1
WHR1 Task
WHR1
WHR1
WHR1
WHR1
WHR1 WHR1
WHR1 WHR1
WHR1
STAGE
LOAD
STAGE VAS
© SAP AG 2006, 35
Warehouse Order Creation Rules in Action
Single Task Grouped by Activity Area
2 3 5 6
Consolida-
AA1 AA1 AA1
Apply Item tion Group
Filter of BR Σ Σ
Σ Subtotals
AA2 PA2
AA2 PA2
AA2
AA3 PA3
AA3 PA3
AA3
Filter on
7 Subtotals level
Warehouse AA1 PA1
AA1
1 Wave Release/ Order Creation
Warehouse Task 4 Rule Search Apply
Creation Σ
Σ Limits
AA3 AA2 AA1 9 AA2 PA2
AA2
and
WOCR2 WOCR4 WOCR1 AA3 PA3
AA3
WOCR5 WOCR5 WOCR2 Create
WOCR3
Pick-HUs
WO3
Warehouse Order Creation
Rules per Activity Area 8 WO1
WO2
© SAP AG 2006, 36
Outbound Process with Internal Routing
Pick-HU
HU# 462910
Door
Pack-HU Pack-HU TU
HU# 462912 HU# 462912 Vehicle
Pick-HU
HU# 462911
© SAP AG 2006, 37
Landscape
Inbound Processing
Outbound Processing
Wrap-up
EWM Internal Warehouse Processes
Enhanced
Yard Management Quality Inspection Engine Inventory Counts
Record Accuracy
New Enhanced
New
Kitting Rearrangement
Replenishment
New
Process Exceptions/Manage Work in Process
© SAP AG 2006, 39
Slotting
Slotting automatically determines a storage concept for a product
Slotting takes into account master data that is not dependent on the
execution process. If the putaway process for a product is dependent
on execution parameters, this dependency is taken into account later
on during storage bin determination. This does not, however, have an
effect on the results of slotting.
© SAP AG 2006, 40
Slotting (cont.)
© SAP AG 2006, 41
Slotting (cont.)
Slotting Process
BAdI-based
Product Storage Rules
Determination Table
data (Defaults for process-
Fixed
dependent parameters) Storage Bin
Product Demand
data
Product Storage Type Search
to Slot Putaway Strategy
Sequence
Product Hazard
data
Storage Type
Maximum
BAdI-based
Product HU data Quantities
Rules
Slotting Result
Search Sequence
BAdI-based
Parameters independent of Rules
Execution process
Parameters depending on
Execution process
© SAP AG 2006, 42
Slotting (cont.)
Result of slotting:
Slotting provides the basis for rearrangement (carrying out the results
of the slotting run)
© SAP AG 2006, 43
Physical Inventory
Periodic Inventory
Continuous Inventory
Cycle Counting
Features:
Annual Inventory (location or product)
Cycle Counting (product-specific)
Ad Hoc (location or product)
Putaway (location-specific)
Zero Stock (location-specific)
Low Stock (location-specific)
Product in Right Location (location-specific)
© SAP AG 2006, 44
Physical Inventory (cont.)
Difference Analyzer
9 Evaluate Differences
9 Enter Notes
9 Enter Corrections
9 Clear Differences (EWM and ERP)
Stock Types
9 Unrestricted Use Stock in putaway and in the warehouse
9 Blocked Stock in putaway and in the warehouse
9 Quality Stock in putaway and in the warehouse
© SAP AG 2006, 45
Landscape
Inbound Processing
Outbound Processing
Wrap-up
Resources
© SAP AG 2006, 47
7 Key Points to Take Home
© SAP AG 2006, 48
7 Key Points to Take Home (cont.)
© SAP AG 2006, 49
Contact Information
Questions?
© SAP AG 2006, 50
Thank you for your interest and attention!
© SAP AG 2006, 51
Copyright 2006 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.
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 2006, 52