Student Guide

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2015, Oracle and/or its affiliatesฺ
ble
fe r a
ans
n - t r
a no
a s
R12.x Oracle h Warehouse
) deฺ
Management c m i
o GuFundamentals
e ฺ
r a cl ent
@ d
oStudenttuGuide
n S
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
D
T oni
D60471GC10
Edition 1.0
November 2011
D71671
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
bl e
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
fe r a
Trademark Notice
an s
n - t r
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
o
an
owners.
Author
s
ha eฺ
)
Kevin Brown, John Salvini
ฺ c om Guid
a c le nt
Technical Contributors and Reviewers
Tyra Crockett, Lez Stodart, Mark Lewisn@
or tude
o i s S
s
id se t h
a v
This book was published
o n iฺdusing:toOracle
u Tutor
n (t nse
d s o l i ce
av i
D
T oni
Table of Contents
R12.x Oracle Warehouse Management Overview .........................................................................................1-1

R12.x Oracle Warehouse Management .........................................................................................................1-3
Objectives ......................................................................................................................................................1-4
Agenda...........................................................................................................................................................1-5
What Is a Warehouse?...................................................................................................................................1-7
Processes of a Warehouse ............................................................................................................................1-8
Additional Product Requirements...................................................................................................................1-9
Warehouse Management Application Hierarchy ............................................................................................1-10
Inventory, Warehouse Management and MSCA ............................................................................................1-12
Radio Frequency Devices ..............................................................................................................................1-13
Agenda...........................................................................................................................................................1-14
Overview of Inbound Logistics .......................................................................................................................1-15
ble
Reverse Logistics...........................................................................................................................................1-17
fe r a
an s
Agenda...........................................................................................................................................................1-18
- t r
Overview of Outbound Logistics.....................................................................................................................1-19
n
o
an
Agenda...........................................................................................................................................................1-23
s
Value Added Services....................................................................................................................................1-24
ha eฺ
)
Agenda...........................................................................................................................................................1-26
ฺ c om Guid
Storage and Facility Management..................................................................................................................1-27
a c le nt
Agenda...........................................................................................................................................................1-29
or tude
Oracle Mobile Applications Architecture.........................................................................................................1-30
@
s o n is S
License Plate Numbers (LPNs) ......................................................................................................................1-31
a v id se th
Nesting LPNs .................................................................................................................................................1-33
Generating LPNs............................................................................................................................................1-34
n iฺd to u
LPN Context...................................................................................................................................................1-35
o
(t nse
LPN Material Status .......................................................................................................................................1-40
n
d s o l i ce
Subinventory and Locator Material Status .....................................................................................................1-42
a v i
Lot and Serial Attributes.................................................................................................................................1-43
D
oni
Cost Groups ...................................................................................................................................................1-44
T Cost Group Assignment .................................................................................................................................1-46
Task Assignment............................................................................................................................................1-47
Rules and the Rules Engine...........................................................................................................................1-49
Rules Engine Uses.........................................................................................................................................1-51
Material Allocation Example ...........................................................................................................................1-53
Allocation Decision Tree ................................................................................................................................1-54
Rules Setup ...................................................................................................................................................1-55
Defining Rules: Restrictions ...........................................................................................................................1-56
Defining Rules: Sort Criteria...........................................................................................................................1-57
Defining Rules: Default ..................................................................................................................................1-58
Strategies .......................................................................................................................................................1-59
Task Type, Label Format, and Operation Plan Selection Rules.....................................................................1-60
Consistency Requirements ............................................................................................................................1-61
Rules Simulation ............................................................................................................................................1-62
RFID Technology ...........................................................................................................................................1-63
Labeling .........................................................................................................................................................1-64
Label Types ...................................................................................................................................................1-66
R12.x Oracle Warehouse Management Fundamentals Table of Contents

i
Label Formats ................................................................................................................................................1-68
Assigning Label Types to Business Flows .....................................................................................................1-69
Agenda...........................................................................................................................................................1-70
Summary........................................................................................................................................................1-71
R12.x Oracle Warehouse Management Inbound Logistics ..........................................................................2-1

Objectives ......................................................................................................................................................2-4
Agenda...........................................................................................................................................................2-5
Overview of Inbound Logistics .......................................................................................................................2-7
Receiving Flows or Routings..........................................................................................................................2-9
Subinventories ...............................................................................................................................................2-10
Locator Types ................................................................................................................................................2-11
Receiving Locators.........................................................................................................................................2-12
Document Based Receiving ...........................................................................................................................2-14
ble
Item Based Receiving ....................................................................................................................................2-16
fe r a
s
Agenda...........................................................................................................................................................2-17
an
n - t r
Receiving Methods.........................................................................................................................................2-18
o
Standard Routing Flow...................................................................................................................................2-19
an
Inspection Routing Receipt ............................................................................................................................2-20
s
ha eฺ
Direct Receipt Flow ........................................................................................................................................2-21
)
ฺ c om Guid
Express Receipt Flow ....................................................................................................................................2-22
Express Receipts ...........................................................................................................................................2-23
a c le nt
Mixed Receipt Routing ...................................................................................................................................2-24
or tude
Desktop vs. Mobile Receiving ........................................................................................................................2-25
@
o n is S
Mobile Receiving Options ..............................................................................................................................2-26
s
v id se th
Unavailable Mobile Receiving Options...........................................................................................................2-27
a
o n iฺd to u
LPN Receipts .................................................................................................................................................2-28
(t nse
Lot and Serial Receiving ................................................................................................................................2-29
n
d s o l i ce
Automated Matching of Received Material.....................................................................................................2-30
a v i
Automated Matching of Material Received.....................................................................................................2-31
D
Receiving - GTINs..........................................................................................................................................2-32
T oni GTIN Setup ....................................................................................................................................................2-33

Receiving Open Interface...............................................................................................................................2-34
Quality Vs. Purchasing Inspection..................................................................................................................2-35
Standard Inspection .......................................................................................................................................2-36
Quality Inspection...........................................................................................................................................2-37
Inspection Storage Requirements ..................................................................................................................2-38
Returns ..........................................................................................................................................................2-39
Agenda...........................................................................................................................................................2-40
Cost Groups ...................................................................................................................................................2-41
System Assigned Cost Groups ......................................................................................................................2-43
Cost Groups Setup.........................................................................................................................................2-44
Commingling ..................................................................................................................................................2-45
Agenda...........................................................................................................................................................2-47
Put Away Rules..............................................................................................................................................2-48
Restrictions and Sort Criteria for Put Away Rules ..........................................................................................2-49
Setting Up Put Away Rules ............................................................................................................................2-50
Setting Up Put Away Rules: Define Rules......................................................................................................2-51
Setting Up Put Away Rules: Define Strategies...............................................................................................2-53

ii
Setting Up Put Away Rules: Assign Strategies to Business Objects..............................................................2-54
Put Away........................................................................................................................................................2-55
Put Away Load ...............................................................................................................................................2-57
Put Away Drop ...............................................................................................................................................2-58
Put Away Drop - Nested LPN.........................................................................................................................2-60
Item Based Put Away.....................................................................................................................................2-61
Cross Docking Put Away................................................................................................................................2-63

Cross Docking to Outbound Staging Flow .....................................................................................................2-64
Cross Docking to WIP Staging Flow ..............................................................................................................2-65
Cross Docking to WIP Issue Flow ..................................................................................................................2-66
Agenda...........................................................................................................................................................2-67
Advanced Task Framework (ATF) .................................................................................................................2-68
ATF Capabilities.............................................................................................................................................2-69
ATF Concepts ................................................................................................................................................2-70
ATF Example .................................................................................................................................................2-77
ble
fe
ATF Setup......................................................................................................................................................2-78 r a
an
ATF – Zones : Setup ......................................................................................................................................2-79 s
- t r
ATF Operation Plan Setup .............................................................................................................................2-80
n
no
Agenda...........................................................................................................................................................2-81
a
h a s
Implementation Considerations......................................................................................................................2-82
) deฺ
Agenda...........................................................................................................................................................2-88
m
ฺ c o Gui
Summary........................................................................................................................................................2-89
cl ente
a
R12.x Oracle Warehouse Management Warehousing Features...................................................................3-1
r
o t ud
n @ S
i d so this
Objectives ......................................................................................................................................................3-4
d a v
Agenda...........................................................................................................................................................3-5
s e
ฺ
i Partner u
Compliance Labeling......................................................................................................................................3-7
toLabel Printing Responsibilities ......................................................3-9
Warehouse Management
( t onversus e
o
Label Printing Components
s ns
n ce............................................................................................................................3-10
Label Formats
v li
id ................................................................................................................................................3-11
a
DLabel Types ...................................................................................................................................................3-12
o n i Setup..............................................................................................................................................................3-14
T Registering Label Formats .............................................................................................................................3-15
Assigning Label Types to Business Flows .....................................................................................................3-16
Label Format Assignment Rules ....................................................................................................................3-17
Defining and Assigning Printers .....................................................................................................................3-18
Printing Modes ...............................................................................................................................................3-19
Asynchronous Mode ......................................................................................................................................3-20
Synchronous Mode - Generic ........................................................................................................................3-21
Synchronous Mode TCP / IP..........................................................................................................................3-22
Viewing Label Requests.................................................................................................................................3-23
Label Printing Implementation Considerations ...............................................................................................3-24
Agenda...........................................................................................................................................................3-26
Task Management .........................................................................................................................................3-27
Task Types ....................................................................................................................................................3-28
Setting Up Task Type Rules ..........................................................................................................................3-30
Task Dispatch Engine ....................................................................................................................................3-31
Resource Skills ..............................................................................................................................................3-32
Available Equipment and Resources .............................................................................................................3-33

iii
WMS Control Board .......................................................................................................................................3-34
Task Status ....................................................................................................................................................3-35
Exception Management .................................................................................................................................3-38
Task Setup Steps...........................................................................................................................................3-39
Task Type Implementation Considerations ....................................................................................................3-40
Agenda...........................................................................................................................................................3-42
Distributed Warehouse Management.............................................................................................................3-43
Distributed Warehouse Management Architecture.........................................................................................3-44
How the Integration Works .............................................................................................................................3-46
Agenda...........................................................................................................................................................3-48
Mobile Personalization ...................................................................................................................................3-49
Mobile Personalization Setup.........................................................................................................................3-50
Agenda...........................................................................................................................................................3-51
Labor Management ........................................................................................................................................3-52
ble
Resource Planning.........................................................................................................................................3-53
fe r a
an s
Labor Productivity ..........................................................................................................................................3-54
- t r
Definitions ......................................................................................................................................................3-55
n
no
Setting Up Labor Management ......................................................................................................................3-57
a
h a s
Labor Management Process ..........................................................................................................................3-58
) deฺ
Agenda...........................................................................................................................................................3-60
m
ฺ c o Gui
Summary........................................................................................................................................................3-61
cl ente
a
R12.x Oracle Warehouse Management Outbound Logistics........................................................................4-1
r
o t ud
n @ S
i d so this
Objectives ......................................................................................................................................................4-4
d a v
Agenda...........................................................................................................................................................4-6
s e
ฺ u
oni se to
Overview of Outbound Logistics.....................................................................................................................4-7
t
Overview of Picking........................................................................................................................................4-9
(
d s onPicking...................................................................................................................................4-11
Sales Order Picking
l i c en
.......................................................................................................................................4-10
a i
Replenishment
vPicking....................................................................................................................................................4-12
DWIP
T oni Pick Release Process ....................................................................................................................................4-13

Components of Pick Release .........................................................................................................................4-14
Over Allocation For Pick Release...................................................................................................................4-15
Overview of Picking Rules .............................................................................................................................4-16
Release Sequence Rules...............................................................................................................................4-17
Pick Slip Grouping Rules ...............................................................................................................................4-19
Release Rules................................................................................................................................................4-20
Cross Docking................................................................................................................................................4-21
Direct Ship .....................................................................................................................................................4-25
Agenda...........................................................................................................................................................4-26
Pick Methodologies ........................................................................................................................................4-27
Picking Rules Order Allocation.......................................................................................................................4-29
Rules Engine Framework ...............................................................................................................................4-30
Components of the Rules Engine...................................................................................................................4-32
Put Away Rules..............................................................................................................................................4-33
Picking Rules .................................................................................................................................................4-34
Task Type Assignment Rules ........................................................................................................................4-35
Rules Definition – Directed Picking ................................................................................................................4-36

iv
Allocation Modes............................................................................................................................................4-37
Allocation Modes: No LPN Allocation.............................................................................................................4-40
Allocation Modes: No LPN Allocation, Prioritize Pick UOM............................................................................4-41
Allocation Modes: Allocate LPN and Loose ...................................................................................................4-42
Allocation Modes: Allocate Entire LPN Only ..................................................................................................4-43
Agenda...........................................................................................................................................................4-45
Automated Task Dispatch, Allocation and Assignment ..................................................................................4-46

Agenda...........................................................................................................................................................4-50
Advance Pick Load ........................................................................................................................................4-51
Advanced Pick Load Setup ............................................................................................................................4-52
Advanced Pick Load Page Setup...................................................................................................................4-53
Advanced Pick Load Use ...............................................................................................................................4-56
Advanced Pick Load – Task Setup ................................................................................................................4-57
Advanced Pick Load Menu Setup ..................................................................................................................4-58
ble
Advanced Pick Load Exceptions ....................................................................................................................4-59
fe r a
Advanced Pick Load - Execution....................................................................................................................4-60
an s
- t r
Agenda...........................................................................................................................................................4-61
n
o
s an
Replenishments in a Warehouse ...................................................................................................................4-62
Replenishment Challenges ............................................................................................................................4-63
) ha eฺ
Strict Pick UOM Allocation .............................................................................................................................4-64
ฺ c om Guid
Pull Replenishment ........................................................................................................................................4-66
a c le nt
Push Replenishment ......................................................................................................................................4-68
or tude
Agenda...........................................................................................................................................................4-70
@
s o n is S
Catch Weight Description...............................................................................................................................4-71
a v id se th
Catch Weight Benefits....................................................................................................................................4-72
Catch Weight Item Setup ...............................................................................................................................4-73
n iฺd to u
Catch Weight Setup .......................................................................................................................................4-74
o
(t nse
Catch Weight Use ..........................................................................................................................................4-75
n
d s o l i ce
Agenda...........................................................................................................................................................4-76
a v i
Consolidation .................................................................................................................................................4-77
D
oni
Consolidation Setup .......................................................................................................................................4-79
T Consolidation Inquiry......................................................................................................................................4-80
Cartonization ..................................................................................................................................................4-82
Packing ..........................................................................................................................................................4-85
Packing Workbench Flow...............................................................................................................................4-86
Eligible Material..............................................................................................................................................4-87
Mobile Packing...............................................................................................................................................4-88
Packing Workbench and Outbound Logistics.................................................................................................4-89
Packing Workbench and Inbound Logistics ...................................................................................................4-90
Packing Initialization.......................................................................................................................................4-91
LPN Pack .......................................................................................................................................................4-92
LPN Unpack ...................................................................................................................................................4-93
LPN Split ........................................................................................................................................................4-94
LPN Reconfiguration ......................................................................................................................................4-95
LPN close.......................................................................................................................................................4-96
DFI and the Packing Workbench....................................................................................................................4-97
Agenda...........................................................................................................................................................4-98
Overview of Shipping .....................................................................................................................................4-99

v
Staging Lanes ................................................................................................................................................4-100
Setting Up Staging Lanes ..............................................................................................................................4-101
Dock Doors ....................................................................................................................................................4-102
Setting Up Dock Doors...................................................................................................................................4-103
Staging Lane to Dock Door Relationship .......................................................................................................4-104
Setting Up Staging Lane to Dock Door Relationships ....................................................................................4-105
Staging and Consolidation .............................................................................................................................4-106

Loading and Shipping ....................................................................................................................................4-107
Trips and Trip Stops.......................................................................................................................................4-108
Ship Confirmation...........................................................................................................................................4-109
Direct Shipping...............................................................................................................................................4-110
Dock Door Ship ..............................................................................................................................................4-111
LPN Ship........................................................................................................................................................4-112
Quick Ship......................................................................................................................................................4-113
Shipment Planning .........................................................................................................................................4-114
ble
Dock Door Appointments ...............................................................................................................................4-115
fe r a
an s
Agenda...........................................................................................................................................................4-116
- t r
n
no
Agenda...........................................................................................................................................................4-119
a
h a s
Summary........................................................................................................................................................4-120
m ) deฺ
R12.x Oracle Warehouse Management Wave Planning................................................................................5-1
ฺ c o Gui
cl ente
a
Objectives ......................................................................................................................................................5-4
r
o t ud
Agenda...........................................................................................................................................................5-5
n @ S
i d so this
Overview of Wave Planning ...........................................................................................................................5-6
d a v
The Wave Planning Process ..........................................................................................................................5-7
s e
ฺ u
oni se to
Agenda...........................................................................................................................................................5-8
Release Criterian
( t
Creating a Wave ............................................................................................................................................5-9
d s l i c en
o .............................................................................................................................................5-11
a vi
Wave Templates ............................................................................................................................................5-13
DAgenda...........................................................................................................................................................5-14
T oni Planning a Wave ............................................................................................................................................5-15

Labor Planning ...............................................................................................................................................5-17
Setting Up Labor Planning .............................................................................................................................5-19
Wave Planning Results ..................................................................................................................................5-21
Agenda...........................................................................................................................................................5-22
Releasing a Wave ..........................................................................................................................................5-23
Agenda...........................................................................................................................................................5-25
Monitoring Waves ..........................................................................................................................................5-26
Monitoring Warehouse Activity.......................................................................................................................5-28
Agenda...........................................................................................................................................................5-30
Agenda...........................................................................................................................................................5-33
Summary........................................................................................................................................................5-34

vi
Preface
Profile
Before You Begin This Course

• Thorough knowledge of Oracle Inventory.
• Working experience with Warehouse Management principles.
How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations
and written practice sessions reinforce the concepts and skills introduced.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

vii
Related Publications
Oracle Publications
Title Part Number
Oracle Warehouse Management User’s Guide Release 12.2 E23271-01
Oracle Warehouse Management Implementation Guide Release 12.2 E23270-01
Additional Publications
• System release bulletins
• Installation and user’s guides
• Read-me files
• International Oracle User’s Group (IOUG) articles
ble
• Oracle Magazine
fe r a
• Typographic Conventions ans
• Typographic Conventions for Words within Regular Text n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

viii
Typographic Conventions
The following two lists explain Oracle University typographical conventions for words that
appear within regular text or within code samples.
1. Typographic Conventions for words within regular text

Convention Object or Term Example

Courier new, User input; Use the SELECT command to view
commands; information stored in the LAST_NAME
column, table, and column of the EMPLOYEES table.
schema names;
functions; Enter 300.
PL/SQL objects;
paths Log in as scott ble
Initial cap Triggers; Assign a When-Validate-Item trigger to fe r a
user interface object the ORD block. ans
names, such as n - t r
button names Click the Cancel button.
a no
Italic Titles of
h a s
For more information on the subject see
courses and
m ) deฺ
Oracle SQL Reference Manual
manuals;
ฺ c o Gui
emphasized Do not save changes
c l eto the t
database.
n
words or phrases; r a e
placeholders or Enter @
n
o
hostname, S tud hostname is the
where
variables
d o on which
shost t h isthe password is to be changed
Quotation i
v Thisssubject
Lesson or module
a e is covered in Lesson 3, “Working with
ฺ d u
marks
( oni se to
title referenced
t
within a course
Objects.”
d s on licen
a vi
D
T oni

ix
2. Typographic Conventions for words within code samples
Convention Object or term Example

Uppercase Commands, SELECT employee_id
functions FROM employees
Lowercase Syntax variables
CREATE ROLE role

italic
Initail cap Forms triggers Form module: ORD
Trigger level: S_ITEM.QUANTITY
item
Trigger name: When-Validate-Item
. . .
Lowercase Column names, . . .
table names
Filenames,
OG_ACTIVATE_LAYER
ble
PL/SQL objects
(OG_GET_LAYER ('prod_pie_layer'))
fe r a
. . .
ans
SELECT last_name
FROM employees; n - t r
Bold Text that must be CREATE USER scott
a no
entered by a user IDENTIFIED BY tiger;
h a s
m ) deฺ
3. Typographic Conventions for Oracle Application
ฺ c o Gui Paths
Navigation
This course uses simplified navigation paths, suchc as e
l the following
n t example, to direct you
r a e
through Oracle Applications.
n @ o
S tud
(N) Invoice > Entry > Invoice BatchesoSummaryis (M) Query > Find (B) Approve
i d s t h
a
This simplified path translates
d vto the following:
s e
ฺ u
( t oni swindow,
1. (N) From the Navigator
e to select Invoice then Entry then Invoice Batches
Summary.n
d s o licen
2. (M)
a viFrom the menu, select Query then Find.
D
T oni3. (B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab
4. Typographic Conventions for Oracle Application Help System Paths

This course uses a “navigation path” convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example—

x
(Help) General Ledger > Journals > Enter Journals
—represents the following sequence of actions:
1. In the navigation frame of the help system window, expand the General Ledger entry.
2. Under the General Ledger entry, expand Journals.
3. Under Journals, select Enter Journals.
4. Review the Enter Journals topic that appears in the document frame of the help system
window.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

xi
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

xii
ble
fe r a
ans
n - t r
a no
a s
) deฺ
Management c m i
o GuOverview
e ฺ
r a cl 1 ent
n @ oChapter
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
D
T oni
Copyright © Oracle, 2011. All rights reserved.
R12.x Oracle Warehouse Management Overview

Chapter 1 - Page 1
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 2
R12.x Oracle Warehouse Management
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 3
Objectives
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 4
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 5
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 6
What Is a Warehouse?
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 7
Processes of a Warehouse
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Processes d s oofna Warehouse
l i c en
a i
vfollowing
The
D is an abbreviated list of the functions operators can perform in Oracle
o n i Warehouse Management (Warehouse Management):
T • Receiving: Receive materials and finished goods.
• Put away: Put away materials and finished goods you receive.
• Storage: Store items within the warehouse.
• Picking: Pick orders for manufacturing and shipping.
• Packing: Pack orders for shipping.
• Shipping: Ship orders to customers.
• Value added services: Manufacturing, assembly, kitting, and labeling.

Chapter 1 - Page 8
Additional Product Requirements
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oProduct
d
Additional
v i li Requirements
D a
To use Warehouse Management, you must implement Oracle Inventory (Inventory), Oracle
n i
o Purchasing (Purchasing), Oracle Bills of Material (Bills of Material), and Oracle Order
T Management (Order Management). You use Inventory to set up items, organizations,
subinventories and locators. You use Bills of Material to define people, resources, and
calendars. Order Management and Purchasing provide the basic shipping and receiving
capabilities on which Warehouse Management builds.
• For more information on Inventory setup see, Overview of Setting Up, Oracle Inventory
User’s Guide.
• For more information on Bills of Material setup see, Overview of Setting Up, Oracle Bills
of Material User’s Guide.
• For more information on receiving setup see, Overview of Setting Up, Oracle Purchasing
User’s Guide.
• For more information on shipping setup see, Oracle Shipping Execution Setup, Oracle
Order Management Implementation Manual.

Chapter 1 - Page 9
Warehouse Management Application Hierarchy
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d son licManagement
Oracle iWarehouse
en Application Hierarchy
a v
n i D
The above graphic represents the relationship between existing Oracle manufacturing
T o applications, Warehouse Management, and Oracle Mobile Supply Chain Applications
(MSCA).
MSCA provides a mobile user interface for existing inventory, receiving, manufacturing,
quality, and shipping transactions. The mobile environment provides operators with an
alternate set of pages to perform the transactions supported in these environments. Operators
can use hand-held frequency devices to perform transactions in both Warehouse
Management and MSCA. Warehouse Management extends the capabilities available in
MSCA to encompass the demands placed on a dynamic high-volume warehouse.
Oracle Warehouse Management Features

Warehouse Management provides the following features in addition to the features available
in MSCA:
• Task management
• Material tracking with License Plate Numbers (LPNs)
• A configurable rules engine that enables you to create custom picking rules, put away
rules, and compliance labeling rules.

Chapter 1 - Page 10
• Advanced inventory and materials management including material status, lot, and serial
support.
Warehouse Management also is heavily integrated with, and extends some of the current
functionality in Oracle manufacturing applications.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 11
Inventory, Warehouse Management and MSCA
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Inventory, s on licenManagement and MSCA
Warehouse
a viyou implement Warehouse Management, you must implement Inventory as well. In
DWhen
T oni addition, you must consider additional attributes such as LPN management when you
implement Warehouse Management.
MSCA does not have the same capabilities as Warehouse Management. MSCA provides a
streamlined radio frequency (RF) based user interface for core inventory, shipping, quality,
WIP, and receiving capabilities. Warehouse Management extends these capabilities beyond
the base functionality Inventory and MSCA provide.

Chapter 1 - Page 12
Radio Frequency Devices
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on lDevices
Radio Frequency i c en
a vi Managements supports two types of user interfaces, telenet based, and graphical.
D
Warehouse
T oni You can use either a character mode interface, or a graphical user interface (GUI) that mimics
the desktop application. The type of interface you choose depends on the type of data entry in
your implementation, and the capabilities of the mobile device. If you plan to use the GUI
interface, you must install a J2ME compatible Java virtual machine and the GUI client
application on the mobile device. If you plan to use the telnet based user interface in your
implementation, the device must support telnet over TCP/IP.

Chapter 1 - Page 13
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 14
Overview of Inbound Logistics
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n ceLogistics
oInbound n
Overview
d of l i
vi Management inbound logistics refers to receiving, inspection, and put away
a
Warehouse
D
T oni processes within the warehouse. It includes the following features:
• Receiving: Warehouse Management uses the three standard purchasing receipt modes:
standard receipt, direct receipt, and inspection receipt. It also handles return material
authorizations (RMAs), internal requisitions, and in-transit shipments.
• Quality Inspection: Warehouse Management provides RF user interfaces for mobile
Quality, or mobile receiving inspection pages for required inspections.
• Label Printing: Warehouse Management can print product or packaging labels on
demand according to any number of criteria you define.
• Directed Put Away and Storage Optimization: Warehouse Management matches the
material handling constraints and item or inventory attributes to provide operators with
an available storage location for put away.
• Cross Docking: Warehouse Management checks backordered sales orders and
redirects inbound items at receipt. If necessary, it routes the material directly from the
receiving dock to a staging lane or shipping dock without placing it in a put away
location.

Chapter 1 - Page 15
• Advanced Task Framework: You can use Warehouse Management to create operation
plans that enable operators to perform multi-step directed put away throughout the
warehouse.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 16
Reverse Logistics
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Reverse d s on licen
Logistics
a i
vReturn
n i D• Material Authorization (RMA): Warehouse Management enables operators to
T o record the inspection and receipt information of customer authorized returned items.
Operators can verify receipt items, date, and quantity against the RMA.
• Return to Vendor (RTV): Warehouse Management allows operators to return material
back to the appropriate supplier from a previously received purchase order or purchase
agreement.
• Refurbishment and Recycling: Optionally, if you install Oracle Service and Oracle Depot
Repair, then you can use Warehouse Management as part of the refurbishment or
recycling process.

Chapter 1 - Page 17
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 18
Overview of Outbound Logistics
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Pick Release
d s on licen
a
The
i release process selects sales order lines to release for picking and shipping. You
vpick
D
T oni can perform manual pick release, or create a series of rules to automate the process. The
system uses the following rules to release orders: pick release rules, release sequence rules,
and pick slip grouping rules. Pick release rules determine how the system selects sales orders
for release. If trips are not scheduled for dock doors, then pick release rules also determine
the appropriate staging lane for sales orders. After the system determines which sales orders
to release, it uses release sequence rules to determine the order lines are released for picking
based on sales order number, outstanding invoice value, scheduled date, departure date, and
shipment priority.
Pick slip grouping rules establish how tasks are grouped on a pick slip. They work in
conjunction with the different pick methodologies. Pick methodologies refer to the different
ways operators perform picking tasks. For example, an operator may select to pick an order
by itself, or to pick multiple orders at the same time.
Once you establish the rules for your implementation, the system generates picking tasks and
dispatches them to qualified operators. After operators complete picks, the system suggests
the appropriate number and size of containers the order requires for shipping.

Chapter 1 - Page 19
Wave Planning
Wave Planning groups orders and helps plan the work in a warehouse. Wave Planning
enables better visibility and control during order fulfillment. Wave planning provides real-time
monitoring and exception reporting and flexibility during the order fulfillment process.
Consolidation
Warehouse Management enables operators to consolidate partially filled containers into fewer
and better-optimized containers.
Packing
Warehouse Management enables operators to pack containers with multiple levels of nesting,
and sends notifications if an order contains special packing instructions. Operators can
perform packing during picking or as an independent process.
Dock Appointments for Trips bl e

Managers can use Warehouse Management to schedule outbound carrier appointments, e r
fdock a
n s
door availability, and staging lane usage within the warehouse.
n - tra
Shipment Verification and Close
a no
a s
Once operators pick and load an order, the system automatically determines
h the items and
) ฺ
om Guide
quantities to deduct from inventory.
ฺ c
le nt
a c
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
av i
D
T oni

Chapter 1 - Page 20
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Pick Methodologies
a i
vmethodologies
n i DPick refer to the different ways in which you might select to perform picking
o tasks. For example, you might select to pick an order by itself, or to pick multiple orders at the
T same time. The type of picking methodology that a warehouse uses depends on the kinds of
operations that they run. For example, you may choose to use cluster picking in order to pick
multiple orders in one pass.
Warehouse Management Control Board

The WMS Control Board provides warehouse managers with a real-time snap shot of the
warehouse, and enables them to redistribute operators as needed. They can monitor the
progress of tasks as well as manually dispatch tasks to operators.
Cartonization
With container management features, Oracle Warehouse Management can automatically
suggest packing configurations for groups of items. You can base Cartonization on the
following packing requirements:
• Container weight capacity
• Volume
• Item and container dimensions

Chapter 1 - Page 21
• Item's packaging restrictions
Case Picking
Case picking enables businesses to streamline the pick release process by labeling cases
and pallets directly. Case picking enables you to assign case labels printed at order release to
pick operators who can perform case picks such as Pick to Belt or Pick to Pallet by scanning
multiple case labels. This enables warehouse workers to simply scan a case already packed
with items and move it directly onto a pallet or belt.
Tasks
Task planning is the release of work to the warehouse floor in order to optimally run the day-
to-day warehousing operations. Tasks are comprised of demand pick tasks for sales orders,
work orders, and replenishment. Tasks are also comprised of inbound receiving and put away
tasks, slotting inventory transfer tasks, inventory control related cycle counting tasks, and
inbound-outbound hybrid crossdocking tasks. Once multiple tasks are created from the
ble
various task creation sources, they are placed in one single pool and released appropriately to
fe r a
the warehouse floor for optimal operation of the warehouse. Optimization is performed by task
ans
interleaving and resource-workload balancing.
n - t r
Release Rules a no
h a
You set up release rules to specify the release criteria that you want
sthe system to consider
m ) criteria:
d e ฺ
during pick release. Release rules specify the following release
o Gu
ฺcorders i
l
• Order, either for all, backordered, or un-released
c e n t
r a e
n @ o and ship
• Shipping, including specifying the carrier
S t udfrom location
• Inventory, including specifyingothe warehouse
is and pick slip grouping rule
i d s t h
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
To ni D

Chapter 1 - Page 22
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 23
Value Added Services
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s
Value Added
d onServices
l i c en
a i
vKitting
•
D and kit and De-kitting: Supports kit to stock (supported by work order-less completion)
o n i to order (supported by pick to order).
T • Mixed-Mode Manufacturing: Supports assemble to order (ATO), project-based or
engineer to order (ETO), discrete and repetitive or flow environments concurrently.
• Manufacturing Component Picking: Supports picking for work in process (WIP) through
the mobile user interface.
• Manufacturing Assembly Completion and Put Away: Supports WIP completion and put
away through the mobile user interface.
• Product Compliance Labeling: Supports product specific labels, based on rules you
define.
• Manufacturing Quality Inspections: The system automatically generates material
movement transactions to move an item into the quality control inspection area from
manufacturing, based on options you define during implementation.
• Integration with Project Manufacturing, Flow Manufacturing, and Shop Floor
Manufacturing: Warehouse Management integrates with Project Management, Flow
Manufacturing, and Shop Floor Management.
• Radio Frequency Identification (RFID): Warehouse Management supports RFID. RFID is
an automated data collection technology that enables equipment to read tags attached

Chapter 1 - Page 24
to the objects without contact or line of sight. RFID uses radio frequency (RF) waves to
transfer data between a reader and an item to identify, track, or locate the item.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 25
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 26
Storage and Facility Management
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cManagement
oFacility en
Storage d
i and l i
•avAdvanced Lot and Serial Control: Warehouse Management enables operators to split,
D merge, and rename lots. For more information see, Describing Lot Split, Merge, and
T oni Genealogy, Oracle Warehouse Management User’s Guide.
• LPN Management: Warehouse Management enables operators to track the contents of
any container in receiving, WIP, inventory, shipping, and in-transit.
• Material Status Control: Material status control enables operators to control the eligibility
of material for various transactions.
• Kanban Management: Warehouse Management supports both internal and external
supplier kanbans. Kanban is a means of supporting pull–based replenishment in
manufacturing systems. For more information on kanban management see: Overview of
Kanban Management, Oracle Inventory User’s Guide.
• Inventory Features: Warehouse Management facilitates the movement of goods in to,
out of, and within the warehouse.
• Workflow Based Exception Management: You can configure real-time alerts and
workflow based notifications of supply chain events to improve the efficiency of business
operations. For example, when an operator picks less than the required amount for an
order, workflow sends a notification to the operator to count the locator.

Chapter 1 - Page 27
• Counting: operators can perform cycle counts and physical inventory counts. For more
information see Overview of Cycle Counting, and Overview of Physical Inventory, Oracle
Inventory User’s Guide.
Replenishment
• Warehouse Management enables managers to manage inventory levels using any
combination of planning and replenishment features, including: min-max planning,

reorder point planning, or kanban replenishment. You can use Inventory and MRP
replenishment planning, dynamic replenishment, and replenishment direct from
receiving.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 28
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 29
Oracle Mobile Applications Architecture
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on liceArchitecture
Mobile Applications
d
n
a vi applications enables operators to input real-time transactions and receive warehouse
Mobile
D
T oni tasks the system assigns. Warehouse Management and MSCA use the same applications
architecture.

Chapter 1 - Page 30
License Plate Numbers (LPNs)
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oLicense
d
Explaining
v i li Plate Numbers (LPNs)
D a
An LPN is any object that exists in a location and holds items. You can use Warehouse
n i
o Management to track, transact, and nest LPNs.
T
Using LPNs
You can use LPNs in the following ways:
• Store information about an LPN such as item, revision, lot, serial, organization,
subinventory, or locator
• Track contents of any container in receiving, inventory, or in-transit
• Receive, store, and pick material by LPN
• View on hand balances by LPN
• Move multiple items in a transaction by LPN
• Transfer LPN contents
• Pack, unpack, consolidate, split, and update LPNs
• Print labels and reports for referencing container contents
• Track nested LPNs
• Reuse empty LPNs

Chapter 1 - Page 31
• Receive and send LPN information on an ASN
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 32
Nesting LPNs
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
son Plate
NestingidLicense l i cenNumbers
D avcan nest LPNs within other LPNs. In the above example, item A is packed in LPN 2, and
You
T oni LPN1, LPN2, and LPN3 are nested within LPN4. When you transact LPN4, all of the LPNs
nested within it are transacted.

Chapter 1 - Page 33
Generating LPNs
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oLicense
d
Generating
v i li Plate Numbers
D a
You can generate a License Plate Number (LPN) to match industry standards, such as SSCC-
n i
o 18, that includes the required check digit. You can also configure the numbering scheme to
T match an existing internal method.

Chapter 1 - Page 34
LPN Context
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
LPN Context
on licen
a vi Management defines a context for each LPN to denote the current state. You can
D
Warehouse
T oni use these contexts to define specialized picking and put away rules. You can also query by
context in the material workbench.
Resides in Inventory
An LPN with this context indicates material associated with this LPN is costed and accounted
for in inventory. an operator cannot this context when receiving material against a standard or
inspection routed receipt, but can use it for a direct delivery routed receipt. operators can
perform outbound transactions on LPNs with this context.
Resides in WIP
An LPN with this context indicates material associated with this LPN is currently part of a WIP
operation. The material does not reside in inventory, and is not costed.
Resides in Receiving
An LPN with this context indicates material associated with this LPN was received using a
standard routing or inspection routing receipt, but still resides at the receiving dock. The
material does not reside in inventory and is not costed.

Chapter 1 - Page 35
Resides in In-transit
An LPN with this context indicates material is moving from one location to another. For
example, when an LPN moves from one organization to another. LPNs in this context are in
an intermediary state, but are accounted for in the system. This context is used only for inter-
org transit or internal sales orders where an indirect shipping network is defined between the
organizations.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 36
LPN Context
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
LPN Contexts o l i ce
av i
D
T oniIssued out of Stores
LPNs with this context do not reside in the warehouse. However, the system retains the LPN
transaction history. LPNs shipped out of inventory receive this context and cannot be received
again.
Pre-generated
Pre-generated LPNs exist in the system, but, are not associated with any physical material.
Packing
The system uses this context internally as an intermediary during picking, put away or
packing. Do not use it anywhere, including the setup of picking or put away rules.
Picked
Picked LPNs receive this context. They are in-transit within the warehouse.

Chapter 1 - Page 37
LPN Context
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
LPN Contexts o l i ce
av i
D
T oniDefined but not Used
This context refers to a defined LPN that does not contain material. An example is a reusable
tote an operator can use to pick orders.
Resides at Vendor Site

When a vendor sends an Advanced Shipment Notice (ASN) ASN, Warehouse Management
generates an LPN and associates it with the material information on the ASN. Warehouse
Management does not recognize material associated with LPNs of this context as on hand or
costed.
Pre-Pack for WIP

LPNs that reside in WIP, and are associated with material pre-packed in WIP, receive this
context. This context is used after Warehouse Management associates the LPN with the
material, but the material is not physically packed in the LPN.

Chapter 1 - Page 38
Loaded for Shipment
This context refers to material loaded for shipment onto a carrier that is ready to leave the
warehouse. Once the carrier leaves the dock, the LPN context changes to resides in in-transit,
or issued out of stores.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 39
LPN Material Status
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Definingd s on lStatus
Material i c en Control
a vi status control provides more granular transaction control than item status control. It
D
Material
T oni controls the types of transactions you can perform and restricts the movement and usage of
portions of on-hand
Inventory. You can use material status controls to control picking or shipping an internal order,
sales order, or issue material for a work order. You can also specify whether material needs to
be quarantined until you inspect it. In addition, you can determine whether products with a
particular status can be reserved, included in available to promise calculations, or netted in
production planning. You can set material status at Subinventory, Locator, Lot, Serial, or On-
hand levels. To enable LPN material Status control, you must enable On-hand material status
control.
Transaction Control
You can use on-hand material status control to restrict material movement by on-hand
quantity and enables you to track the material status of LPN contents. The material status of
the LPN is the status of the on-hand balances packed into the LPN. When you perform LPN
transactions, the application evaluates whether you can perform the transaction type on the
contents of the LPN. The LPN material status also controls whether the material packed in the
LPN is nettable or reservable. When you update the LPN material status, it changes the
material status for all contents of the LPN.

Chapter 1 - Page 40
Assigning and Updating Material Status Control
• Assign material status control to lot and serial controlled items upon entrance to the
warehouse.
• Determine the allowed transactions for subinventories and locators during set up.
• Update material status control as necessary.
• Disallowed material status transactions are cumulative. For example, if you have a lot
controlled item with the lot status HOLD, that resides in a locator with the status
INACTIVE, then transaction types disallowed by HOLD and INACTIVE statuses are not
allowed for the lot.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 41
Subinventory and Locator Material Status
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Subinventory
onandliLocator
c en Material Status
a i
vcan
n i D
You set a status to allow or disallow various inventory transactions. For example, if for
T o your implementation you set the status to Immature or Pending, based on QA results, the
system allows operators to perform organization transfers and subinventory transfers from the
subinventory or locator, but does not allow them to pick or ship sales orders from the
subinventory or locator.

Chapter 1 - Page 42
Lot and Serial Attributes
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Lot andid son Attributes
Serial l i cen
v
Lotaand serial attributes track the characteristics of items based on lot or serial numbers.
D
T oni Descriptive flexfields enable you to configure lot and serial attribute flexfields to capture
additional information. You can define required or optional attributes, or track information at
the item or item category level. Sample lot and serial attribute values include grade, cycles
since new, and best buy date.
To set up attributes and attribute value sets, you associate them with a flexfield segment. The
difference between lot and serial attributes and common flexfields is, once you define a set of
attributes ( a context) you can assign the set to an item or category. When an operator creates
a lot or serial, the system prompt the operator for the category attributes. For example, you
can set up a value set for the Grade segment. The Grade value set includes three grades:
Excellent, Average, and Poor.
Using Lot and Serial Attributes

You can build pick and put away rules based on lot and serial attributes.

Chapter 1 - Page 43
Cost Groups
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Cost Groups s on licen
a i
vgroups
n i D
Cost associate account information with on hand inventory. Cost groups provide a way
T o to track the inventory accounting attributes of material in the warehouse, and enable
managers to effectively manage inventory with different accounting attributes.
Material receives a cost group upon receipt into inventory. Material enters the warehouse by:
• Receiving (from external source), including:
- Standard receiving
- Direct receiving
- Receiving with inspection
- Miscellaneous receipt
- In-transit receipt
- Direct org transfer
• WIP transactions (from internal manufacturing), including:
- WIP assembly completion
- WIP component return

Chapter 1 - Page 44
Cost Group Information
The rules engine can use any number of different attributes to assign cost groups including:
• Supplier
• Descriptive flexfield information
• Customer
• Item
• Location
• Item category
• Item status
• Item disposition (used, new, and refurbished)
Cost Group Restrictions

After the rules engine assigns the cost group, the transaction manager checks for conflicts ble
between the assigned cost group and cost groups of existing material in the location. fe r a
ans
Commingling n - t r
o
an
Multiple cost groups of a single item can reside in the same locator or LPN if material within
s
a transaction in a commingled LPN or locator. ) ha eฺ
each cost group that resides in the LPN or locator is uniquely identifiable. You cannot perform
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 45
Cost Group Assignment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oAssignments
d
Cost Group
v i li
D a
Oracle Warehouse Management uses the cost group rules engine to assign cost groups.
n i
o Inventory derives cost groups based on the primary cost method of the organization and the
T destination location. Within Inventory, if the costing method is standard-costing, then the
system assigns the cost group associated with subinventory to the material. For the other
costing methods, Inventory uses the cost group associated with the organization.
Changing Cost Group Assignments

Oracle Warehouse Management retains cost group information for material within an
organization. If an operator performs a subinventory transfer, the cost group does not change.
To change a cost group, the operator performs a cost group update transaction.
In Inventory, the cost group associated with the material changes based on location. If an
operator performs a subinventory transfer, the cost group changes to the cost group of the
destination subinventory.
Costing and Valuation Reporting

Oracle Warehouse Management bases costing and valuation reports on cost group, and
Inventory bases costing and valuation reports on subinventory.

Chapter 1 - Page 46
Task Assignment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oTasks
d
Explaining
v i li
D a
Warehouse Management uses tasks to control the flow of material through the warehouse. It
n i
o dispatches tasks to operators based on skill sets. You can group operators into common skill
T set groups and designate them as resources.
You must define each skill and associate it with an employee before the system can dispatch
tasks to qualified operators.
Warehouse Management uses the BOM Resource window to capture the skill sets of the
employees required to perform specific tasks. For each task that requires a unique set of
skills, you must define a new resource. However, if operators that have the same set of skills
can perform a variety of tasks, then you do not need to define individual resource types.
Describing the Task Type Assignment Process

The task type assignment process enables the system to assign task types you define based
on any number of criteria including:
• Location: For example, high bay picks require a forklift.
• Material type: For example, the task type assignment engine dispatches a refrigerated
material pick differently than a hazardous material pick.

Chapter 1 - Page 47
Task Splitting and Merging
The system splits tasks if the equipment required cannot hold the number of containers the
task requires, or if the packing containers the task requires cannot fit the entire task quantity.
The system merges tasks if bulk picking is selected.
Task Dispatch
The task dispatch engine considers the current location of the operator and dispatches the
next task based on proximity if the operator meets the task criteria.
Exception Messages
The task dispatch engine has a set of predefined exception messages and transaction
reasons, which handle all generic exceptions during task dispatch, and trigger appropriate
actions and workflows based on these exceptions.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 48
Rules and the Rules Engine
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Rules andd s onRules
the l i c n
eEngine
a i
vcan
n i D
You use the rules engine to create rules to effectively dispatch tasks and manage
T o inventory. You can use it to streamline picking and put away of material, assign newly
received material to a cost group, ensure customer compliant labeling, assign tasks to a
resource with the appropriate training and equipment, and select the correct operation plan for
tasks. You can create rules based on nearly any attribute in the database, including flexfields
you define.
Restriction
All rules have restrictions. You compare two different attributes to define restrictions. For
instance, a put away restriction that puts material away to the subinventory BULK, equates the
destination subinventory with the text BULK.
Strategies
A strategy is a sequence of rules the rules engine runs to try to allocate material, allocate
space, or fulfill a request. Picking, put away and cost group assignment rules use strategies.
You construct strategies in the Strategies window from one or more rules. You can reuse rules
for multiple strategies. If a strategy cannot find enough material to fulfill a pick or find enough
space for a put away, then the material is backordered or the put away fails. This may be the
desired outcome, or you may wish to put less restrictive rules at the end of the strategy.

Chapter 1 - Page 49
Dual Unit of Measure Allocation
If the item is under dual unit of measure (UOM) control, then the system uses the primary unit
of measure for allocation. For example, if item FG1 has a primary UOM of EA and a
secondary UOM of LB, and a sales order exists that requires 2 KG of the item, then the
allocation engine converts he quantity in KG to EA and allocates the required quantity in EAs.
The system allocates the secondary quantity based on the conversion between EAs and LBs.
If lot specific UOM conversions exist for the item, then the actual allocated quantity in the
secondary UOM could differ from the standard conversion.
Other Rules Components

Rules and strategies have other components as well, such as quantity functions, allocation
modes, consistency restrictions, return values, and strategy assignments, which are covered
in later modules.
Note: Warehouse Management assigns some rules based on strategies, and other rules
based on weight. It runs weighted rules in descending order until it finds a match. ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 50
Rules Engine Uses
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Rules Engine s onUses l i c en
a i
vcan
n i D
You use the rules engine to create six different types of rules, including picking, put away,
T o task type assignment, cost group assignment, label format assignment, and operation plan
assignment.
Material Allocations for Picking

Directed picking determines how material is allocated for an order, and directs operators to
pick material from specific locators. Warehouse Management allocates stock to meet
customer requirements such as stock condition, stock quality, lot expiration date, or country of
origin.
You can use a rule to allocate material based on FIFO (first in first out) or FEFO (first expired,
first out). You can also use picking rules to perform a pick that depletes a location in order to
free up additional warehouse space, or to perform a pick by cost group.
Directed Put Away Rules

Directed put away directs operators to put material receipts into the most appropriate locators.
Some common processes the rules model include:
• Minimize item fragmentation
• Control lot commingling in a locator

Chapter 1 - Page 51
• Direct hazardous materials to a corresponding hazardous storage location
• Store seasonal items in a subinventory dependent on time of year
• Put away material based on inspection results, purchase order type, or item category.
You can also put away material to locations the rules engine suggests for any items anywhere
within the warehouse.
Note: Picking and put away rules also have a quantity function, which specifies how to
determine the material available for picking, or the space available for put away.
Task Type Assignment Rules

Task type assignment captures skill sets and equipment required for a warehouse task.
Operators can sign onto a mobile RF device, and optionally specify the available equipment.
Warehouse Management assigns tasks to operators based on skill set, equipment
requirements and capacity, or subinventory. For instance, the system assigns hazardous
tasks to operators with the appropriate hazmat training, and can limit material put away to the
ble
top racks to operators signed onto high-reach forklifts.
fe r a
ans
Compliance Labeling Rules
n - t r
a no
You can use the rules engine to select the appropriate label format, type, and printer for
material, based on customer, carrier, item category, or transportation method. You can then
h a s
generate a label with the required information and barcode symbols for the material based on
m ) deฺ
ฺ c o Gui
the result. The system can print different labels for freight carrier or shipment type. The rules
e
engine can also generate labels for use inside the warehouse.
cl ent
r a
Cost Group Rules
n @ o
S tud
Cost groups capture the material s
d o thaccounts
valuation is necessary for tracking inventory value.
For instance, you can set up i
avdifferent e
saccounts for refurbished, new, components or finished
goods. When material iisฺdreceivedo u
into the warehouse, Warehouse Management determines
t o n t
the owning cost (group
o n e
and
n se
the material valuation accounts.
i
Operation
v dsPlan Selection
lic Rules
D a
You create operation plan selection rules to determine the operation plan for consolidation.
i
on For example, if you want certain item categories to go through a consolidation step, and item
T categories to be dropped directly to a staging lane, you can create an operation plan selection
rule that selects the operation plan based on the item category.

Chapter 1 - Page 52
Material Allocation Example
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Material d s on licExample
Allocation
en
a vruni a warehouse that sells strawberries. The strawberries are set up as a lot controlled
D
You
T oni and expiration date controlled item. They are also tracked by the lot attribute Grade. Excellent,
Good, and Average are the possible grades within the system. Supreme Berries is a
strawberry distributor that services grocery stores. They do not accept Average strawberries.
They request Excellent strawberries if they are available, but accept Good strawberries if
necessary. The system allocates graded lots on a FEFO basis. Cost Cutters makes
strawberry jam. They can use any grade of strawberry, but because they do not pay top dollar,
you prefer to ship them Average strawberries. However, if there are no Average strawberries
available, you ship higher grade strawberries. Lots are allocated on a FEFO basis. All other
customers have no preference on the grade of strawberries they receive, and they are
allocated lots on a FEFO basis.

Chapter 1 - Page 53
Allocation Decision Tree
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Allocationd s on licTree
Decision
en
a i
vdecision
n i D
This tree represents the business scenario from the previous slide. Drawing a
T o decision provides a baseline for the strategies and rules to define. Before you set up rules and
strategies, you must understand the types of rules to model. Though you can create new rules
and strategies without code changes, it is important to carefully think through your rules and
strategies during implementation. Additionally, well defined rules and strategies can be reused
in multiple strategy assignments.

Chapter 1 - Page 54
Rules Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Rules Setup s on licen
a i
vsetup
n i D
The for picking rules, put away rules, and cost group rules are similar. Setting up these
T o rules involves three steps covered in the following slides.

Chapter 1 - Page 55
Defining Rules: Restrictions
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Rule Restrictions
a i
vdefine
n i D
You rules for picking and put away tasks based on available items and locators. Picking
T o rules can place restrictions on lot attributes, source subinventory or locator, item category, or
any of hundreds of other item attributes. The rules engine does not allocate material that does
not meet the rule restrictions. If the available quantity is as indicated above, and the single
restriction “lot grade of Excellent” is imposed, then the rules engine does not consider good
and average strawberries.

Chapter 1 - Page 56
Defining Rules: Sort Criteria
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Sort Criteria
on licen
a i
vcriteria
n i D
Sort specify the most desirable material that meets the restrictions of the rule. The
T o example above sorts the excellent strawberries in order of expiration date; those that expire
first are shipped first.

Chapter 1 - Page 57
Defining Rules: Default
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Defining d s on Default
Rules: l i c en
a i
vcan
n i D
You also define a default rule that does not have any restrictions. You can assign a
T o default rule as part of a strategy, or as the organization default picking or put away rule, that
executes if the rules engine does not return an applicable strategy assignment. In this
example any available box of strawberries meets these restrictions.

Chapter 1 - Page 58
Strategies
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Strategies s on licen
a vi is a list of sequential rules the rules engine applies until a task is performed. Once
D
A strategy
T oni the rules engine determines the strategy it does not search for another strategy if the strategy
cannot fulfill the task. Therefore, unless you want the strategy to fail, the last rule of a strategy
should be a generic rule with no restrictions.
Assigning Strategies in the Rules Workbench

You can assign strategies to various objects or combinations of objects in the rules workbench
such as customer, vendor, transaction type, or item category. You can also specify dates for
strategies in the rules workbench.

Chapter 1 - Page 59
Task Type, Label Format, and Operation Plan Selection Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oLabel
d
Task Type,
v i i
lFormat and Operation Plane Selection Rules
D a
Task type rules, label format rules, and operation plan rules are not assigned to strategies, but
n i
o are automatically linked directly to an organization. Rule weights determine the search order,
T and you can set a rule weight for each rule. Rules with higher weights take precedence over
rules with lower weights.
For example, an organization has three types of tasks:
• HAZMAT task - Required whenever item has a HAZMAT code
• High reach - Required whenever an item is in a locator with rack number greater than 4
• Default task - All other tasks
Assuming the HAZMAT task takes priority (if a task is both a HAZMAT task and a high reach
task, then HAZMAT task should be returned), three rules are required:
1. High weight rule: If item has a HAZMAT code, return HAZMAT task
2. Mid weight rule: If item is in a rack greater than 4, return high reach task.
3. Low weight rule: Return default task.

Chapter 1 - Page 60
Consistency Requirements
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Consistencys onRequirements
l i c en
a vi Requirements are unique to picking rules. They ensure all allocations for a
D
Consistency
T oni particular line meet one or several common criteria. The most common consistency
requirement is customer acceptance of a single lot. This means a customer does not accept
an order if it contains more than one lot. You can set up a rule strategy for a customer that
prefers a single lot, but accepts mixed lots if necessary. You can also use consistency
requirements for other lot and allocation attributes.
Note: Rules that include consistency restrictions do not perform partial allocations. If the
allocation quantity cannot be found in its entirety, the rule does not allocate at all.

Chapter 1 - Page 61
Rules Simulation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Rules Simulation
a vi information on rules simulation see: Explaining the WMS Rules Engine Simulator,
D
For more
T oni Oracle Warehouse Management User’s Guide.

Chapter 1 - Page 62
RFID Technology
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
RFID ids
on licen
D avis a technology that tags physical items with a unique identifier a scanner can read. You
RFID
T oni can associate the identifier with a system representation of the object that contains all
associated item records. An RFID device can communicate directly with Warehouse
Management via the Oracle Sensor Edge server, which receives the physical details of an
RFID reader and filters out background noise. Warehouse Management can trigger a
response message to signal a light stack, buzzer, or message board via the Sensor Edge
server to provide the operator with physical confirmation of the transaction, which is performed
without a UI or mobile device.

Chapter 1 - Page 63
Labeling
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Receiptid son licen
Labeling
D avcan scan and print bar codes for material you receive in to the warehouse. This results in
You
T oni less receipt processing time, immediate recognition of available materials, and higher
receiving accuracy.
Customer Labeling
You can produce customer specific labels on demand for each shipment, to comply with
customer requirements for bar code labeling and advance shipment notifications (ASNs).
Manufacturing
You can use compliance labeling within manufacturing. There are four major points identified
where Warehouse Management prints labels for manufacturing:
• Prior to the start of the first operation: For example, a label that contains routing
information.
• During any operation: Based on a special outcome of an operation, the location of the
next assembly the system can dynamically determine the routing. The system can print
a label to route the material to the desired destination such as a scrap subinventory.

Chapter 1 - Page 64
• After quality inspection of an operation: The material may not pass inspection. The
system can print a label that sends the material to a prior operation, to scrap, or forward
to the next operation.
• At assembly completion: An organization may build finished goods or assemble to order
products. The system can print a stock label that contains the finished goods information
for flow manufacturing items, or a shipping label for assemble to order products that
contains the shipping instructions, address, and the sales order number.
Other Transactions
The above examples are just a few of the automatically triggered label flows. Cycle counting,
physical counting, purchase order receipts, packing or movement transactions can also trigger
labels. Operators can also create one off label requests as needed.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 65
Label Types
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
Label Typess o l i ce
i
avsystem supports the following label types:
D
The
T oni • Materials: This label provides information about the item, including lot information if
applicable.
• Serial: This label provides information specific to the serial number of the item.
• Location: This label provides information about specific warehouse locators.
• WIP Content: This label provides information about WIP components picked for a job. It
includes the component number, serial, lot, job number, assembly number, and start
date.

Chapter 1 - Page 66
Label Types
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Label Typess on licen
a i
vLPN:
n i D • This label provides information about the LPN. It does not contain content
T o information. You use this information to track the LPN through the warehouse.
• LPN Content: This label provides information about the LPN and content details.
• LPN Summary: This label provides information about the LPN and a summary of the
contents. If the LPN contains nested LPNs, the label also summarizes the content of
those LPNs.
• Shipping: This label provides information about the outbound shipment, such as the
address. It does not include shipment content information.
• Shipping Contents: This label provides information about the outbound shipment and the
contents of the shipment.

Chapter 1 - Page 67
Label Formats
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Label Formats
on licen
a vi format sets the data and layout of a label. You may require data to appear in a
D
A label
T oni different format for each customer. For example, Customer A and Customer B require
different shipping content information. Customer A requires you to specify UOM information,
and Customer B does not. During implementation, you can create a label format that contains
the UOM field for Customer A, and a label format for Customer B that does not. The rules
engine determines which format to print when an operator requests a shipping content label.

Chapter 1 - Page 68
Assigning Label Types to Business Flows
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 69
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 70
Summary
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 71
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 1 - Page 72
ble
fe r a
ans
n - t r
a no
a s
) deฺ
Management c m i
o GuInbound
e ฺ
r a cl ent
Logistics
n @ o
S t ud
i d so thChapter
is 2
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
D
T oni
R12.x Oracle Warehouse Management Inbound Logistics

Chapter 2 - Page 1
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 2
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 3
Objectives
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 4
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 5
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 6
Overview of Inbound Logistics
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n ceLogistics
oInbound n
Overview
d of l i
vi Management inbound logistics refers to receiving, inspection, and put away
a
Warehouse
D
T oni processes within a warehouse. It includes the following features:
• Receiving: Warehouse Management uses the three purchasing standard receipt modes;
standard receipt, direct receipt, and inspection. It also handles return material
authorizations (RMAs), internal requisitions, and in-transit shipments.
• Quality Inspection: Warehouse Management inspects incoming material based on
supplier, product, or organization.
• Label Printing: Warehouse Management can print product or packaging labels on
demand according to any number of criteria you define during implementation.
• Directed Put Away and Storage Optimization: Warehouse Management matches the
material handling constraints and item or inventory attributes to provide operators with
an available storage location for put away.
• Cross Docking: Warehouse Management checks backordered sales orders and
redirects inbound items at receipt. If necessary, it routes the material directly from the
receiving dock to a staging lane or shipping dock without placing it in a put away
location.

Chapter 2 - Page 7
• Advanced Task Framework: You can use Warehouse Management to create operation
plans that enable operators to perform multi-step directed put away throughout
warehouse.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 8
Receiving Flows or Routings
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Receivingd s on or
Flows l i c en
Routings
a i
vsame
n i D
The three types of receipt routings Purchasing uses are also available in Warehouse
T o Management.
• Standard Receipt – This routing is used when material needs to be received and put
away at a later time. The on hand balance is not incremented until the put away step is
complete.
• Inspection Receipt – This routing is used when an inspection of incoming material is
required. An operator may reject or accept the material during the inspection step. The
inspection determines where the operator puts away the material. The on hand balance
is not incremented until the put away step is completed. For more information see,
Explaining the Inspection Process, Oracle Warehouse Management User’s Guide.
• Direct Receipt - This routing is used when material must appear in the on hand balance
immediately. An operator can receive material directly to a receiving staging lane that is
modeled as a stock locator and put it away into the final stock locator at a later time, or
receive the material directly in to the final stock locator. The on hand balance is
incremented as soon as the material is received in to the warehouse.
Note: The term put away refers to the delivery of material to inventory.

Chapter 2 - Page 9
Subinventories
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Subinventories
a vi
n i D
Subinventories are unique physical or logical separations of material inventory, such as raw
T o inventory, finished goods, or defective material. All material within an organization resides in a
subinventory. There are two types of subinventories within Warehouse Management, storage
and receiving.
Storage subinventories are intermediate or final put away locations for material. Material that
resides in a storage subinventory appears in on hand quantity, and is tracked by the system.
The system can book orders against, and use manufacturing processes on material that
resides in a storage subinventory. You must define at least one storage subinventory for your
implementation.
Optionally, you can create receiving subinventories to track material in the receiving area. You
use receiving subinventories when you want to track the material as soon as it enters the
warehouse before an operator puts it away. Receiving subinventories enable managers to see
where the material resides as soon as it enters the warehouse. Material located in a receiving
subinventory does not appear in on hand quantity, and the system cannot reserve the
material. An operator can also only specify a receiving subinventory if they are using a mobile
device to receive the material.
Note: Operators cannot transfer material from a storage subinventory to a receiving
subinventory.

Chapter 2 - Page 10
Locator Types
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
son licen
LocatoridTypes
D av identify physical areas where inventory is stored. Warehouse Management uses
Locators
T oni locators for many different purposes. For information on locator types see Defining Stock
Locators, Oracle Inventory User’s Guide.

Chapter 2 - Page 11
Receiving Locators
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Receivings on licen
Locators
a vi locators enable operators and managers to view newly received material in the
D
Receiving
T oni warehouse. A receiving locator is a physical location assigned to receive items. They provide
real-time tracking of received items, and their current location. Material that resides in a
receiving locator is not counted or costed as on hand inventory. You can query material in the
material workbench.
Receiving locators also enable operators to perform complex and multi stage material
movement throughout the warehouse before depositing the material at the final storage
location. Receiving locators must be associated with a receiving subinventory. The following
lists some of the uses of receiving locators:
• Movement to consolidation locators
• Movement to inspection stations
• Movement to packing stations
• Cross dock to outbound staging lane
• Possible to model ‘n’ step put away process

Chapter 2 - Page 12
Locators in the Receiving Area
An operator can specify the receiving locator during receipt for a PO with a standard or
inspection routing. The system enables the operator to specify receiving locators for material
received using a mobile device. Additionally, material that resides in a receiving locator, is not
recognized as on hand stock, and cannot be reserved.
Note: The subinventory type Receiving is required to set up receiving locators.
See: Defining Stock Locators, Oracle Inventory User’s Guide for more information about
locators.
Using Receiving Locators

If you plan on using receiving locators in your implementation, you must set up at least one
receiving subinventory for the organization.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 13
Document Based Receiving
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oBased
Document
v i d i
lReceiving
D a
Document based receiving is used when an operator knows the document at the time of
n i
o receipt. Operators can use the following documents to receive material in to the warehouse:
T • Purchase orders – Standard purchase orders, or blanket purchase orders. For more
information on purchase orders, see Overview of Purchase Orders, Oracle Purchasing
User’s Guide.
• Inter-org transfers - Items received from other internal organizations.
• RMAs - Material returned from customers.
• Internal requisitions - Material received against an internal order or requisition.
• Advanced Shipment Notice (ASN) - A supplier can use ASNs to send detailed
information about a shipment before it arrives at the warehouse. The system can receive
ASN information via an EDI, Oracle iSupplier Portal or Oracle XML Gateway. An ASN
contains the following information:
- Item
- Quantity
- Lot
- Serial number

Chapter 2 - Page 14
- LPN
• WIP Completion: Assemblies completed in WIP
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 15
Item Based Receiving
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oReceiving
Item Based
v i d li
D a
Item based receiving is used when operators do not know the document type. Operators can
n i
o receive different types of items in the single receiving common user interface. Items include:
T vendor, substitute, expense, shop floor, and one-time items. To use item receiving, an
operator scans the item number and selects the document from the list of values. Item based
receiving is useful if operators know the item to receive, but not the document number.

Chapter 2 - Page 16
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 17
Receiving Methods
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 18
Standard Routing Flow
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n Standard
othe c en Routing Flow
Explaining
d l i
vi the standard receipt process an operator scans the incoming document, or enters the
To
D astart
T oni document number. Next the operator scans the LPN if it exists. If an LPN does not exist, the
operator can create a new LPN. The operator then scans or enters the item numbers,
quantity, lot number and serial numbers if applicable. The system then matches the material
to the document shipping lines according to the matching algorithm. The operator then enters
the receipt header information and finally puts away the material. The system does not
increment the on hand balance for the material until the operator transfers the material from a
receiving subinventory in to a storage subinventory.
For more information on standard receipts see Managing Receipts, Oracle Purchasing User’s
Guide.

Chapter 2 - Page 19
Inspection Routing Receipt
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oRouting
Inspection
v i d li Receipt
D a
The inspection receipt process is identical to the standard receipt process, except an
n i
o inspection is performed on the material before it is put away. For more information see,
T Explaining the Inspection Process, Oracle Warehouse Management User’s Guide.

Chapter 2 - Page 20
Direct Receipt Flow
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oDirect
d
Explaining
v i i
lReceipt Flow
D a
The direct receiving flow is very similar to the standard receipt flow. An operator scans the
n i
o incoming document or enters the document number to start the receiving process. Next, the
T operator scans the LPN if it exists. If an LPN does not exist, the operator can create a new
LPN. Next the operator can scan or enter the item numbers, quantity, lot number and serial
number if applicable. Finally the operator scans or enters an inbound staging lane or stock
locator for the material. The system then matches the material entered to the document
shipment lines according to the matching algorithm. The system increments the on hand
balance for this material as soon as the operator completes the receipt.
For more information see Managing Receipts, Oracle Purchasing User’s Guide.
An operator can optionally choose to perform a put away to enable the rules engine to
suggest a storage location, but if the operator received the material directly in an appropriate
storage location no further transactions are necessary.

Chapter 2 - Page 21
Express Receipt Flow
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oExpress
d
Explaining
v i li Receipt Mode
D a
Express receipts enable you to streamline your receiving process. Operators can use express
n i
o receipts for ASNs, internal requisitions and in-transit shipments. Express receipts do not
T require an operator to enter item, quantity, lot or serial information, because the system
retrieves this information directly from the document (ASN, internal requisition, or in-transit
shipment number).
Note: If the document does not contain the required information, or the import fails, the
system directs the operator to the receiving window where the operator can enter the
information.
For more information express receipts see, Explaining the Express Receipt Process Using
ASNs, Explaining the Express Receipt Process Using Internal Requisitions, and Explaining
the Express Receipt Process Using Internal Shipments, Oracle Warehouse Management
User’s Guide.

Chapter 2 - Page 22
Express Receipts
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 23
Mixed Receipt Routing
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on Routing
Mixed Receipt
d l i c en
A a vi routing is an LPN that contains material that has different receipt routings. When this
mixed
D
T oni occurs the system applies the most restrictive routing to the LPN. For example, if an LPN
contains material that has a standard routing and other material that requires inspection, the
system applies the inspection routing to the entire LPN.

Chapter 2 - Page 24
Desktop vs. Mobile Receiving
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oMobile
Desktop
v i dvs. li Receiving
D a
The above chart reflects the differences in receiving material using the desktop application,
n i
o and receiving material using the mobile device.
T * - Material must be packed into LPNs before inspection using desktop packing workbench
† - If the receipt routing is direct, then material can be in loose
You can also use the desktop to pack and inspect an LPN, but use the mobile device to put
the material away.

Chapter 2 - Page 25
Mobile Receiving Options
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Receiving s on licen
Substitutes
a vi can use the mobile device to receive substitutes if Allow Substitutes is enabled on
D
Operators
T oni the shipment line, and substitutes are defined for the item. For more information see
Purchasing Attribute Group, Oracle Inventory User’s Guide.
Receive Expense Items

Operators can use the mobile device to receive expense items, but the expense items cannot
be traced in the warehouse after receipt.
Receive Vendor Item

Operators can use the mobile device to receive vendor items by the vendor item number.
However, vendor items are traced through the original item number in the warehouse.
Receive by GTIN Number

Operators can use the mobile device to receive numbers by GTIN number instead of the
internal item number.
Enable Shortage Notification Messages

The system can generate shortage notifications after receipt when material shortage is
enabled for items and a backordered sales order or WIP job exists.

Chapter 2 - Page 26
Unavailable Mobile Receiving Options
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
Unavailable
o
s Mobile
l i e
cReceiving Options
a v i
n i D
Warehouse Management does not support the following receiving options:
T o • Blind receipts- Warehouse management does not support blind receipts. For information
blind receipts see, Defining Receiving Options, Oracle Purchasing User’s Guide.
• Receipts without a document or item- Operators cannot use the mobile device to
receiving material if they do not have the document information or the item information.
• Unordered receipts- Operators cannot use the mobile device to receive unordered
material in to the warehouse.
• Receipt Corrections- Operators cannot use the mobile device to make receipt
corrections.

Chapter 2 - Page 27
LPN Receipts
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Receiving s on Using
LPNs l i c ena Mobile Device
a vithe mobile device for receipts helps operators to track material in the warehouse.
D
Using
T oni Operators can reuse defined but not in use LPNs, and nest an LPN for a normal receipt.
The system requires LPNs for receipts except in the following cases:
• Expense items
• Direct receipts
Desktop Receiving
Operators cannot use the desktop application to receive LPNs. The system receives the
material as loose, and does not retain the nesting information for ASNs, internal requisitions,
inter-organization transfers, and in-transit receipts.

Chapter 2 - Page 28
Lot and Serial Receiving
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Lot andid son Receiving
Serial l i cen
D av can use a configurable hot key on the mobile device to dynamically generate LPN,
Operators
T oni lot, or serial numbers. The default key is ctrl-g. Warehouse Management generates a number
according to the sequencing rules set up for the business object. Operators can map the hot
key to any available button on the mobile device. As an implementer, you can also set up
multiple configurations in the same warehouse depending on the device type, or the job
function.
Upon receipt of lot or serialized material, the system prompts the operator to enter a material
status code for the lot, serial number or user-defined attributes for the lot or serial number.
The operator can accept the default values or modify them if necessary. This page does not
appear if the inbound material is not lot or serial controlled, is not material status enabled, or
has no attributes defined.

Chapter 2 - Page 29
Automated Matching of Received Material
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oMatching
Automated
v i d li of Received Material
D a
Warehouse Management requires information about received material, including document
n i
o number, item, quantity, lot, and serial numbers, and matches the information collected to
T expected receipts for that document and item combination.

Chapter 2 - Page 30
Automated Matching of Material Received
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oAutomated
d
Explaining
v i li Matching
D a
The above example depicts a purchase order for eighty units of item AS81947 the supplier
n i
o sends over two shipments of forty. Currently in Purchasing, an operator must select an eligible
T order line within a purchase order. In Warehouse Management does not require an operator
to select an eligible line within a purchase order. Warehouse Management matches the
purchase order lines to the item numbers and quantities in the background using a First In
First Out (FIFO) algorithm. The matching algorithm consumes open approved shipment lines
and consumes exactly the pending quantity on all shipment lines except the last shipment line.
Warehouse Management applies tolerances only to the last shipment line.
The example above represents a receiving tolerance based on early or late receipts.
Warehouse Management supports receiving tolerances based on the following information:
• Over-receipt quantity
• Early receipts
• Late receipts
• Ship to locations

Chapter 2 - Page 31
Receiving - GTINs
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Receiving s on licen
GTINs
a vian operator receives GTINs, they scan the GTIN number and the system resolves the
D
When
T oni internal number unit of measure and quantity of the scanned material. If the warehouse
receives material from suppliers that is labeled with an internal item number or an industry
standard number, operators can scan vendor item numbers or GTIN numbers at receipt.
Note: GTIN number scanning is available in all mobile user interfaces except WIP and
Quality.

Chapter 2 - Page 32
GTIN Setup
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
Receivingd o
sGTIN lice
v i
Toareceive GTINs, you must perform the following setups:
D
T oni • Define UOMs
• Define UOM conversions
• Define GTIN numbers in item cross reference
• Associate the cross reference type GTIN in the profile option INV: GTIN cross reference
type.
For more information on defining units of measure and units of measure conversions see:
Defining Units of Measure, and Defining Unit of Measure conversions, Oracle Inventory User’s
Guide.
For more information on cross references see Defining Customer Item Cross References,
Oracle Inventory User’s Guide.
For more information on Inventory profile options see Inventory Profile Options, Oracle
Inventory User’s Guide.

Chapter 2 - Page 33
Receiving Open Interface
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 34
Quality Vs. Purchasing Inspection
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cenInspection
oPurchasing
Quality d
v i Vs. li
a
To initiate the LPN inspection process, the operator scans the LPN, item, and quantity to
D
n i
o inspect. If only one item is packed in the LPN, the operator can press enter and the item and
T quantity information appear automatically.
Depending on the value of the QA:PO Inspection system profile, the system directs the
operator to either the Purchasing Inspection or Quality Inspection page. If the value is set to
Quality but the system cannot find an applicable plan, it defaults to Purchasing Inspection.
If you choose Purchasing Inspection for your implementation, the operator scans the quantity
of the accepted and rejected material and provides optional reasons and quality codes if
necessary.
If you choose Quality Inspection for your implementation, the operator enters information into
a collection plan. The collection plan includes customizable quality related fields to capture
during inbound inspection. The operator also enters the accepted and rejected quantities. In
addition to capturing data using Quality Inspection, the system can automatically assign
material statuses and lot or serial number attributes based on the results of a Quality
Inspection.
After completing the inspection, the operator must scan an LPN for the accepted quantity (this
value defaults to the original LPN), and generate a different value for the LPN to track the
rejected quantity. At this point, the LPN inspection is complete.

Chapter 2 - Page 35
Standard Inspection
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 36
Quality Inspection
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 37
Inspection Storage Requirements
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 38
Returns
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Returnsdso
n cen
v i li
a
Operators can perform returns in a one or two step process. The profile option WMS:Express
D
n i
o Returns determines the process to use for returns. If you enable the profile option for your
T implementation, an operator can perform a return in two steps.
To perform a one step return, an operator retrieves the material and puts it away. To perform
a two step return, a manager initiates a return (step 1) and an operator retrieves the material
and puts it away. (step 2). If you do not enable the profile option, the return transaction is
initiated and completed in one step.
Note: Returns to suppliers can be based on an LPN.

Chapter 2 - Page 39
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 40
Cost Groups
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 41
Cost Groups
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 42
System Assigned Cost Groups
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cAssigned
oSystem en
Explaining
v i d l i Cost Group
D a
Warehouse Management can assign a cost group to inbound material at receipt. You can set
o n i up rules to determine the appropriate cost group based on item, item category, supplier, or
T many other objects included in the Warehouse Management rules engine. If the system does
not find an applicable cost group rule, then it assigns the default cost group of the
subinventory where the material is put away to the material.
The system assigns a cost group when operators perform transactions. The following are
examples of when cost groups are assigned:
• Material is put away in a storage locator
• Material is cross docked
• Any material movement in an operation plan which is in inventory

Chapter 2 - Page 43
Cost Groups Setup
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 44
Commingling
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 45
Commingling
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 46
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 47
Put Away Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n Away
oPut c n
eRules
Explaining
d l i
vi rules enable the system to direct operators to put newly received material into the
D a
Put away
T oni most appropriate location. The follow is a list of possible uses for put away rules:
• Direct operators to put an item away in the same locator where the item is already stored
• Prohibit commingling of different items or different lots of the same item in a single
locator
• Avoid lot commingling in a locator
• Base the put away location on inspection results, the type of purchase order, or item
category
• Direct operators to put away items based on refrigeration restrictions.
For example, if your implementation has items that require a storage temperature of 32
degrees or below, you can create a put away rule to put away those items into a refrigerated
subinventory and locator.
An operator can override put away rule suggestions. For example, if the system suggests a
put away location, the operator can instead put the material into any locator and override the
suggestion. If the operator chooses to override a suggestion, then they must also enter a
reason code for the override. If necessary, you can setup an Oracle Workflow to send a
notification of the override to the appropriate personnel, or to trigger an appropriate action,
such as a cycle count.

Chapter 2 - Page 48
Restrictions and Sort Criteria for Put Away Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oRestrictions
v i d
Explaining li and Sort Criteria for Put Away Rules
D a
Restrictions - The graphic above shows a restriction of put away in refrigerated subinventory
n i
o for item # Bottle01. This restriction precludes placing an item that needs refrigeration into a
T subinventory for frozen items.
Sort Criteria - There may be many matches to the given restrictions. In this case, the
restriction is simply to put the item away in the Refrigerated subinventory. The sort criteria
breaks the restriction down further to a more detailed instruction, in this case the sort criteria
assigns a locator for put away that is on the lowest available shelf.
For more information on defining rules, refer to the Oracle Warehouse Management User’s
Guide.

Chapter 2 - Page 49
Setting Up Put Away Rules
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 50
Setting Up Put Away Rules: Define Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n Away
oPut c n Restrictions and Sort Criteria
eRule
Explaining
i d
vdefine l i
D a
You put away rules in the Warehouse Management Rules window (N) Setup >
o n i Warehouse Configuration > Rules > Warehouse Execution > Rules. Within the Warehouse
T Management Rules window you select the type of rule and enter a unique name and
description for the rule. The Quantity Function defaults as Subinventory and Locator, but you
select the parameter for the Subinventory and Locator. The parameters include the following:
• Available Capacity by Customer-Specific Algorithm – Available capacity calculated by
customer-specific algorithm implemented within
WMSCustom_PUB.GetAvailableLocationCapactiy
• Available Capacity by Units - Available capacity by units calculated as total capacity by
units minus occupied capacity by units without any consideration of UOM's
• Available Capacity by Volume - Available capacity in transaction UOM calculated as total
capacity by volume minus occupied capacity by volume
• Available Capacity by Weight - Available capacity in transaction UOM calculated as total
capacity by weight minus occupied capacity by weight
• Minimum Available Capacity by Units, Volume and Weight - Available capacity in
transaction UOM calculated as minimum of available capacity by units and available
capacity by volume and available capacity by weight

Chapter 2 - Page 51
• Minimum Available Capacity by Volume and Weight - Available capacity in transaction
UOM calculated as minimum of available capacity by volume and available capacity by
weight.
Next you define the restriction of the rule in the Restrictions tab. You define a sequence (Seq),
select an Object, Parameter, Operator, Object, Parameter/Value/LOV, and value. You can
build on a rule by using AND or OR. For example, you create a put away rule that has a
restriction stating if item category = Frozen AND Item = AS61142, then put away to
subinventory FROZEN. In this case, if one of the two restrictions is not met, the rule is not be
However, if you replaced the AND with OR, then if one of the two restrictions is met, then the
rule would be used regardless if the other restriction is met.
Finally, enable the rule, and select Common to All Orgs if you want to user this rule in all
organizations.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 52
Setting Up Put Away Rules: Define Strategies
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oStrategies
d
Explaining
v i li for Put Away Rules
D a
A strategy is a list of rules to apply, in sequence, until the put away is complete.
o n i
T You define strategies in the Warehouse Management Strategies window (N) Setup >
Warehouse Configuration > Rules > Warehouse Execution > Strategies. Within the
Warehouse Management Strategies window, you select the type of strategy (picking, put
away, or cost group), define a unique name and description, define a sequence number,
select the rule, and optionally define Effective Dates (From and To dates). Next, you enable
the strategy and decide if it is common to all organizations.

Chapter 2 - Page 53
Setting Up Put Away Rules: Assign Strategies to Business Objects
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oStrategy
d
Explaining
v i li Assignment for Put Away Rules
D a
You assign strategies to business objects in the Rules Workbench. For more information on
n i
o the rules workbench see Describing the Rules Workbench, Oracle Warehouse Management
T User’s Guide.

Chapter 2 - Page 54
Put Away
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Put Away d s on licen
a vi the put away of material the operator scans an LPN. If the LPN requires inspection
D
To initiate
T oni the operator receives an error message. In addition to supporting LPN put away from a
standard routing or direct routing receipt flow, Warehouse Management allows an operator to
scan an LPN anywhere in the warehouse to initiate a put away.
After the operator scans the LPN, they have the option to Load the LPN onto their current
equipment, or drop the LPN immediately. If the LPN is loaded, the operator can load
additional LPNs onto their equipment and drop the LPNs when ready.
When an LPN drop occurs, the Rules Engine determines an optimal put away location for the
material. If the system does not return a suggestion, either because no applicable rule or
capacity exists, the operator receives an error that indicates the system failed to allocate
space for the put away. If the system returns a suggestion, it displays the suggestion and asks
the operator to verify the quantity and the drop location. The operator may also choose to drop
to a different LPN. If the system suggests multiple drop locations, for example the system
suggests the operator split the LPN, the operator must enter new LPNs for the material
dropped out of the original LPN.
If a discrepancy exists, such as the operator drops less than the full quantity, or drops the
material to a location that differs from the suggested location, Warehouse Management
requires the operator to enter a reason for the discrepancy. Based on the reason, the system
can initiate custom built workflows to perform corrective action such as schedule a cycle

Chapter 2 - Page 55
count, or notify the appropriate people. After the operator verifies the drop location, the put
away drop is complete.
Note: For performance reasons you may choose to pregenerate put away suggestions at
receipt rather than waiting for the system to determine them when an operator scans the LPN.
During implementation you can set an organization parameter to pregenerate put away
suggestions at receipt
Note: Suggested put away location may become invalid when material movement occurs.
You can set an organization parameter to control the frequency Warehouse Management
refreshes put away suggestions.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 56
Put Away Load
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Put Away d s on licen
Load
a i
vcan
n i D
You use form function parameters to optimize the fields and buttons the operator views on
T o the mobile device.

Chapter 2 - Page 57
Put Away Drop
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 58
Put Away Drop
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 59
Put Away Drop - Nested LPN
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 60
Item Based Put Away
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n Away
oPut c en
Item Based
i d
vbased l i
D a
Item put away allows you to control put away by item for mixed load LPNs.
o n i
T

Chapter 2 - Page 61
Item Based Put Away
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 62
Cross Docking Put Away
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on putlicaway
Cross Docking
d en
a vi using the Rules Engine to determine a put away suggestion, Warehouse Management
Before
D
T oni checks for backordered sales order lines or WIP jobs that incoming material can fulfill. If an
eligible line exists, the system prompts the operator to put away the incoming material directly
to an outbound staging lane, or issue to the WIP job to immediately meet backordered
demand. This flow avoids the unnecessary material handling and processing of storing the
material in a storage area before moving it to the outbound staging area.
If a partial quantity of the incoming material can fulfill a sales order demand, the system
directs the operator to put away the backordered quantity to outbound staging, and the Rules
Engine determines an optimal storage location for the remaining material.
Warehouse Management uses put away rules to validate the staging locator. If you use cross
docking, verify put away rules allow you to store an item in an outbound staging lane.

Chapter 2 - Page 63
Cross Docking to Outbound Staging Flow
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Cross Docking
on toliOutbound
c en Staging Flow
a vienabled cross docking in your organization, the system checks for back orders sales
D
If you
T oni order lines incoming material can fulfill before it uses the rules engine to determine a put away
suggestion. If it finds an eligible sales order line, the system prompts the operator to put away
the material directly to an outbound staging lane.
If a sales order line consumes only part of the incoming material, Warehouse Management
directs the operator to put away the partial quantity to the staging lane, and the rules engine
determines a storage location and directs the operator to put away the remaining material.

Chapter 2 - Page 64
Cross Docking to WIP Staging Flow
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Cross Docking
on toliWIP
c enStaging Flow
a vienable cross docking for your organization Warehouse Management checks for
D
If you
T oni component pick requests that were not fully allocated, before it uses the rules engine to
determine a put away location for incoming material. If it finds an eligible component pick line,
the system prompts the operator to put away the material to a WIP staging lane.
If the component pick demand quantity is less than the incoming material, the system directs
the operator to put away that quantity to a WIP staging lane, and uses the rules engine to
suggest to an operator a storage location for the remaining material.

Chapter 2 - Page 65
Cross Docking to WIP Issue Flow
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oCross
d
Explaining
v i i
lDocking to WIP Issue Flow
D a
The system can also suggest a direct WIP issue as a put away option. In this case, the
n i
o system first executes a receipt transaction into the default WIP staging lane, and then
T performs the issue. These transactions are invisible to the operator and are for transaction
costing reasons. the operator only sees a WIP issue on the mobile device.

Chapter 2 - Page 66
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 67
Advanced Task Framework (ATF)
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Advanced
d s on Framework
Task l i c en
a vi Task Framework enables you to configure and execute complex material flows for
Advanced
D
T oni inbound items for your implementation. You can plan and configure material flows to address
specific business objectives. Advanced task framework also simplifies the inbound material
movement execution process. Advanced task framework enables you to:
• Perform multi-step material movement
• Define sequence of operations to be performed during material flow
• Define predictable material movement paths
• Perform advanced operations such as incremental consolidation, sorting, and packing
• Use zones to balance workloads
• Monitor progress

Chapter 2 - Page 68
ATF Capabilities
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o
ATF Capabilities l i ce
i
avcan use ATF to perform the following functions:
D
You
T oni • Consolidation of similar items for palletization
• Consolidation of items going to the same destination
• Deconsolidation of LPNs with mixed items
• Movement of material requiring inspection to Inspection Station
• Movement of loose material to Packing Station
• Use of Pick and Drop Locator to perform an ‘n’ step put away

Chapter 2 - Page 69
ATF Concepts
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 70
ATF Concepts
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 71
ATF Concepts
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 72
ATF Concepts
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Load dso
n cen
li
visi the act of picking
D a
Load material from a locator and transferring it into the hands of an
on i operator, onto equipment, into a tote, or onto a conveyor. An operator performs loads when
T material needs to be moved. Loading is the first step performed for material movement.
Drop
Drop is the act of dropping loaded material into a locator. A load operation should always
precede a drop operation.

Chapter 2 - Page 73
ATF Concepts
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 74
ATF Concepts
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Material d s on licen
Grouping
a i
vcan
n i D
You use operation plans to control the material grouping in locators and LPNs during
T o intermediate moves. You can consolidate material in a locator or LPN based on one of the
following attributes:
• Destination
• Operation
• Subinventory
• Similar item
For example, items with the same final put away location are consolidated in to an
intermediate locator, and a worker assigned to a forklift performs the final put away.

Chapter 2 - Page 75
ATF Concepts
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 76
ATF Example
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
ATF Example
d s on licen
a i
vapplies
ATF
D to standard and inspection receipts. You cannot use ATF for direct routed
o n i receipts. Above is an example of a complex receiving process you can use ATF to map.
T Material received into the R1.1.1 receiving subinventory is routed to either to the inspection
area, to inventory, or to an outbound staging area.
Each operation shows how material moves through the warehouse. The rules engine
determines which operation plan to use. Once the rules engine selects the operation plan, the
material is moved from operation to operation until it is finally inspected, put away in inventory,
or cross-docked.

Chapter 2 - Page 77
ATF Setup
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 78
ATF – Zones : Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Zones dso
n cen
v i li
a
A zone is a logical collection of locators sharing some common warehouse attributes. A
D
n i
o locator can exist in more than one zone and a zone may consist of locators from one or more
T subinventories. You can also manage tasks by zone.

Chapter 2 - Page 79
ATF Operation Plan Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Operation s on Setup
Plan l i c en
a viare three types of operation plans standard, inspection, and cross dock. You can define
D
There
T oni multiple operation plans for a warehouse. Warehouse Management automatically selects an
operation plan for material during item receipt. The operation plan also specifies the physical
location where a particular operation occurs. The location of the operation could be a pre-
specified zone, determined according to material grouping criteria, or determined by the rules
engine.
The example above shows a sample operation plan that involves loading received material
and dropping it to an inspection station. The inspection station is defined as a locator in a
subinventory of type Receiving. Once inspection is complete another user moves the
inspected items from inspection station to the final put away location.

Chapter 2 - Page 80
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 81
Implementation Considerations
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on Considerations
Implementation
d l i c en
a viyou create subinventories, you must consider the following:
When
D
T oni • Types: You must determine if the subinventory is a storage subinventory or a receiving
subinventory. Receiving subinventories are optional for your implementation. You cannot
define receiving locators if you do not define a receiving subinventory.
• Material Status: You must determine if there are any transactional restrictions for your
subinventories.
• Cost Groups: You must determine the default cost group for the subinventory. The
system uses this cost group assignment if the rules engine fails to determine a cost
group for the material.
• Zones: You must determine if you need to create logical zones for the locators within the
subinventories.

Chapter 2 - Page 82
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on Considerations
Implementation l i c en
a vi you set up items, you must determine if your warehouse will accept supplier part
DBefore
T oni numbers or substitute part numbers.
• You can define supplier part number relationships so operators can scan supplier part
numbers on receipt.
• You can define substitute part numbers so operators can automatically accept a
substitute by scanning it as they would the original number.

Chapter 2 - Page 83
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on Considerations
Implementation l i c en
a viyou receive items into the warehouse you must account for the following system
DWhen
T oni considerations:
• You cannot mix desktop and mobile transactions for a single receipt process
• An LPN is required on material received in a Warehouse Management enabled
organization
• You can model a cart as an LPN and receive and put away material into and from the
cart
• You cannot perform a direct receipt into a non-LPN controlled subinventory
• If you mark a subinventory as non-LPN controlled, Warehouse Management forces
material to be put away loose and the LPN modeled cart is then be available to receive
more material.

Chapter 2 - Page 84
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oModes
d
Explaining
v i liof Inspecting Serialized Material
D a
When you define your items you must decide which mode of serial number entry you plan to
n i
o use. The modes are controlled through a form function parameter. For more information, refer
T to the Oracle Warehouse Management Implementation Guide.

Chapter 2 - Page 85
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 86
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 87
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 88
Summary
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 89
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 2 - Page 90
ble
fe r a
ans
n - t r
a no
a s
) deฺ
Management c m i
o GuWarehousing
e ฺ
r a cl ent
Features
n @ o
S t ud
i d so thChapter
is 3
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
D
T oni
R12.x Oracle Warehouse Management Warehousing Features

Chapter 3 - Page 1
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 2
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 3
Objectives
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 4
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 5
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 6
Compliance Labeling
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Supplierd s on licen
Labeling
a vi labeling enables users to move inventory more efficiently through the warehouse.
Compliance
D
T oni It enables bar code scanning of inbound purchase orders, which results in less receipt
processing time, immediate recognition of available materials, and higher receiving accuracy.
Customer Labeling
Compliance labeling produces customer specific labels on demand for each shipment to
comply with customer requirements for bar code labeling and ASNs.
Flow Manufacturing
You can also use compliance labeling in flow manufacturing. Each step in the manufacturing
flow can utilize compliance labeling. You can use compliance labeling in manufacturing as
follows:
• Prior to the start of the first operation - For example, a label that contains routing
information.
• During any operation - Based on the outcome of a flow operation, flow manufacturing
determines the location of the next assembly routing dynamically.

Chapter 3 - Page 7
• Warehouse Management prints the routing information when flow manufacturing
determines it. For example, material may need to be scrapped during an operation. A
user can print a label to route the material to the scrap subinventory.
• After quality inspection of a flow operation - Material may not pass quality inspection,
and therefore it may be sent to a prior operation, to scrap, or sent forward to the next
operation.
• At flow completion – A user can print inventory labels for material for finished goods as
well as labels with the shipping instructions, address, and sales order number for
assemble to order material.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 8
Warehouse Management versus Partner Label Printing
Responsibilities
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 9
Label Printing Components
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 10
Label Formats
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s
Label Formats
d on licen
a
When
viyou define label formats, you determine the fields associated with a particular label and
D
T oni label type.

Chapter 3 - Page 11
Label Types
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
Label Typess o l i ce
i
av Management supports the following label types:
D
Warehouse
T oni • Materials: This label provides information about the item, including lot information if
applicable.
• Serial: This label provides information specific to the item serial number.
• Location: This label provides information about warehouse locators.
• WIP Content: This label provides information about WIP components picked for a job. It
includes the component number, serial, lot, job number, assembly number, and start
date.
• Flow Content: This label provides information about components picked for a schedule.
It includes the kanban number, component number, serial, lot, schedule number, and
start date.

Chapter 3 - Page 12
Label Types
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Label Typess on licen
a i
vLPN:
n i D • This label provides information about the LPN. It does not contain content
T o information. Warehouse managers and users use this information to track the LPN
through the warehouse.
• LPN Content: This label provides information about the LPN and the associated
contents.
• LPN Summary: This label provides information about the LPN and a summary of the
contents. If the LPN contains nested LPNs, then the label summarizes the content of
those LPNs.
• Shipping: This label provides information about an outbound shipment. It does not
include shipment content information.
• Shipping Contents: This label provides information about an outbound shipment and the
contents of the shipment.
Multi Record Labels

The shipping contents label, and the LPN contents label formats support more than one row of
data on a single label. This enables a user to print a single label that contains multiple lines of
content information for an LPN or outbound shipment. For example, if an LPN contains two
items, a user can print two rows of item information on the LPN contents label.

Chapter 3 - Page 13
Setup
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 14
Registering Label Formats
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 15
Assigning Label Types to Business Flows
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Assigningd s on Types
Label l i c ento Business Flows
a i
vyou
After
D set up label formats, you must associate the label types to a specific warehouse
o n i business flow. This association enables the system to print the label type automatically as part
T of the business flow.
A user can print the same label type for different business flows with a different format. For
example, a package has a carton label when it is picked, but an operator re-labels it with a
shipping label when it is shipped.
You can also print multiple label types for a business flow. For example you can print a
shipping content label and a shipping label for the Ship Confirm business flow.

Chapter 3 - Page 16
Label Format Assignment Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Label Format
onAssignment
l i c en Rules
a viformat assignment rules associate a label to a business object based on parameters
D
Label
T oni and restrictions you specify. After you define label formats and associate them to the
appropriate business flows, you can define label format assignment rules. The figure in the
slide provides an example of the type of rule you could create to generate an LPN Content
label for hazardous items. If the material meets all of the restrictions when the rules engine
executes the rule, then Warehouse Management generates the hazardous item LPN Contents
label.
Creating label format rules is an optional step. Some implementations require only a single
label format for each label type. In this case, the Warehouse Management uses the default
label format for each type. It also uses the default if there are no applicable rules. If the
implementation requires more than one label format for a label type, you must create label
format rules.

Chapter 3 - Page 17
Defining and Assigning Printers
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Defining d s
and
onAssigning
l i c en Printers
a i
vmust
n i D
You define printers and assign them to the appropriate label types before you can print
T o labels. You define printers in the System Administrator responsibility, and assign printers in
the Choose Document and Label Printers window.
System Administrator (N) Install > Printer > Register
(N) Setup > Warehouse Configuration > Printers & Devices > Assign Printers to documents
For more information on defining printers see, Setting Up Your Printers Oracle Applications
System Administrator’s Guide – Configuration.
For more information on assigning printers see, Choosing Printers for Shipping Documents
and Labels Oracle Order Management Implementation Manual.

Chapter 3 - Page 18
Printing Modes
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Printingd s on licen
Modes
a viThe profile option WMS: Label Print Mode determines the printing mode.
D
Note:
T oni

Chapter 3 - Page 19
Asynchronous Mode
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Asynchronous
on Mode l i c en
a vi
n i D
In Asynchronous Mode, Warehouse Management creates an Extensible Markup Language
T o (XML) file and transfers it to a directory the third party software monitors. You cannot use
Warehouse Management to monitor the status of the print request after creation of the XML
file.
Note: The profile option WMS: Label output directory determines the output directory.

Chapter 3 - Page 20
Synchronous Mode - Generic
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Synchronouss onMode l i c–
n
eGeneric
a vi Synchronous Mode is a real-time integration between Warehouse Management and
D
Generic
T oni the third party software handled through a PL/SQL Application Program Interface (API). The
third party software returns a success or failure message regarding the status of the label print
request to Warehouse Management. Warehouse Management stores these messages in the
label print history.
For more information see Synchronous API Specification, Oracle Warehouse Management
Implementation Guide.

Chapter 3 - Page 21
Synchronous Mode TCP / IP
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Synchronouss onMode l i c en
TCP/IP
a vi
n i D
Synchronous Mode TCP/IP is a real-time integration mode between Warehouse Management
T o and third party software that is handled through a standard ethernet TCP/IP connection.
Warehouse Management ensures the printer or print server is listening to the IP and port and
successfully receives the XML string, but does not receive the status the detailed status of the
print request.

Chapter 3 - Page 22
Viewing Label Requests
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Viewingd s on Requests
Label l i c en
a via user requests a label, the system creates a record. The label request record contains
D
When
T oni the XML data and other information the system generated for the label request. Managers can
use the Label Requests history window to query, view and resubmit label requests.

Chapter 3 - Page 23
Label Printing Implementation Considerations
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on Implementation
Label Printing l i c en Considerations
a v i
n i D
Warehouse Management supports two types of label printing configurations:
T o • Printing using third party label software and print server
• Printing using XML enabled direct label printers
The printing strategy selection depends on the following factors:
• Return on investment
• Real time latency
• Need for compliance labeling
• Current printer modes
• Label volume
• Network infrastructure
Though adding layers between Warehouse Management and printing gives you additional
flexibility, it creates additional complexity and cost.
Before you can print labels, the third party software may require additional setup. The third
party software must recognize Warehouse Management printers, defined label formats, and
field data variables. The third party software must also read the XML format Warehouse
Management generates.

Chapter 3 - Page 24
If you use the generic synchronous mode, you must load the PL / SQL API in to the Oracle
database.
If you use synchronous mode TCP / IP the printer or print server must receive TCP / IP
message, and a firewall cannot block messages from the environment to the printer or print
server of the specified port.
If you use the asynchronous mode, you must set the third party software to scan the
appropriate directory for XML files to process as print requests.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 25
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 26
Task Management
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
Task Management
d
a viare comprised of demand pick tasks for sales orders, work orders, and replenishment.
Tasks
D
T oni Tasks are also comprised of inbound receiving and put away tasks, inventory transfer tasks,
inventory control related cycle counting tasks, and inbound-outbound hybrid cross-docking
tasks.
Warehouse Management creates and dispatches tasks based on a configurable set of rules
you define and maintain. You create task type assignment rules in the same way you create
other rules. Task management optimizes the sequencing of tasks based on task priority,
locator pick sequence, approximate distance between the locator x-y coordinates and the
current location of the warehouse operator currently signed on to the equipment.
Using task management decreases the number of operator trips and distance traveled, and
increases operator efficiency and productivity.

Chapter 3 - Page 27
Task Types
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Task Types s on licen
a i
vtask
n i D
Each the system generates requires a System Task Type. Warehouse Management
T o contains pre-defined system task types grouped by similar sets of features. When Warehouse
Management creates a task, it assigns the System Task Type. You cannot edit a system task
type for an existing task. The rules engine can use User Task Types to further classify System
Task Types. The System Task Types are:
• Pick
• Put away
• Replenishment
• Move order issue
• Move order transfer
• Cycle count
You use the BOM Standard Operations window to define User Task Types. You must create a
User Task Type for each task that requires a unique combination of human and equipment
type resources.
You must set up at least one pick, one move order issue, and one replenishment task type.
You can also define one cycle count task type if you want to dispatch cycle counts as tasks.
Do not define more than one cycle count task type for the organization.

Chapter 3 - Page 28
For more information see Setup Warehouse Task Types, Oracle Warehouse Management
User’s Guide.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 29
Setting Up Task Type Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
n cen
soTask
Settingid
v Up li Rules
Type
D a
Task type rules determine which task type to use. You use the Task Type Rules window to
n i
o define Task Type Rules.
T (N) Setup > Warehouse Configuration > Rules > Warehouse Execution > Task Type
The rule returns a value if the restrictions are met, and the rule weight determines the rule
priority. Rules with a higher weight receive a higher priority.
If the rules engine cannot find a Task Type Rule that meets the restrictions, it uses the default
task type you setup in the Warehousing tab of Organization Parameters window. If you did not
set up a default task type, then managers must use the WMS control board to dispatch tasks.
You must define Task Type Rules for each of the different types of tasks Warehouse
Management dispatches.

Chapter 3 - Page 30
Task Dispatch Engine
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Task Dispatch
on Engine
l i c en
a i
vtask
n i D
The dispatch engine evaluates rules based on priority, and assigns tasks to users based
T o on rules you define. The task dispatch engine splits and merges tasks based on equipment
capacity, equipment maximum and minimum fill capacity, and the locator pick UOM at the
subinventory level. Task splitting occurs if the available equipment can handle the volume and
the weight of the items in the pick line. Task merging occurs for picks of the same item and
revision from the same subinventory and locator if you enable bulk picking at the organization
level.
The capacity of the equipment is calculated based on the equipment volume, the maximum
weight capacity, and item volume and weight. There is also a minimum weight requirement
called the safe handling limit. If the weight is below the safe handling limit, the equipment is
not safe to operate.
The system dispatches tasks based on equipment requirements. For example, high pick tasks
require a forklift, which can reach a minimum height.
The task dispatch engine assigns tasks to a qualified user based on certain criteria such as
zone restrictions or resource allocation.
The task dispatch engine considers the current location of the user and calculates the next
task based on the proximity of the location after the above criteria are met. This minimizes the
distance user travels and increases the efficiency and productivity of the warehouse.

Chapter 3 - Page 31
Resource Skills
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Resource s on licen
Availability
a vi can dispatch tasks based on resource availability and skill sets. After the system
D
Managers
T oni makes allocations, it determines the task type and dispatches the task to an appropriately
trained user. The system assigns user tasks types during task creation, and dispatches the
task to a user to a task after it determines the user has the sufficient skills for the task.
This task type identification ensures that users receive picks for which they have adequate
training and for which they are using the appropriate equipment.
Before a user logs on to accept tasks, the tasks are grouped, sorted and possibly merged
according to the pick methodology and available equipment capacity.
When the user logs on, the system dispatches an appropriate task for their skills and
appropriate equipment that is close to their current location.
The system orders all subsequent tasks for the user according to the picking order on the
storage locator. The Picking order determines the path the user traverses through the
warehouse to pick required materials.

Chapter 3 - Page 32
Available Equipment and Resources
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Available s on licen
Equipment
a vi implementation, you set up equipment as serialized items within the item master. You
D
During
T oni can define the equipment as a container, vehicle, or both. You can also specify the capacity
(volume and weight) and the minimum fill percentage.
Employees are assigned to resources based on their skill set and type of equipment they can
handle. For example, one employee may be certified to handle hazardous pick equipment,
whereas another employee may not.
The system assigns equipment to resources based on their types, such as forklifts, pallet
jacks, hazardous material handling, or high pick.
Finally, resources are assigned to departments, which carry out specific tasks such as picking
department or hazardous material handling department.

Chapter 3 - Page 33
WMS Control Board
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oControl
Warehouse
v i d li Board
D a
The WMS Control Board is a tool managers use to monitor, plan, control, and execute various
n i
o warehouse operations, including the following:
T • Effectively use resources
• Query tasks
• Plan tasks
• Release tasks to the warehouse floor
• Assign, reassign, and prioritize the progress of tasks
• Perform manual scheduling
• Manage tasks by logical zone
• Create operation plan based on material routing

Chapter 3 - Page 34
Task Status
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
Task Statuss o l i ce
i
avtask status is the current task state. Task statuses are as follows:
D
The
T oni • Unreleased: The task was created, but is not eligible for dispatch. Managers use this
status to control when the task is released. Managers can update tasks in this status to
Pending, (eligible for dispatching), or Queued.
• Pending: The task was created and can be sent to any available operator. Pending tasks
are dispatched to operators in sequence of priority, subinventory picking order, and
locator picking order in relation to the operator’s last known position. Warehouse
Management filters tasks by task type, current operator equipment, and subinventory. It
dispatches a task in Pending status only when there are no more Queued and
Dispatched tasks assigned to the operator.
• Queued: Managers use this task type to manually assign a task to a particular operator
in the warehouse control board.
• Dispatched: The task is dispatched to an operator, but the operator has not started the
task.
Note: Dispatched behaves like queued except the system assigns the operator to the
task based on pick methodology instead of by a manager in the control board.
• Active: The task the operator is performing. The system dispatched the task to the
mobile device, but the user has not loaded or dropped the task. The status of the task

Chapter 3 - Page 35
changes, as soon as either the task is loaded or dropped. The operator assigned to the
task also displays in the WMS Control Board.
• Loaded: The task is loaded; however, no material transaction has posted. To complete
the task, the operator must drop the task.
• Completed: The task has been completely transacted.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 36
WMS Control Board
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 37
Exception Management
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Exception
d s on licen
Management
A a viexception is an unexpected task result, such as if material does not exist in a picking
task
D
T oni location, or if a put away location is full. Transaction reasons enable a user to record and
monitor exceptions to tasks. A user must enter an exception when performing something
unexpected during a task. The user can optionally associate a transaction reason with a
workflow process or transaction reason action. Transaction reason actions support
customized alternative process flows to automatically handle task exceptions.
Common types of corrective actions are placing locators or subinventories on hold if they are
damaged, cycle counting an item in a locator if it is short picked, or reallocating an order line if
insufficient material exists in a locator.
The task dispatch engine includes a set of predefined exception messages and transaction
reasons, which handle the generic exceptions during task dispatching, and triggers a set of
actions based on these exceptions. You can set up the transaction reasons and workflow
patterns based base on the practice and operations of the warehouse.

Chapter 3 - Page 38
Task Setup Steps
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 39
Task Type Implementation Considerations
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen Considerations
oImplementation
Task Type
v i d li
a
Prior to defining entities, you must identify the task types for your implementation. Use the
D
n i
o following questions to help define task types:
T • Beyond the five system-defined task types, what criteria are used to differentiate, who is
qualified, or what equipment is required to perform a task? This helps determine which
task types to define.
• Do operators typically work with one or two pieces of material handling equipment all
day, such as a dedicated fork truck driver? If so, then equipment resources should be
defined.
• Do operators typically switch equipment frequently? If so, then it may not even be
necessary to define equipment resources because operators are already deciding which
equipment to use based on the task attributes.
• Are there different classes of material handling equipment in the warehouse, such as a
pallet jack, fork truck, or cart? Are these classes broken down further, by weight
capacity, or by material handling properties? Can only some equipment be used for
refrigerated or hazardous items? Is some equipment required to reach certain areas,
such as high racks, in the warehouse? This helps determine which equipment items
should be defined and how they should be associated to task types.

Chapter 3 - Page 40
• Are different operators trained to operate different pieces of equipment, move different
classes of items, or are all operators qualified to move all material? This helps determine
which manual resources should be defined and how they should be associated to task
types.
Though you define Task Types to model skill sets and equipment, you can also use them to
restrict tasks to particular operators. Operators can elect to perform tasks in the refrigerated
cooler in the morning, and tasks in the freezer in the afternoon.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 41
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 42
Distributed Warehouse Management
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
Distributed
d o
s Warehouse
l i ce Management
i
avHealthcare Provider value chain consists of 4 tiers:
The
D
T oni • Suppliers
• Payors/Regulators
• Providers
• Patients
Healthcare providers include hospitals, long term care facilities, outpatient care offices (e.g.
doctor’s, labs), and integrated networks (e.g. Kaiser). Regulatory agencies monitor activities
such as transaction costs, and increase consumer confidence in this industry.

Chapter 3 - Page 43
Distributed Warehouse Management Architecture
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oWarehouse
d
Distributed
v i li Management Architecture
D a
Oracle provides an implementation approach to deploy Warehouse Management in a
n i
o distributed model. This can be integrated with the central ERP system using the Oracle Fusion
T Middleware / Oracle Data integrator (ODI).
The approach is to implement multiple instances, separately for plants and corporate levels.
Oracle MES for Discrete Manufacturing R 12.1 is to be deployed as a distributed instance for
each plant. Operators carry out the manufacturing transactions through these plant level
Manufacturing Execution Systems. Each group of plants or locations that requires carrying out
manufacturing independent of the central ERP needs a separate instance of the application.
Transactions can be synchronized between the central Oracle ERP and distributed MES
instances.
The central corporate ERP instance can span across multiple plants and/or locations and is
used for global functions like accounts, order booking etc. Manufacturing transactions carried
out in the distributed MES instances would need to be synchronized with the central ERP
system. This way the distributed MES captures all manufacturing transactions and the
corporate ERP captures and consolidates all cost related data.
In order to make ERP instance aware of transactions executed in MES instance mainly for
costing purpose, an integration layer is required to provide logic for Extracting new
transactions that have been completed in MES but not replayed in ERP:

Chapter 3 - Page 44
• Transforming those transactions so that they are ready for ERP to process
• Sending those transactions over to ERP for actual processing
Oracle Data Integrator (ODI) can be used for this purpose.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 45
How the Integration Works
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
How the d s o l
Integrationi ceWorks
i
avCreate and Update the Purchase Order
D1.
T oni 2. Send the Purchase Order information to the Distributed instance
3. Create and update the Purchase Order
4. Receive ASN information from the supplier (optional)
5. Forward ASN information to the Distributed instance
6. Create ASN on top of the Purchase Order (optional)
7. Receive material from the supplier
8. Send receipt confirmation to ERP
9. Update inventory, close the Purchase Order, and initiate payment and journal entries

Chapter 3 - Page 46
How the Integration Works
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
How the d s o l
Integrationi ceWorks
i
avCreate and Update the Sales Order (Internal sales orders)
D1.
T oni 2. Send shipment request to the distributed Instance
3. Create and update orders
4. Release orders for picking
5. Warehouse task execution
6. Ship goods to hospitals and clinics
7. Send shipment advice to ERP
8. Update inventory, close the sales order, and finishing invoicing

Chapter 3 - Page 47
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 48
Mobile Personalization
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
Mobile Personalization
d
a vi Personalization enables you to customize Oracle Warehouse Management pages
Mobile
D
T oni without making code changes. You can hide fields and provide default field values to reduce
the amount of information a user must enter on a page. These changes reduce the number of
scans and improve overall efficiency and execution. You can also set additional fields as
required if these fields are essential to your business.
With mobile personalization you can:
• Hide fields and buttons
• Provide default field values
• Copy the value of a field to another field
• Set editable fields as read only
• Set non-required fields as required
Mobile Personalization is available for common Oracle Warehouse Management transactions
including:
• Inbound: Receipt, Putaway, Load, and Drop
• Outbound: Pick Load, Drop, and Ship Confirm

Chapter 3 - Page 49
Mobile Personalization Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d son licenSetup
Mobile iPersonalization
D avcan perform the personalization at the responsibility level, organization level, or across
You
T oni organizations.

Chapter 3 - Page 50
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 51
Labor Management
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
Labor Management
d
a viManagement enables warehouse managers to track the amount of time each user
Labor
D
T oni takes to complete a set of tasks. It records this information at specific levels and generic
levels. It also records the task type, material transacted, and material source and destination
locations.
Labor Management then analyzes the data for resource planning and employee evaluation.
Because the application tracks the amount of time and expected work required to complete
each task, it can predict how much time or staff is required to complete the work in the
warehouse.
Labor Management can also assist in the employee evaluation process. The application
compares the time performance of each employee against colleagues or engineered
standards for labor productivity, and then rates each employee based on performance levels.
The performance rating enables the warehouse manager to make staffing, compensation,
training, and work assignment decisions.

Chapter 3 - Page 52
Resource Planning
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Resourced s on licen
Planning
a vi requirements are the number of employees and time required to complete the
D
Resource
T oni outstanding work in the warehouse. Labor Management provides these estimated resource
requirements. These estimations enable you to make decisions for optimizing warehouse
operations efficiency.

Chapter 3 - Page 53
Labor Productivity
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Labor Productivity
a viManagement improves tracking of employee productivity. It provides detailed
D
Labor
T oni productivity information of individual employees and warehouses. It breaks down information
into the following functional areas:
• Inbound
• Warehousing
• Outbound
• Manufacturing
The application provides a score and a rating for each employee and warehouse to determine
productivity level. You can use this information when making compensation, incentive,
staffing, and training decisions.

Chapter 3 - Page 54
Definitions
ble
fe r a
an s
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d
Definitionss o l i ce
av i
D
T oniLabor Standards
Labor Standards are standards that you establish for a specific work unit. You can define a work unit at
different levels of specificity. One labor standard may refer to general picking tasks. Another may refer
to picking tasks, for example, from the CASE subinventory to the STAGING3 staging lane, for quantities
between fifteen and fifty using a rolling cart.
Non-Standardized Transactions
Non-standardized transactions are transactions the application cannot match to an existing labor
standard.
Transaction Time
Transaction time is the time a user takes to scan the appropriate fields and physically perform the work.
Travel Time
This is the amount of time the user takes to travel from one location to another during a transaction.
Idle Time
Idle time is the time in between tasks when the user is not performing work.

Chapter 3 - Page 55
Ratings Algorithm
The ratings algorithm is a grading rubric the application uses to assign scores and performance levels
to individuals. Each work unit in the warehouse has an expected time that it takes to complete within
Labor Management. The ratings Excellent, Standard, Slow, and Unacceptable correspond to the
expected time that each activity takes to complete.
ble
fe r a
an s
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 56
Setting Up Labor Management
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
n cen
soLabor
Settingid
v Up i
lManagement
D a
After you set up the Labor Management parameters, you can optionally use the time and
n i
o motion study to determine the labor standards that Labor Management uses.
T
Non-Tracked Users
You can also set up non-tracked users in the application. Non-tracked users can be
supervisors or other specialty employees who sometimes perform tasks in the application.

Chapter 3 - Page 57
Labor Management Process
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licProcess
Labor Management
en
a viManagement begins to capture data after you set up the Labor Management
D
Labor
T oni parameters and you proceed with normal warehouse operations. To view information in Labor
Management, you must run two different reports, the Expected Resource Requirements
Analysis report, and the Labor Productivity Analysis report. You use the Expected Resource
Requirements Analysis report to determine the time that is necessary to complete the
outstanding work in the warehouse if the resource levels are fixed.
Expected Resource Requirements

Labor Management bases resource requirements on outstanding work within the organization
according to the setup parameter that determines how far into the future to look to consider
outstanding work.
Labor Productivity Analysis

Labor Management enables you to evaluate the productivity of individuals as well as the
organization as a whole. It measures the performance of each individual for completed tasks
against existing labor standards to determine how the time spent performing each task
compares with expected task completion time.

Chapter 3 - Page 58
Refine Labor Standards
You can continue to refine labor standards while using Labor Management. You can add new
labor standards as users perform non-standardized transactions, and delete labor standards
for transactions that users no longer perform in the warehouse.
Labor Management Summary

The Labor Management Summary page displays all of the key Labor Management statistics. It
contains resource requirement information, warehouse labor productivity information, a list of
the work outstanding, and graphical representations of resource estimations and labor
productivity. The Labor Management Summary page includes the same information on the
Analysis tab, but condenses it into a single view.
Resource Requirements
The Resource Requirements alternative region displays the number of resources required and
time needed to complete the outstanding work in the warehouse. The Variable Time table ble
depicts the time needed with a constant resource level. The Variable Resource table depicts fe r a
the resources required for the given time period for the work outstanding. ans
n - t r
Warehouse Productivity
a no
The Warehouse Productivity table shows the productivity performance
h a s of the entire
organization.
m ) deฺ
ฺ c o Gui
Work Outstanding e
cl ent
r a
The Work Outstanding table shows a listingoof all theu d
n @
broken down by functional activity. It breaks t outstanding
downSthe
work in the warehouse,
number of tasks left to complete, and
provides you with details aboutid sotask. this
each
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
D
T oni

Chapter 3 - Page 59
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 60
Summary
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 61
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 3 - Page 62
ble
fe r a
ans
n - t r
a no
a s
) deฺ
Management c m i
o GuOutbound
e ฺ
r a cl ent
Logistics
n @ o
S t ud
i d so thChapter
is 4
d a v s e
ฺ u
( t oni se to
d s on licen
a vi
D
T oni
R12.x Oracle Warehouse Management Outbound Logistics

Chapter 4 - Page 1
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 2
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 3
Objectives
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 4
Objectives
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 5
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 6
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cenLogistics
oOutbound
Overview
v i d of li
a
Outbound logistics enables operators to pick, pack, and ship orders to customers. Outbound
D
n i
o logistics contains the following components:
T • Pick Release
• Picking Rules
• Tasks
• WMS Control Board
• Packing
• Dock Door Appointments
• Shipping
Pick Release
The picking process enables operators to pick material to fulfill orders. Warehouse
Management supports three types of picking: order picking, replenishment picking, and WIP
picking. The system distributes picks to operators as tasks.

Chapter 4 - Page 7
Rules
During implementation, you can create rules to fulfill orders in the most efficient manner. The
following rules support the picking process:
• Release Rules: The picking criteria of order lines for pick release.
• Release Sequence Rules: The order the system releases delivery lines for picking.
• Pick Slip Group Rules: How the system groups tasks on a move order pick slip report for
picking.
Tasks
Warehouse Management creates and dispatches tasks to qualified operators based on rules
you configure.
WMS Control Board

The WMS Control Board provides managers with a real-time snap shot of the warehouse, and ble
enables them to redistribute tasks as needed. They can monitor the progress of tasks as well fe r a
as manually dispatch tasks to operators.
ans
n - t r
Consolidation
a no
Warehouse Management enables operators to consolidate partially
h a sfilled containers in to
fewer and better-optimized containers.
m ) deฺ
ฺ c o Gui
Packing e
cl containers
n t
Warehouse Management enables operators o r
to apack d e with multiple levels of nesting,
@
n independent
and sends notifications if an order contains special t u
Spacking instructions. Operators can
perform packing during picking d oan
orsas h i s process.
a v i se t
Dock Appointments for n d ou
iฺTrips
( t o e t
Managers can
o use
n andcstaging
e s
Warehouse
n laneManagement to schedule outbound carrier appointments, dock
i d s
door availability, li usage within the warehouse.
v
a Verification and Close
n i D
Shipment
To Once an operator picks and loads an order, Warehouse Management automatically
determines the items and quantities to deduct from inventory.

Chapter 4 - Page 8
Overview of Picking
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oPicking
Overview
v i d of li
D a
Picking enables operators to pick material to fulfill orders. Warehouse Management supports
n i
o three types of picking, order picking, replenishment picking, and WIP picking. Warehouse
T Management dispatches picks to operators as tasks. Managers can perform manual pick
release, or you can create a series of rules to automate the process during implementation.
Warehouse Management uses the following rules to release orders: pick release rules,
release sequence rules, and pick slip grouping rules.
Pick release rules determine how the system to selects sales orders for release. If trips are
not scheduled for dock doors, then pick release rules also determine the appropriate staging
lane for sales orders. After the system determines the sales orders to release, it can use
release sequence rules to determine the sequence delivery lines are released for picking,
based on sales order number, outstanding invoice value, scheduled date, departure date, and
shipment priority.
Pick slip grouping rules establish how tasks are grouped on a move order pick slip. They work
in conjunction with the different pick methodologies. Pick methodologies refer to the different
method an operator performs picking tasks. For example, an operator may select to pick an
order by itself, or to pick multiple orders at the same time.
The system generates picking tasks and dispatches them to qualified operators based on
rules. After picking is complete, the system provides operators with the appropriate number
and size of containers the order requires for shipping.

Chapter 4 - Page 9
Sales Order Picking
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oPicking
d
Sales Order
v i li
D a
Warehouse Management dispatches sales order tasks to qualified operators based on their
n i
o skill set and equipment. After an operator picks a sales order task, they deliver it to a staging
T lane to prepare it for shipping.
Note: All picks are delivered to a staging subinventory and locator.

Chapter 4 - Page 10
Replenishment Picking
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on Picking
Replenishment l i c en
a vi Management dispatches replenishment tasks to qualified operators to replenish
D
Warehouse
T oni forward picking areas.

Chapter 4 - Page 11
WIP Picking
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
WIP Pickingd s on licen
a vi Management dispatches WIP picking tasks to qualified operators to pick material
D
Warehouse
T oni to fulfill work order requirements based on rules you define. Operators can pick the following
supply types: push, assembly pull, and operation pull.
Note: Operators deliver all picks to a subinventory and locator except for WIP picks.
Operators can optionally drop WIP picks directly to a job. This enables operators to perform
the pick and the issue in one step. This capability is enabled for push components where the
supply subinventory and locator are blank on the BOM.

Chapter 4 - Page 12
Pick Release Process
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 13
Components of Pick Release
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Components
d s onof Pickl i c n
eRelease
a vi Management uses pick release rules to store the criteria used to select sales
Warehouse
D
T oni orders for pick release. If trips are not scheduled for dock doors, then the pick release rule
also determines the appropriate staging lane. Pick release rules enable operators to select
orders based on the criteria you define during implementation.
Warehouse Management has three modes of pick release:
• Apply a release rule: Managers can apply a release rule to release sales orders. The
system automatically releases all eligible orders that meet the rule qualifications.
• Scheduled pick release: During implementation, you can build a schedule that applies a
release rule at a predetermined date and time. For example, you can choose to build a
rule that releases all DHL orders schedule for today’s date.
• Manually pick release orders: Managers can use the pick release window to manually
pick release orders.

Chapter 4 - Page 14
Over Allocation For Pick Release
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 15
Overview of Picking Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n ceRules
oPicking n
Overviewd of l i
vi rules create material allocations and direct operators to pick material from specific
a
Picking
D
T oni locations.

Chapter 4 - Page 16
Release Sequence Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Released s on licRules
Sequence
en
a vi sequence rules specify the order the system allocates eligible delivery lines. This
D
Release
T oni enables managers to control who receives inventory if a shortage exists. Warehouse
Management uses release sequence rules if inadequate material exists to fulfill multiple sales
order lines. Release sequence rules determine the lines to allocate. You can use the following
attributes to create a release sequence rule:
• Order number
• Outstanding invoice value
• Scheduled date
• Departure date
• Shipment priority
For example, if you want to ensure delivery line items with the earliest scheduled ship dates
are allocated before any other similar items, you can create a release sequence rule. You can
include the release sequence rule when you define a release rule, select the release
sequence in the Release Sales Orders for Picking window, or run a concurrent program.
You can assign a priority level to one or more attributes. You can also define if you want the
picking lines released in ascending or descending order.

Chapter 4 - Page 17
For example, if you select the ascending button for picking lines, then Warehouse
Management releases the lines by ascending order number. If you select the descending
button, then Warehouse Management releases the picking lines by descending order.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 18
Pick Slip Grouping Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Pick Slipd s on licRules
Grouping
en
a i
vcan
n i D
You create pick slip grouping rules to organize how picking lines for released sales orders
T o and manufacturing tasks are grouped on pick slips. For example, if you select delivery as the
grouping criterion, all picking lines for the same delivery are grouped together on the same
pick slip.
You can also select additional grouping attributes for grouping rules. For example, if you
select delivery and carrier as grouping criteria, picking lines for the same delivery and carrier
are grouped together on a pick slip.

Chapter 4 - Page 19
Release Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Released s on licen
Rule
a vi rules store the criteria used to select sales orders for release. If trips do not exist for
D
Release
T oni dock doors, release rules also determine the staging lane for the material; you can use the
following criteria to create release rules:
• Customer
• Ship to, Zone
• Item
• Schedule / Request Date
• Carrier
• Order Type
• Container
• Trip or Delivery
• Shipment Priority
• Project / Task

Chapter 4 - Page 20
Cross Docking
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Cross Docking
a vi
n i D
Crossdocking is the use of inbound receipts to satisfy outbound demands. You can use
T o crossdocking to match outbound shipments to scheduled receipts in advance. This enables
you to achieve faster flow-through times and optimize warehouse resources.
Oracle Warehouse Management supports two types of crossdocking
• Planned Crossdocking - matches expected receipts to a demand source
• Opportunistic Crossdocking - matches demands to received supply
You use planned crossdocking and opportunistic crossdocking for different scenarios.
Planned crossdocking works best when you know your supply in advance. It enables you to
control the throughput of your warehouse and matches known demand with expected
supplies.
Opportunistic crossdocking helps with uncertainties. It uses the rules engine to match newly
arriving supply to existing demands. This helps in cases in which a supply or demand source
is changed, modified, or cancelled.

Chapter 4 - Page 21
Cross Docking
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Cross Docking
on licen
a vi it uses the rules engine to determine a put away suggestion, Warehouse Management
D
Before
T oni checks for backordered sales order lines or WIP jobs that incoming material can fulfill if you
enable cross docking for the organization. If Warehouse Management finds an eligible line, it
prompts operator to put away the incoming material directly to an outbound staging lane or
issue it to the WIP job. This flow avoids the unnecessary material handling and material
processing.
If only a portion of the incoming material is needed to fulfill the requirement, the system directs
the operator to cross dock the material needed to fulfill requirement. The system then uses the
rules engine to find an optimal storage location for the remaining quantity.
The system checks for cross docking opportunities before it suggests storage put away
locations, if you enable cross docking for the organization. Cross docking is available only for
standard and inspection routing receipts. Depending on the parameter setting for the
organization, the system may prioritize WIP demand before or after sales order demand.

Chapter 4 - Page 22
Cross Docking
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 23
Cross Docking
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 24
Direct Ship
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s
Direct Ship
d on licen
a vi Management enables operators to ship confirm material for a sales order line
Warehouse
D
T oni without performing pick release or pick confirm for the delivery lines. To enable this feature,
select the Direct Shipping Allowed check box located on the Warehouse tab of the
Organizational Parameters window. If you enable direct ship, operators can perform regular
pick release as well as direct ship. This is useful for just in time assemble to order instances
where you send material directly from the end of the production line to a trailer for shipment.

Chapter 4 - Page 25
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 26
Pick Methodologies
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
Pick Methodologies
d
a i
vmethodologies
Pick
D refer to the different ways an operator can fulfill a group of orders. For
o n i example, an operator can pick one order or multiple orders at the same time. The type of
T picking methodology a warehouse uses depends on the operations they perform. For
example, a high volume warehouse concerned with picking speed may not use bulk picking.
Warehouse Management supports the following pick methodologies:
• Discrete picking: The application dispatches a discrete group of tasks, grouped by pick
slip grouping rules.
• Order picking: The application assigns picks for one order, job, or schedule at a time to
an operator. When an operator accepts a task for the first line of a job, schedule, or
sales order, all other picking tasks associated with that job, schedule, or order are
automatically assigned to the operator regardless of the task type or subinventory.
• Wave picking: The application dispatches tasks line by line, regardless of the picking
location, or to whom other lines on the order have been dispatched.
• Label picking: The application generates LPNs during cartonization and prints labels
prior to picking. To pick, the operator scans the LPN, and Warehouse Management
dispatches the picking task associated with the LPN. the operator can then pass the
LPN to the next operator or continue picking all material for the LPN. Warehouse
Management does not prompt the operator to drop the LPN in the staging lane the
complete the pick.

Chapter 4 - Page 27
• Case Picking: The application lets you assign case labels printed at order release to pick
operators who can perform case picks such as Pick to Belt or Pick to Pallet by scanning
multiple case labels. This enables warehouse workers to simply scan a case already
packed with items and move it directly onto a pallet or belt.
• Bulk picking: The system groups tasks to pick the same items that are sourced from the
same locator. The system displays one task that may represent picks for several order
lines. Deconsolidation of order lines occurs at pick drop. Warehouse Management

automatically splits bulk tasks based on equipment constraints during pick release.
Managers can use pick slip grouping rules to bulk pick items at pick, or choose to use
the concurrent program to bulk pick across pick waves after pick release. It is possible to
bulk pick within a delivery or across deliveries. The following bulk pick exceptions apply:
- The system does not allow bulk picking for cartonized items.
- The bulk picked item must be the same revision.
Note: If during implementation, you select order picking as the pick release
ble
methodology, and specify an order picking rule type at pick release, then the system
fe r a
s
bypasses all bulk picking checks at the subinventory and item levels, and does not bulk
an
pick any material as part of that pick release.
n - t r
• no
Paper-based picking: operators pick according to a paper pick slip printed at pick
a
release. This enables an operator to dispatch tasks to themselves when working in a
paper-assisted environment. h a s
m ฺ operator at
) todaesingle
• Cluster picking: A specified number of clusters are o dispatched
ฺcto a sales u i
l e
once. A cluster is defined as all the tasks related t G order delivery, manufacturing
job, or schedule.
o rac uden
• User-defined pick grouping: See, n @ s Pick
Defining S t Slip Grouping Rules, Oracle Inventory
User's Guide. o
ds e thi
a v i
n i ฺ d
t o us
n (to nse
i d so lice
D av
To ni

Chapter 4 - Page 28
Picking Rules Order Allocation
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
Pickingid
o
s Order
Rules l i ceAllocation
D avcan use picking rules to allocate material as follows:
You
T oni • Suggest material sourcing for order fulfillment based on:
- Subinventory
- Revision
- Lot
- Serial
• Allocate material based on rules you configure using the rules engine:
- Rules based on customer, carrier, and item handling restrictions
- Rules based on stock rotation policies
• Allocate material based on pick unit of measure to efficiently allocate picks by container
size.
• The output of the material allocation process becomes a task that includes the
subinventory, locator, revision, and lot.
• The system may also suggest serials but this is not advisable because serials may
reside in multiple LPNs makes picking difficult.

Chapter 4 - Page 29
Rules Engine Framework
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Rules Engines onFramework
l i c en
a i
vrules
n i D
The engine provides a repository for restrictions and business policies. You define and
T o implement rules directly from standard Oracle Applications windows. You select from the
elements in the lists of values to compose rules.
Note: The rules engine does not allow you to modify rules currently in use.
Based on the restrictions that you define, the rules engine performs the following activities:
• Enables directed picking and put away
• Assigns tasks to a resource with the appropriate training and equipment
• Assigns cost groups to received material
• Ensures customer compliant labeling
• Determines which operation plan to use for consolidation
You can base rules on nearly any attribute in the database, including user-defined flexfields.
You can create rules based on the following rule types:
• Put Away
• Picking
• Task Type Assignment
• Cost Group Assignment

Chapter 4 - Page 30
• Label Format Assignment
• Operation Plan Selection
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 31
Components of the Rules Engine
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Components s onof thel i c en Engine
Rules
a vi Objects are the entities that you use within a rule. They correspond to tables and
D
Objects:
T oni their attributes (or columns). Oracle Warehouse Management also includes two objects you
can use to specify constant values: Constant Character and Constant Number.
Rules: A rule is one or more restrictions that must be fulfilled to satisfy a business or
customer requirement. For picking and put away rules, you assign a sort criteria that
determines in which order the system uses a rule to suggest an allocation.
Strategies: A strategy is an ordered sequence of rules that the system uses to fulfill complex
business demands. The system selects the rules of a strategy in sequence until it fully
allocates a picking or put away task, or until it finds a cost group that meets restrictions.

Chapter 4 - Page 32
Put Away Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Put Awayd s on licen
Rules
a vi put away directs operators to put newly received material into the most appropriate
D
Directed
T oni location. You can base the rule on virtually any business process, and the rules engine
provides intelligent suggestions for put away locations for the material. Some typical
processes that put away rules are capable of modeling include:
• Direct an operator to put away an item in the same locator where other quantity of the
item already resides. This minimizes item fragmentation.
• Prohibit commingling of different items or different lots of the same item in a single
locator
• Avoid lot commingling in a locator
• Base the put away location on inspection results, the type of purchase order, or item
category
You can also use the rules engine to suggest locations to put away any item anywhere within
the warehouse.

Chapter 4 - Page 33
Picking Rules
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 34
Task Type Assignment Rules
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cenRules
oAssignment
Task Type
v i d li
a
The rules engine can identify the task type for each task that is generated by the application
D
n i
o based on user-defined criteria such as the source subinventory, locator, or item attributes.
T Task type assignment captures the skill sets and equipment required for a warehouse task
and ensures the application assigns the task to the appropriate operator.
An operator can sign onto a mobile radio frequency (RF) device, and optionally specify the
equipment they are using. Based on the operator skill set, the equipment requirements, and
the equipment capacity, the rules engine can then assign tasks to the operator. In some
cases, the application assigns tasks based on the subinventory in which the task occurs.
For example, the rules engine assigns hazardous tasks to personnel who have completed
hazardous material handling training. Another task assignment example includes limiting put
aways to top racks for those operators who signed on to a high-reach forklift.

Chapter 4 - Page 35
Rules Definition – Directed Picking
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 36
Allocation Modes
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cenModes
oAllocation
Explaining
v i d li
a
You can use the Allocation Mode field, in the Rules window, only for picking rules. The
D
n i
o allocation modes include the following:
T • No LPN Allocation
• No LPN Allocation, Prioritize Pick UOM
• Allocate LPN and Loose
• Allocate Entire LPN Only
No LPN Allocation
In this allocation mode, the rules engine considers loose and packed material equally. The
rules engine ignores LPNs because the system does not allocate picks based on LPN. If the
system allocates material in a locator where packed material exists, the operator can select
LPNs, though the operator must honor other attributes of the allocation such as particular lot
or revision numbers. If during implementation you defined a pick UOM and assigned it to the
locator or subinventory, then the system prioritizes the pick UOM based on the rule sort
criteria.

Chapter 4 - Page 37
No LPN Allocation Prioritize Pick Unit of Measure
In this allocation mode, the rules engine considers packed and loose material and does not
make allocations at the LPN level; however, the rule engine does prioritize the pick unit of
measure above the sort criteria. The system uses the pick unit of measure to minimize the
number of picks required for a task, subject to the rule restrictions. Units of measure and
conversions are defined in Inventory, and optionally assigned to the subinventory and locator.
Pick UOM is similar to the process a store clerk uses to make change for a cash transaction.
Suppose the clerk has to return $0.99 to the customer, and chooses to give them the shiny
coins first (sort criteria). The pick units of measure are the different coins: quarter, dime,
nickel, and penny.
If the first allocation mode is used, where sort criteria is prioritized before pick unit-of-measure,
then the customer might end up getting 99 brightest pennies in the cash drawer. If there are
quarters, nickels, and dimes that are just as clean and shiny as the pennies, the pick unit-of-
measure takes precedence; however, if the No LPN Allocation, Prioritize Pick UOM allocation
is used, the pick unit-of-measure is honored above sort criteria. The customer receives the ble
three shiniest quarters, then the two best dimes, and finally, the four brightest pennies, for afe r a
an
total of $0.99. If there are fewer than three quarters available, the clerk tries to find mores
dimes, or if necessary, more nickels, and finally, more pennies. n - t r
no
The only difference between this example and how the rules engine actually allocates material
a
a s
using this allocation mode is when the clerk would be unable to make exact change. If there
h
) deฺ
were only four quarters and five dimes in the clerk’s cash drawer, it would be impossible to get
m
c o Gui
exactly $0.99. The rules engine would allocate three quarters and two dimes as before, but
ฺ
e
cl ent
when it fails to find any pennies for the last $0.04, it would roll back up to larger coins, on the
r a
can if necessary to avoid customer backorder.
n @ o
S tud
assumption that while the warehouse does not want to break the larger units of measure, it
i d so this
Allocate LPN and Loose av s e
i ฺ d
nconsiders u
o and loose material equally; however, the rules engine
This allocation mode
( t o e tpacked
selects an LPN
s o c e ns material
n if it allocates from a locator that contains packed material. Instead of
allowing an
v
engine i operator i to select
dchooses a lparticular one
LPN.
of the
During
LPNs that contains the required item, the rules
implementation, you can define restrictions or sort
D a that restrict or prioritize packed material
oni
criteria or loose material. The system displays the
T allocated LPN to the operator when the task is performed, and the allocated portion of the
LPN is not available for other transactions. This allocation mode can allocate partial LPNs, so
the operator can select LPNs with mixed items. When this allocation mode allocates packed
material, the allocation is made to the innermost LPN.
Allocate Entire LPN Only

This allocation mode considers only LPNs the current allocated move order line can
completely consume. The system does not consider LPNs that contain multiple items, are
partially allocated or reserved to other move order lines, or have a quantity greater than the
required quantity. In addition, if only part of the material in the LPN meets the rule restrictions,
then the system does not allocate the LPN because the move order line cannot completely
consume it. As in the Allocate LPN and Loose mode, this allocation mode allocates only the
innermost LPN.
Exercise caution when you use this allocation mode as the only rule in a strategy, or in
conjunction with consistency requirements. When it is the only rule (or last rule) in a strategy,
the move order is not allocated if the allocation cannot completely consume the LPN. Unless
the warehouse requires that only complete LPNs are picked and sales orders are backordered
in the absence of complete LPNs, a rule that allocates packed or loose material should follow

Chapter 4 - Page 38
a rule with this allocation mode. This enables the system to allocate move orders with partial
LPNs, or loose material, if the system cannot allocate complete LPNs.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 39
Allocation Modes: No LPN Allocation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Allocation s on licNoenLPN Allocation
Modes:
a viuse the No LPN Allocation mode, allocations are not made at the LPN level. In the
D
If you
T oni above figure Warehouse Management discards lot A from consideration. This leaves 16 of lot
B, the preferred lot, in C1.1.1, and 7 in E1.1.1. Because the sort criterion places C1.1.1 before
E1.1.1, the Warehouse Management allocates all 15 of the item from C1.1.1, even though the
material is packed in an LPN, no LPN is indicated on the allocation, and the operator must
indicate the LPNs for the task.

Chapter 4 - Page 40
Allocation Modes: No LPN Allocation, Prioritize Pick UOM
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Explainingd s oNon LPNlicAllocation,
en Prioritize Pick UOM
a v i
n i D
If you use the No LPN Allocation, Prioritize Pick UOM, allocations are not made to the LPN
T o level. Honoring the restrictions, lot A is discarded from consideration. That leaves 16 of lot B,
the preferred lot, in C1.1.1, and 7 in E1.1.1. Because the pick unit of measure is prioritized
before the sort criterion, the system allocates 1 DZ (12 Ea) from C1.1.1, and 3 Ea from E1.1.1.
This creates two tasks for the two different locators. No LPN is indicated on the allocation, and
the operator must indicate the LPNs for the task.

Chapter 4 - Page 41
Allocation Modes: Allocate LPN and Loose
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oAllocate
Explaining
v i d li LPN and Loose
D a
If you use Allocate LPN and Loose, allocations are made to the LPN level, and pick unit-of-
n i
o measure is completely ignored. The rule restrictions are honored, so lot A is discarded from
T consideration. There are 16 of lot B in C1.1.1, and 7 in E1.1.1. Because the sort criterion
indicates that C1.1.1 should be allocated before E1.1.1, 15 Ea are allocated from specific
LPNs in C1.1.1. There are two allocations created, one for each LPN selected for allocation.
Note that in this example, 7 were allocated from LPN l1A and 8 from LPN L2A, because no
sort criteria or restrictions dictated which LPN to allocate first, the rules engine could instead
have allocated 6 from LPN L1A and 9 from LPN L2A.
The system could also allocate the loose material in E1.1.1 if the sort criterion did not exist.
This allocation mode can allocate both loose and packed material, and in the absence of other
sort criteria or restrictions.

Chapter 4 - Page 42
Allocation Modes: Allocate Entire LPN Only
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oAllocate
Explaining
v i d li Entire LPN Only
D a
If you use Allocate Entire LPN Only, the system allocates material at the LPN level, and
n i
o ignores the pick unit of measure. It considers only LPNs that can be completely allocated for
T the move order. It does not consider loose material.
Warehouse Management does not consider partially reserved LPNs, LPNs allocated for other
requirements, LPNs that contain more than the requested material, or LPNs that contain
multiple items.
Warehouse Management then allocates material in sequence the sort criterion determines.
Whenever part of an LPN is allocated, the system attempts to allocate the entire LPN. If it
cannot, then it discards the LPN from allocation. In this example, the rules engine first
allocates 7 of lot B from LPN L1A. Because LPN L1A has been partially allocated, the rules
engine attempts to allocate the rest of LPN L1A. Lot A is excluded because of restrictions in
the rule, and therefore, the entire LPN cannot be allocated. The rules engine discards the
initial allocation of 7 of lot B from LPN L1A and proceeds to the next LPN.
The rules engine now allocates 9 of lot B from LPN L2A, and uses the same rule to allocate
the rest of LPN L2A. Three items on the sales order line remain; however, because LPN L1A
and LPN L3A contain more than three items, the rules engine cannot completely allocate the
LPN and backorders the item if this is the only rule in the strategy. Typically, broken cases
and loose material resides at a different location in the warehouse, so a rule that allows

Chapter 4 - Page 43
allocation of loose material should follow a rule with the allocation mode Allocate Entire LPN
Only.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 44
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 45
Automated Task Dispatch, Allocation and Assignment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n Dispatch
oTask c en and Allocation
Automated
i d
vmaking l i
D a
After material allocations, the system determines the task type and dispatches it to an
o n i appropriately trained operator. The system may assign task types based on the source
T location, item, or category of the pick. Task type identification ensures operators receive picks
for which they have adequate training and are using the appropriate equipment. The system
performs the following functions before dispatching tasks to the operator:
• Group by pick methodology
• Merge for bulk picking
• Split to meet equipment capacity
• Order by pick path
When the operator logs on, Warehouse Management dispatches a task appropriate for their
skills and equipment, and in close proximity to their current location. Warehouse Management
orders all subsequent tasks for the operator according to the picking order on the storage
locator. Picking order determines the path the operator traverses through the warehouse to
retrieve material for picking. You establish picking order during implementation.

Chapter 4 - Page 46
WMS Control Board
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
WMS Controls onBoardl i c en
a i
vWMS
n i D
The Control Board enables managers to view workloads across the entire warehouse,
T o manage exceptions, and review, release, reassign, and re-prioritize tasks. The WMS Control
Board enables managers to do the following:
• View tasks
- Unreleased
- Pending
- Queued
- Dispatched
- Active
- Loaded
- Completed
- Exception
• Manage task assignments
- Add task
- Remove task

Chapter 4 - Page 47
- Update task status
- Update task priority
- Update resource assignments
- Task sorting
Note: At pick release (Sales Order or WIP), managers can choose to plan the release of
tasks. If a manger chooses to plan tasks, the system creates pick tasks with a status of
Unreleased, so operators cannot perform or execute the tasks immediately. If managers do
not want to plan tasks, the system creates pick tasks with a status of Pending.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 48
WMS Control Board
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 49
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 50
Advance Pick Load
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 51
Advanced Pick Load Setup
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 52
Advanced Pick Load Page Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Advancedd s on Load
Pick l i c n
eSetup
a vi implementation, you can optionally use the Pick Load Page Setup window to arrange
During
D
T oni the way mobile pages display.
General Fields Tab
You set up the behavior of the mobile fields in the General Fields tab. The behaviors are as
follows:
• Hide fields
• Display Only, No Confirmation
• Show both fields, Confirm second with LOV/No LOV
• Decide if data defaults automatically – Single Line Input
LPN Fields Tab

The LPN Fields tab determines how the system retrieves, transfers, nests and transacts
material on the Pick Load page. You can set different configurations for loose picks and fully
consumable LPN scans. A fully consumable LPN is an LPN a pick completely consumes. If a
pick partially consumes an LPN, the remaining material stays in the LPN. After you enter the
pick information, the following fields for moving the pick contents are displayed:
• Transfer LPN: Transfers the contents of the LPN to another LPN (Transfer LPN).

Chapter 4 - Page 53
• Into LPN: Nests the LPN within another LPN.
Note: You can choose to configure the pick load page differently for serial controlled, and
non-serial controlled items.
Buttons Tab
Once an operator enters and confirms pick information, the system provides a number of
actions to perform. You can use the Visible check box to show or hide buttons. If you choose
to hide the buttons, the operator cannot perform the associated action.
You can also define the display order for the buttons. The available choices are
10,20,30,40,50 and 60. The button with the lowest number appears first on the mobile page.
The options are as follows:
• Load: Enables the loading of the picked material.
• Load and Drop: Enables loading and then suggests a drop for the picked material.
• Attachment: Allows any attachment. ble
• Exception: Enables operators to perform and record any picking exceptions. fe r a
ans
• Skip Task: Allows operators to skip a task.
n - t r
• Info: Provides information about the picking document.
a no
Page Level h a s
m ) deฺ
This page enables you to control the behavior of attachments,
ฺ c o catch
u iweight, and exceptions
when picking partial lot quantity. e
cl ent G
r a
• Attachments: The choice available foro
n @ S t ud
display are:
- Always: The attachmento is displayed.
button is always
- By Request: The v i d s t h
attachmentebutton displays by request.
i ฺ d a us is never displayed.
- Never: The n attachmentt o buttons
n
• Catch Weight (toEntry:nsThee available choices are:
o e
d- s Hide: Catch
lic weight entry is hidden.
v i
a - Mandatory: Catch weight entry is mandatory.
n i D
To - Optional: Catch weight entry is optional.
• Bypass Exception When Picking Partial Lot Quantity behavior: The available choices
are:
- No: Prompts for an exception when an operator tries to pick a partial amount of the
task. This facilitates picking lots out of order.
- Yes: Does not prompt for the exception when an operator tries to pick a partial
amount of the task.
• Allow Negative Balance: Operators can pick a quantity in excess of available to transact.
This is allowed for plain and lot controlled items.
• Show Task Quantity in Pick UOM: Suggests to operators the pick quantity during pick
load in terms of the standard pack UOM.
• Allow Over Pick without Exception: In some warehouses over picking is not treated as
an exception. If this is enabled the operator can over pick without invoking an exception.
If set to No, then the over picking is treated as an exception.

Chapter 4 - Page 54
• Allow under pick without exception: In some warehouses under picking is not treated as
an exception. If this is enabled the operator can under pick without invoking an
exception. If set to No, then under picking is treated as an exception.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 55
Advanced Pick Load Use
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 56
Advanced Pick Load – Task Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Advanced d s on Load
Pick l i c e–nTask Setup
a i
vtask
The
D filter window enables you to determine which tasks the picking page can perform. If
o n i you include a task type, then the picking page can perform the task type. You can use task
T filters to control the types of tasks the system dispatches to operators. For example, you can
create task filters so an operator receives internal order pick tasks, but not replenishment
tasks.

Chapter 4 - Page 57
Advanced Pick Load Menu Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Advanced d s on Load
Pick l i c n
eMenu Setup
a v i
n i D
Form function parameters control the appearance and behavior of the pick load page. The
T o Advanced Pick Load Setup page lists the parameters you can use. The cache parameter
determines if the system rechecks the task user interface and filter setup for changes. During
testing set this parameter to no, but for performance reasons, set this parameter to yes in the
production environment.

Chapter 4 - Page 58
Advanced Pick Load Exceptions
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
Advancedd o
sPick Load
l i ceExceptions
i
av types determine the changes an operator can make.
D
Exception
T oni

Chapter 4 - Page 59
Advanced Pick Load - Execution
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d
Advanced s on Load
Pick l i c e-nExecution
a vi can choose to scan either the LPN or locator. The system automatically
D
An operator
T oni recognizes which field the operator scanned. If the operator scans the locator, then the LPN
field appears. If the operator scans the LPN, then the locator field and the LPN field appear
and the operator can proceed to the next field.

Chapter 4 - Page 60
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 61
Replenishments in a Warehouse
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on inlicaeWarehouse
Replenishments
d
n
a vi
Warehouses require a picking area closer to outbound staging that is optimized for picking
n i D
outbound orders when:
T o
• Items are sourced in bulk but fulfilled in smaller handling units, or they have a large
warehouse and high-order volume.

Chapter 4 - Page 62
Replenishment Challenges
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on Challenges
Replenishment l i c en
a vithat is optimized for unit picking stores material in eaches or cases, and must be
D
A pick
T oni compact to reduce travel time. The pick has limited locators and limited capacity, and you can
only stock a limited number of items within this area. The selection of locators for times in the
pick area depends on the item demand profile. Dedicated locators are used for items with high
uniform demand. Floating locators on the other hand are used for volatile demand items. The
bulk or reserve area is optimized for storage. Replenishment in this area must be in full
standard packs, pallets, cases, etc. Pick tasks are dispatched only if enough stock is available
in the pick area. This requires careful synchronization between replenishments and pick
release.

Chapter 4 - Page 63
Strict Pick UOM Allocation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oUOM
v i d
Strict Pick li
Allocation
D a
Strict pick allocation prevents the splitting of pallets or cases in the bulk or reserve areas when
n i
o sufficient quantity does not exist in the pick area. For example, in Release 12, if you have a
T sales order for quantity of 18, and an on-hand quantity of 2 eaches in the pick area, then the
application would automatically split the cases into 16 eaches during allocation. In Release
12.1 using Strict Pick UOM, the application allocates the 2 eaches, and allocates 1 case or 10
eaches to fulfill the order. Case splitting no longer occurs and back ordering may or may not
occur depending upon rules.

Chapter 4 - Page 64
Strict Pick UOM Allocation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oUOM
v i d
Strict Pick li
Allocation
D a
Strict pick UOM ensures that picks occur in full standard packs and minimizes material
n i
o handling. The application considers demand that cannot be fulfilled with the lower pick UOMs
T for replenishment. Strict pick UOM is useful for warehouses that stock material in standard
packs.

Chapter 4 - Page 65
Pull Replenishment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Pull Replenishment
a i
vreplenishment
n i D
Pull is initiated during pick release for items with high uniform demand when:
T o • There is not enough stock on hand in the pick face.
• Material is pulled from the reserve area to the pick area instead of picking directly from
the reserve area.

Chapter 4 - Page 66
Pull Replenishment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Pull Replenishment
a viare a lot of benefits to pull replenishment. The system does not back order lines if the
D
There
T oni material does not exist in the forward pick face, or pick material from case or bulk depending
on the rules. The system automatically creates replenishment tasks when the forward pick
face does not contain enough onhand quantity to fulfill an order. This is useful in a standard
pack environment.

Chapter 4 - Page 67
Push Replenishment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Push Replenishment
a i
vreplenishment
n i D
Push is used for items with non-uniform demand. It enables you to replenish
T o the pick area based on future demand visibility. You execute replenishment tasks prior to pick
release.

Chapter 4 - Page 68
Push Replenishment
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Push Replenishment
a i
vreplenishment
n i D
Push is useful for distribution centers that stock large numbers of items with
T o irregular demand and limited numbers of items in forward pick locations. You perform push
replenishment prior to pick release to replenish forward pick locators in anticipation of
demand. Push replenishment can be conditional. For example, you can replenish only items
with a minimum of five (5) order lines. Push replenishment also requires a cleanup of the
forward pick area when demand for items drops.

Chapter 4 - Page 69
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 70
Catch Weight Description
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
Catch Weight
d
a viweight pricing is a term the grocery industry uses when pricing is based on a unit of
Catch
D
T oni measure that differs from the packaging or selling unit of measure.
For instance, you purchase one package of meat; but you pay based on the weight of the
package. The packaging, or primary unit of measure, is each while the pricing, or secondary
unit of measure is pounds.
That secondary quantity is used only for pricing. Warehouse Management tracks on hand
inventory balances and performs transactions in the primary quantity. An operator can enter
the secondary quantity anytime during or after the picking process prior to shipment.

Chapter 4 - Page 71
Catch Weight Benefits
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s onBenefits
Catch Weight l i c en
a viweight pricing is not the full dual unit of measure support Oracle Process Manufacturing
D
Catch
T oni uses. Warehouse Management uses the secondary quantity for pricing only, and not to
maintain on hand balances.

Chapter 4 - Page 72
Catch Weight Item Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Catch Weight
onSetup
l i c en
a vi catch weight, you must define the item as catch weight controlled. To do this, you set
D
To setup
T oni the Pricing UOM to Secondary on the Main tab of the Master Item window. You then enter the
Secondary UOM used to capture pricing. For instance, the secondary UOM for foods or
metals might be Pounds.
You can also define positive and negative deviation factors. These indicate the maximum
amount Warehouse Management allows the pricing and secondary quantity to deviate from
the standard secondary quantity expected when it uses a nominal conversion from the primary
quantity. For instance, a roll of steel may typically weigh 2000 pounds, and it often deviates
plus or minus 10%. Therefore, during implementation you could enter a pricing quantity of
anywhere from 1800 to 2200 pounds for a single pallet, and the system would prevent
operators from entering a quantity outside that range when processing transactions.
The defaulting method indicates if the secondary quantity should be defaulted based on the
nominal conversion, or if operators must enter the secondary quantity. If you set defaulting to
yes, the system does not require operators to enter a secondary quantity to perform ship
confirm.
For more information on catch weight see: Main Attribute Group, Oracle Inventory User’s
Guide, and Setting up Catch Weight, Oracle Warehouse Management User’s Guide.

Chapter 4 - Page 73
Catch Weight Setup
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Catch Weight
onSetup
l i c en
a vi to defining the item attributes, you must perform other setup steps. You must
D
In addition
T oni define the nominal conversion between the tracking and pricing unit of measure. This is how
the system knows a pallet of steel weighs 2000 pounds. You use Inventory to define UOM
conversions. For more information on conversions see, Defining Unit of Measure
Conversions, Oracle Inventory User’s Guide.
You must also define the pricing UOM on the price list used for the orders. An operator can
enter the catch weight information during picking, or at any time after pick load, but before
shipment. In the Advanced Pick Load page, the secondary quantity is captured in the Sec Qty
field. You can set the field to Required, Optional, or Hidden.
Finally, the operator must verify the order line workflow process indicates the line is re-priced
during order fulfillment, so the price is recalculated at shipment.

Chapter 4 - Page 74
Catch Weight Use
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Catch Weight
onUselicen
a vi on the configuration of the Advanced Pick Load page, the secondary quantity may
D
Depending
T oni be required or optional during picking. Operators can also enter catch weight information in
the Catch Wt Entry page if the catch weight quantity is not captured during picking. Operators
can enter information in the Catch Wt Entry page while the task is loaded or after it is dropped.
The operator must enter catch weight information prior to shipping.
The Catch Wt Entry page displays loaded or staged tasks that do not have the associated
catch weight information. Operators can use this page to identify which LPNs contain weighed
material. The Catch Wt Update page displays all lines of loaded or completed catch weight
tasks.
If the operator uses Direct Ship, then they cannot enter the catch weight information during
the picking process, on the Catch Wt Entry page or Catch Wt Update page; however,
Warehouse Management allows the operator to directly enter the catch weight information
during loading.

Chapter 4 - Page 75
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 76
Consolidation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
Consolidation
d
a vi
Consolidation enables multiple operators to drop material assigned to a delivery in to the
n i D
same locator or LPN prior to placing the consolidated load in a staging lane.
T o
Note: If necessary, operators can ship material directly from the consolidation location.

Chapter 4 - Page 77
Consolidation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
son licen
StagingidMoves
v
•a Moves staged LPNs to another staging, consolidation or packing locators.
D
T oni • Facilitates movement within shipment area for weighing, packing, or further
consolidation.
• System suggested staging locators.
LPN Mass Moves

• Moves staged LPNs from one subinventory and locator to another subinventory and
locator.
• Shows the number of LPNs available at source subinventory and locator.

Chapter 4 - Page 78
Consolidation Setup
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 79
Consolidation Inquiry
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s
Consolidation
d on Inquiry
l i c en
a i
vmaterial
Once
D is consolidated, it is ready for further processing, such as packing, shipping, or
o n i loading. It is essential operators know the status of consolidated material so they can
T determine the eligible material.
Consolidation Locators Inquiry

The Consolidation Locators Inquiry page enables operators to view consolidation locators with
material in various states, so they can determine which material is ready for further
processing. Operators can perform three inquiries in the Consolidation Locators Inquiry mobile
page.
• Complete Locators- The Complete Locators mobile page enables operators to view
consolidation locators with completely consolidated material for at least one delivery.
• Empty Locators- The Empty Locators mobile page enables operators to view empty
consolidation locators.
• Non-Empty Locators- The Non-Empty Locators mobile page enables operators to view
consolidation locators that contain at least one staged LPN. It includes locators with
either completely or partially consolidated material.

Chapter 4 - Page 80
Consolidated LPN Inquiry
The Consolidated LPN Inquiry page enables operators to view LPNs with deliveries in various
states so they can determine which materials are ready for further processing. Operators can
perform a Consolidated LPN Inquiry on any staged LPN, delivery, order number, or any
combination of the three. Operators can perform the following inquiries in the Consolidated
LPN Inquiry window:
• Find LPNs- The Consolidated LPNs page enables operators to view consolidated
LPN(s) depending on the query criteria. It displays the following information:
- Subinventory and locator
- Number of LPNs
- Delivery number
- Consolidation status
- Order umber e
Note: If the LPN contains material belonging to more than one order, it displays multiple r a bl
orders. s fe
- t r an
Query by Delivery on
Query by delivery displays all LPNs for a particular delivery. s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
av i
ni D
To

Chapter 4 - Page 81
Cartonization
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Cartonization
on licen
a vi Management uses cartonization to suggest the best packaging configuration for a
D
Warehouse
T oni group of items. The system presents packaging suggestions to operators in the following
ways: automatically generating LPNs, printing container and shipping labels, and during tasks.
Oracle Warehouse Management uses cartonization for the following tasks:
• Sales order and manufacturing picking (pick release)
• Cartonization prior to WIP completion
• Mobile bulk packing
• Cartonization at task release
Cartonization can segregate items by categories you identify during implementation based on
different packaging requirements. For instance, refrigerated goods may require a particular
type of insulated cooler, while miscellaneous goods can be packed into any standard
corrugated cardboard box. In addition, the warehouse may use several sizes of each type of
container. You can also set minimum fill percentages for containers, below which, the system
suggests a smaller container.
You can create multiple levels of packaging, along with the requisite labels, so operators can
generate labels in a single operation, for inner cartons, outer cartons, and pallets. Operators
can halt packing with a hierarchy of containers midway, and then continue again at a later

Chapter 4 - Page 82
point. Operators can pack material in a storage container during receipt, and pack it again
during sales order picking into a final shipping container.
All these considerations, in addition to the item dimensions, weight, and volume in comparison
to the physical attributes of the container, are made when the system selects the container
type and quantity to use.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 83
Cartonization
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s onSetup
Cartonization l i c en
a vifor cartonization uses Category and Category Set functionality. There are two pre-
D
Setup
T oni seeded category sets:
• Contained Item
• Container Item
Within these category sets, you create categories that model the different types of packaging
used for outbound loads. For example, miscellaneous loose material requires a simple
corrugated cardboard box. These boxes, and the items that use these boxes, are given the
category MISC within the category sets Container Item and Contained Item.
For more information on categories and category sets see Overview of Item Categories,
Defining Categories, and Defining Category Sets, Oracle Inventory User’s Guide.

Chapter 4 - Page 84
Packing
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Packing d s on licen
Material
a vi involves transferring of loose items or LPNS into an LPN. Operators can pack items
D
Packing
T oni either on receipt, while they reside in inventory, or during outbound shipment to customers.
Operators can use both the desktop and the mobile device to pack material. While desktop
packing allows packing for inbound and outbound material, mobile packing allows packing for
outbound material only. The benefits of packing include:
• Consolidation of items into suitable containers based on criteria such as item, delivery,
sales order, or warehouse location
• Confirmation and record the contents of containers while packing
• Transaction by container
• Protection of packed items from damage
Packing Options
Warehouse Management includes the following packing options:
• Pack transactions
• Unpack transactions
• Split transactions

Chapter 4 - Page 85
Packing Workbench Flow
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
Packing d s o
Flow l i ce
v i
D •a Query eligible items: Look for eligible items to pack.
T oni • Move eligible items to packing station.
- Man to goods: Look for eligible items and move them to the packing station.
- Goods to man: Items move to the packing station on a conveyor.
• Packing transaction: Use the mobile device or the desktop application to execute a
packing transaction.
• Close LPN: Confirm the packing and the system performs the following actions:
- Prints a label for the packed LPN
- Performs an implicit move of contents to the packing station when you close the
LPN

Chapter 4 - Page 86
Eligible Material
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Eligibleid son licen
Material
D
Theavpacking workbench enables you to pack material in receiving, but not delivered to
T oni inventory, or material picked for a sales or internal order that has not shipped.
• Inbound: If the transaction source is inbound, received material that resides in a
receiving subinventory is eligible for packing. Operators can use the Packing Workbench
to pack loose material received through the desktop into LPNs.
• Outbound: Staged material that resides in a staging subinventory is eligible for packing.
Operators can perform packing transactions after pick drop and prior to ship confirm.
Material can be consolidated at pick drop into an LPN or locator prior to packing.

Chapter 4 - Page 87
Mobile Packing
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 88
Packing Workbench and Outbound Logistics
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on liceand
PackingdWorkbench
n Outbound Logistics
To a vi the Packing Workbench to pack outbound material, operators must perform packing
use
D
T oni transactions after pick drop, but prior to pick confirm. Operators can consolidate material at
pick drop into an LPN or locator, prior to packing. Operators can then move packed LPNs to a
staging lane.
Note: The packing workbench allows you to scan GTIN codes instead of internal item
numbers.

Chapter 4 - Page 89
Packing Workbench and Inbound Logistics
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Packing d s on liceand
Workbench
n
Inbound Logistics
a v i
n i D
To use the Packing Workbench to pack inbound material, the packing station must reside in a
T o Receiving subinventory. Operators can perform packing transactions any time after material is
received and prior to movement into inventory.
GTIN in the Packing Workbench

an operator can scan a GTIN to perform packing transactions. The information that displays in
the Packing Workbench depends on the type of GTIN scanned.
• If an operator scans EAN-8, EAN-13, or UCC-12 then the item displays.
• If an operator scans EAN.UCC-14, then the item and UOM corresponding to the
packaging configuration displays.

Chapter 4 - Page 90
Packing Initialization
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Packing d s on licen
Initialization
a vi packing tasks the operator enters the transaction source, and then a packing
D
To perform
T oni process such as pack, split, unpack, or reconfigure. Next the operator specifies additional
parameters such as each pack, serial triggered or kitting.
• Each pack: This option always defaults the pack quantity to 1. This is useful if the
operator must scan every unit.
• Serial triggered: This option enables the operator to scan the serial number. Warehouse
Management does not require the operator to enter the item if the serial number is
unique.
• Kitting: If an order was placed for a PTO item, the Packing Workbench displays the BOM
when an operator scans a component of the BOM to assist the operator in building the
kit.

Chapter 4 - Page 91
LPN Pack
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 92
LPN Unpack
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 93
LPN Split
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 94
LPN Reconfiguration
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
LPN Reconfiguration
d
Toa vi LPN reconfiguration, an operator scans an LPN and chooses either Merge up or
perform
D
T oni Breakdown to un-nest the LPN. Breakdown results in one or more child LPNs. Merge up
consolidates the contents of all inner LPNs into the outermost LPN.

Chapter 4 - Page 95
LPN close
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 96
DFI and the Packing Workbench
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 97
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 4 - Page 98
Overview of Shipping
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s on licen
DefiningdShipping
a vi is when picked and packed material leaves the warehouse to fulfill an order.
Shipping
D
T oni Shipment confirmation is when an operator confirms all LPNs picked and staged for a
particular order or trip are loaded onto a truck.
You can use the following four methods to ship your material:
• Quick Ship
• LPN Ship
• Dock Ship
• Direct Ship

Chapter 4 - Page 99
Staging Lanes
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oStaging
d
Explaining
v i li Lanes
D a
A staging lane is a locator used to stage outbound shipments before vehicle loading. To
n i
o create a staging lane, define a locator with the classification type Staging Lane. You can
T assign multiple staging lanes to one dock door. You can also specify a default shipping lane
for the organization during implementation.

Chapter 4 - Page 100
Setting Up Staging Lanes
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oStaging
d
Explaining
v i li Lane Setup
D a
You do not have to define a new subinventory specifically for staging lanes. You can use an
n i
o existing subinventory and define a staging lane locator.
T

Dock Doors
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oDock
v i d
Explaining li
Doors
D a
A dock door is a locator used to load outbound shipments onto a vehicle. If the organization
n i
o uses Shipping Execution or Transportation to plan trips for departures from the warehouse,
T operators can schedule appointments for dock doors to load LPNs for a specific trip. Dock
doors are modeled as locators in Warehouse Management. To create a dock door, define a
locator with the classification type Dock Door. You can associate a dock door with many
staging lanes.

Setting Up Dock Doors
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oDock
v i d
Explaining li Setup
Door
D a
Like staging lanes, you do not have to define a new subinventory specifically for dock doors.
n i
o You can use an existing subinventory and define a dock door locator.
T

Staging Lane to Dock Door Relationship
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
sonto Dock
StagingidLane l i cenDoor Relationship
D avan operator performs a pick, the system directs the operator to deliver the item to a
After
T oni specific staging lane, which depends on the dock door to be used to load the transportation
vehicle. For example, the organization may use an overnight shipping service and a local
courier. Each service is assigned a dock door to pick up deliveries. If dock door 1 is assigned
to the overnight service, then one (or many) of the staging lanes is used specifically for
overnight shipments. If the order is an overnight shipment, the system directs the operator to
deliver the order a staging lane associated to the overnight dock door.
This setup is useful only if you use dock door appointment scheduling. If a released line is
assigned to a trip with a dock appointment, then the system directs the operator to drop the
load in a staging lane assigned to the dock door. If the sales order line is not associated with a
trip, the system uses the put away rules engine to determine the staging lane, or directs the
operator to the staging lane specified during pick release.

Setting Up Staging Lane to Dock Door Relationships
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oStaging
d
Explaining
v i li Lane and Dock Door Relationships
D a
During implementation, you can use the Associate Staging Lanes to Dock Doors window to
n i
o associate dock doors to staging lanes. You select a dock door from a list of values, and then
T define a sequence number for each staging lane to associate with the dock door. If there are
multiple staging lanes associated to the dock door, then the system uses the staging lanes for
picking per the sequence number. You then assign the subinventory and staging lane to the
dock door.
Note: You can skip this step for your implementation if you do not use dock door
appointments

Staging and Consolidation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
sonConsolidation
Stagingidand l i cen
D avan operator picks an order, Warehouse Management directs the operator to the
After
T oni appropriate staging lane and consolidation area. The staging and consolidation area depends
on the customer order and the specific shipping requirements. Typically as part of outbound
planning, an order is linked to an outbound staging lane, which is linked to a dock door.
The system determines consolidation requirements, based on the pick item physical attributes
and customer requirements. The easiest method of consolidating is to consolidate by LPN;
however, this requires that each container has an LPN.

Loading and Shipping
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Loading d s
and
onShipping
l i c en
a vi beginning the loading process, an operator must scan the dock door, and then scan
D
Before
T oni each order into the staging lane. After an operator scans and consolidates orders Warehouse
Management prompts the operator to scan the desired dock door. The system then prompts
the operator to scan the first LPN and load it onto the designated vehicle.
Note: Operators can use either the mobile user interface or the desktop shipping transactions
window to ship loaded material. Operators can also bypass loading and ship material in the
shipping transactions window any time after picking.

Trips and Trip Stops
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oTrips
Explaining
v i d li Trip Stops
and
D a
A trip is a group of deliveries shipped on the same truck. A trip stop is created for each pick up
n i
o and delivery address on the trip. For example, a customer places four different orders on the
T same day, three of the orders have the same delivery location, and one differs from the rest.
All four orders are part of the same trip, but there are two trip stops, one for the first location
and one for the second location.
Note: Trips and trips are optional. You are not required to set them up or use them.

Ship Confirmation
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Ship Confirm
on licen
a i
vshipment
n i D
The confirmation process is the final step in the outbound process. an operator can
T o create shipments on the mobile device for individual order lines, for order lines grouped into a
common destination, and for entire trips that consist of multiple deliveries. All material is
packed into containers uniquely identified by an LPN assigned during the pick confirmation
process. Shipment confirmation then confirms all LPNs picked for a particular order or trip are
loaded onto a truck.
• Delivery: A collection of order lines with same customer and delivery address. A delivery
can have many different items, and can span multiple orders, if the orders have the
same customer and delivery address. One order can be split among different deliveries.
• Trip: A collection of deliveries shipped on the same outbound truck.
• Trip Stop: Each pick up and delivery address on the trip.
• Ship Set: A group of order lines linked by a common number, for which the full quantity
must ship together.

Direct Shipping
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oDirect
d
Explaining
v i i
lShipping
D a
Direct Ship does not require an operator to perform pick release or pick confirm to ship
n i
o confirm material for a sales order line. The system requires an LPN for all material to ship.
T operators can also unload LPNs from a truck. The delivery lines must be either Ready to
Release, or Backordered, and the organization must be direct ship enabled.
The system checks only for missing items on the trip if an operator created trips, deliveries, or
ship sets prior to shipping. The system does not check for missing LPNs because staged
material does not exist.
If you pre-reserved LPNs to a sales orders through an ATO, LPN completion, flow completion,
or manually reserved in the reservation window, you do not need to enter the sales order
information during direct ship.

Dock Door Ship
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oDock
v i d
Explaining li Ship Flow
Door
D a
An operator scans the dock door to begin the dock door shipping process. Because the dock
n i
o door is scheduled for a trip through the dock appointment calendar, the system knows which
T LPNs to load onto the dock. The system directs the operator to the staging lane that contains
the LPNs to load. If LPNs or items are missing after the operator completes the load, the
system directs the operator to the missing LPN(s) or indicates the item(s) to pick.
Note: Dock Door Ship requires that created trips exist, and that trips are scheduled to the
dock door.

LPN Ship
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oLPN
v i d
Explaining li
Ship
D a
An operator can use LPN ship with the mobile user interface if dock door appointments are
n i
o not used. the operator scans a dock door, but since no appointment exists for a trip, the
T system does not direct the operator to a staging lane. Instead, the operator can select any
staged LPN for loading at the dock. The operator continues to scan LPNs until the loading is
complete. the operator then selects Ship Confirm to close the shipment.
At this time, if a delivery, trip, or ship set exists, the system ensures the entire delivery, trip, or
ship set is loaded. If LPNs or items are missing after the operator completes the load, the
system directs the operator to the missing LPN(s) or indicates the item(s) to pick.
Note: The system checks only for missing LPNs or items on the trip if an operator created
trips, deliveries, or ship sets prior to shipping.

Quick Ship
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oQuick
d
Explaining
v i i
lShip
D a
An operator can use Quick Ship to ship an entire delivery without confirming the individual
n i
o LPNs. Quick ship requires operators to setup deliveries. Prior to performing a Quick Ship, an
T operator must stage all of the order lines on the delivery. The material statuses of the staging
subinventory, locator, lots, and serials contained in the delivery must allow the shipment
confirmation transaction.
Note: Serialized items at Sales Order Issue items cannot be included on the delivery.

Shipment Planning
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oShipment
Overview
v i d of li Planning
D a
Warehouse Management enables you to access the Shipping Transactions form, a
n i
o consolidated shipping workbench that enables you to query on shipping information and plan
T your shipments.
Note: The management of trips, stops, and dock management are optional.

Dock Door Appointments
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oDock
v i d
Explaining li Appointments
Door
D a
An operator must set up a dock door appointment for a trip, for the system to suggest the
n i
o appropriate staging lane for the material prior to pick release. After the operator sets up the
T appointment at pick release, the system checks the trip to determine if any dock door
appointments exist, and then assigns a staging lane to the pick up trip stop.
Note: Dock doors and staging lanes must be set up prior to defining dock door appointments.
For more information setting up dock doors and staging lanes see Defining Stock Locators,
Oracle Inventory User’s Guide.
After an operator assigns the trip to a staging lane and a dock door, the actual shipment
loading resembles LPN Ship except, selecting the dock door with appointment initiates the
process. Instead of displaying all of the available dock doors, the system displays the dock
doors with open trips during the current time.
A trip that does not have an appointment must be shipped using LPN Ship. operators can use
Dock Door Ship or LPN Ship if an appointment exists.

Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen Considerations
oImplementation
Explaining
v i d li
a
If your implementation utilizes auto-pick confirm, the material the operator picks must be
D
n i
o loose. If the material is packed in LPNs, then the system drives loose quantity negative and
T the LPNs remain in inventory. Also, the operator must either use Quick ship or ship through
the shipping transactions desktop window. operators cannot perform ship confirm in the other
Warehouse Management mobile pages.

ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oImplementation
v i d
Explaining li Considerations
D a
When you define a locator, you are given the opportunity to determine capacity constraints
n i
o including volume and weight. It is recommended that you do not define capacity constraints
T for locators that are Staging Lanes or Dock Doors. Material allocations fail if the staging lane
or dock door is past capacity.

Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Summary
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Summary
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

ble
fe r a
ans
n - t r
a no
a s
) deฺ
Managementc m
o GuWavei Planning
l e ฺ t
o rac u5 den
Chapter
o n @ s St
v i ds e thi
i ฺ d a us
n t o
n (to nse
i d so lice
a v
D
T oni
R12.x Oracle Warehouse Management Wave Planning

Chapter 5 - Page 1
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 2
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 3
Objectives
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 4
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 5
Overview of Wave Planning
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cPlanning
oWave en
Overviewd of l i
vi Warehouse Management fully supports Wave Planning to group orders and plan the
a
Oracle
D
T oni work in a warehouse. Wave Planning enables better visibility and control during order
fulfillment. Wave planning provides real-time monitoring and exception reporting and flexibility
during the order fulfillment process. Using wave planning, you can:
• Create, plan, and release a wave in one step or multiple steps
• Schedule the entire wave planning process to be run at certain intervals based on
specified criteria
• Monitor and correct exceptions that may occur (exception handling)
A wave is a grouping of orders and lines for processing as a set, and is defined by a common
set of attributes. Examples of common order attributes include:
• All orders with a dock appointment within the next x number of hours
• All UPS orders
• All high priority orders
• Specific carriers

Chapter 5 - Page 6
The Wave Planning Process
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
The Waved o
sPlanning
l i e
cProcess
i
avwave planning process consists of:
D
The
T oni 1. Creating a Wave
2. Planning a Wave
3. Releasing a Wave
4. Monitoring a Wave

Chapter 5 - Page 7
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 8
Creating a Wave
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Creatingdaso
n
Wave lice
n
a i
vfirst
The
D step in the wave planning process is creating a wave. When you create a wave, you
i
on select the criteria that determines the sales orders and sales order lines that are eligible for
T fulfillment. For example, you can create a wave that enables you to pick all orders with a dock
appointment within the next x number of hours, all UPS orders, or all high priority orders.
Estimated Start Time

The Estimated Start Time is the projected time that users will start picking the orders to fulfill
the wave. The application defaults the current system time as the estimated start time. You
must edit this time to accurately reflect the estimated picking start time. The planning process
considers the estimated start time when performing fulfillment and labor planning. If you try to
plan a wave if the estimated start time occurs in the past, then the application will not allow
you to plan the wave.
Selection Criteria
You can select simple selection criteria to create waves based on order, customer, carrier,
item, trip, delivery, and dock door appointment. For example, you can create a wave that picks
all orders with dock appointments within the next x number of hours, all UPS orders, or all
high priority orders.

Chapter 5 - Page 9
You can also select advanced criteria for creating and releasing waves. Advanced criteria are
similar to rules you write using the WMS rules engine. They enable you to specify additional
conditions which the simple criteria tab may not return. You can write criteria based on the
objects delivery, wave, sales order, trip, sales order line, and item. These objects have
individual parameters like order revenue. For example, you can select criteria to pick all single
line orders or pick orders when a total tare weight or dollar value is greater than a specific
threshold. You can use any combination of selection criteria to meet your needs. This enables
you select the exact type of orders to fulfill.

You can also create multiple waves with different selection criteria. When you create multiple
waves you can compare and contrast waves. This enables you to you to release the most
optimum wave to the warehouse.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 10
Release Criteria
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Release d s on licen
Criteria
a i
vyou
n i D
After determine the order selection criteria, set the criteria used to release the wave (sales
T o orders) to the warehouse for fulfillment using the Wave Options tab. You determine whether or
not to create deliveries at wave release, set the picking and staging locations, as well as the
release sequence for the picks. You can also choose the allocation method to use for your
orders.
The allocation method you select determines from where the material will be sourced. You
can choose to source the material from Inventory, Cross dock Only, Prioritize Inventory, or
Prioritize Cross dock. If you choose Inventory Only, then only material which resides in on-
hand locations will be considered to fulfill orders. Inbound material which is available through
cross docking will not be considered to fulfill orders. If you selected CrossDock Only, then only
inbound material will be considered to fulfill the sales order demand. On-hand material will not
be considered. If you choose either Prioritize Inventory or Prioritize CrossDock, then both
inbound material and on-hand material will be considered, but in a different order. The order of
the material considered to fulfill the allocations depends on your selection. For example, if you
choose Prioritize Inventory, then the application checks all supply in on-hand locations before
checking inbound material to fulfill demand.
After you have selected the release criteria, you can create the wave online or use a
concurrent request. You can also choose to Firm, Plan, or Release the wave during the initial
creation process.

Chapter 5 - Page 11
Note: If you want to perform pull replenishment for the wave, then select the Pull
Replenishment check box and ensure that the appropriate setup steps are complete.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 12
Wave Templates
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Wave Templates
a i
vcan
n i D
You create and save a wave template to be reused. When you create a wave template,
T o you set the selection and release criteria. You can create wave templates to be used for
different circumstances. For example, you can create a wave template which selects orders
for a particular customer. To reuse a wave template, perform a query for the template name.

Chapter 5 - Page 13
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 14
Planning a Wave
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Planning ao
s n
Wave lice
n
i
vyoud
D a
After create the wave, use the Plan Wave window from the Wave Workbench to plan the
i
on wave. Planning a wave includes selecting criteria that further defines the fulfillment process.
T For example, you can set default actions to occur when stock is unavailable, or reserve
material so it is not allocated or promised to other orders.
Note: You reserve material and then allocate it. The material is allocated only after the wave
is released.
Before you release the wave, you can perform material fulfillment planning and labor planning.
Fulfillment planning verifies that enough material is available to fulfill the sales orders within
the wave. Labor planning establishes the number of workers required to perform the work in
the wave, and checks the existing workload within the warehouse.
Warehouse Management also offers two types of planning:
• Rules-based planning
• Availability check planning.
When you use rules-based planning, the application simulates the rules engine allocation and,
if enabled, the labor to perform the picks. When you use availability check the application
verifies whether the material exists in the organization, and if you enable labor planning,
simulates the labor required to perform the picks. You can plan a wave using online
processing, or run wave planning as a concurrent request. If you use online processing, then

Chapter 5 - Page 15
all other transactions which are running will stop while you are planning the wave. You must
use concurrent processing if you choose to use rules-based planning.
Note: When planning the wave, the estimated start time must be greater than the current
system time, or the application will not plan the wave.
Fulfillment Planning
Fulfillment planning verifies that there is enough material to fulfill the wave demand. When
performing fulfillment planning, you can check the fill rate of the wave based on the stock
availability. This enables you to know exactly how much of the wave will be fulfilled. The
results you receive may differ based on the Planning Method you select.
Planning Actions
You can perform different actions if material is available, or if material is unavailable to fulfill
the demand. Performing these actions saves time and provides more visibility to the order
fulfillment process. ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 16
Labor Planning
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s on licen
Labor Planning
a viplanning determines the number of resources required to perform the work for the
D
Labor
T oni wave. The application considers the required resources for the tasks and if those resources
are available to perform the tasks. When planning the labor for the wave, you must enter
specific parameters such as Source Type, Source, Destination, and Pick UOM. You must also
enter the Resource to perform the task. Finally, you must specify the transaction, travel, and
processing overhead times.
To further narrow the labor planning calculations, you can plan labor by item category. This
lets you account for the difference in picking times for different categories of items within the
same subinventory.
Rules-Based Planning
If you use Rules-Based Planning for labor, then you can more accurately predict the time and
labor required to fulfill a wave. The Labor Setup mode lets you choose to track labor
movement from Subinventory-to-Subinventory, or from Zone-to- Zone. If tracking from Zone-
to-Zone, then you can specify a logical grouping of locators as necessary.
You can also specify the Operation Plan used as the material movement and sequence of
operations through the warehouse. The outbound Operation Plans include:
• LPN based consolidation in staging lane within delivery

Chapter 5 - Page 17
• Direct consolidation in staging lane across deliveries
• Direct consolidation in staging lane within delivery
• LPN based consolidation in consolidation locator across deliveries in staging lane
• LPN based consolidation in consolidation locator within delivery in staging lane
• LPN based consolidation in staging lane across deliveries
• Locator based consolidation in consolidation locator, across deliveries in staging lane

• Locator based consolidation in consolidation locator within delivery in staging lane
If you use Rules-Based planning, then you can also simulate the labor required to perform
planned crossdocking. This lets you accurately estimate the effort required to cross dock
material within your warehouse.
Planning Templates
Like wave templates, you can create planning templates. Planning templates save time and
ble
let you create a series of criteria on which you can plan the wave.
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 18
Setting Up Labor Planning
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
Settingid
Up
o i ce
s Labor lPlanning
D av
T oniResource Setup
Before you can plan labor for the wave, you must set up the resources required to perform
picks. If you do not set up resources, then the application cannot plan the labor for the wave.
In addition to the standard resource setup, you must set up the following:
• Instance: Determines how many instances of the resource are available to perform
picking tasks. The instance of a resource directly correlates to an employee name.
• Utilization: The percentage of time the resource is performing picking tasks.
• Efficiency: The Efficiency percentage is a subset of the Utilization percentage. It
measures how efficient the resources are when performing the picks. This is a user-
defined value.
• Shift information: If the resource is not available 24 hours, then you must determine the
shift information. This enables the application to determine the duration of time
resources that are available for work.

Chapter 5 - Page 19
Pick Units of Measure
You must determine the pick unit of measure for the subinventory. The pick unit of measure
establishes the relationship between the task type and the allocation. If you do not set the pick
UOM, then the application cannot plan the labor for the wave.
You must establish a default UOM conversion for every picking UOM. For example, a case
UOM and a pallet UOM. You can also establish item-level conversions. The item level
conversion takes precedence over the standard UOM conversion.

Note: When you are using rules-based planning, the application considers the allocation UOM
during labor planning.
Labor Set Up Modes

If you choose to use Zone-to-Zone as the Labor Setup Mode in the Plan Wave window, Labor
Planning tab, then you must establish a zone type of Labor Planning to use for labor planning
calculations. If a locator exists in one zone of type Labor Planning, then it cannot exist in e
another zone of type Labor planning. The locator may, however, exist in one or more zones of r a bl
type ATF, or in a Zone of type Labor Planning and a zone of Type ATF. s fe
- t r an
on
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 20
Wave Planning Results
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
d s
Wave Planning
on Results
l i c en
a i
vyou
n i D
After have planned the wave, you can view the results of the plan in the Wave
T o Workbench. The Lines tab displays the planned fulfillment rate. If you have waves which can
be cross docked, then the application displays these as the cross-dock fill rate.
The Labor Statistics tab displays the Resources available for the tasks and the associated
capacities. You can view the total capacity of the resource, the total existing work load, and
the planned work load for the wave. The chart in this window displays the number of tasks for
the wave which correspond to the graph.
After you have reviewed the results of the wave plan, you can make adjustments as needed,
re-plan the wave, and then release the wave to the warehouse.

Chapter 5 - Page 21
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 22
Releasing a Wave
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
Releasing s n
aoWavelice
n
i
vyoud
D a
After make the needed adjustments to the wave, you release it to the warehouse. You
i
on can use online processing or a concurrent request from the Wave Dashboard to release a
T wave. You can also schedule the Wave Release concurrent request to run at regular intervals.
When you release the wave, the pick release process is initiated and material is allocated to
orders. This releases the orders for picking and pull replenishment (pull replenishment is one
of many replenishment types).
After you release a wave, you can use the Wave Workbench to view the order and order line
status, track the progress of operators as they pick tasks, or remove lines from the wave.
Firming a Wave
Prior to wave release, you must firm a wave. Firming the wave sets orders to a particular
wave. During the wave creation and planning process, you can create multiple waves which
pull the same sales orders. This enables you to compare waves and plan for optimum wave
fulfillment. For example, you can create Wave 1 which contains Sales orders 110, 111, and
112, and Wave 2 which contains Sales Orders 111, 112, and 113. After you have planned
Wave 1, you realize you do not have the material to fulfill sales order 110. You decide to go
ahead and proceed with Wave 2. You can firm Wave 2 and Sales Orders 111, and 112 will be
removed from Wave 1.

Chapter 5 - Page 23
Note: When releasing a wave that has not been firmed, the application firms the wave
automatically.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 24
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 25
Monitoring Waves
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oWaves
Monitoring
i
vcand li
D a
You view a wave (and related wave activity) before and after it is released. Use the Wave
i
on Dashboard to search for waves by wave number or other criteria, view high-level summary
T information about waves, monitor all picking activity in a warehouse, view automatic and
recurring requests, and view the wave status for specific dates. You can view an overall
summary of waves and wave activity for created, planned, or released waves.
Use the Wave Workbench to search for waves and preview a wave after it has been created
and planned. You can view order and order line level details, track progress of orders in the
warehouse, manage tasks, review labor planning criteria, and manage exceptions.
Wave Dashboard
The Dashboard tab of the Wave Dashboard provides an overview of the work across waves in
the warehouse. You can select criteria for viewing a summary, and if desired, view the details
of the wave. You can view waves using:
• Target Completion Date
• Estimated Start Date
• Actual Completion date

Chapter 5 - Page 26
You can also select the dates from which to view the associated waves and the
accompanying Wave Statues. The Wave Report: Fullfillment Summary chart changes based
on selections that you make.
Find Wave
Use the Find Wave tab of the Wave Dashboard to find any wave, or view multiple waves
concurrently that fit certain criteria. For example, you can choose to view all released waves
for the customer SmartBuy that are being shipped using carrier DHL. The result of the query is
presented on the wave workbench where order lines and tasks can be further examined by
selecting different waves in the navigation tree region.
Requests
Use the Requests tab to view waves that were created, planned, or released using concurrent
programs. You can also track requests that are scheduled to run on a regular basis.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 27
Monitoring Warehouse Activity
ble
fe r a
ans
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s n cen
oWarehouse
Monitoring
v i d li Activity
D a
After you have selected the wave or group of waves to view, use the Wave Workbench to
n i
o monitor the progression of work throughout the warehouse.
T
Orders
After you release a wave to the Warehouse, the information on the Orders tab changes to
reflect the order fulfillment rate at pick release. The graph at the top of the page depicts the
order Fill Rate Summary for the entire wave. The table at the bottom of the page depicts the
Planned Fill Rate, the Release Fill Rate, and then as warehouse workers progress through
wave, the Actual Fill Rate.
Lines
The Lines tab displays the progress of sales order lines as warehouse workers pick them in
the warehouse. The Wave Fill Rate charts display the Planned Fill Rate, Release Fill Rate,
and if required, the percentage of cross docked lines. The Wave Progress chart displays the
work percentages in the warehouse. You can view the percentage of sales order lines that are
Tasked Picked, Packing, Staged, and Completed.
The bottom half of the page provides details about the individual sales order lines. It displays
the Sales Order, Sales Order Line, and the status of the order line. A warehouse manager can
view if the line has been Tasked, Picked, or if the line has already been Staged.

Chapter 5 - Page 28
Tasks
The Tasks tab provides you with a real-time view of the task progress within the wave.
Warehouse managers can view the state of tasks. For example, if a task has been loaded or
completed. This window updates when you navigate away from it and then return. It provides
an accurate view of the activities in the warehouse. For example, if a task remains in the
Active or Dispatched state too long, then you will know that workers within the warehouse
have not completed their work.

The chart displays a visual distribution of task statuses after a wave is released. You should
expect the leftmost bar to be the tallest immediately after the wave is released. As the wave
progresses in the warehouse, the right side status bars increase. At the completion of all tasks
in the wave, the chart will display all tasks with a completed status.
Wave Exceptions
Use the wave workbench to monitor wave exceptions. The scheduled concurrent request
detects and posts exceptions, and you use the Exceptions tab to view the exceptions and take ble
actions. The application bases exceptions in a hierarchical order using dock door fe r a
an
appointments, scheduled ship date, and expected ship date. First the application checks for s
- t r
dock door appointments. If appointments do not exist, then the application uses the scheduled
n
no
ship date. If a scheduled ship date does not exist, then the application uses the expected ship
a
h a s
date to log dock door appointments. You can log exceptions for a wave, trip, delivery, order,
) deฺ
and order line level at two levels of severity – high and low. You can log a wave level
m
ฺ c o Gui
exception that says if 80 percent of the orders for a wave are not staged two hours prior to the
e
dock door appointment time, then log a low severity exception. You can create a trip level high
cl ent
r a
severity exception if all order lines for a trip are not loaded one hour prior to the end of the
n @ o
S tud
dock door appointment time. When logging a wave or a trip level appointment, the application
i d so this
checks for the earliest basis (dock door appointment, etc.) to log the exception. You can log
d a v
order level line exceptions, for example, if 100 percent of the lines for an order are not packed
s e
ฺ u
three hours prior to the end of a dock door appointment. You can also log exceptions for
t oni se to
individual order lines. This can be useful if a line is in the replenishment requested status for
(
d s on licen
more than a specified amount of time.
You v
a i also perform actions on the exceptions detected by the concurrent request. You can
can
ni D
choose to perform automatic corrective actions when you run the concurrent request, or take
To action on the exceptions in the Wave Workbench. You can re-release backordered lines,
release planned tasks, change the priority of a task, place a hold on pending task, and view
existing tasks.

Chapter 5 - Page 29
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 30
ble
fe r a
an s
n - t r
a no
h a s
m ) deฺ
ฺ c o Gui
e
cl ent
r a
n @ o
S tud
i d so this
d a v s e
ฺ u
( t oni se to
s
Implementation
d on Considerations
l i c en
a i
vcan
DYou implement wave planning in several different ways. Consider the following when
i
on implementing wave planning:
T • Determine the selection criteria used to plan waves.
• Determine if you want to manually plan the wave, or plan waves automatically using
concurrent requests.
• If you plan on using Pull Replenishment, verify all replenishment setups have been
performed.
• Determine if Rules-Based Planning or Availability Check is the best method for your
warehouse.
• If using rules-based planning, verify that your labor set up utilizes all of the
subinventories which the rules pull from. This will ensure a complete picture with rules
based planning.
• Determine the Labor Setup Mode for your warehouse Zone to Zone or Subinventories.
• If using Zone to Zone verify that all of your labor zones are set up properly.
• When adding lines to an unreleased wave, you will be able to re-plan the wave, the
system will re-calculate the all of the necessary calculations for planning purposes.
• Expected fill rate and actual fill rate may differ after release due to replenishment.

Chapter 5 - Page 31
• If exception reporting does not appear to be working, consider the hierarchy for reporting
exceptions: dock door appointment, scheduled ship date, and finally, expected ship date.
• The system considers the lowest common denominator when reporting exceptions.
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 32
Agenda
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 33
Summary
ble
fe r a
ans
n - t r
o
s an
) ha eฺ
ฺ c om Guid
a c le nt
@ or tude
s o n is S
a v id se th
o n iฺd to u
n (t nse
d s o l i ce
a v i
D
T oni

Chapter 5 - Page 34

Student Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Student Guide

Uploaded by

Copyright:

Available Formats

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2015, Oracle and/or its affiliatesฺ

Restricted Rights Notice

U.S. GOVERNMENT RIGHTS

R12.x Oracle Warehouse Management Overview .........................................................................................1-1

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

R12.x Oracle Warehouse Management Inbound Logistics ..........................................................................2-1

T oni GTIN Setup ....................................................................................................................................................2-33

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Cross Docking Put Away................................................................................................................................2-63

R12.x Oracle Warehouse Management Fundamentals Table of Contents

T oni Pick Release Process ....................................................................................................................................4-13

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Automated Task Dispatch, Allocation and Assignment ..................................................................................4-46

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Staging and Consolidation .............................................................................................................................4-106

T oni Planning a Wave ............................................................................................................................................5-15

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Before You Begin This Course

• Working experience with Warehouse Management principles.

How This Course Is Organized

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Oracle Warehouse Management Implementation Guide Release 12.2 E23270-01

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

1. Typographic Conventions for words within regular text

Convention Object or Term Example

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Convention Object or term Example

CREATE ROLE role

4. Typographic Conventions for Oracle Application Help System Paths

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

R12.x Oracle Warehouse Management Fundamentals Table of Contents

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Oracle Warehouse Management Features

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview

Copyright © Oracle, 2011. All rights reserved.

R12.x Oracle Warehouse Management Overview