Warehouse Management Fundamentals SG

11i Oracle Warehouse
Management Fundamentals
Ed 2
y
l
n
Student Guide
O
e
I
A
&
l
a
n
r
te
D16446GC20
n
I
e
Edition 2.0
November 2005
l
c
a
D22740
r
O
s
U
Copyright Oracle Corporation, 2005. All rights reserved.

This documentation contains proprietary information of Oracle Corporation. It is provided under a license agreement containing
restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited. If this
documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights
and the following legend is applicable:
Restricted Rights Legend
Use, duplication or disclosure by the Government is subject to restrictions for commercial computer software and shall be deemed
to be Restricted Rights software under Federal law, as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in
Technical Data and Computer Software (October 1988).
This material or any portion of it may not be copied in any form or by any means without the express prior written permission of the
Education Products group of Oracle Corporation. Any other copying is a violation of copyright law and may result in civil and/or
criminal penalties.
If this documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with
Restricted Rights, as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).
The information in this document is subject to change without notice. If you find any problems in the documentation, please report
them in writing to Worldwide Education Services, Oracle Corporation, 500 Oracle Parkway, Box SB-6, Redwood Shores, CA 94065.
Oracle Corporation does not warrant that this document is error-free.
Oracle and all references to Oracle Products are trademarks or registered trademarks of Oracle Corporation.
All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.
Author
Tyra Crockett
y
l
n
Technical Contributors and Reviewers
Lokesh Verma, Jennifer Sherman, Jack Moses Paul Taylor, Madhu Punuganti, Sharma Manda
This book was published using:
O
e
oracletutor
I
A
&
l
a
n
r
te
r
O
l
c
a
n
I
e
s
U
Table of Contents
11i Oracle Warehouse Management Overview.............................................................................................1-1
11i Oracle Warehouse Management Overview .............................................................................................1-2
Objectives ......................................................................................................................................................1-3
Agenda...........................................................................................................................................................1-4
What is a Warehouse? ...................................................................................................................................1-6
Processes of a Warehouse..............................................................................................................................1-7
Additional Product Requirements..................................................................................................................1-8
Warehouse Management Application Hierarchy...........................................................................................1-9
Inventory, Warehouse Management and MSCA ...........................................................................................1-11
Radio Frequency Devices ..............................................................................................................................1-12
Agenda...........................................................................................................................................................1-13
Overview of Inbound Logistics .....................................................................................................................1-14
Reverse Logistics...........................................................................................................................................1-16
Agenda...........................................................................................................................................................1-17
Overview of Outbound Logistics...................................................................................................................1-18
Agenda...........................................................................................................................................................1-20
Value Added Services ...................................................................................................................................1-21
Agenda...........................................................................................................................................................1-23
Storage and Facility Management .................................................................................................................1-24
Agenda...........................................................................................................................................................1-26
Oracle Mobile Applications Architecture......................................................................................................1-27
License Plate Numbers (LPNs) .....................................................................................................................1-28
Nesting LPNs.................................................................................................................................................1-30
Generating LPNs ...........................................................................................................................................1-31
LPN Context..................................................................................................................................................1-32
Material Status...............................................................................................................................................1-37
Subinventory and Locator Material Status ....................................................................................................1-39
Lot and Serial Attributes................................................................................................................................1-40
Cost Groups ...................................................................................................................................................1-41
Cost Group Assignment.................................................................................................................................1-43
Task Assignment ...........................................................................................................................................1-44
Rules and the Rules Engine ...........................................................................................................................1-46
Rules Engine Uses .........................................................................................................................................1-48
Material Allocation Example.........................................................................................................................1-50
Allocation Decision Tree...............................................................................................................................1-51
Rules Setup....................................................................................................................................................1-52
Defining Rules: Restrictions..........................................................................................................................1-53
Defining Rules: Sort Criteria .........................................................................................................................1-54
Defining Rules: Default.................................................................................................................................1-55
Strategies .......................................................................................................................................................1-56
Task Type, Label Format, and Operation Plan Selection Rules ....................................................................1-57
Consistency Requirements ............................................................................................................................1-58
Rules Simulation ...........................................................................................................................................1-59
RFID Technology ..........................................................................................................................................1-60
Labeling.........................................................................................................................................................1-61
Label Types ...................................................................................................................................................1-63
Label Formats ................................................................................................................................................1-65
Assigning Label Types to Business Flows ....................................................................................................1-66
Agenda...........................................................................................................................................................1-67
Summary........................................................................................................................................................1-68
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
r
O
11i Receiving Material with Warehouse Management.................................................................................2-1

11i Receiving Material with Warehouse Management..................................................................................2-2
Copyright Oracle, 2005. All rights reserved.
11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

i
Objectives ......................................................................................................................................................2-3
Agenda...........................................................................................................................................................2-4
Overview of Inbound Logistics .....................................................................................................................2-6
Receiving Flows or Routings.........................................................................................................................2-8
Subinventories ...............................................................................................................................................2-9
Locator Types................................................................................................................................................2-11
Receiving Locators ........................................................................................................................................2-12
Document Based Receiving...........................................................................................................................2-14
Item Based Receiving....................................................................................................................................2-16
Agenda...........................................................................................................................................................2-17
Receiving Methods ........................................................................................................................................2-18
Standard Routing Flow..................................................................................................................................2-19
Inspection Routing Receipt............................................................................................................................2-20
Direct Receipt Flow.......................................................................................................................................2-21
Express Receipt Flow ....................................................................................................................................2-22
Express Receipts............................................................................................................................................2-23
Mixed Receipt Routing..................................................................................................................................2-24
Desktop vs. Mobile Receiving.......................................................................................................................2-25
Mobile Receiving Options.............................................................................................................................2-26
Unavailable Mobile Receiving Options.........................................................................................................2-27
LPN Receipts.................................................................................................................................................2-28
Lot and Serial Receiving ...............................................................................................................................2-29
Automated Matching of Received Material...................................................................................................2-30
Automated Matching of Material Received...................................................................................................2-31
Receiving - GTINs.........................................................................................................................................2-32
GTIN Setup ...................................................................................................................................................2-33
Receiving Open Interface ..............................................................................................................................2-34
Quality Vs. Purchasing Inspection.................................................................................................................2-35
Standard Inspection .......................................................................................................................................2-37
Quality Inspection..........................................................................................................................................2-38
Inspection Storage Requirements ..................................................................................................................2-39
Returns...........................................................................................................................................................2-40
Practice - Receiving Material ....................................................................................................................2-41
Solution Receiving Material ...................................................................................................................2-43
Agenda...........................................................................................................................................................2-48
Cost Groups ...................................................................................................................................................2-49
System Assigned Cost Groups.......................................................................................................................2-51
Cost Groups Setup .........................................................................................................................................2-52
Commingling.................................................................................................................................................2-53
Agenda...........................................................................................................................................................2-55
Put Away Rules .............................................................................................................................................2-56
Restrictions and Sort Criteria for Put Away Rules ........................................................................................2-58
Setting Up Put Away Rules ...........................................................................................................................2-59
Setting Up Put Away Rules: Define Rules ....................................................................................................2-60
Setting Up Put Away Rules: Define Strategies..............................................................................................2-62
Setting Up Put Away Rules: Assign Strategies to Business Objects .............................................................2-63
Practice - Creating a Put Away Rule .........................................................................................................2-64
Solution Creating a Put Away Rule ........................................................................................................2-65
Put Away .......................................................................................................................................................2-69
Put Away Load ..............................................................................................................................................2-71
Put Away Drop ..............................................................................................................................................2-72
Put Away Drop - Nested LPN .......................................................................................................................2-74
Item Based Put Away ....................................................................................................................................2-75
Cross Docking Put Away ..............................................................................................................................2-77
Practice - Put Away ...................................................................................................................................2-78
Solution Put Away..................................................................................................................................2-79
Cross Docking to Outbound Staging Flow ....................................................................................................2-84
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

ii
s
U
Cross Docking to WIP Staging Flow.............................................................................................................2-85

Cross Docking to WIP Issue Flow.................................................................................................................2-86
Agenda...........................................................................................................................................................2-87
Advanced Task Framework (ATF)................................................................................................................2-88
ATF Capabilities ...........................................................................................................................................2-89
ATF Concepts................................................................................................................................................2-90
ATF Example ................................................................................................................................................2-97
ATF Setup .....................................................................................................................................................2-98
ATF Zones : Setup......................................................................................................................................2-99
ATF Operation Plan Setup.............................................................................................................................2-100
Practice - Using Advanced Task Framework ............................................................................................2-101
Solution Using Advanced Task Framework ...........................................................................................2-102
Agenda...........................................................................................................................................................2-109
Implementation Considerations .....................................................................................................................2-110
Agenda...........................................................................................................................................................2-116
Summary........................................................................................................................................................2-117
11i Warehouse Features ..................................................................................................................................3-1
11i Warehousing Features .............................................................................................................................3-2
Objectives ......................................................................................................................................................3-3
Agenda...........................................................................................................................................................3-4
Compliance Labeling.....................................................................................................................................3-6
Warehouse Management versus Partner Label Printing Responsibilities......................................................3-8
Label Printing Components ...........................................................................................................................3-9
Label Formats ................................................................................................................................................3-10
Label Types ...................................................................................................................................................3-11
Setup..............................................................................................................................................................3-13
Registering Label Formats.............................................................................................................................3-14
Assigning Label Types to Business Flows ....................................................................................................3-15
Label Format Assignment Rules ...................................................................................................................3-16
Defining and Assigning Printers....................................................................................................................3-17
Printing Modes ..............................................................................................................................................3-18
Asynchronous Mode......................................................................................................................................3-19
Synchronous Mode - Generic ........................................................................................................................3-20
Synchronous Mode TCP / IP .........................................................................................................................3-21
Practice - Compliance Labeling.................................................................................................................3-22
Solution Compliance Labeling ...............................................................................................................3-23
Viewing Label Requests ................................................................................................................................3-27
Agenda...........................................................................................................................................................3-28
Task Management..........................................................................................................................................3-29
Task Types.....................................................................................................................................................3-30
Setting Up Task Type Rules ..........................................................................................................................3-32
Task Dispatch Engine....................................................................................................................................3-33
Resource Skills ..............................................................................................................................................3-35
Available Equipment and Resources .............................................................................................................3-36
WMS Control Board......................................................................................................................................3-37
Task Status.....................................................................................................................................................3-38
Exception Management .................................................................................................................................3-41
Task Setup Steps............................................................................................................................................3-42
Practice - Task Setup .................................................................................................................................3-43
Solution Task Setup................................................................................................................................3-44
Agenda...........................................................................................................................................................3-51
Label Printing Implementation Considerations .............................................................................................3-52
Task Type Implementation Considerations ...................................................................................................3-54
Agenda...........................................................................................................................................................3-56
Summary........................................................................................................................................................3-57
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

iii
s
U
11i Outbound Logistics ...................................................................................................................................4-1

11i Outbound Logistics .................................................................................................................................4-2
Objectives ......................................................................................................................................................4-3
Agenda...........................................................................................................................................................4-5
Overview of Outbound Logistics...................................................................................................................4-7
Overview of Picking......................................................................................................................................4-9
Sales Order Picking .......................................................................................................................................4-11
Replenishment Picking ..................................................................................................................................4-12
WIP Picking...................................................................................................................................................4-13
Pick Release Process .....................................................................................................................................4-14
Components of 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-24
Agenda...........................................................................................................................................................4-25
Pick Methodologies .......................................................................................................................................4-26
Picking Rules Order Allocation.....................................................................................................................4-28
Rules Engine Framework ..............................................................................................................................4-29
Rules Definition Directed Picking..............................................................................................................4-30
Allocation Modes ..........................................................................................................................................4-31
Allocation Modes: No LPN Allocation .........................................................................................................4-34
Allocation Modes: No LPN Allocation, Prioritize Pick UOM ......................................................................4-35
Allocation Modes: Allocate LPN and Loose .................................................................................................4-36
Allocation Modes: Allocate Entire LPN Only...............................................................................................4-37
Practice - Creating a Picking Rule .............................................................................................................4-39
Solution - Creating a Picking Rule ............................................................................................................4-40
Practice - Pick Release...............................................................................................................................4-44
Solution Pick Release .............................................................................................................................4-46
Agenda...........................................................................................................................................................4-53
Automated Task Dispatch, Allocation and Assignment ................................................................................4-54
Practice - Picking Execution......................................................................................................................4-55
Solution Picking Execution ....................................................................................................................4-56
Agenda...........................................................................................................................................................4-65
Advance Pick Load........................................................................................................................................4-66
Advanced Pick Load Setup............................................................................................................................4-67
Advanced Pick Load Page Setup...................................................................................................................4-68
Advanced Pick Load Use ..............................................................................................................................4-71
Advanced Pick Load Task Setup ................................................................................................................4-72
Advanced Pick Load Menu Setup .................................................................................................................4-73
Advanced Pick Load Exceptions ...................................................................................................................4-74
Advanced Pick Load - Execution ..................................................................................................................4-75
Agenda...........................................................................................................................................................4-76
Catch Weight Description .............................................................................................................................4-77
Catch Weight Benefits...................................................................................................................................4-78
Catch Weight Item Setup...............................................................................................................................4-79
Catch Weight Setup .......................................................................................................................................4-81
Catch Weight Use..........................................................................................................................................4-82
Agenda...........................................................................................................................................................4-83
Consolidation.................................................................................................................................................4-84
Consolidation Setup.......................................................................................................................................4-86
Consolidation Inquiry ....................................................................................................................................4-87
Cartonization .................................................................................................................................................4-89
Packing ..........................................................................................................................................................4-92
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

iv
s
U
Packing Workbench Flow..............................................................................................................................4-93

Eligible Material ............................................................................................................................................4-94
Mobile Packing..............................................................................................................................................4-95
Packing Workbench and Outbound Logistics................................................................................................4-96
Packing Workbench and Inbound Logistics ..................................................................................................4-97
Packing Initialization.....................................................................................................................................4-98
LPN Pack.......................................................................................................................................................4-99
LPN Unpack ..................................................................................................................................................4-100
LPN Split .......................................................................................................................................................4-101
LPN Reconfiguration.....................................................................................................................................4-102
LPN close ......................................................................................................................................................4-103
Practice - Packing Workbench...................................................................................................................4-104
Solution Packing Workbench .................................................................................................................4-105
DFI and the Packing Workbench...................................................................................................................4-107
Agenda...........................................................................................................................................................4-108
Overview of Shipping....................................................................................................................................4-109
Staging Lanes ................................................................................................................................................4-110
Setting Up Staging Lanes ..............................................................................................................................4-111
Dock Doors....................................................................................................................................................4-112
Setting Up Dock Doors..................................................................................................................................4-113
Staging Lane to Dock Door Relationship ......................................................................................................4-114
Setting Up Staging Lane to Dock Door Relationships ..................................................................................4-115
Staging and Consolidation.............................................................................................................................4-116
Loading and Shipping....................................................................................................................................4-117
Trips and Trip Stops ......................................................................................................................................4-118
Ship Confirmation .........................................................................................................................................4-119
Direct Shipping..............................................................................................................................................4-120
Dock Door Ship .............................................................................................................................................4-121
LPN Ship .......................................................................................................................................................4-122
Quick Ship .....................................................................................................................................................4-123
Shipment Planning.........................................................................................................................................4-124
Dock Door Appointments..............................................................................................................................4-125
Practice - LPN Ship ...................................................................................................................................4-126
Solution LPN Ship..................................................................................................................................4-128
Agenda...........................................................................................................................................................4-129
Implementation Considerations .....................................................................................................................4-130
Agenda...........................................................................................................................................................4-132
Summary........................................................................................................................................................4-133
y
l
n
O
e
I
A
s
U
11i Warehouse Management Case Study ......................................................................................................5-1

11i Warehouse Management Case Study ......................................................................................................5-2
Objectives ......................................................................................................................................................5-3
Beanz n' Leavz Overview ..............................................................................................................................5-4
B&L Financials .............................................................................................................................................5-5
Application Landscape ..................................................................................................................................5-6
Challenges .....................................................................................................................................................5-7
Product Profile...............................................................................................................................................5-9
Customer Profile............................................................................................................................................5-13
Vendor Profile ...............................................................................................................................................5-16
Inbound Process.............................................................................................................................................5-17
Outbound Process ..........................................................................................................................................5-19
Outbound Process ..........................................................................................................................................5-27
Replenishment ...............................................................................................................................................5-28
Accuracy and Counting .................................................................................................................................5-29
&
l
a
n
r
te
n
I
e
l
c
a
r
O

v
y
l
n
O
e
I
A
&
l
a
n
r
te
r
O
l
c
a
n
I
e
s
U
Preface
Profile
Before You Begin This Course
Before you begin this course, you should have the following qualifications:
Thorough knowledge of Oracle Inventory
Working experience with sales orders and receipts
Prerequisites
Oracle Inventory Fundamentals
Oracle Receivables Fundamentals
Oracle Order Management Fundamentals
Oracle Purchasing Fundamentals
How This Course Is Organized
y
l
n
Oracle Warehouse Management Fundamentals Ed 2 is an instructor-led course featuring lecture

and hands-on exercises. Online demonstrations and written practice sessions reinforce the
concepts and skills introduced.
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

vii
s
U
Related Publications
Oracle Publications
Title
Part Number
Oracle Inventory Users Guide
A83507-10
Oracle Warehouse Management Users Guide
A90844-05
Oracle Warehouse Management Implementation Guide
A86607-07
Oracle Mobile Supply Chain Applications Users Guide
A86726-04
Additional Publications
System release bulletins
Installation and users guides
Read-me files
International Oracle Users Group (IOUG) articles
Oracle Magazine
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

viii
s
U
Typographic Conventions
Typographic Conventions in Text
Convention
Bold italic
Caps and
lowercase
Courier new,
case sensitive
(default is
lowercase)
Initial cap
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Code output,
directory names,
filenames,
passwords,
pathnames,
URLs,
user input,
usernames
Italic
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books and
courses,
variables
Interface elements
with long names
that have only
initial caps;
lesson and chapter
titles in crossreferences
SQL column
names, commands,
functions, schemas,
table names
Menu paths
Key names
Key sequences
Quotation
marks
Uppercase
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.
For further information, see Oracle7 Server SQL Language
Reference Manual.
Enter user_id@us.oracle.com, where user_id is the
name of the user.
Select Include a reusable module component and click Finish.
y
l
n
O
e
I
A
&
l
a
Use the SELECT command to view information stored in the

LAST_NAME
column of the EMP table.
n
r
te
Arrow
Brackets
Commas
Plus signs
l
c
a
n
I
e
r
O
Key combinations
s
U
This subject is covered in Unit II, Lesson 3, Working with

Objects.
Select File > Save.

Press [Enter].
Press and release keys one at a time:
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

ix
Typographic Conventions in Code

Convention
Caps and
lowercase
Lowercase
Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
DROP USER scott

IDENTIFIED BY tiger;
OG_ACTIVATE_LAYER
(OG_GET_LAYER (prod_pie_layer))
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
Syntax variables
CREATE ROLE role
SQL commands and SELECT userid

FROM emp;
functions
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
O
e
y
l
n
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
(M) From the menu, select Query then Find.
3.
(B) Click the Approve button.
Notations:
(N) = Navigator
n
r
te
(M) = Menu
n
I
e
(T) = Tab
(B) = Button
&
l
a
I
A
l
c
a
(I) = Icon
r
O
(H) = Hyperlink
(ST) = Sub Tab

x
s
U
Typographical Conventions in 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
(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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

xi
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

xii
s
U
11i Oracle Warehouse

Management Overview
Chapter 1
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
11i Oracle Warehouse Management Overview

Chapter 1 - Page 1
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 2
s
U
Objectives
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 3
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 4
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 5
s
U
What is a Warehouse?
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 6
s
U
Processes of a Warehouse
y
l
n
O
e
s
U
Processes of a Warehouse
The following is an abbreviated list of the functions operators can perform in Oracle
Warehouse Management (Warehouse Management):
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 7
Additional Product Requirements
y
l
n
O
e
s
U
Additional Product Requirements

To use Warehouse Management, you must implement Oracle Inventory (Inventory), Oracle
Purchasing (Purchasing), Oracle Bills of Material (Bills of Material), and Oracle Order
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
Users Guide.
For more information on Bills of Material setup see, Overview of Setting Up, Oracle
Bills of Material Users Guide.
For more information on receiving setup see, Overview of Setting Up, Oracle Purchasing
Users Guide.
Fore more information on shipping setup see, Oracle Shipping Execution Setup, Oracle
Order Management Implementation Manual.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 8
Warehouse Management Application Hierarchy
y
l
n
O
e
s
U
Warehouse Management Application Hierarchy

The above graphic represents the relationship between existing Oracle manufacturing
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.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 9
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 10
s
U
Inventory, Warehouse Management and MSCA
y
l
n
O
e
s
U
Inventory, Warehouse Management and MSCA

When you implement Warehouse Management, you must implement Inventory as well. In
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 11
Radio Frequency Devices
y
l
n
O
e
s
U
Radio Frequency Devices

Warehouse Managements supports two types of user interfaces, telenet based, and graphical.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 12
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 13
s
U
Overview of Inbound Logistics
y
l
n
O
e
s
U

Warehouse Management inbound logistics refers to receiving, inspection, and put away
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 14
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 15
s
U
Reverse Logistics
y
l
n
O
e
s
U
Reverse Logistics
Return Material Authorization (RMA): Warehouse Management enables operators to
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 16
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 17
s
U
Overview of Outbound Logistics
y
l
n
O
e
s
U
Pick Release
The pick release process selects sales order lines to release for picking and shipping. You 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 18
WMS 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.
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
Managers can use Warehouse Management to schedule outbound carrier appointments, dock
door availability, and staging lane usage within the warehouse.
Shipment Verification and Close
Once operators pick and load an order, the system automatically determines the items and
quantities to deduct from inventory.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 19
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 20
s
U
Value Added Services
y
l
n
O
e
s
U
Value Added Services

Kitting and De-kitting: Supports kit to stock (supported by work order-less completion)
and kit to order (supported by pick to order).
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 21
Radio Frequency Identification (RFID): Warehouse Management supports RFID. RFID

is an automated data collection technology that enables equipment to read tags attached
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 22
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 23
s
U
Storage and Facility Management
y
l
n
O
e
s
U
Storage and Facility Management

Advanced Lot and Serial Control: Warehouse Management enables operators to split,
merge, and rename lots. For more information see, Describing Lot Split, Merge, and
Genealogy, Oracle Warehouse Management Users 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 pullbased replenishment in
manufacturing systems. For more information on kanban management see: Overview of
Kanban Management, Oracle Inventory Users 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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 24
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.
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 Users 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 25
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 26
s
U
Oracle Mobile Applications Architecture
y
l
n
O
e
s
U
Mobile Applications Architecture

Mobile applications enables operators to input real-time transactions and receive warehouse
tasks the system assigns. Warehouse Management and MSCA use the same applications
architecture.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 27
License Plate Numbers (LPNs)
y
l
n
O
e
s
U
Explaining License Plate Numbers (LPNs)

An LPN is any object that exists in a location and holds items. You can use Warehouse
Management to track, transact, and nest LPNs.
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 28
Reuse empty LPNs

Receive and send LPN information on an ASN
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 29
s
U
Nesting LPNs
y
l
n
O
e
s
U
Nesting License Plate Numbers

You can nest LPNs within other LPNs. In the above example, item A is packed in LPN 2, and
LPN1, LPN2, and LPN3 are nested within LPN4. When you transact LPN4, all of the LPNs
nested within it are transacted.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 30
Generating LPNs
y
l
n
O
e
s
U
Generating License Plate Numbers

You can generate an LPN to match industry standards, such as SSCC-18, that includes the
required check digit. You can also configure the numbering scheme to match an existing
internal method.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 31
LPN Context
y
l
n
O
e
s
U
LPN Context
Warehouse Management defines a context for each LPN to denote the current state. You can
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 32
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 33
s
U
LPN Context
y
l
n
O
e
s
U
LPN Context
Issued 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 34
LPN Context
y
l
n
O
e
s
U
LPN Context
Defined 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.
Loaded for Shipment
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 35
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 36
s
U
Material Status
y
l
n
O
e
s
U
Defining Material Status Control

Material status control provides more granular transaction control than item status control. It
controls the types of transactions you can perform. You can assign material status to an item
lot, serial, subinventory, or locator.
Transaction Control
You use material status control to specify the allowed and disallowed transactions for
inventory material. It also enables you to query material by current status, and to generate and
view reports of all historical status changes for material in the warehouse.
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 37
INACTIVE, then transaction types disallowed by HOLD and INACTIVE statuses are not
allowed for the lot.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 38
s
U
Subinventory and Locator Material Status
y
l
n
O
e
s
U
Subinventory and Locator Material Status

You can set a status to allow or disallow various inventory transactions. For example, if for
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 39
Lot and Serial Attributes
y
l
n
O
e
s
U
Lot and Serial Attributes

Lot and serial attributes track the characteristics of items based on lot or serial numbers.
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 setup 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
Using Lot and Serial Attributes

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

Chapter 1 - Page 40
Cost Groups
y
l
n
O
e
s
U
Cost Groups
Cost groups associate account information with on hand inventory. Cost groups provide a way
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 41
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
between the assigned cost group and cost groups of existing material in the location.
Commingling
Multiple cost groups of a single item can reside in the same locator or LPN if material within
each cost group that resides in the LPN or locator is uniquely identifiable. You cannot perform
a transaction in a commingled LPN or locator.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 42
s
U
Cost Group Assignment
y
l
n
O
e
s
U
Cost Group Assignments

Warehouse Management, uses the cost group rules engine to assign cost groups. Inventory
derives cost groups based on the primary cost method of the organization and the 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
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
Warehouse Management bases costing and valuation reports on cost group, and Inventory
bases costing and valuation reports on subinventory.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 43
Task Assignment
y
l
n
O
e
s
U
Explaining Tasks
Warehouse Management uses tasks to control the flow of material through the warehouse. It
dispatches tasks to operators based on skill sets. You can group operators into common skill 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 44
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 45
s
U
Rules and the Rules Engine
y
l
n
O
e
s
U
Rules and the Rules Engine

You can use the rules engine to create rules to effectively dispatch tasks and manage 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 46
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 47
s
U
Rules Engine Uses
y
l
n
O
e
s
U
Rules Engine Uses

You can use the rules engine to create six different types of rules, including picking, put away,
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 48
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 top racks to
operators signed onto high-reach forklifts.
Compliance Labeling Rules
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
generate a label with the required information and barcode symbols for the material based on
the result. The system can print different labels for freight carrier or shipment type. The rules
engine can also generate labels for use inside the warehouse.
Cost Group Rules
Cost groups capture the material valuation accounts necessary for tracking inventory value.
For instance, you can set up different accounts for refurbished, new, components or finished
goods. When material is received into the warehouse, Warehouse Management determines the
owning cost group and the material valuation accounts.
Operation Plan Selection Rules
You create operation plan selection rules to determine the operation plan for consolidation. For
example, if you want certain item categories to go through a consolidation step, and item
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 49
s
U
Material Allocation Example
y
l
n
O
e
s
U
Material Allocation Example

You run a warehouse that sells strawberries. The strawberries are set up as a lot controlled 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 50
Allocation Decision Tree
y
l
n
O
e
s
U
Allocation Decision Tree

This decision tree represents the business scenario from the previous slide. Drawing a 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 51
Rules Setup
y
l
n
O
e
s
U
Rules Setup
The setup for picking rules, put away rules, and cost group rules are similar. Setting up these
rules involves three steps covered in the following slides.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 52
Defining Rules: Restrictions
y
l
n
O
e
s
U
Rule Restrictions
You define rules for picking and put away tasks based on available items and locators. Picking
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 53
Defining Rules: Sort Criteria
y
l
n
O
e
s
U
Sort Criteria
Sort criteria specify the most desirable material that meets the restrictions of the rule. The
example above sorts the excellent strawberries in order of expiration date; those that expire
first are shipped first.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 54
Defining Rules: Default
y
l
n
O
e
s
U
Defining Rules: Default

You can also define a default rule that does not have any restrictions. You can assign a 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 55
Strategies
y
l
n
O
e
s
U
Strategies
A strategy is a list of sequential rules the rules engine applies until a task is performed. Once
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.
I
A
&
l
a
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.
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 56
Task Type, Label Format, and Operation Plan Selection Rules
y
l
n
O
e
s
U
Task Type, Label Format and Operation Plane Selection Rules

Task type rules, label format rules, and operation plan rules are not assigned to strategies, but
are automatically linked directly to an organization. Rule weights determine the search order,
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 57
Consistency Requirements
y
l
n
O
e
s
U
Consistency Requirements
Consistency Requirements are unique to picking rules. They ensure all allocations for a
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 58
Rules Simulation
y
l
n
O
e
s
U
Rules Simulation
For more information on rules simulation see: Explaining the WMS Rules Engine Simulator,
Oracle Warehouse Management Users Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 59
RFID Technology
y
l
n
O
e
s
U
RFID
RFID is a technology that tags physical items with a unique identifier a scanner can read. You
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 60
Labeling
y
l
n
O
e
s
U
Receipt Labeling
You can scan and print bar codes for material you receive in to the warehouse. This results in
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 61
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 62
s
U
Label Types
y
l
n
O
e
s
U
Label Types
The system supports the following label types:
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 63
Label Types
y
l
n
O
e
s
U
Label Types
LPN: This label provides information about the LPN. It does not contain content
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 64
Label Formats
y
l
n
O
e
s
U
Label Formats
A label format sets the data and layout of a label. You may require data to appear in a 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 65
Assigning Label Types to Business Flows
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 66
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 67
s
U
Summary
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 1 - Page 68
s
U
11i Receiving Material with

Warehouse Management
Chapter 2
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
11i Receiving Material with Warehouse Management

Chapter 2 - Page 1
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 2
s
U
Objectives
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 3
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 4
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 5
s
U
y
l
n
O
e
s
U

Warehouse Management inbound logistics refers to receiving, inspection, and put away
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 6
Advanced Task Framework: You can use Warehouse Management to create operation
plans that enable operators to perform multi-step directed put away throughout
warehouse.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 7
s
U
Receiving Flows or Routings
y
l
n
O
e
s
U
Receiving Flows or Routings

The same three types of receipt routings Purchasing uses are also available in Warehouse
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 Users 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 8
Subinventories
y
l
n
O
e
s
U
Subinventories
Subinventories are unique physical or logical separations of material inventory, such as raw
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 9
Note: Operators cannot transfer material from a storage subinventory to a receiving

subinventory.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 10
s
U
Locator Types
y
l
n
O
e
s
U
Locator Types
Locators identify physical areas where inventory is stored. Warehouse Management uses
locators for many different purposes. For information on locator types see Defining Stock
Locators, Oracle Inventory Users Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 11
Receiving Locators
y
l
n
O
e
s
U
Receiving Locators
Receiving locators enable operators and managers to view newly received material in the
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

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 Users 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 13
s
U
Document Based Receiving
y
l
n
O
e
s
U
Document Based Receiving

Document based receiving is used when an operator knows the document at the time of receipt.
Operators can use the following documents to receive material in to the warehouse:
Purchase orders Standard purchase orders, or blanket purchase orders. For more
information on purchase orders, see Overview of Purchase Orders, Oracle Purchasing
Users 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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 14
- Serial number
- LPN
WIP Completion: Assemblies completed in WIP
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 15
s
U
Item Based Receiving
y
l
n
O
e
s
U
Item Based Receiving

Item based receiving is used when operators do not know the document type. Operators can
receive different types of items in the single receiving common user interface. Items include:
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 16
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 17
s
U
Receiving Methods
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 18
s
U
Standard Routing Flow
y
l
n
O
e
s
U
Explaining the Standard Routing Flow

To start the standard receipt process an operator scans the incoming document, or enters the
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 Users
Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 19
Inspection Routing Receipt
y
l
n
O
e
s
U
Inspection Routing Receipt

The inspection receipt process is identical to the standard receipt process, except an inspection
is performed on the material before it is put away. For more information see, Explaining the
Inspection Process, Oracle Warehouse Management Users Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 20
Direct Receipt Flow
y
l
n
O
e
s
U
Explaining Direct Receipt Flow

The direct receiving flow is very similar to the standard receipt flow. An operator scans the
incoming document or enters the document number to start the receiving process. Next, the
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 Users 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 21
Express Receipt Flow
y
l
n
O
e
s
U
Explaining Express Receipt Mode

Express receipts enable you to streamline your receiving process. Operators can use express
receipts for ASNs, internal requisitions and in-transit shipments. Express receipts do not
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 Users
Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 22
Express Receipts
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 23
s
U
Mixed Receipt Routing
y
l
n
O
e
s
U
Mixed Receipt Routing

A mixed routing is an LPN that contains material that has different receipt routings. When this
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 24
Desktop vs. Mobile Receiving
y
l
n
O
e
s
U
Desktop vs. Mobile Receiving

The above chart reflects the differences in receiving material using the desktop application, and
receiving material using the mobile device.
* - 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 25
Mobile Receiving Options
y
l
n
O
e
s
U
Receiving Substitutes
Operators can use the mobile device to receive substitutes if Allow Substitutes is enabled on
the shipment line, and substitutes are defined for the item. For more information see
Purchasing Attribute Group, Oracle Inventory Users 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 26
Unavailable Mobile Receiving Options
y
l
n
O
e
s
U
Unavailable Mobile Receiving Options

Warehouse Management does not support the following receiving options:
Blind receipts- Warehouse management does not support blind receipts. For information
blind receipts see, Defining Receiving Options, Oracle Purchasing Users 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 27
LPN Receipts
y
l
n
O
e
s
U
Receiving LPNs Using a Mobile Device

Using the mobile device for receipts helps operators to track material in the warehouse.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 28
Lot and Serial Receiving
y
l
n
O
e
s
U
Lot and Serial Receiving

Operators can use a configurable hot key on the mobile device to dynamically generate LPN,
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 29
Automated Matching of Received Material
y
l
n
O
e
s
U
Automated Matching of Received Material

Warehouse Management requires information about received material, including document
number, item, quantity, lot, and serial numbers, and matches the information collected to
expected receipts for that document and item combination.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 30
Automated Matching of Material Received
y
l
n
O
e
s
U
Explaining Automated Matching

The above example depicts a purchase order for eighty units of item AS81947 the supplier
sends over two shipments of forty. Currently in Purchasing, an operator must select an eligible
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 31
Receiving - GTINs
y
l
n
O
e
s
U
Receiving GTINs
When an operator receives GTINs, they scan the GTIN number and the system resolves the
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 32
GTIN Setup
y
l
n
O
e
s
U
Receiving GTIN (Cont)

To receive GTINs, you must perform the following setups:
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
Users Guide.
For more information on cross references see Defining Customer Item Cross References,
For more information on Inventory profile options see Inventory Profile Options, Oracle
Inventory Users Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 33
Receiving Open Interface
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 34
s
U
Quality Vs. Purchasing Inspection
y
l
n
O
e
s
U
Quality Vs. Purchasing Inspection

To initiate the LPN inspection process, the operator scans the LPN, item, and quantity to
inspect. If only one item is packed in the LPN, the operator can press enter and the item and
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 35
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 36
s
U
Standard Inspection
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 37
s
U
Quality Inspection
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 38
s
U
Inspection Storage Requirements
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 39
s
U
Returns
y
l
n
O
e
s
U
Returns
Operators can perform returns in a one or two step process. The profile option WMS:Express
Returns determines the process to use for returns. If you enable the profile option for your
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 40
Practice - Receiving Material

Overview
In this practice you will create:
Three subinventories
Two locators for each subinventory
Three items
One purchase order
You will then receive your items into your receiving locator.
Assumptions
You must have access to an Oracle Vision database, or comparable training or test
instance to complete this practice.
This practice assumes you know how to create items, subinventories, and purchase
orders. It does not provide a solution for those parts of the practice.
Manufacturing and Distribution Manger (USA) Responsibility
Whse Mgmt Mobile User Vision Operations Responsibility
Tasks
I
A
y
l
n
O
e
s
U
Create a receiving subinventory with two receiving locators
1.
Create a new receiving subinventory named XX_REC with a description of your

subinventory. XX represents the number your instructor assigned to you. The subinventory
is LPN controlled, and locator control is pre-specified.
2.
Create two receiving locators for your XX_REC subinventory. Name the first locator
R7.7.1 and the second locator R7.1.2.
&
l
a
n
r
te
n
I
e
Create a storage subinventory with two storage locators

3.
4.
l
c
a
Create a new storage subinventory named XX_STORE. The subinventory is LPN

controlled, and locator control is pre-specified.
r
O
Create two new storage locators for your XX_STORE subinventory. Name the first locator
S1.1.1 and the second locator S1.1.2.

Chapter 2 - Page 41
5.
Create a new storage subinventory named XX_LOT. The subinventory is LPN controlled,
and locator control is pre-specified.
6.
Create two storage locators for your XX_LOT subinventory. Name the first locator L1.1.1
and the second locator L1.1.2.
Create three items

7.
Use the FGI template to create item XX_Plain and assign it to organization W1- Kansas
City. This item is a plain item, and is not under lot or serial control.
8.
Use the FGI template to create item XX_Lot and place it under full lot control. Assign this
item to W1-Kansas City.
9.
Use the FGI template to create item XX_Serial and assign the serial numbers at receipt.
Assign this item to W1-Kansas City.
Create a Purchase Order

10. Create a purchase order for your three items with the following information:
Supplier
Consolidated Supplies
Site
Dallas-ERS
Ship-To
W1- Kansas City
XX_Plain item quantity
1000
XX_Serial item quantity
100
XX_Lot item quantity
500
Promised Date
Tomorrows Date
- Receipt Routing
Standard
- Deliver To
W1- Kansas City
y
l
n
O
e
I
A
11. Note the PO Number: ______________________________

12. Approve the purchase order.
Receive your items into the warehouse
&
l
a
s
U
13. Receive 100 of XX_Plain, 10 of XX_Serial, and 50 of XX_Lot into the warehouse. Receive
the material in to the XX_REC subinventory.
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 42
Solution Receiving Material

Receive your items into the warehouse
Responsibility = Mobile Whse Mgmt User, Vision Operations (USA)
1.
Select Inbound from the Main Menu.
2.
Select Receive from the Inbound menu.
3.
Select PO from the Receive menu.
4.
Enter W1 as the Organization code if necessary, and select enter.
5.
Enter the number of the PO you created and select Enter. The name of the supplier defaults
in the Supplier field after you enter the purchase order number.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 43
s
U
O
e
y
l
n
6.
Enter 1 in the Line Num field to receive the first item on your purchase order. After you
enter the line number, the item number and description number appear.
7.
Press Enter.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 44
s
U
8.
Select [CTRL+G] to generate an LPN for your receipt. After you generate the LPN, the
receiving location and the UOM display.
9.
Press Enter twice to display the To Sub and To Loc information.
10. Note the LPN Number for your item. _____________
y
l
n
O
e
11. Enter XX_REC in the To Sub field, and enter R7.1.1 in the To Loc field, and press enter.
Verify the UOM is each, and press enter.
I
A
s
U
12. Enter 50 in the qty field. The remaining quantity left on the purchase order line defaults in
the Remaining field.
&
l
a
13. Select [CTRL+G] to generate a new lot number in the Lot field.
14. Enter 50 in the Lot Qty field.
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 45
15. Select <Next Item> to receive your next item.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
16. Repeat steps 6-12 to receive your two remaining items.

Chapter 2 - Page 46
s
U
Note:
One of the remaining items is under serial control. You must enter the serial
information for that item. Enter any serial number in the From SN Field, and the TO SN
field defaults automatically.
17. Select <Done> on the receipt information page. The Receipt Information page displays
optional information about the Carrier, Pack Slip, BOL, Waybill and Airbill.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 47
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 48
s
U
Cost Groups
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 49
s
U
Cost Groups
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 50
s
U
System Assigned Cost Groups
y
l
n
O
e
s
U
Explaining System Assigned Cost Group

Warehouse Management can assign a cost group to inbound material at receipt. You can set up
rules to determine the appropriate cost group based on item, item category, supplier, or 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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 51
Cost Groups Setup
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 52
s
U
Commingling
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 53
s
U
Commingling
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 54
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 55
s
U
Put Away Rules
y
l
n
O
e
s
U
Explaining Put Away Rules

Put away rules enable the system to direct operators to put newly received material into the
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 56
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 57
s
U
Restrictions and Sort Criteria for Put Away Rules
y
l
n
O
e
s
U
Explaining Restrictions and Sort Criteria for Put Away Rules

Restrictions - The graphic above shows a restriction of put away in refrigerated subinventory
for item # Bottle01. This restriction precludes placing an item that needs refrigeration into a
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 Users
Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 58
Setting Up Put Away Rules
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 59
s
U
Setting Up Put Away Rules: Define Rules
y
l
n
O
e
s
U
Explaining Put Away Rule Restrictions and Sort Criteria

You define put away rules in the Warehouse Management Rules window (N) Setup >
Warehouse Configuration > Rules > Warehouse Execution > Rules. Within the Warehouse
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 60
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
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 61
s
U
Setting Up Put Away Rules: Define Strategies
y
l
n
O
e
s
U
Explaining Strategies for Put Away Rules

A strategy is a list of rules to apply, in sequence, until the put away is complete.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 62
Setting Up Put Away Rules: Assign Strategies to Business

Objects
y
l
n
O
e
I
A
s
U
Explaining Strategy Assignment for Put Away Rules

You assign strategies to business objects in the Rules Workbench. For more information on
the rules workbench see Describing the Rules Workbench, Oracle Warehouse Management
Users Guide.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 63
Practice - Creating a Put Away Rule

Overview
In this practice you will define a new put away rule, strategy, and strategy assignment.
Assumptions
Whse Mgmt Super User, Vision Operations (USA) Responsibility
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
Create two put away rules
Because your lot controlled items are stored separately, you must create a put away rule to
restrict the put away of item XX_lot to the XX_LOT subinventory.
You must also create a default put away rule for your items.
1.
Define a rule named XX_LOT_putaway, and include a description of the rule. XX

represents the number assigned to you by your instructor.
2.
Define a rule named XX_putaway and add description of the put away rule.
O
e
Define a put away strategy

3.
s
U
Define a strategy named XX_Strategy and add your two put away rules to the strategy.
I
A
Assign your strategies

4.
y
l
n
Assign your strategy to the XX_Lot item.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 64
Solution Creating a Put Away Rule

Responsibility = Whse Mgmt Super User, Vision Operations (USA)
1.
Navigate to the WMS Rules Window.
(N) Setup > Warehouse Configuration > Rules > Warehouse Execution > Rules
2.
If necessary, select W1 as the organization.
3.
Enter Put away in the Type field, or select it from the LOV.
4.
Enter XX_LOT_putaway in the Name field.
5.
Enter a description in the Description field.
6.
Verify Subinventory and Locator appear in the first Quantity Function field.
7.
Enter Available Capacity by Units in the second Quantity Function field.
8.
Verify 10 default in the Seq field.
9.
Enter Destination Subinventory in the first Object field, or select it from the LOV.
y
l
n
10. Enter Subinventory Name in the first Parameter field, or select it from the LOV.
O
e
11. Enter = in the Operator field, or select it from the LOV.

12. Enter Constant Character in the second Object Field.
I
A
s
U
13. Enter your XX_LOT subinventory in the second in the second Parameter field.
Note: The second parameter field is free form. The rules engine does not verify
constant character names in this field. Verify the parameter and the subinventory name
match exactly.
&
l
a
14. Select the Enabled check box to enable your rule.
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 65
15. Save your work.
y
l
n
Note: the Object field is the name of a table, and the Parameter field is the name of table
column. Using Constant Character as the name of the second Object enables you to use
free form text for the second Parameter.
O
e
16. Select (M) File > New to create a new rule.
I
A
17. Enter XX_putaway in the Name field.

18. Enter a description in the description field.
&
l
a
s
U
19. Verify Subinventory / Locator appears in the first Quantity Function field.
20. Enter Available Capacity by Units in the second Quantity Function field, or select it from
the LOV.
n
r
te
21. Select the Enabled check box to enable the rule.
n
I
e
l
c
a
r
O

Chapter 2 - Page 66
22. Save your work.
y
l
n
Create a new strategy
O
e
23. Navigate to the WMS Strategies window.
s
U
(N) Setup > Warehouse Configuration > Rules > Warehouse Execution > Strategies
I
A
24. Select Put away from the Type LOV.

25. Enter XX_strategy in the Name field.
&
l
a
26. Enter a description for your strategy in the Strategy field.

27. Enter 10 in the Seq field.
n
r
te
28. Enter your XX_LOT_putaway rule in the Rule Name field.
n
I
e
29. Select Always from the Date Type list of values.
l
c
a
30. Select the next line, and Enter 20 in the Seq field.
r
O
31. Enter your XX_putaway in the Rule Name field.


Chapter 2 - Page 67
y
l
n
33. Select the Strategy Enabled box to enable the strategy.
O
e
34. Save your work.

Assign the strategy to items.
I
A
35. Navigate to the Strategy Assignments window.
s
U
Workbench
&
l
a
36. Select Put Away from the Type drop down list.
n
r
te
37. Enter a sequence number in the Sequence field.

38. Enter your XX_Strategy in the Strategy field.
n
I
e
39. Enter your XX_Lot item in the Item field.
l
c
a
40. Enter Always in the Date Type field.
r
O
41. Select the Enabled check box to enable your strategy.

42. Save your work.

Chapter 2 - Page 68
Put Away
y
l
n
O
e
s
U
Put Away
To initiate the put away of material the operator scans an LPN. If the LPN requires inspection
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 69
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 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 70
s
U
Put Away Load
y
l
n
O
e
s
U
Put Away Load

You can use form function parameters to optimize the fields and buttons the operator views on
the mobile device.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 71
Put Away Drop
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 72
s
U
Put Away Drop
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 73
s
U
Put Away Drop - Nested LPN
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 74
s
U
Item Based Put Away
y
l
n
O
e
s
U
Item Based Put Away

Item based put away allows you to control put away by item for mixed load LPNs.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 75
Item Based Put Away
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 76
s
U
Cross Docking Put Away
y
l
n
O
e
s
U
Cross Docking put away

Before using the Rules Engine to determine a put away suggestion, Warehouse Management
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 77
Practice - Put Away

Overview
In this practice you will put away the items you received in the Receiving Materials practice.
Assumptions
Whse Mgmt Mobile User, Vision Operations responsibility
Tasks
Put away your plain item.
1.
Put away your XX_Plain item in the XX_STORE subinventory and S1.1.1 locator. Nest the
contents of the LPN in a new LPN.
Put away your serial controlled item.

2.
Put away your XX_Serial item in the XX_STORE subinventory and S1.1.1 locator. Transfer
the contents of the LPN into another LPN.
O
e
Use your put away strategy to put away your lot controlled item.
3.
y
l
n
s
U
Use your put away strategy to suggest a put away location for your lot-controlled item.
Verify the lot controlled item exists in inventory.
&
l
a
I
A
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 78
Solution Put Away

Responsibility = Whse Mgmt Mobile User Vision Operations
Put Away your plain item
1.
Log on to the mobile application.
2.
Navigate to the Manual Load page.
(M) Tasks > Manual Tasks > Manual Load
3.
Enter the Org Code if necessary.
4.
Enter the LPN for your plain item.
y
l
n
O
e
I
A
&
l
a
n
r
te
5.
Select <Load Full LPN> to load the contents of the LPN.
6.
Select F2 to return to the Manual Tasks menu.
7.
Navigate to the Drop Loaded LPNs page.
8.
9.
n
I
e
l
c
a
(M) Manual Tasks > Manual Drop
r
O
Enter your LPN in the LPN field.

Select [Ctrl + G} to generate a new LPN for the item.

Chapter 2 - Page 79
s
U
10. Enter XX_STORE as the destination subinventory and S1.1.1 as the destination locator for
the LPN.
11. Select <Drop Full LPN> to nest your LPN within the new LPN.
Put away your serial item
12. Navigate to the Manual Load page.
13. Enter the LPN for your serial item.

14. Select <Load Full LPN> to load the contents of the LPN.
15. Select F2 to return to the Manual Tasks menu.
16. Navigate to the Drop Loaded LPNs page.
(M) Manual Tasks > Manual Drop
17. Enter your LPN in the LPN field.

18. Enter XX_STORE as the destination subinventory, and S1.1.1 as the destination locator for
the LPN.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
19. Select <Transfer Contents>.

Chapter 2 - Page 80
s
U
Put away your lot item

20. Navigate to the Manual Load page.
21. Enter the LPN for your lot controlled item.

22. Select <Load Full LPN> to load the contents of the LPN.
23. Select F2 to return to the Manual Tasks menu.
24. Navigate to the Drop Loaded LPNs page.
(M) Manual Tasks > Goto Directed Move > Drop Loaded LPNs
Note you may be prompted to select equipment. If prompted, tab through the page, and
select done.
25. Select [Ctrl + L] in the Current Tasks field, to retrieve a list of current tasks.
26. Select your task from the list of values and press enter.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
Note: Notice your team subinventory locator populated in the To Sub and To Loc fields.
This is due to the put away rule you created in the previous lab.
r
O
27. Enter the subinventory and locator information in the Confirm fields to verify the destination
subinventory and locator.

Chapter 2 - Page 81
28. Select <Drop Full LPN> to drop the LPN in the locator.
29. Navigate to the Material Workbench
(N) Inquiry > Material Workbench
30. Enter XX_LOT in the Item / Revision field
y
l
n
O
e
I
A
&
l
a
n
r
te
31. Click Find
n
I
e
l
c
a
r
O

Chapter 2 - Page 82
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 83
s
U
Cross Docking to Outbound Staging Flow
y
l
n
O
e
s
U
Cross Docking to Outbound Staging Flow

If you enabled cross docking in your organization, the system checks for back orders sales
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 84
Cross Docking to WIP Staging Flow
y
l
n
O
e
s
U
Cross Docking to WIP Staging Flow

If you enable cross docking for your organization Warehouse Management checks for
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 85
Cross Docking to WIP Issue Flow
y
l
n
O
e
s
U
Explaining Cross Docking to WIP Issue Flow

The system can also suggest a direct WIP issue as a put away option. In this case, the system
first executes a receipt transaction into the default WIP staging lane, and then 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 86
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 87
s
U
Advanced Task Framework (ATF)
y
l
n
O
e
s
U
Advanced Task Framework

Advanced Task Framework enables you to configure and execute complex material flows for
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 88
ATF Capabilities
y
l
n
s
U
ATF Capabilities
You can use ATF to perform the following functions:
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 89
O
e
ATF Concepts
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 90
s
U
ATF Concepts
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 91
s
U
ATF Concepts
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 92
s
U
ATF Concepts
y
l
n
O
e
s
U
Load
Load is the act of picking material from a locator and transferring it into the hands of an
operator, onto equipment, into a tote, or onto a conveyor. An operator performs loads when
material needs to be moved. Loading is the first step performed for material movement.
I
A
&
l
a
Drop
Drop is the act of dropping loaded material into a locator. A load operation should always
precede a drop operation.
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 93
ATF Concepts
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 94
s
U
ATF Concepts
y
l
n
O
e
s
U
Material Grouping
You can use operation plans to control the material grouping in locators and LPNs during
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 95
ATF Concepts
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 96
s
U
ATF Example
y
l
n
O
e
s
U
ATF Example
ATF applies to standard and inspection receipts. You cannot use ATF for direct routed
receipts. Above is an example of a complex receiving process you can use ATF to map.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 97
ATF Setup
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 98
s
U
ATF Zones : Setup
y
l
n
O
e
s
U
Zones
A zone is a logical collection of locators sharing some common warehouse attributes. A
locator can exist in more than one zone and a zone may consist of locators from one or more
subinventories. You can also manage tasks by zone.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 99
ATF Operation Plan Setup
y
l
n
O
e
s
U
Operation Plan Setup

There are three types of operation plans standard, inspection, and cross dock. You can define
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 prespecified 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 2 - Page 100
Practice - Using Advanced Task Framework

Overview
In this practice you will create an operation plan, an operation plan selection rule, and receive
material against the operation plan.
Assumptions
Whse Mgmt Super user, Vision Operations (USA)Responsibility
Whse Mgmt Mobile User Vision Operations Responsibility
Tasks
Create an operation plan
1.
Create an operation plan named XX_team_op_plan that loads an item, drops it in to your
XX_REC subinventory, and suggests a put away location.
y
l
n
Create and operation plan selection plan

2.
O
e
Create an operation plan selection rule named XX_team and assign your operation plan to
the operation plan selection rule. Assign your XX_Plain item to the rule.
Receive and put away your plain item

3.
I
A
s
U
Use Advanced ATF to put away item XX_Plain after you receive it.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Solution Using Advanced Task Framework

Responsibility = Whse Mgmt Super user, Vision Operations (USA) Responsibility
Create an operation plan
1.
Navigate to the Operations Plans window.
(N) Setup > Warehouse Configuration > Warehouses > Operation Plans
2.
Enter Standard in the Plan Type field or select it from the list of values.
3.
Enter XX_Team in the Name field.
4.
In the Details tab Enter 10 in the first Seq field.
Enter Load, or select it from the list of values.

5.
Select the next line. 20 automatically defaults in the next Seq field.
Drop automatically populates in the Operation field.
7.
Enter Pre-specified as the subinventory determination method.
8.
Enter Pre-specified as the locator determination method, or select it from the list of values..
9.
Select the Zone/ Subinventory / Locator tab.
y
l
n
O
e
s
U
10. Enter XX_REC in the Subinventory field, and R7.1.1 in the Locator field.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

y
l
n
O
e
11. Select the Details tab.

12. Enter 30 in the next Seq field.
I
A
s
U
Enter Load in the Operation field, or select it from the list of values.
13. Enter 40 in the next Seq field Drop automatically populates in the Operation field..
&
l
a
15. Check the In Inventory check box. This transfers the material to a storage subinventory and
locator. Once material reaches this part of the operation plan it is tracked as on-hand
quantity.
n
r
te
16. Enter Putaway rule as the Determination Method in the Locator field.
n
I
e
17. Save the operation plan.
l
c
a
r
O

y
l
n
18. Check the Enabled check box to enable to the operation plan.
19. Save the operation plan.
I
A
Create an operation plan selection rule

20. Navigate to the WMS Rules window.
&
l
a
O
e
s
U
n
r
te
21. Enter Operation Plan Selection in the Type field or select it from the list of values.
22. Enter XX_Team in the Name field.
n
I
e
Enter a rule description in the Description field, or select it from the list of values.
l
c
a
23. Enter Inbound in the Activity field, or select it from the list of values.
r
O
24. Enter Standard in the Plan Type field, or select it from the list of values.
25. Enter XX_team_op_plan in the Return Value field27. Assign a weight to your rule.

Note: The rule weight should be high to avoid another rule taking precedence over your
operation plan selection rule.
26. Enter the following Restrictions:
Seq
Object
10
Item
Parameter
Item
Operator
Object
Parameter
/ Value /
LOV
Constant
character
XX_Plain
(where XX
is the
number
assigned by
your
instructor)
28. Save your work.

29. Select the Enabled check box to enable the operation plan.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
30. Save your work.
r
O

s
U
Receive and put away your plain item

Responsibility= Whse Mgmt Mobile User Vision Operations Responsibility
31. Navigate to the Receipt page.
(M) Inbound > Receive > PO > Receipt
Enter W1 as the organization if necessary.
32. Enter the PO Number you created in the Receiving Materials practice.
33. Enter the Line number of your plain item.
34. Generate an LPN for your item.
35. Enter RCV as the subinventory, and select a locator.
36. Enter 100 in the QTY field.
y
l
n
O
e
I
A
&
l
a
s
U
n
r
te
n
I
e
l
c
a
37. Select <Done>.
38. Return to the Main Menu.
r
O
39. Navigate to the Move LPN page.
(M) Tasks > Directed Tasks > Directed Move > Move Any LPN


41. Select <Drop>.
Note: Notice the system directs you to drop the item in the location you setup in your
operation plan.
y
l
n
42. Confirm your XX_REC subinventory in the first Confirm field.

43. Confirm your XX_R7.1.1 locator in the second Confirm field.
I
A
44. Select <Drop Full LPN>.

&
l
a
46. Select <Drop>.
O
e
s
U
n
r
te
Note: Notice the system directs you to drop the LPN in a different location. The system
derived this location from an existing put away rule.
n
I
e
l
c
a
r
O

47. Confirm the To Sub and To Loc.

48. Select <Drop Full LPN>.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Implementation Considerations
y
l
n
O
e
s
U
When you create subinventories, you must consider the following:
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

y
l
n
O
e
s
U
Before you set up items, you must determine if your warehouse will accept supplier part
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

y
l
n
O
e
s
U
When you receive items into the warehouse you must account for the following system
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

y
l
n
O
e
s
U
Explaining Modes of Inspecting Serialized Material

When you define your items you must decide which mode of serial number entry you plan to
use. The modes are controlled through a form function parameter. For more information, refer
to the Oracle Warehouse Management Implementation Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Summary
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
11i Warehouse Features

Chapter 3
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 1
s
U
11i Warehousing Features
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 2
s
U
Objectives
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 3
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 4
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 5
s
U
Compliance Labeling
y
l
n
O
e
s
U
Supplier Labeling
Compliance labeling enables users to move inventory more efficiently through the warehouse.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 6
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 7
s
U
Warehouse Management versus Partner Label Printing

Responsibilities
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 8
s
U
Label Printing Components
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 9
s
U
Label Formats
y
l
n
O
e
s
U
Label Formats
When you define label formats, you determine the fields associated with a particular label and
label type.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 10
Label Types
y
l
n
O
e
s
U
Label Types
Warehouse Management supports the following label types:
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 11
Label Types
y
l
n
O
e
s
U
Label Types
LPN: This label provides information about the LPN. It does not contain content
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 12
Setup
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 13
s
U
Registering Label Formats
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 14
s
U
y
l
n
O
e
s
U

After you set up label formats, you must associate the label types to a specific warehouse
business flow. This association enables the system to print the label type automatically as part
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 15
Label Format Assignment Rules
y
l
n
O
e
s
U
Label Format Assignment Rules

Label format assignment rules associate a label to a business object based on parameters 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 16
Defining and Assigning Printers
y
l
n
O
e
s
U
Defining and Assigning Printers

You must define printers and assign them to the appropriate label types before you can print
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 Administrators Guide Configuration.
For more information on assigning printers see, Choosing Printers for Shipping Documents
and Labels Oracle Order Management Implementation Manual.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 17
Printing Modes
y
l
n
O
e
s
U
Printing Modes
Note: The profile option WMS: Label Print Mode determines the printing mode.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 18
Asynchronous Mode
y
l
n
O
e
s
U
Asynchronous Mode
In Asynchronous Mode, Warehouse Management creates an Extensible Markup Language
(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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 19
Synchronous Mode - Generic
y
l
n
O
e
s
U
Synchronous Mode Generic

Generic Synchronous Mode is a real-time integration between Warehouse Management and 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 20
Synchronous Mode TCP / IP
y
l
n
O
e
s
U
Synchronous Mode TCP/IP

Synchronous Mode TCP/IP is a real-time integration mode between Warehouse Management
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 21
Practice - Compliance Labeling

Overview
In this practice you will learn how to set up labels in Warehouse Management. It assumes that
you have defined your label in the appropriate third party software.
Assumptions
Whse Mgmt Super User, Vision Operations (USA)
Tasks
Define a label format
1.
Define an LPN content label named XX_LPN_Content with the following information:
Item
Quantity
UOM
Organization
License Plate Number
y
l
n
O
e
Assign a label type to a business flow

2.
Create a label format assignment rule

3.
s
U
Assign the LPN Content label type to the Receiving Put Away Drop business flow. Assign
the label type to the mobile user your instructor assigned to you.
I
A
Create a label format assignment rule that generates the label you created for your plain
item.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 22
Solution Compliance Labeling

Define a label format
Responsibility = Whse Super User Vision Operations (USA)
1.
Navigate to the Define Label Formats window.
(N) Setup > Warehouse Configuration > Printers & Devices > Define Label Formats
2.
Enter LPN Content in the Label Type field or select it from the LOV.
3.
Enter the following information in the Label Formats region.

Name = XX_LPN_Content
Description = Team XX LPN Content
y
l
n
O
e
I
A
&
l
a
4.
s
U
n
r
te
Select Label Fields and Variables.
5.
n
I
e
(B) Label Fields and Variables
l
c
a
Enter the following information in the Label Fields region.
r
O
Field Name
Field Description
Field Variable Name
Item
Item
Item
Quantity
Qty
Quantity

Chapter 3 - Page 23
Field Name
Field Description
Field Variable Name
UOM
UOM
UOM
Organization
Organization
Org
LPN
Note: Field Variable Names are the names that appear on the actual labels.
y
l
n
O
e
I
A
6.
Save your work.
&
l
a
s
U
n
r
te
(M) File > Save
n
I
e
Assign a label type to a business flow

7.
r
O
8.
l
c
a
Navigate to the Assign Label Types to Business Flows window.

(N) Setup > Warehouse Configuration > Printers and Devices > Assign Label Types to
Business Flows.
Expand the Business Flows tree.


Chapter 3 - Page 24
9.
Select the Receiving Put Away Drop business flow.
10. Create a new label type.
(M) File > New
11. Enter the following information:

Label Type = LPN Content
Level = User
Value = your mobile user
y
l
n
O
e
I
A
&
l
a
12. Save your work.
(M) File > Save.
s
U
n
r
te
Create a label format assignment rule
n
I
e
13. Navigate to the Rules window.
l
c
a
r
O
14. Enter the following information:

Type = Label Format
Name = XX_label_format
Description = Team XX label format rule

Chapter 3 - Page 25
Return Value = XX_LPN_Content

Weight = 900
15. Enter the following information in the restrictions tab:
Seq= 10
Object = Item
Parameter = Item
Operator = =
Object = Constant character
Parameter / Value / LOV = XX_Plain
y
l
n
O
e
I
A
&
l
a
16. Save your work.
(M) File > Save
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 26
s
U
Viewing Label Requests
y
l
n
O
e
s
U
Viewing Label Requests

When a user requests a label, the system creates a record. The label request record contains 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 27
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 28
s
U
Task Management
y
l
n
O
e
s
U
Task Management
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, 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 29
Task Types
y
l
n
O
e
s
U
Task Types
Each task the system generates requires a System Task Type. Warehouse Management
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 30
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.
For more information see Setup Warehouse Task Types, Oracle Warehouse Management
Users Guide.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 31
s
U
Setting Up Task Type Rules
y
l
n
O
e
s
U
Setting Up Task Type Rules

Task type rules determine which task type to use. You use the Task Type Rules window to
define Task Type Rules.
(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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 32
Task Dispatch Engine
y
l
n
O
e
s
U
Task Dispatch Engine

The task dispatch engine evaluates rules based on priority, and assigns tasks to users based 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 33
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 34
s
U
Resource Skills
y
l
n
O
e
s
U
Resource Availability
Managers can dispatch tasks based on resource availability and skill sets. After the system
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..
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 35
Available Equipment and Resources
y
l
n
O
e
s
U
Available Equipment
During implementation, you set up equipment as serialized items within the item master. You
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 36
WMS Control Board
y
l
n
O
e
s
U
Warehouse Control Board

The WMS Control Board is a tool managers use to monitor, plan, control, and execute various
warehouse operations, including the following:
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 37
Task Status
y
l
n
O
e
s
U
Task Status
The task status is the current task state. Task statuses are as follows:
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 operators 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 38
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 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 39
s
U
WMS Control Board
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 40
s
U
Exception Management
y
l
n
O
e
s
U
Exception Management
A task exception is an unexpected task result, such as if material does not exist in a picking
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 41
Task Setup Steps
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 42
s
U
Practice - Task Setup

Overview
In this practice you will define a new employee resource, assign a new task type to your
employee resource, and create a task type rule.
Assumptions
Whse Mgmt Super User, Vision Operations (USA) responsibility
Tasks
Define a new employee resource
Define a new employee resource named XX_EMP. XX represents a number assigned by your
instructor. Associate the resource with the Picking department.
Define a new task type and assign your employee resource to it
y
l
n
Define a new task type named XPCK. X represents a number assigned to you by your instructor.
Assign your newly created employee resource to the task type.
O
e
Define a new task type rule
s
U
Define a new task type rule named XX_Task_Type. Use your XPCK task type as the return
value. The rule should restrict the picking from your XX_STORE subinventory to only someone
with the task type of XPCK.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 43
Solution Task Setup

Define a new employee resource
1.
Navigate to the Resources window.
(N) Setup > Warehouse Configuration > Resources > Resources
2.
In the Resource field, enter XX_EMP. XX represents a number assigned by your instructor.
3.
In the Description field, enter Employee Resource.
4.
Select Person from the Type field.
5.
In the UOM field, select Ea.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
6.
r
O
Select Employees

Chapter 3 - Page 44
s
U

7.
(B) Employees
In the Employees field, select the employee number assigned to you by your instructor.
y
l
n
8.
Save your work.
9.
Navigate to the Departments window.
O
e
I
A
s
U
(N) Setup > Warehouse Configuration > Resources > Departments
10. Query the department named Picking.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 45
11. Select Resources.
(B) Resources
12. Select the New button on the toolbar or select New from the File pull down menu.
13. Enter your XX_EMP resource or select it from the list of values.
y
l
n
14. Warehouse Management does not utilize the Units field but it is required. Enter 1.
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 46
s
U
y
l
n
15. Save your work.
O
e
Define a new task type and assign your employee resource to it
s
U

16. Navigate to the Standard Operations window.
I
A
(N) Setup > Warehouse Configuration > Tasks > Standard Task Types
17. Select New from the File pull down menu or from the toolbar.
18. In the Code field, enter XPCK.
&
l
a
n
r
te
19. In the Description field, enter Pick Task Type.
n
I
e
20. Select Picking in the Department field.

21. In the Task Type field, select Pick.
l
c
a
r
O

Chapter 3 - Page 47
22. Select Operation Resources.
(B) Operation Resources
y
l
n
23. Enter 10 in the Seq field.
O
e
24. Enter, or select from the list of values, your XX_EMP resource in the Resource field.
s
U
25. Warehouse Management does not utilize the Usage field but it is a required field. Enter 1 in
this field. The inverse field populates automatically when you exit the usage field.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 48
26. Save your work.
y
l
n
Define a new task type rule

O
e
27. Navigate to the Rules window.
s
U
I
A
28. In the Type field, select Task Type Assignment from the list of values.
29. In the Name field, enter XX_Task_Type.
&
l
a
30. In the Description field, enter Task Type Rule.
n
r
te
31. Select your XPCK task type from the list of values in the Return Value field.
32. Enter 600 in the Weight field.
n
I
e
l
c
a
r
O

Chapter 3 - Page 49
33. Within the Restrictions tab, select the Seq field. 10 will default.
y
l
n
34. In the Object field, enter Source Subinventory.
O
e
35. In the parameter field, select Subinventory Name.

36. Enter = as the Operator.
I
A
37. In the Object field, enter Constant character.
s
U
38. Enter your XX_STORE subinventory as the Parameter/Value/LOV.
&
l
a
39. Enable your rule.

40. Save your work.
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 50
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 51
s
U
Label Printing Implementation Considerations
y
l
n
O
e
s
U
Label Printing Implementation Considerations

Warehouse Management supports two types of label printing configurations:
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 52
field data variables. The third party software must also read the XML format Warehouse
Management generates.
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 53
s
U
Task Type Implementation Considerations
y
l
n
O
e
s
U
Task Type Implementation Considerations

Prior to defining entities, you must identify the task types for your implementation. Use the
following questions to help define task types:
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,
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 54
in the warehouse? This helps determine which equipment items should be defined and
how they should be associated to task types.
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 55
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 56
s
U
Summary
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 57
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 3 - Page 58
s
U
11i Outbound Logistics

Chapter 4
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 1
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 2
s
U
Objectives
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 3
s
U
Objectives
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 4
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 5
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 6
s
U
y
l
n
O
e
s
U

Outbound logistics enables operators to pick, pack, and ship orders to customers. Outbound
logistics contains the following components:
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

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
enables them to redistribute tasks as needed. They can monitor the progress of tasks as well as
manually dispatch tasks to operators.
Consolidation
Warehouse Management enables operators to consolidate partially filled containers in to 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
Managers can use Warehouse Management to schedule outbound carrier appointments, dock
door availability, and staging lane usage within the warehouse.
Shipment Verification and Close
Once an operator picks and loads an order, Warehouse Management automatically determines
the items and quantities to deduct from inventory.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 8
s
U
Overview of Picking
y
l
n
O
e
s
U
Overview of Picking
Picking enables operators to pick material to fulfill orders. Warehouse Management supports
three types of picking, order picking, replenishment picking, and WIP picking. Warehouse
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 9
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 10
s
U
Sales Order Picking
y
l
n
O
e
s
U
Sales Order Picking

Warehouse Management dispatches sales order tasks to qualified operators based on their skill
set and equipment. After an operator picks a sales order task, they deliver it to a staging lane to
prepare it for shipping.
Note: All picks are delivered to a staging subinventory and locator.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 11
Replenishment Picking
y
l
n
O
e
s
U
Replenishment Picking
Warehouse Management dispatches replenishment tasks to qualified operators to replenish
forward picking areas.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 12
WIP Picking
y
l
n
O
e
s
U
WIP Picking
Warehouse Management dispatches WIP picking tasks to qualified operators to pick material
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 13
Pick Release Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 14
s
U
Components of Pick Release
y
l
n
O
e
s
U
Components of Pick Release

Warehouse Management uses pick release rules to store the criteria used to select sales 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 todays date.
Manually pick release orders: Managers can use the pick release window to manually
pick release orders.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 15
Overview of Picking Rules
y
l
n
O
e
s
U
Overview of Picking Rules

Picking rules create material allocations and direct operators to pick material from specific
locations.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 16
Release Sequence Rules
y
l
n
O
e
s
U
Release Sequence Rules

Release sequence rules specify the order the system allocates eligible delivery lines. This
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 17
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.
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 18
s
U
Pick Slip Grouping Rules
y
l
n
O
e
s
U
Pick Slip Grouping Rules

You can create pick slip grouping rules to organize how picking lines for released sales orders
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 19
Release Rules
y
l
n
O
e
s
U
Release Rule
Release rules store the criteria used to select sales orders for release. If trips do not exist for
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 20
Cross Docking
y
l
n
O
e
s
U
Cross Docking
Before it uses the rules engine to determine a put away suggestion, Warehouse Management
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 21
Cross Docking
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 22
s
U
Cross Docking
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 23
s
U
Direct Ship
y
l
n
O
e
s
U
Direct Ship
Warehouse Management enables operators to ship confirm material for a sales order line
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 24
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 25
s
U
Pick Methodologies
y
l
n
O
e
s
U
Pick Methodologies
Pick methodologies refer to the different ways an operator can fulfill a group of orders. For
example, an operator can pick one order or multiple orders at the same time. The type of
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 system dispatches a discrete group of tasks, grouped by pick slip
grouping rules.
Order picking: The system 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 system dispatches tasks line by line, regardless of the picking
location, or to whom other lines on the order have been dispatched.
Label picking: The system 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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 26
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.
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 methodology,
and specify an order picking rule type at pick release, then the system bypasses all bulk
picking checks at the subinventory and item levels, and does not bulk pick any material
as part of that pick release.
Paper-based picking: operators pick according to a paper pick slip printed at pick release.
This enables an operator to dispatch tasks to themselves when working in a paperassisted environment.
Cluster picking: A specified number of clusters are dispatched to a single operator at
once. A cluster is defined as all the tasks related to a sales order delivery, manufacturing
job, or schedule.
User-defined pick grouping: See, Defining Pick Slip Grouping Rules, Oracle Inventory
User's Guide.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 27
s
U
Picking Rules Order Allocation
y
l
n
O
e
s
U
Picking Rules Order Allocation

You can use picking rules to allocate material as follows:
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 28
Rules Engine Framework
y
l
n
O
e
s
U
Rules Engine Framework

The rules engine enables directed picking and put away, assigns newly received material to a
cost group, ensures customer compliant labeling, assigns tasks to a resource with the
appropriate training and equipment, and selects the correct operation plan for a task. You can
base rules on nearly any attribute in the database, including user-defined flexfields. Strategies,
or a collection of rules, can be organization specific, customer specific, item specific, or
specific to one of many additional business objects.
When the system releases a pick wave to the warehouse floor, the rules engine determines the
allocation suggestions. You can create picking rules for many business scenarios such as, to
ensure stock rotation, or meet customer requirements such as stock condition or quality. You
can allocate material by a FIFO or FEFO rule at the organization level, by a picking rule that
depletes a location to free up additional warehouse space, or by cost group ownership. You can
also use the rules engine model customer requirements so a single lot fills an entire order, or
warehouse preferences so an item is picked from a single locator.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 29
Rules Definition Directed Picking
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 30
s
U
Allocation Modes
y
l
n
O
e
s
U
Explaining Allocation Modes

You can use the Allocation Mode field, in the Rules window, only for picking rules. The
allocation modes include the following:
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 31
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-ofmeasure, 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 three shiniest quarters, then the two best dimes, and finally, the four brightest
pennies, for a total of $0.99. If there are fewer than three quarters available, the clerk tries to
find more dimes, or if necessary, more nickels, and finally, more pennies.
The only difference between this example and how the rules engine actually allocates material
using this allocation mode is when the clerk would be unable to make exact change. If there
were only four quarters and five dimes in the clerks cash drawer, it would be impossible to get
exactly $0.99. The rules engine would allocate three quarters and two dimes as before, but
when it fails to find any pennies for the last $0.04, it would roll back up to larger coins, on the
assumption that while the warehouse does not want to break the larger units of measure, it can
if necessary to avoid customer backorder.
Allocate LPN and Loose
This allocation mode considers packed and loose material equally; however, the rules engine
selects an LPN if it allocates material from a locator that contains packed material. Instead of
allowing an operator to select one of the LPNs that contains the required item, the rules engine
chooses a particular LPN. During implementation, you can define restrictions or sort criteria
that restrict or prioritize packed material or loose material. The system displays the 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 32
s
U
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 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 33
s
U
Allocation Modes: No LPN Allocation
y
l
n
O
e
s
U
Allocation Modes: No LPN Allocation

If you use the No LPN Allocation mode, allocations are not made at the LPN level. In the
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 34
Allocation Modes: No LPN Allocation, Prioritize Pick UOM
y
l
n
O
e
s
U
Explaining No LPN Allocation, Prioritize Pick UOM

If you use the No LPN Allocation, Prioritize Pick UOM, allocations are not made to the LPN
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 35
Allocation Modes: Allocate LPN and Loose
y
l
n
O
e
s
U
Explaining Allocate LPN and Loose

If you use Allocate LPN and Loose, allocations are made to the LPN level, and pick unit-ofmeasure is completely ignored. The rule restrictions are honored, so lot A is discarded from
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 36
Allocation Modes: Allocate Entire LPN Only
y
l
n
O
e
s
U
Explaining Allocate Entire LPN Only

If you use Allocate Entire LPN Only, the system allocates material at the LPN level, and
ignores the pick unit of measure. It considers only LPNs that can be completely allocated for
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 37
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 allocation
of loose material should follow a rule with the allocation mode Allocate Entire LPN Only.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 38
s
U
Practice - Creating a Picking Rule

Overview
In this practice you will define a new picking rule, a new strategy, and create a strategy
assignment.
Assumptions
Whse Mgmt Super User, Vision Operations (USA) responsibility
Tasks
Create a picking rule
1.
Define an ascending picking rule named XX_Each_Row where XX represents the number
assigned to you by your instructor.
Define a new strategy for your picking rule

2.
y
l
n
Define a strategy named XX_Pick where XX represents the number assigned to you by your
instructor.
O
e
Assign your strategy

3.
Assign your strategy to your XX_Store subinventory.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 39
s
U
Solution - Creating a Picking Rule

Create a new picking rule
Responsibility = Whse Mgmt Super User, Vision Operations
1.
Navigate to the WMS Rules window.
2.
Select Pick from the Type list of values.
3.
In the Name field, enter XX_Each_Row.
4.
In the Description field, enter Ascending pick rule.
5.
In the Allocation Mode field, select Allocate LPN and Loose from the LOV.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
6.
Select the Sort Criteria tab.
7.
Enter 10 in the Seq field.
8.
9.
l
c
a
r
O
In the Object field, select Source Locator.

In the Parameter field, select Picking Order.

Chapter 4 - Page 40
s
U
10. In the Order field, select Ascending.
y
l
n
11. Enable your rule by selecting the Enabled check box.
O
e
12. Save your work.

Create a new strategy
I
A
13. Navigate to the WMS Strategies window.
s
U
(N) Setup > Warehouse Configuration > Rules > Warehouse Execution > Strategies
&
l
a
14. Select Pick from the Type list of values.

15. In the Name field, enter XX_Pick.
n
r
te
16. In the Description field, enter XX picking strategy.
n
I
e
17. In the Rules area, enter 10 in the Seq field.
l
c
a
18. Select your XX_Each_Row rule from the list of values in the Rule Name field.
r
O
19. In the Date Type field, select Always from the list of values.

Chapter 4 - Page 41
y
l
n
20. Enable your strategy by selecting the Strategy Enabled check box.
O
e
21. Save your work.

Assign your strategy
I
A
22. Navigate to the Strategy Assignments window.
s
U
Workbench
&
l
a
23. Select Pick from the Type list of values.
n
r
te
24. Enter the number assigned to you by your instructor in the Seq field.
25. Enter XX_Pick in the Strategy field.
n
I
e
26. Enter XX_Store in the Source Subinventory field.
l
c
a
r
O
28. Select the Strategy Enabled check box to enable your strategy.
29. Save your work.

Chapter 4 - Page 42
(M) File > Save
y
l
n
O
e
30. Exit the Rules Workbench
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 43
s
U
Practice - Pick Release

Overview
In this practice you will add your items to a price list, and book and pick release a sales
order.
Assumptions
Tasks
Assign Items to a price list
1.
Add you three items (XX_Plain, XX_Lot and XX_Serial) to the corporate price list using
the following information:
Product Context
Item
Product Attribute
Item Number
Product Value
XX_Plain, XX_Lot, or XX Serial
Value
1
y
l
n
O
e
Create a sales order

2.
s
U
Use the following information to create and book a sales order:

Customer Number
1005
Order Type
Mixed
Salesperson
Jonathan Smith
Ordered Item
XX_Plain
Qty
10
Ordered Item
XX_Lot
Qty
10
Ordered Item
XX_Serial
Qty
10
I
A
&
l
a
n
r
te
n
I
e
Pick release a sales order

3.
l
c
a
Use the following information to pick release your sales order:

Based on Rule
WMS Pick Release
Order Number
your order number
Scheduled Ship Dates
Empty
Requested Dates
Empty
Warehouse
W1
r
O

Chapter 4 - Page 44
Pick Slip Grouping Rule
Order Number
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 45
s
U
Solution Pick Release

Responsibility = Whse Mgmt Super User Vision Operations (USA)
Assign items to a price list
1.
Navigate to the Advance Pricing Price Lists window.
(N) Order Management > Pricing > Price Lists > Price List Setup
2.
Query the Corporate price list.
3.
Enter a new line on the price list.
(M) File > New
4.
Enter the following information on the List Lines tab for the XX Plain Item.
Product Context
Item
Product Attribute
Item Number
Product Value
XX_Plain
Value
1
5.
Repeat steps 3 and 4 for your XX_Lot and XX_Serial items.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 46
s
U
6.
Save your work.
(M) File > Save.
Create a Sales Order

7.
Navigate to the Sales Order window.
8.
(N) Order Management > Orders, Returns > Sales Orders
Enter the following information on the Order information tab:

Customer Number
1005
Order Type
Mixed
Salesperson
Jonathan Smith
Note: When you enter the customer number, and tab through the remaining customer
screens, the Customer, Ship To Location, and Bill to Location populate automatically.
y
l
n
O
e
I
A
&
l
a
n
r
te
9.
n
I
e
l
c
a
Select the Line Items tab.
r
O
10. Enter the following information for your XX_Plain Item.

Line 1
Ordered Item
XX_Plain
Qty
10

Chapter 4 - Page 47
s
U
UOM
Ea
11. Select the Shipping tab.

12. Verify W1 is the Shipping Warehouse.
13. Select the Main tab.
14. Enter the following information for your XX_Lot item
Ordered Item
XX_Lot
Qty
10
UOM
Ea
16. Verify W1 is the Shipping Warehouse.
17. Select the Main tab.
18. Enter the following information for you XX_Serial item.
Line 3
Ordered Item
XX_Serial
Qty
10
UOM
Ea
y
l
n
O
e
20. Verify W1 is the shipping Warehouse.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 48
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 49
s
U
21. Book your sales order.
(B) Book Order
22. Note your order number. The Order Number appears on the Main tab of the Sales order
window.
Order Number: _____________________
y
l
n
O
e
I
A
23. Close the Sales Order window.
&
l
a
Pick Release a Sales Order
s
U
n
r
te
24. Navigate to the Release Sales Orders for Picking page.
(N) Outbound Logistics > Release Pick Waves
n
I
e
25. Enter WMS Pick Release in the Based on Rule field.
l
c
a
26. Select Unreleased from the drop-down list in the Orders field.
r
O
27. Enter your order number in the Order Number field.

28. Remove the Scheduled Ship Dates or the Requested Dates if they appear.

Chapter 4 - Page 50
y
l
n
29. Select the Inventory tab.
O
e
30. Verify W1 appears in the Warehouse field.

31. Enter Order Number in the Pick Slip Grouping field.
I
A
s
U
32. In the Default Stage region, enter STA in the Subinventory field, and L1.1.1 in the Locator
field.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 51
y
l
n
33. Select Concurrent to release your sales order for picking.
O
e
(B) Concurrent
34. Note the request number: _________________________
I
A
35. Note the batch number. _______________________
s
U
36. Navigate to the Requests window to view your concurrent request and ensure it completed
successfully.
&
l
a
(M) View > Requests
n
r
te
Close the Release Sales Orders for Picking window.
n
I
e
l
c
a
r
O

Chapter 4 - Page 52
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 53
s
U
Automated Task Dispatch, Allocation and Assignment
y
l
n
O
e
s
U
Automated Task Dispatch and Allocation

After making material allocations, the system determines the task type and dispatches it to an
appropriately trained operator. The system may assign task types based on the source 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 54
Practice - Picking Execution

Overview
In this practice you will perform a picking task, and use the WMS Control Board to monitor the
task.
Assumptions
Whse Mgmt Super User, Vision Operations (USA)
Whse Mgmt Mobile User, Vision Operations (USA)
Tasks
Verify the picking tasks were created
Use the WMS Control Board to verify the picking tasks were created with the status Pending.
Perform the picking tasks for your order
y
l
n
Perform the picking tasks you created during pick release, and place them in the L1.1.1 locator
of the STA staging subinventory.
O
e
Verify the picking tasks are complete
s
U
Once you complete your picking tasks, use the WMS Control Board to verify the task is
complete.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 55
Solution Picking Execution

Verify the picking tasks were created
1.
Navigate to the WMS Control Board.
2.
(N) Inquiry > Warehouse Control Board
Select Outbound from the Source alternative region.

Note: A source is required when you perform a task query.
3.
Select Pending from the Status alternative region.

Note: A status is required when you perform a task query.
y
l
n
O
e
I
A
&
l
a
n
r
te
4.
5.
n
I
e
l
c
a
r
O
Click Find.
Verify your tasks appear.

Chapter 4 - Page 56
s
U
6.
y
l
n
Close the window.
Perform the picking tasks for your order

Whse Mgmt Mobile User, Vision Operations (USA)
7.
Log on to the mobile device.
8.
Navigate to the Accept Any Tasks page.
9.
&
l
a
I
A
O
e
s
U
(N) Tasks > Directed Tasks > Interleaved Tasks > Accept Any Task
n
r
te
Enter W1 as the organization.
10. Select <Done> on the Choose Eqp / Sub page.
n
I
e
11. The first of your tasks should now appear. The tasks appear by sales order line.
l
c
a
r
O

Chapter 4 - Page 57
12. Confirm the subinventory listed in the Sub field.

13. Confirm the Locator in the Loc / LPN field.
y
l
n
14. Select an LPN if necessary.
O
e
15. Confirm the item in the Item field.

16. Confirm the pick quantity in the Confirm field.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 58
s
U
17. Use <CTRL+G> to generate a new LPN to transfer the pick quantity.
18. Select <Load and Drop>
19. Confirm the to subinventory and locator.
20. Use <CTRL+G> to generate a new drop LPN.
21. Note the Drop LPN ________________________.
y
l
n
O
e
I
A
22. Repeat steps 11through 20 for the remaining items.

Verify the picking tasks are complete
&
l
a
s
U

23. Navigate to the WMS Control Board.
n
r
te
(N) Inquiry > Warehouse Control Board
n
I
e
24. Select Outbound from the Source alternative region.
l
c
a
25. Select Completed from the Status alternative region.

26. Click Find.
r
O

Chapter 4 - Page 59
y
l
n
27. Verify your tasks appear with the Status Completed.
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 60
s
U
y
l
n
28. Close the window.
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 61
s
U
WMS Control Board
y
l
n
O
e
s
U
WMS Control Board

The WMS Control Board enables managers to view workloads across the entire warehouse,
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 62
- Remove task
- 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 63
s
U
WMS Control Board
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 64
s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 65
s
U
Advance Pick Load
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 66
s
U
Advanced Pick Load Setup
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 67
s
U
Advanced Pick Load Page Setup
y
l
n
O
e
s
U
Advanced Pick Load Setup

During implementation, you can optionally use the Pick Load Page Setup window to arrange
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:
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 68
Transfer LPN: Transfers the contents of the LPN to another LPN (Transfer LPN).
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.
Exception: Enables operators to perform and record any picking exceptions.
Skip Task: Allows operators to skip a task.
Info: Provides information about the picking document.
Page Level
This page enables you to control the behavior of attachments, catch weight, and exceptions
when picking partial lot quantity.
Attachments: The choice available for display are:
- Always: The attachment button is always displayed.
- By Request: The attachment button displays by request.
- Never: The attachment buttons is never displayed.
Catch Weight Entry: The available choices are:
- Hide: Catch weight entry is hidden.
- Mandatory: Catch weight entry is mandatory.
- 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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 69
s
U
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 70
s
U
Advanced Pick Load Use
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 71
s
U
Advanced Pick Load Task Setup
y
l
n
O
e
s
U
Advanced Pick Load Task Setup

The task filter window enables you to determine which tasks the picking page can perform. If
you include a task type, then the picking page can perform the task type. You can use task
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 72
Advanced Pick Load Menu Setup
y
l
n
O
e
s
U
Advanced Pick Load Menu Setup

Form function parameters control the appearance and behavior of the pick load page. The
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 73
Advanced Pick Load Exceptions
y
l
n
Advanced Pick Load Exceptions

Exception types determine the changes an operator can make.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 74
s
U
O
e
Advanced Pick Load - Execution
y
l
n
O
e
s
U
Advanced Pick Load - Execution

An operator can choose to scan either the LPN or locator. The system automatically 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 75
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 76
s
U
Catch Weight Description
y
l
n
O
e
s
U
Catch Weight
Catch weight pricing is a term the grocery industry uses when pricing is based on a unit of
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 77
Catch Weight Benefits
y
l
n
O
e
s
U
Catch Weight Benefits

Catch weight pricing is not the full dual unit of measure support Oracle Process Manufacturing
uses. Warehouse Management uses the secondary quantity for pricing only, and not to maintain
on hand balances.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 78
Catch Weight Item Setup
y
l
n
O
e
s
U
Catch Weight Setup

To setup catch weight, you must define the item as catch weight controlled. To do this, you set
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 79
For more information on catch weight see: Main Attribute Group, Oracle Inventory Users
Guide, and Setting up Catch Weight, Oracle Warehouse Management Users Guide.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 80
s
U
Catch Weight Setup
y
l
n
O
e
s
U
Catch Weight Setup

In addition to defining the item attributes, you must perform other setup steps. You must 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,
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 81
Catch Weight Use
y
l
n
O
e
s
U
Catch Weight Use

Depending on the configuration of the Advanced Pick Load page, the secondary quantity may
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 82
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 83
s
U
Consolidation
y
l
n
O
e
s
U
Consolidation
Consolidation enables multiple operators to drop material assigned to a delivery in to the same
locator or LPN prior to placing the consolidated load in a staging lane.
Note: If necessary, operators can ship material directly from the consolidation location.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 84
Consolidation
y
l
n
O
e
s
U
Staging Moves
Moves staged LPNs to another staging, consolidation or packing locators.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 85
Consolidation Setup
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 86
s
U
Consolidation Inquiry
y
l
n
O
e
s
U
Consolidation Inquiry
Once material is consolidated, it is ready for further processing, such as packing, shipping, or
loading. It is essential operators know the status of consolidated material so they can 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 87
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
Note: If the LPN contains material belonging to more than one order, it displays multiple
orders.
Query by Delivery
Query by delivery displays all LPNs for a particular delivery.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 88
s
U
Cartonization
y
l
n
O
e
s
U
Cartonization
Warehouse Management uses cartonization to suggest the best packaging configuration for a
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.
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 point.
Operators can pack material in a storage container during receipt, and pack it again during
sales order picking into a final shipping container.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 89
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.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 90
s
U
Cartonization
y
l
n
O
e
s
U
Cartonization Setup
Setup for cartonization uses Category and Category Set functionality. There are two pre-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 Users Guide.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 91
Packing
y
l
n
O
e
s
U
Packing Material
Packing involves transferring of loose items or LPNS into an LPN. Operators can pack items
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 92
Packing Workbench Flow
y
l
n
O
e
s
U
Packing Flow
Query eligible items: Look for eligible items to pack.
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 93
Eligible Material
y
l
n
O
e
s
U
Eligible Material
The packing workbench enables you to pack material in receiving, but not delivered to
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 94
Mobile Packing
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 95
s
U
Packing Workbench and Outbound Logistics
y
l
n
O
e
s
U
Packing Workbench and Outbound Logistics

To use the Packing Workbench to pack outbound material, operators must perform packing
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 96
Packing Workbench and Inbound Logistics
y
l
n
O
e
s
U
Packing Workbench and Inbound Logistics

To use the Packing Workbench to pack inbound material, the packing station must reside in a
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 97
Packing Initialization
y
l
n
O
e
s
U
Packing Initialization
To perform packing tasks the operator enters the transaction source, and then a packing 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 98
LPN Pack
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 4 - Page 99
s
U
LPN Unpack
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
LPN Split
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
LPN Reconfiguration
y
l
n
O
e
s
U
LPN Reconfiguration
To perform LPN reconfiguration, an operator scans an LPN and chooses either Merge up or
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

LPN close
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Practice - Packing Workbench

Overview
In this practice you will use the packing workbench to pack the material you picked in
the previous practice.
Assumptions
Tasks
Use the Packing Workbench to pack the material you picked
1.
Query for a packing station within the STA subinventory.
2.
Select Outbound as the source, and LPN Pack as the process.
3.
Pack the following items in to one LPN:

XX_Plain
XX_Lot
XX_Serial
4.
y
l
n
O
e
Close the LPN and exit the Packing Workbench
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Solution Packing Workbench

Use the Packing Workbench to pack the material you picked
1.
Navigate to the Packing Workbench.
(N) Material Manager > Material Transaction > Packing Workbench
2.
Query for a packing station within the STA subinventory. Packing stations are locators of
the type Packing.
3.
Select Outbound in the Source region.
4.
Select LPN Pack as the Packing process.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
5.
r
O
Click Find.

s
U
6.
Enter a new LPN in the Scanned Value field.
7.
Note the LPN number ______________________.
8.
Enter the LPNs the outermost LPNs that belong to your sales order.
y
l
n
9.
O
e
Click Close LPN.
I
A
10. Click Done.

11. Close the Packing Workbench.
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
DFI and the Packing Workbench
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Overview of Shipping
y
l
n
O
e
s
U
Defining Shipping
Shipping is when picked and packed material leaves the warehouse to fulfill an order.
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Staging Lanes
y
l
n
O
e
s
U
Explaining Staging Lanes

A staging lane is a locator used to stage outbound shipments before vehicle loading. To create
a staging lane, define a locator with the classification type Staging Lane. You can assign
multiple staging lanes to one dock door. You can also specify a default shipping lane for the
organization during implementation.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Setting Up Staging Lanes
y
l
n
O
e
s
U
Explaining Staging Lane Setup

You do not have to define a new subinventory specifically for staging lanes. You can use an
existing subinventory and define a staging lane locator.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Dock Doors
y
l
n
O
e
s
U
Explaining Dock Doors

A dock door is a locator used to load outbound shipments onto a vehicle. If the organization
uses Shipping Execution or Transportation to plan trips for departures from the warehouse,
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Setting Up Dock Doors
y
l
n
O
e
s
U
Explaining Dock Door Setup

Like staging lanes, you do not have to define a new subinventory specifically for dock doors.
You can use an existing subinventory and define a dock door locator.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Staging Lane to Dock Door Relationship
y
l
n
O
e
s
U
Staging Lane to Dock Door Relationship

After an operator performs a pick, the system directs the operator to deliver the item to a
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Setting Up Staging Lane to Dock Door Relationships
y
l
n
O
e
s
U
Explaining Staging Lane and Dock Door Relationships

During implementation, you can use the Associate Staging Lanes to Dock Doors window to
associate dock doors to staging lanes. You select a dock door from a list of values, and then
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
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Staging and Consolidation
y
l
n
O
e
s
U
Staging and Consolidation

After an operator picks an order, Warehouse Management directs the operator to the
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Loading and Shipping
y
l
n
O
e
s
U
Loading and Shipping

Before beginning the loading process, an operator must scan the dock door, and then scan 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Trips and Trip Stops
y
l
n
O
e
s
U
Explaining Trips and Trip Stops

A trip is a group of deliveries shipped on the same truck. A trip stop is created for each pick up
and delivery address on the trip. For example, a customer places four different orders on the
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Ship Confirmation
y
l
n
O
e
s
U
Ship Confirm
The shipment confirmation process is the final step in the outbound process. an operator can
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Direct Shipping
y
l
n
O
e
s
U
Explaining Direct Shipping

Direct Ship does not require an operator to perform pick release or pick confirm to ship
confirm material for a sales order line. The system requires an LPN for all material to ship.
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Dock Door Ship
y
l
n
O
e
s
U
Explaining Dock Door Ship Flow

An operator scans the dock door to begin the dock door shipping process. Because the dock
door is scheduled for a trip through the dock appointment calendar, the system knows which
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

LPN Ship
y
l
n
O
e
s
U
Explaining LPN Ship

An operator can use LPN ship with the mobile user interface if dock door appointments are not
used. the operator scans a dock door, but since no appointment exists for a trip, the 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Quick Ship
y
l
n
O
e
s
U
Explaining Quick Ship

an operator can use Quick Ship to ship an entire delivery without confirming the individual
LPNs. Quick ship requires operators to setup deliveries. Prior to performing a Quick Ship, an
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Shipment Planning
y
l
n
O
e
s
U
Overview of Shipment Planning

Warehouse Management enables you to access the Shipping Transactions form, a consolidated
shipping workbench that enables you to query on shipping information and plan your
shipments.
Note: The management of trips, stops, and dock management are optional.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Dock Door Appointments
y
l
n
O
e
s
U
Explaining Dock Door Appointments

an operator must set up a dock door appointment for a trip, for the system to suggest the
appropriate staging lane for the material prior to pick release. After the operator sets up the
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,
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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Practice - LPN Ship
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Practice - LPN Ship

Overview
In this practice you will ship the LPN you packed in the previous lab.
Assumptions
Whse Mgmt Mobile User, Vision Operations (USA) Responsibility
Tasks
Ship a packed LPN
1.
Use the mobile device to perform an LPN ship of the sales order you packed in the previous
practice.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Solution LPN Ship

Whse Mgmt Mobile User, Vision Operations (USA) Responsibility
1.
Log on to the mobile device.
2.
Navigate to the LPN Ship page.
(N) Outbound > Shipping > LPN Ship
3.
Enter a dock door in the Dock Door field.
4.
Enter the LPN you packed in the previous lab in the LPN field.
y
l
n
5.
O
e
Select <Continue / Ship>
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
7.
Select <Done>.

s
U
Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
y
l
n
O
e
s
U
Explaining Implementation Considerations

If your implementation utilizes auto-pick confirm, the material the operator picks must be
loose. If the material is packed in LPNs, then the system drives loose quantity negative and 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.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

y
l
n
O
e
s
U
Explaining Implementation Considerations

When you define a locator, you are given the opportunity to determine capacity constraints
including volume and weight. It is recommended that you do not define capacity constraints for
locators that are Staging Lanes or Dock Doors. Material allocations fail if the staging lane or
dock door is past capacity.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Agenda
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Summary
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
Summary
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

s
U
11i Warehouse Management

Case Study
Chapter 5
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O
11i Warehouse Management Case Study

Chapter 5 - Page 1
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 2
s
U
Objectives
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 3
s
U
Beanz n Leavz Overview
y
l
n
O
e
s
U
Beanz n Leaves Overview

Beanz n Leavz (B&L) is a leading specialty coffee company that sells high quality whole bean
coffee, rich-brewed Italian style espresso beverages, a variety of confections, coffee-related
accessories, and equipment primarily through company operated retail stores. In addition to
sales through retail stores, B&L sells whole bean coffees and specialty items online at
B&L.com and to supermarkets and hotels. Additionally, B&L produces and sells the Beanzo
bottled coffee drink.
The companys objective is to establish B&L as the most recognized and respected brand in the
world. To achieve this goal, the company plans to continue to rapidly expand its retail
operations, grow specialty sales and other operations, and selectively pursue opportunities to
leverage the B&L brand through the introduction of new products.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 4
B&L Financials
y
l
n
O
e
s
U
B&L Financials
B&L has approximately $2.5 billion in yearly revenue and has two distribution centers, one in
Pennsylvania, and one in Washington. The business is rapidly growing at the rate of around
1000 new retail stores per year. Revenues are growing at 20% per year, and operating income
by 30% per year. Recently, B&L decided to replace its paper-based warehouse management
system, and implement Warehouse Management in its Pennsylvania facility. The company has
brought in a team of consultants to analyze the operations, propose an implementation plan,
and recommend how Warehouse Management can increase efficiency.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 5
Application Landscape
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 6
s
U
Challenges
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 7
s
U
Challenges
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 8
s
U
Product Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 9
s
U
Product Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 10
s
U
Product Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 11
s
U
Product Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 12
s
U
Customer Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 13
s
U
Customer Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 14
s
U
Customer Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 15
s
U
Vendor Profile
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 16
s
U
Inbound Process
y
l
n
O
e
s
U
Inbound Process
B&L uses six inbound dock doors to receive general merchandise and non-green coffee. It
uses an unload, stage, and check in process for material received via purchase orders. Inbound
shipments are scheduled by appointments over two shifts.
Operators apply a color-coded pallet ticket to loads that contains the receipt quantity upon
receipt. The operator also enters the expiration code date in the system if available. Inbound
staging lane space is highly utilized on the first shift.
Receipts are put away on a first in basis. Material is always received and put away in full
pallets, and pallets are put away one at a time. An attempt is made to put away product in the
primary pick location, but high space utilization causes product to be put away in random
locations in the warehouse.
Production coffee is staged in the production staging area. Production inventory is updated in
the JDA system three to four times per shift. Production inventory is not reconciled between
production and the warehouse.
Only visibly damaged material or non-compliant pallets are sent to the rework area. In the
rework area, three to four people correct vendor errors and prepare the product for put away.
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 17
Vendors are charged back for non-compliant material. This information is maintained in a
spreadsheet and sent to vendors twice a month.
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 18
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 19
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 20
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 21
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 22
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 23
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 24
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 25
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 26
s
U
Outbound Process
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 27
s
U
Replenishment
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 28
s
U
Accuracy and Counting
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 29
s
U
y
l
n
O
e
I
A
&
l
a
n
r
te
n
I
e
l
c
a
r
O

Chapter 5 - Page 30
s
U

Warehouse Management Fundamentals SG

Uploaded by

Document Information

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

Warehouse Management Fundamentals SG

Uploaded by

Copyright:

Available Formats

11i Oracle Warehouse

Copyright Oracle Corporation, 2005. All rights reserved.

Technical Contributors and Reviewers

11i Receiving Material with Warehouse Management.................................................................................2-1

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Cross Docking to WIP Staging Flow.............................................................................................................2-85

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

11i Outbound Logistics ...................................................................................................................................4-1

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Packing Workbench Flow..............................................................................................................................4-93

11i Warehouse Management Case Study ......................................................................................................5-1

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Thorough knowledge of Oracle Inventory

Working experience with sales orders and receipts

Oracle Inventory Fundamentals

Oracle Receivables Fundamentals

Oracle Order Management Fundamentals

Oracle Purchasing Fundamentals

How This Course Is Organized

Oracle Warehouse Management Fundamentals Ed 2 is an instructor-led course featuring lecture

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Oracle Inventory Users Guide

Oracle Warehouse Management Users Guide

Oracle Warehouse Management Implementation Guide

Oracle Mobile Supply Chain Applications Users Guide

System release bulletins

Installation and users guides

International Oracle Users Group (IOUG) articles

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Use the SELECT command to view information stored in the

This subject is covered in Unit II, Lesson 3, Working with

Select File > Save.

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Typographic Conventions in Code

DROP USER scott

CREATE ROLE role

SQL commands and SELECT userid

Typographic Conventions in Oracle Application Navigation Paths

(M) From the menu, select Query then Find.

(B) Click the Approve button.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Typographical Conventions in Oracle Application Help System Paths

Under the General Ledger entry, expand Journals.

Under Journals, select Enter Journals.

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Fundamentals Ed 2 Table of Contents

11i Oracle Warehouse

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Overview

11i Oracle Warehouse Management Overview

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Overview

Copyright Oracle, 2005. All rights reserved.

11i Oracle Warehouse Management Overview