Streamline Internal

Warehouse Functions
with SAP’s Extended
Warehouse Management
(EWM) Solution

Patti Gardner
SAP Labs
Overview: Service Parts Execution
Internal Processes

In/Outbound Processes

Other Warehouse Enhancements

Wrap-up
 Service Parts Management — Building Blocks
SAP SCM 5.0
Service Parts Planning
Strategic Supply Chain Design
Parts Demand Planning
Parts Inventory Planning
Parts Supply Planning
Parts Distribution Planning
Parts Monitoring
Supply Network Collaboration
Supply Chain Analytics
Service Parts Execution
Quality Assurance and Control
Warehousing and Storage
Physical Inventory
Cross-Docking
Outbound Processing Transportation
Management
Execution Monitoring
Execution Collaboration
Analytics
SAP NetWeaver 2004s
© SAP AG 2006, 3
SAP CRM 5.0
Service Parts Execution
Marketing Campaign Processing
Sales Order Processing
Billing incl. Invoice Corrections
and Entitlement Management
Complaints and Returns Processing
Analytics
Execution Collaboration
SAP NetWeaver 2004s
SAP ERP 2005
Service Parts Execution
Purchase Order Processing
Inbound Processing and
Receipt Confirmation
Analytics
SAP NetWeaver 2004s
 Key Capability: Service Parts Execution

Service Parts Execution enables a logical flow of parts through

the service network

This includes:
„ Procurement
„ Goods movement of new parts and returned parts
„ Quality management
„ Warehouse and storage management

New Parts
Quality
Inspections
Warehouse
Management
Goods Movement

Returned Parts
Repair Services

Physical
Inventory

Cross-Docking

© SAP AG 2006, 4
 Service Parts Execution

Warehouse Monitor for overview of all warehouse activities

Parts Execution Monitoring

Parts
Inbound Parts Parts Quality Physical Parts Cross-
Warehousing
Processing Management Inventory Docking
and Storage

„ Stock visibility in staging area Warehouse optimization „ Physical inventory „ Transportation

„ Counting triggered by various „ Slotting: Find the best bin management based cross- docking:
criteria for a material on various strategies Forward parts to the
„ Bundling: Group warehouse (strategy for slow end facility/customer
„ Packaging for consolidation
management requests to movers, fast movers, via one or more
and deconsolidation of critical parts, etc.) intermediate facilities
optimize picking, packing, and
parts/inbound packaging for
staging of goods
long-term storage
„ Transportation chain route
„ Scrapping requests (all or optimization
except best n pieces) and „ Kitting: Enhanced kit-to-order
scrapping strategies for part process
identification
„ Rules-based rebalancing
„ Enhanced customer returns based on planning results
management process and full „ Flexible warehouse modeling
visibility (storage bins, staging areas,
„ Contract Packager inbound work stations)
processing „ Emergency replenishment –
picker encountered empty bin
„ Picker-directed replenishment
– picker does replenishment by
himself
© SAP AG 2006, 5
 EWM Basics — Example of Business Requirements

Handling of multi-step picking and putaway Æ Internal routing

Finding the best location in the warehouse based on

product demand (fast changing) and Æ Slotting
product dimensions
Optimizing warehouse constantly Æ Rearrangement
(Housekeeping)

Assigning the right workload (weight, volume,

number of items) to the warehouse worker Æ Warehouse Order Creation
that can be picked together

Handling resources (forklift, picker) in the

warehouse and assigning only the work that can
Æ Resource Management
be done by this resource; visibility of stock
on resources
Wave picking based on flexible criteria Æ Wave Management

Central monitoring of the warehouse activities Æ Warehouse Monitor

Driving Warehouse logistics by Handling Units (Hus) Æ Cross-delivery HU and Delivery Split

© SAP AG 2006, 6
Overview: Service Parts Execution
Internal Processes

In/Outbound Processes

Other Warehouse Enhancements

Wrap-up
 Resource Definition

Resource:
„ User or equipment that can execute work in
the warehouse
„ RF (automatic or manual)
„ Non-RF environment (manual)
„ Tracked and displayed in the
Warehouse Monitor

Resource Type:
„ Grouping of resources with similar
technical or physical characteristics
Resource Group:
„ Groups resources for queue
assignment purposes

© SAP AG 2006, 8
 Assignment of Warehouse Order to Resource

ƒ Manual: Warehouse Order is assigned to the resource via the

Warehouse Monitor

ƒ Automatic: Resource logs onto RF device and chooses System-

Guided option from menu

ƒ Resource can request work by selecting a manual option from the

RF menu (example: Pick by HU)

ƒ Warehouse Order Prioritization

ƒ Ensures most suitable resource
ƒ Highest priority task (LSD, Priority weightings)

© SAP AG 2006, 9
 Execution Qualifications

Bin Access Type

„ Reflects a resource type’s ability to access
stock located in a specific type of physical
area in the warehouse (e.g., up to 2
wBin Access
meters) Type A (up to
2 meters)
Handling Unit Type group
„ Reflects a resource type's ability to handle
the HU

Queue
„ Resource is assigned to Resource
Group, which maintains sequence wFrom wTo
of assigned Queues Activity Area/s Activity Area/s

Bin
Access
wProcess
Type wType

© SAP AG 2006, 10
 Replenishment

„ Replenishment is used to fill a primary picking area

according to the requirement of the products picked from
this area

„ Data Sources are:

‹ Slotting: Calculates Maximum Quantity, Minimum Quantity, and
Minimum Replenishment Quantity on Storage Type Level or on Fixed
Bin Level
‹ Manual Entry of Maximum Quantity, Minimum Quantity, and Minimum
Replenishment Quantity
‹ Open Warehouse Requests according to selection

© SAP AG 2006, 11
 Planned Replenishment

Maximum
Quantity
→ Started in online or batch mode
→ Calculates Replenishment according
to Maximum and Minimum Quantity
Minimum
Quantity → Only started when Stock figure is
lower than the Minimum Quantity
→ Round down to multiples of Minimum
Replenishment Quantity

© SAP AG 2006, 12
 Automatic Replenishment

Maximum
Quantity
→ Started during WT Confirmation
→ Calculates Replenishment according
to Maximum and Minimum Quantity
Minimum
Quantity → Only started when Stock figure gets
lower than the Minimum Quantity
→ Round down to multiples of Minimum
Replenishment Quantity

© SAP AG 2006, 13
 Order-Related Replenishment

Open WHR
Quantity

Maximum
→ Started in online or batch mode
Quantity

→ Calculated Replenishment according

to Open WHR quantity
Minimum
Quantity → Started when Stock figure is lower
than the Required Quantity
→ Round up to multiples of Minimum
Replenishment Quantity
→ Exceeding Maximum Quantity is
possible

© SAP AG 2006, 14
 Direct Replenishment

Maximum
Quantity
→ Started during a Pick Denial when
Exception Code points to the Internal
Process Code “Replenishment”
Exception

→ Only possible for Fixed Bin Scenario

REPL
Minimum
Quantity

→ Calculated Replenishment according

to Maximum and Minimum Quantity
→ Assume that Bin Quantity is zero
→ Round down to multiples of Minimum
Replenishment Quantity
→ Picker performs the Replenishment
(Picker-Directed Replenishment)

© SAP AG 2006, 15
 Scrap Management
Scrap Request
„ Partial Scrap
„ Full Scrap

Partial Scrap
„ Keep quantities for other planned
assignments
„ Special strategies and sequence to identify
worst materials and conditions of allocated
materials

Authorization Process for Scrap Request

Start Scrap Request from:
„ Warehouse Management (e.g., damaged
materials)
„ Inventory Management
„ Service Parts Planning

© SAP AG 2006, 16
 Packaging

Packaging specification:
ƒ Central maintenance and distribution
of packaging specifications
ƒ Multiple packing specifications per material
(condition technique)
ƒ Used in inbound, outbound, and internal processes

Packaging stations:
ƒ Consolidation/deconsolidation stations
ƒ Grouping of stations
ƒ Predefined documents per station

© SAP AG 2006, 17
 Exception Handling

Keeping any gap between the real world (physical

warehouse) and system data (warehouse system)
small over time; all detected inconsistencies shall be
entered, clarified, and corrected in the system as
soon as possible

For example, a warehouse worker must execute a warehouse

task with a pick quantity of 100 pieces from a defined Bin, but the
Bin is empty

With implemented exception handler service, the user will be able to

describe the problem encountered by entering an appropriate
exception code. Configurable follow-up action can be used to solve
the exceptional situation and help the warehouse worker to finish his
work as fast as possible.

© SAP AG 2006, 18
 Possible Scenarios to Solve the Problem

(1) Working in an RF environment, the experienced warehouse

worker will get a screen to enter a new Source Bin by raising an
exception code
(2) Working in an RF environment, the experienced worker will
trigger Replenishment by raising an exception code and skip the
WT processing; after replenishment, the “exceptional” WT can
be executed
(3) Working in an RF environment, the experienced worker will get a
screen proposing a new Source Bin by raising an exception
code; in addition, the Bin will be blocked for picking, and a
Physical Inventory will be initiated
(4) Working in Confirmation-WT-Processing, the low-skilled
warehouse worker will trigger the creation of an Alert only. A
warehouse supervisor is able to trace the WM-Alerts and start
the action, which can solve the problem (Block Bin for picking,
Physical Inventory)

© SAP AG 2006, 19
 Applications with Exception Handling

ƒ RF Transactions

ƒ UI for confirmation of Warehouse Tasks

© SAP AG 2006, 20
Overview: Service Parts Execution
Internal Processes

In/Outbound Processes

Other Warehouse Enhancements

Wrap-up
 Simple Kit
Item UEPOS UEPVW
Material Quantity UoM
Category

10 KIT Brake Kit 1 PC

20 KOMP Brake rotor disc 2 PC 10 K

30 KOMP Carbon-metallic pads 4 PC 10 K

© SAP AG 2006, 22
 Kit to Order — Integration 1

CRM ERP EWM APO GTS

Create Sales order ATP confirmed

quantities - SO
Brake Kit 5 PC Loc: CL
• Brake disc 10 PC Loc: CL • Brake disc 10 PC Loc: CL
• Carb. pads 20 PC Loc: CL • Carb. pads 20 PC Loc: CL

Create unchecked
delivery
Brake Kit 5 PC
• Brake disc 10 PC
• Carb. pads 20 PC

Convert UD -> CD ATP confirmed

Brake Kit 5 PC -> 4 quantities SO -> OD
• Brake disc 10 PC -> 8 • Brake disc 8 PC
• Carb. pads 20 PC -> 16 • Carb. pads 16 PC

Create outbound
delivery
Brake Kit 4 PC
• Brake disc 8 PC
• Carb. pads 16 PC

© SAP AG 2006, 23
 Kit to Order — Integration 2

CRM ERP EWM APO GTS

Confirm outbound
delivery
Brake Kit 3 PC
• Brake disc 6 PC
• Carb. pads 12 PC

Confirm outbound
delivery
Brake Kit 3 PC
• Brake disc 6 PC ATP confirmed
• Carb. pads 12 PC quantity consumption
(OD)
Change delivery and - Brake disc 6 PC
create Material - Carb. pads 12 PC
Movement
APO stock update
- Brake disc 6 PC - Brake disc 6 PC
- Carb. pads 12 PC - Carb. pads 12 PC

+ Brake Kit 3 PC Loc: CL + Brake Kit 3 PC Loc: CL

- Brake Kit 3 PC Loc: CL
- Brake Kit 3 PC Loc: CL

Update CRM Sales

Order
Brake Kits 3 PC Loc: CL
• Brake disc 6 PC Loc: CL
• Carb. pads 12 PC Loc: CL

Update CRM Billing

© SAP AG 2006, 24
 General

„ Basics
„ Kit to Order – no Kit to stock
„ Kit structures are defined within SCM iPPE (Integrated Product and
Process Engineering)

„ Order Management (CRM)

„ Kit structures are very dynamic and can differ from order to order
„ Kit structures are determined via Global ATP
„ One Kit header and the according components will be sourced at the
same location

„ Shipping and Warehouse

„ The quantity relation between Kit header and Kit components needs to be
correlated (linear correlation)
„ Only complete Kits will be shipped
„ All components of a single Kit will be packed into the same Handling Unit

„ Customer Invoice
„ The customer will always be invoiced on Kit header level

© SAP AG 2006, 25
 Kitting in EWM

Packaging specification for a Kit

Level type defined in customizing

© SAP AG 2006, 26
 Definitions — Value-Added Services (VAS)

Value-Added Service (VAS): An operation performed on materials that

enhances their value, worth, functionality, or usefulness. Value added services
are performed by workers in work centers. Example: Preservation, Packaging,
Assembly, Kitting, Tagging, Price Marking.

VAS Order: An instruction to perform a VAS on one or more materials or

items, based on a reference document. A VAS order establishes the
relationship between a reference document and VAS pack specification. It
contains details from the respective pack specification.

VAS Activity: A VAS order consists of one or several activities. An activity is

an operation a worker has to perform at one work center. An activity references
a level of a packaging specification. Within one activity, the worker might get
one or several work steps from the packaging specification that advises
him/her how this activity is performed. Example: Pack product into Carton
(Size M) and label it.

VAS Item: Delivery Items to be handled in the VAS Order

VAS Auxiliary Product: One or more auxiliary products are used to perform
an activity. An auxiliary product can be a packaging material, an auxiliary
packaging material, or a product. Examples: Paint, pallet, label, lid, carton.

© SAP AG 2006, 27
 VAS During Inbound

Truck

Packspec PS1
Delivery X Content: Pyramid
GR-LOC Item 10: Level 1: Preservation
Pyramid,3 pc Level 2: Unit Containment

Work center AP01

VAS Order VO1
Preservation
Activity 1: Workcen. AP01
VAS-item: Pyramid, 3 pc
VAS-auxprod: Oil
Activity 2: Workcen. AP02
VAS-item: Pyramid, 3 pc
VAS-auxprod: Box, 3 pc
Work center AP02 Unit
packing

Final Bin

© SAP AG 2006, 28
 VAS and Kitting

Delivery Y Packspec PS2

Item 10: Kit, Content: Kit
2 pc Level 1:
Item 10-01: 2 pc A Assemble Comp.
Item 10-02: 2 pc B
Item 10-03: 4 pc C Level 2:
Pack into box

Work center
AP01 Kitting
VAS Order VO2
Activity 1: Workcen. AP01
VAS-item: A,2pc
VAS-item: B,2pc
VAS-item: C,4pc
Activity 2: Workcen. AP01
VAS-auxprod: Box, 1 pc
Loading

© SAP AG 2006, 29
 VAS During Outbound

Picking HUs Packspec PS3

Delivery Z
Content: Bike 1pc
Item 10: Bike,
3 pc Pump 1pc
Item 20: Pump, Level 1:
3 pc Gift wrapping

Work center
customer VAS Order VO3
Activity 1: Workcen. CUST
packing
VAS-item: Bike, 3 pc
VAS-item: Pump, 3 pc
VAS-auxprod: Box, 3 pc
VAS-auxprod: Gift paper

Loading

© SAP AG 2006, 30
 Cross-Docking: Definition

Push Deployment (PD)

An APO decision to forward stock from one warehouse to another. The
decision is made upon GR and is based on product demand forecast.

Pick From Goods Receipt (PFGR)

An APO decision, based on a CRM back-order situation, to forward stock
to a customer or another warehouse directly from receiving

Transportation Cross-Docking (TCD)

Procedure to plan and optimize transportation from source to destination
via intermediate cross-docking locations

© SAP AG 2006, 31
 Process Push Deployment/Pick from GR

© SAP AG 2006, 32
 Demand Situation

Warehouse
SPU2
Inbound
Delivery

200 EA

PFGR PD
1 EA 100 EA
18 EA 50 EA

Warehouse Warehouse
Customer Customer SPU3 SPB1
Order 1 Order 2

50 EA 100 EA
1 EA 18 EA

© SAP AG 2006, 33
 Transportation Cross-Docking (TCD)

Definition:

Procedure to plan and optimize transportation from source to destination

via intermediate cross-docking locations

At any intermediate CD location, the goods are brought directly from

goods receipt to goods issue without being put away

Only operates with HUs

Transportation cross-docking supports:

„ Optimized warehouse processing at intermediate warehouses without
the need of storage or repacking
„ Outbound deliveries from sales orders and stock transport orders
„ Integration with storage control
„ Full-pallet operations with Pick-HU-WTs (HU only)

© SAP AG 2006, 34
 TCD — Customer Order
CRM/ MM ERP EWM (SPU1) EWM (SPU2) Customer

Create SO Create SO

Create Outb. DLV Create Outb. DLV

Determine TCD

Exec. Warehouse
Activities

Adjust DLV in case Post GI and

of changed route submit route

Transfer Posting to
Stock in transfer

Create Inb. and

Outb. DLV for Post GR
CD Location
Exec. Warehouse
Activities

Post GI for STO Post GI

Create Inb. DLV Post GR

for final Location

Update Inventory

© SAP AG 2006, 35
 TCD and Route

„ TCD is a decision based on route determination that the goods will not go
directly to the customer, but will go through an intermediate warehouse
„ TCD is the result of Route Determination in an outbound delivery order.
This determination changes the Ship-to to a Cross-Dock facility and marks
the original Ship-to as the Final Ship-to.
„ Basic Setup required to trigger TCD
‹ Routes from Source to CD facility, and from CD facility to Destination
‹ CD Route connecting the Routes at the CD facility
„ Example
‹ Route SPU1_SPU2 is a route from SPU1 to SPU2
‹ Route SPU2_CUST is a route from SPU2 to CUST
‹ Route CD_SPU2 is a CD route at SPU2 linking SPU1_SPU2 and SPU2_CUST

CD_SPU2

SPU1_SPU2 SPU2_CUST
SPU1 SPU2 CUST

© SAP AG 2006, 36
 TCD: Documents

SO from Customer CUST

1 SPU1 determined as shipping location

SO
with plant
SPU1

Delivery from SPU1

2 to CUST
Shipping Location Receiving Location
SPU1 CUST

TCD scenario detected

3 Outbound Delivery to SPU2
Trigger
7 invoicing

Stock transfer
4 Inbound Delivery to SPU2

Cross-Docking Location Final Outbound Delivery

SPU2 6 to CUST

5 Actual Cross-Docking in SPU2

© SAP AG 2006, 37
 Yard Management: Business Process

1. Check-in and move

TU to parking lot

5. Checkout 2. Move TU from

parking lot to door

4. Move TU from door 3. Unload TU

to checkpoint

© SAP AG 2006, 38
 Three Components of Yard Management

1) Yard Location
Management:
Door A1
Adopt physical/
geographical Door A2
locations (parking Slot 17 WHS 001
2) Yard Movements:
lots and doors) and P00A

objects (trucks) to Represent physical

system entities
Door An Door
B1
Door
Bn
movements of trucks
(storage bins and
Checkpoint I by “moving”
transport units) transport units and
vehicles within the
Door Door
Yn Y1
yard locations
Slot 34
Door X1
3) Yard Stock: WHS 00n P00B

Door X2
Report the transport
units content to
Door Xn
support and control Checkpoint II

the loading and

unloading activities

© SAP AG 2006, 39
 Yard Location Management

Whse-Nr 0001 WhType: YARD StoSec: CHPTA

WhType: STAREA WhType: Checkpoint A

DOOR

StoSec: 0003

StoSec: StoSec: 0001

Storage Bin
0001

Storage
StoSec: 000n Section
StoSec: 0002

Storage Type

Whse
StoSec: CHPTB Door

Checkpoint B

© SAP AG 2006, 40
 Yard Stock — Visibility

y Empty TU-HU for all

Yard Movements
y Stock: The HU-
Product itself
1:1 y Stock overview
on Yard only
via assigned TU
TU-HU
Transport Unit

TU knows its assigned deliveries

HU-Product Product A
WHS1
HU-Product Posted Stock can be:
a) On TU-Location or
b) On WHS-Location

Product A Product B
WHS1 Product B WHS2
WHS2

© SAP AG 2006, 41
 Claims/Returns/Entitlements

Claims/Returns:
ƒ Automated, rules-based validation and
processing of claims and returns
ƒ Complex approval processing

Entitlements:
ƒ Integrated in sales order and returns processing

ƒ Deposit invoicing: Deposit to be paid at time

of purchase and refunded at time of return
ƒ Deposit referral: Deposit only needs to be paid
if part is not returned (time frame)

© SAP AG 2006, 42
 Supplier Collaboration — ASN Management

Advanced Shipping Notification (ASN):

ƒ Receive ASN via EDI or WEB/ICH

ƒ Alert functionalities

ƒ Goods receipt based on ASN

ƒ Additional validation process for contract packager ASN

ƒ Automated vendor billing based on ASN

ƒ Overages/under-deliveries can be handled

without valid purchase agreement

ƒ Decentralized goods receipt possible without ASN

ƒ Integration to planning (fulfilled inbound deliveries)

© SAP AG 2006, 43
Overview: Service Parts Execution
Internal Processes

In/Outbound Processes

Other Warehouse Enhancements

Wrap-up
 Serial Number Support

Serial number (SN): Serial numbers are digit and/or character combinations (length 30) assigned
to a product for the whole lifecycle to differentiate that item from items of the product. The
combination of product and serial number is unique.

Serial number profile: Combined data, grouped in a four-figure abbreviation, which determines
the conditions and business transactions for issuing serial numbers to serialized products.
You must enter the serial number profile in the product master records for products that need
serial numbers.

In ERP a global serial number profile has to be defined. Within EWM, a warehouse-number-
dependent profile can be defined: EWM will search for a product with an assigned serial number
profile – first for the warehouse-dependent profile, and if not found, EWM will take the global
profile.

Following serial number requirement types are available:

A Serial Numbers for Document Items
B Serial Numbers on Warehouse Number Level
C Serial Numbers in Inventory Management
D No Serial Number Requirement (only for redefinition necessary)

© SAP AG 2006, 45
 Serial Number Requirement

A B C
Serial numbers on Serial numbers in
Document items warehouse number level Inventory Managment

Wareh. 0001 Bin 4711:

Inb. Delivery
Serial nr.:
Item 10: product x Product x, 2 PC:
SN x1, … SN x10 Product x:
SN x1, x5
Item 20: product y SN x1, x5, …
SN 1, … SN 5 Product y, 1 PC
… Product y:
SN 4
SN 4, SN 5, …

Seriel number Serial number Serial number

Requirements necessary for every necessary for every
depends on Delivery goods receipt/issue movement
item type

Control of SN Information, which Exact information

possible, e.g., in seriel number are where seriel
returns process available in number is located
warehouse in warehouse
© SAP AG 2006, 46
 Goods Receipt (GR)

ASN
(including SN)

ERP
Inb. Delivery
Item 10: product x
SN x1, … SN x10

Item 20: product y

SN 1, … SN 5

t
en n
u m atio
c liz
Do ria
GR se

Inb. Delivery Wareh. 0001

Serial nr:
Serial numbers on
Item 10: product x warehouse level Product x:
SN x1, … SN x10 SN x1, x5, …
Product y:
Item 20: product y SN 4, SN 5, …
EWM SN 1, … SN 5
St
m a oc k
s e na g
nu r i a l e d
mb
… er Bin 4711:
s

Product x, 2 PC:
SN x1, x5
Product y, 1 PC
SN 4

© SAP AG 2006, 47
 Goods Issue

Order
(from CRM
without SN)
ERP
Outbound delivery

Outbound delivery (with

WT
(without SN)

Outb. Delivery Conf.

SN)

Item 10: product x

Item 20: product y Pack-
EWM …
UI/Workcenter

Delivery UI

© SAP AG 2006, 48
 Environmental, Health, and Safety (EH&S) Services

EH&S Services in SCM

„ Provide data/services for Dangerous Goods Management in EWM
„ Provide data for Hazardous Substance Management in EWM
„ Influences route determination

ERP EH&S components communicate with SCM EH&S Services

„ Central data maintenance in ERP and distribution into EWM is possible
„ New EH&S Hazardous Substance component was built in ERP

EH&S Services for Dangerous Goods Management

„ Own master data
„ Master data is regulation-specific (i.e., regulation “ADR”)
„ Service for routing guide engine to check if transport of dangerous goods is allowed on a
determined route/trip
„ Service to retrieve dangerous goods data for shipping documents

EH&S Services for Hazardous Substance Management

„ Own master data
„ Master data contains key information that is used for storage checks, which are performed
for hazardous substances by Warehouse Management
„ Master data contains RF texts (for RF Terminals of the warehouse) that describe potential
risk for the handling of the hazardous substances
„ Provides an inventory list of hazardous substances in the specific warehouse

© SAP AG 2006, 49
 EH&S Services — SCM and ERP

ERP SCM

CIF

Product Master
Material Master

EH&S Specification Database

ALE
EH&S Dangerous Goods Master EH&S Dangerous Goods Master

ALE
EH&S Hazardous Subst. Master EH&S Hazardous Subst. Master

ALE
EH&S Phrase Management EH&S Phrase Management

Filling

© SAP AG 2006, 50
 EH&S Services — Provided Services within SCM

SCM
EWM TM
Storage
Checks
RGE
Shipping
Documents

SCM - Basis

EH&S Services - Core

© SAP AG 2006, 51
Overview: Service Parts Execution
Internal Processes

In/Outbound Processes

Other Warehouse Enhancements

Wrap-up
 Resources

„ Online Help (http://help.sap.com/)

Select Documentation Æ mySAP Business Suite Æ SAP Supply Chain
Management Æ SAP SCM 5.0 (select language) Æ SAP Extended
Warehouse Management (SAP EWM)

„ SCM Portal (http://service.sap.com/scm)

Choose Warehousing, and then either ERP EWM or SCM EWM

© SAP AG 2006, 53
 7 Key Points to Take Home

ƒ Resource Management maximizes the efficiency of

your warehouse processes
ƒ Multiple replenishment strategies are available in
EWM to manage the inventory balance in your primary
pick locations
ƒ When exceptions happen, and they will, EWM offers
exception handling to better manage your warehouse
processes
ƒ You can use a value-added service (VAS) order to
execute VASes in the warehouse through VAS
activities, and to document them. Typical VAS
activities are assembling products, packing products,
labeling, and kitting.

© SAP AG 2006, 54
 7 Key Points to Take Home (cont.)

ƒ There are several cross-docking options to enhance

your warehouse performance, including Pick From
Goods Receipt and Push Deployment. Transportation
Cross-Docking is also new with EWM.
ƒ Yard Management functionality helps you extend the
boundaries of the warehouse and manage vehicles in
your yard
ƒ Support for Serial Numbers is also available with
EWM. With EWM, you can manage serial numbers at
the document level, the warehouse level, the bin level,
or not at all.

© SAP AG 2006, 55
 Contact Information

Questions?

For further information, please contact:

Patti Gardner (patricia.gardner@sap.com)

Markus Rosemann (markus.rosemann@sap.com)

Richard Kirker (richard.kirker@sap.com)

© SAP AG 2006, 56
 Thank you for your interest and attention!

© SAP AG 2006, 57
 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, 58