Documente Academic
Documente Profesional
Documente Cultură
Management Fundamentals
y
m
Student Guide
e
d
a
D49489GC20
Edition 2.0
April 2009
D59282
a
r
O
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Authors
y
m
a
r
O
e
l
c
Oracle Tutor
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
d
a
Table of Contents
R12 Overview of Oracle Inventory ................................................................................................................1-1
R12 Overview of Oracle Inventory ...............................................................................................................1-3
Objectives ......................................................................................................................................................1-4
Overview .......................................................................................................................................................1-5
Inventory Capabilities....................................................................................................................................1-6
Receipt to Issue Life Cycle............................................................................................................................1-8
Receiving Inventory ......................................................................................................................................1-9
Transferring Inventory...................................................................................................................................1-12
Issuing Inventory ...........................................................................................................................................1-14
Oracle Inventory Application Integration......................................................................................................1-16
Integration of Oracle Inventory to Financial Applications ............................................................................1-18
Summary........................................................................................................................................................1-19
R12 Defining Inventory Organizations..........................................................................................................2-1
R12 Defining Inventory Organizations..........................................................................................................2-3
Objective........................................................................................................................................................2-4
Inventory Organizations ................................................................................................................................2-5
Inventory Organization Structure ..................................................................................................................2-6
Sample Inventory Organization.....................................................................................................................2-7
Multi-Organization Structure.........................................................................................................................2-8
Setting Up Locations .....................................................................................................................................2-9
Defining Organizations..................................................................................................................................2-10
Inventory Parameters.....................................................................................................................................2-11
Costing Parameters ........................................................................................................................................2-12
Revision, Lot, Serial, and License Plate Number (LPN) Parameters ............................................................2-13
ATP, Pick, Item-Sourcing Parameters...........................................................................................................2-14
Interorganization Parameters .........................................................................................................................2-15
Other Account Parameters.............................................................................................................................2-16
Warehouse Management Parameters.............................................................................................................2-17
What Is a Subinventory?................................................................................................................................2-18
What Is a Subinventory .................................................................................................................................2-19
Defining Subinventories ................................................................................................................................2-20
Locator Control .............................................................................................................................................2-21
Dynamic and Static Locators.........................................................................................................................2-22
Subinventory-Locator Relationship...............................................................................................................2-23
Locator Flexfield Structure............................................................................................................................2-24
Interorganization Shipping Networks............................................................................................................2-25
Shipping Method ...........................................................................................................................................2-27
Additional Set Up Steps ................................................................................................................................2-28
Additional Organizational Setups..................................................................................................................2-29
Copying Inventory Organizations..................................................................................................................2-30
Organization Hierarchy .................................................................................................................................2-32
Organization Reports.....................................................................................................................................2-34
Profile Options...............................................................................................................................................2-36
Implementation Considerations .....................................................................................................................2-37
Summary........................................................................................................................................................2-43
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
c
A
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Preface
Profile
Before You Begin This Course
Prerequisites
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Related Publications
Oracle Publications
Title
Oracle Inventory Users Guide
Part Number
B31547-02
Additional Publications
Read-me files
Oracle Magazine
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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
Arrow
Brackets
Commas
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
Plus signs
Key combinations
Italic
Quotation
marks
Uppercase
e
l
c
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)
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
a
r
O
Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
Syntax variables
e
d
a
c
A
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
3.
Notations:
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
e
l
c
(I) = Icon
a
r
O
(H) = Hyperlink
(ST) = Sub Tab
Copyright 2009, Oracle. All rights reserved.
y
m
In the navigation frame of the help system window, expand the General Ledger entry.
2.
3.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 1
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Overview
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Overview
Oracle Inventory treats many different types of things as inventory. Inventory can be:
Finished goods that you sell to customers
Services that you sell to customers
Spare parts for maintenance
Raw materials for manufacturing processes
Inventory you purchase from a supplier on consignment
e
l
c
a
r
O
Inventory Capabilities
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Inventory Capabilities
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Receipt to Issue
Oracle Inventory uses the receipt to issue process to manage your inventory. When inventory
arrives in your warehouse you receive it. After you receive inventory, you can transfer it within
your organization or to another organization. Finally, you can issue material out of Oracle
Inventory.
e
l
c
a
r
O
Receiving Inventory
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Receiving Inventory
There are different ways you can receive material into your organization.
Purchasing
You can use Oracle Purchasing to receive material from outside of your organization. You can
receive:
Purchase order receipts
Internal requisitions
In-transit receipts
Return material authorizations
Unexpected receipts
e
l
c
a
r
O
Work in Process
You can use Oracle Work in Process to receive material from the manufacturing floor. You can
receive:
Component returns
Negative component issues
Assembly returns
Inventory
You can use Oracle Inventory to receive material in to your warehouse. You can receive:
Miscellaneous account receipts
Receipt from projects
User-defined receipts
Interorganization transfers
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Receiving Inventory
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transferring Inventory
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Transferring Inventory
Different applications can generate requests to transfer inventory.
Shipping
You can use Oracle Shipping Execution to generate a transfer to move material from a storage
area to a staging to for shipping.
Order Management
You can use Oracle Order Management to generate a transfer to move material from a storage
area to a staging area for shipping.
Work in Process
You can use Oracle Work in Process to generate a transfer to acquire components for a project.
e
l
c
a
r
O
Inventory
You can use Oracle Inventory to:
Transfer material between organizations
Transfer material within an organization
Replenish materials
Request transfers
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Issuing Inventory
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Issuing Inventory
You can use the following applications to issue material:
Order Management
Oracle Order Management can generate an inventory issue through:
Sales orders
Internal orders
Purchasing
Oracle Purchasing can generate an inventory issue for:
Return to vendor materials
Work in Process
Oracle Work in Process can generate an inventory issue through:
Component issues
Assembly returns
e
l
c
a
r
O
c
A
Inventory
Oracle Inventory can issue stock through:
User-defined material issues
Interorganization transfers
Cycle count negative issue
Issue requests
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Oracle Purchasing provides receipt, delivery, ATP supply, and planning supply
information and receives item requisition, and interorganization shipment information
from Oracle Inventory.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 2
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objective
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Inventory Organizations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Inventory Organizations
An inventory organization is a facility where you store and transact items. Before you can use
Oracle Inventory, you must define one or more inventory organizations. Inventory
organizations represent distinct entities in your enterprise and can be one of the following:
A physical entity such as a manufacturing facility, warehouse, or distribution center.
A logical entity such as an item master organization, which you use to define items.
An inventory organization may have the following attributes:
An inventory organization can have its own location, ledger, costing method, workday
calendar, and items.
An inventory organization can share one or more of these characteristics with other
organizations.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Multi-Organization Structure
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Multi-Organization Structure
Multi-Organization structure enables you to model multiple business units in an enterprise
using a single installation of Oracle applications. In a multi-organization architecture you can
keep data secure and separate from each business unit.
The following are the benefits of multi-organization structure:
You can use a single installation of any Oracle Applications product to support any
number of business units, even if those business units use a different ledger.
Secure access to data so users can access only relevant information.
You can define a organizational model that best suits your business requirements.
In Inventory, you can fulfill any Sales Order or Purchase Order regardless of them being
booked from any Inventory organization. You can also determine if any inter-company
invoicing needs to occur based on if the Sales Order or Purchase Order was booked in a
different Operating Unit other than the one to which the Inventory organization is
assigned.
e
l
c
a
r
O
Setting Up Locations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Setting Up Locations
Define information describing the physical locations of employees and organizations.
Locations are shared between Oracle Inventory, Oracle Purchasing, and Oracle Human
Resource Management Systems. Locations flagged as global locations are available to all
business groups. You can associate each organization with only one location; however,
you can associate more than one organization with the same location.
Physical locations are defined in Oracle Human Resource Management Systems.
e
l
c
a
r
O
Defining Organizations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Defining Organizations
Classify the Organization
Choose an organization classification to describe the general purpose of your organization.
Examples of organization classifications are inventory organization, legal company, and
HR organization.
Choose inventory organization as your organization classification to use your organization
for inventory management.
Ledger
Tie each inventory organization to an operating unit. Each operating unit is associated to a
legal entity and a primary ledger.
e
l
c
a
r
O
Inventory Parameters
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Inventory Parameters
Organization Features
You must enter organization information such as the organization code, and the item master
organization. The system defaults this field to the current organization. You must change this
for any organization that is not an item master organization. The item master organization
should be the first inventory organization you create.
Note: The Manufacturing Partner Organization functionality is only available in Japan, Taiwan
and Korea.
Products and Features
You can enable specific products on the Inventory Parameters tab. These include Oracle
Warehouse Management, Oracle Process Execution, and Oracle Enterprise Asset Management.
If you have Oracle Warehouse Management installed, then you can enable the Warehouse
Control System.
e
l
c
a
r
O
Costing Parameters
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Costing Parameters
Standard costing: A costing method where a predetermined standard cost is used for charging
material,resource, overhead, period close, job close, and cost update transactions and valuing
inventory. Any deviation in actual costs from the predetermined standard is recorded as a
variance.
Average costing: A costing method which can be used to cost transactions in both inventory
only and manufacturing (inventory and work in process) environments. As you perform
transactions, the system uses the transaction price or cost and automatically recalculates the
average unit cost of your items.
LIFO costing: Costing method where it is assumed that items that were received most recently
are transacted first.
FIFO costing: Costing method where it is assumed that items that were received earliest are
transacted first.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Interorganization Parameters
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
What Is a Subinventory?
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
What Is a Subinventory?
A subinventory is a physical or logical grouping of inventory such as raw material, finished
goods, defective material, or a freezer compartment. A subinventory can be the primary place
where items are physically stocked. You must specify a subinventory for every inventory
transaction.
e
l
c
a
r
O
What Is a Subinventory
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Defining Subinventories
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Defining Subinventories
You define subinventories by organization. Each subinventory must contain the following
information:
Unique alphanumeric name
Status
Cost Group (if you have Oracle Warehouse Management installed)
Parameters
Lead times
Sourcing information
Account information
For more information about subinventories see Defining Subinventories, Oracle Inventory
Users Guide
e
l
c
a
r
O
Locator Control
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Locator Control
Locators are structures within subinventories. Locators are the third level in the enterprise
structuring scheme of Oracle Inventory. Locators may represent rows, aisles, or bins in
warehouses. You can transact items into and out of locators. You can restrict the life of
locators, establish capacity of a specific locator in weight or units, as well as specify
dimensions which define a locators capacity by volume.
In coordination with locator settings at the subinventory and item level, you must first specify
locator controls at the Organization level:
None: Inventory transactions within this organization do not require locator information.
Prespecified only: Inventory transactions within this organization require a valid,
predefined locator for each item.
Dynamic entry allowed: Inventory transactions within this organization require a locator
for each item. You can choose a valid, predefined locator, or define a locator dynamically
at the time of transaction.
Determined at subinventory level: Inventory transactions use locator control information
you define at the subinventory level.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Subinventory-Locator Relationship
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Subinventory-Locator Relationship
You can structure Oracle Inventory in such a way that some of the subinventories and items
have locator control while others do not. If locator control is turned on at the item level, you
must specify a locator when transacting the item into or out of a subinventory. If locator
control is turned on at the subinventory level, you must specify a locator when transacting any
item into or out of that subinventory. Each stock locator you define must belong to a
subinventory, and each subinventory can have multiple stock locators. The possible locator
control types are:
None
Prespecified
Dynamic entry
Item Level
You cannot use the same locator names within any two subinventories within the same
organization.
For more information about setting up locator control see Defining Stock Locators, Oracle
Inventory Users Guide.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Planning lead-times
Transfer charges
For more information see Interorganization Shipping Network, Oracle Inventory Users Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Shipping Method
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Shipping Method
Shipping methods are the way you ship material. When you create a shipping method, you
must enable it before you can use it in a shipping network. If you disable a shipping method
you cannot use it in a shipping network.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
When you copy a model organization the system automatically copies the following
information:
Subinventories
Locators
Work in Process parameters
Work in Process accounting classes
Planning parameters
Shipping parameters
Note: The system does not copy organization-specific data including: cost type, cost subelement, Process Manufacturing Enabled, Oracle Warehouse Management enabled, and costsharing entities.
For more information about copying inventory organizations see Copy Inventory Organization
Implementation Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Organization Hierarchy
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Organization Hierarchy
Organization hierarchies enable you to group together organizations and perform operations
across all organizations within a hierarchy. You can perform the following operations across
all organizations within an organization hierarchy:
Assign items to organizations: You can assign an item to any organization that belongs
to the same master organization within the same hierarchy. You can also assign a range of
items or item categories to a single organization, as well as a range of items or categories
to multiple organizations.
Copy item attributes: You can manage item attributes for many organizations in one
place. You can verify that an item or group of items were set up correctly, copy
organization-level item attributes from one item to other organizations that use the item,
and copy item attributes from one item to another within an organization.
View item information: You can view on-hand quantity information as well as item
where used information for organizations.
Open and close accounting periods: You can open and close accounting periods.
Purge transactions: You can purge transactions.
e
l
c
a
r
O
Process transactions with the Inventory Transaction Open Interface: You can use the
Inventory Transaction Open Interface to review, submit, or cancel transactions.
Manage bills of materials: You can create common bills of material for organizations as
well as delete items, bills, components, routings, and operations.
Manage engineering change orders: You can automatically implement as well as make
changes to engineering change orders.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Organization Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Organization Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Implementation Considerations
When you set up your organizations you need to determine the organization type. For example,
you need to determine if the organization is a process or a discrete organization and if you are
using Oracle Warehouse Management. You can use Oracle Warehouse Management and
Oracle Process Management in the same organization. You should not however, use Oracle
Asset Management with Oracle Warehouse Management or Oracle Process Execution. If you
plan on using Oracle Warehouse Management you need to determine if you are going to use
the Warehouse Control system. If this organization transacts business with Japan, Taiwan, or
Korea you can enable Chargeable Subcontracting for the organization. You must consider all
of this information before you create items or process transactions.
e
l
c
a
r
O
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Units of Measure
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Unit of Measure
You define units of measure for tracking, moving, storing, and counting items.
Primary Unit of Measure
When you define an item you establish a primary unit of measure. The system tracks on-hand
quantity and calculates transactions based on the primary unit of measure.
Secondary Unit of Measure
You can optionally establish a secondary unit of measure (dual unit of measure control) for an
item. Secondary unit of measure can be used for cases where you need to track in two units of
measure and there is no constant conversion between the two unit of measures (UOMs). For
example, chickens can be tracked in pounds and eaches.
If an item is under dual unit of measure control the system tracks on-hand quantity based on
both the primary and secondary units of measure. For example, you can track an item in both
eaches and liters.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Implementation Considerations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Implementation Considerations
You can use a maximum of five decimal places for an individual unit of measure within
Oracle Inventory.
Note: Inventory transactions and on hand balance supports decimal precision to 5 digits
after the decimal point. Oracle Work in Process supports decimal precision to 6 digits.
Other Oracle Applications support different decimal precision. As a result of the decimal
precision mismatch, transactions another Oracle Application passes may be rounded when
processed by Inventory. If the transaction quantity is rounded to zero, Inventory does not
process the transaction. It is therefore suggested that the base unit of measure for an item
is set up such that transaction quantities in the base unit of measure not require greater
than 5 digits of decimal precision. For example, in some industries such as the gold
jewellery industry, you may need a more granular level of control than 5 decimal places.
You need to carefully determine the base unit of measure for each unit of measure class.
Primary units of measure cannot be changed on items after they are saved.
e
l
c
a
r
O
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 4
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objective
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
What is an Item?
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
What Is an Item?
An item is a part or service you:
Purchase
Sell
Plan
Manufacture
Stock
Distribute
Prototype
Items can also be containers for items as well as components you build into other items.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
Defining Items
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Defining Items
Define only the information you need to maintain the item. You cannot define an item at the
organization level. Oracle Inventory automatically switches to the Master Item window when
you define a new item.
e
l
c
a
r
O
Defining Items
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Master
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Master
Always define items in the master organization. When you define an item, Oracle
automatically changes your current organization to the master organization. You may enable
your new items in as many child organizations as needed.
e
l
c
a
r
O
Item Attributes
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Item Attributes
Item attributes are the collection of information about an item.
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Status
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Status
You can use statuses to provide default values for certain item attributes to control the
functionality of an item. The Item Status attribute has a defined set of yes or no values for the
status attributes. You apply the values to the status attributes when you choose an item status
code when you define an item. For example, in the beginning of a product development cycle
you set the Item Status attribute to Prototype with all of the status attributes defaulted to yes
except for Customer Orders Enabled. When the item is ready, you change the Item Status
attribute to Active to enable all item functions.
You can assign one or more pending statuses for an item, to be implemented on future dates.
These statuses become effective on their assigned effective dates. You can view the status
history of an item if needed.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
converts the quantity to the second unit of measure and displays both quantities. You
can change the quantity in the secondary unit of measure, without changing the
quantity in the primary unit of measure.
- No Default: The system stores inventory in both the primary and secondary units of
measure. Use this option when the default conversion between the two units of
measure is usually not the same. The system does not automatically display in the
secondary unit of measure when you specify the quantity for the primary unit of
measure. You manually enter the quantity of the secondary unit of measure before
you process a transaction. The secondary quantity can fluctuate from the default
conversion by the factors that you specify in the Deviation + and Deviation attributes.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Item Templates
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Templates
Oracle Inventory has several predefined templates that you can use to define and update items
or you can create your own templates.
If you regularly define many items that share the same values for a number of attributes, you
may want to define item templates. You can only use copy once when you define an item. You
can predefine templates with relatively few attributes enabled because you can apply more than
one template to define one item.
Attributes in Templates
You can enable attributes and assign them values in each template that you create. When you
apply a template to an item, Oracle Inventory updates only the attributes that are enabled for
the template. The order in which templates are applied is extremely important.
Further Item Templates Help
For more information about item templates see Item Templates, Oracle Inventory Users
Guide.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Control Levels
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Control Levels
Master-Level Control
An attribute you maintain at the master level has identical values across all organizations that
use the item.
Organization-Level Control
An attribute you maintain at the organization level may have different values for each
organization that uses it.
Attribute Control
Some attributes can be maintained at only the master level or the organizational Level. Units of
measure are controlled at the master level. If you are using multiple organizations, then you
should maintain min-max planning at the organization level.
Technical Note
Master-Level Control
For example, suppose you want to ensure that items defined in two organizations are
transactable at the same time in both organizations. If you make the item not transactable
e
l
c
a
r
O
in one organization, you want the same item to become not transactable in the other
organization.
Organization-Level Control
Suppose only one of the two organizations in your Oracle Inventory implementation
performs manufacturing operations, while the other organization is strictly a distribution
warehouse.
For a finished good item used in both organizations, you would want the flexibility to
select the Build in WIP status attribute check box in the manufacturing organization, and
clear the Build in WIP status attribute check box in the distribution organization.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Revision Control
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Revision Control
A revision is a particular version of an item, bill of material, or routing. Use the revision
control to track item quantities by item revision and specify a revision for each material
transaction.
Enable revision control for items you must track version changes or changes that are
significant enough to track but do not affect the function and feature of the item.
You cannot change the revision control item attribute when an item has quantity on hand. If
revision control is controlled at the Master Item level, the check for on-hand quantity is against
the sum of on-hand quantity in all child organizations. If revision control is controlled at the
organizational level, the check for on-hand quantity is against the sum of on-hand quantity in
that organization.
Use letters, numbers, and characters such as A, A1, 2B, and so on to define revision numbers.
Letters are always in upper case and numbers may include decimals. To ensure revisions sort
properly, decimals should always be followed by a number. Revisions are sorted according to
e
l
c
a
r
O
ASCII rules, therefore each revision must be greater than the previous revision. For example,
you cannot use revision 10 after revision 9 because, according to ASCII sorting, 10 precedes 9.
For more information about setting up Revision Control, see Defining Item Revisions, Oracle
Inventory Users Guide
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Item Relationships
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Relationships
You can define relationships between items. This allows you to search for items through these
relationships. Except in Oracle Purchasing, these relationships are for inquiry and reporting
purposes only. For example, you can create an item relationship for substitute items or items
for which you can up-sell.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Item Catalogs
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Catalogs
To define your catalog, you set up as many distinct item catalog groups as you need to partition
your Item Master. Each group has unique characteristics (called a descriptive element) that
completely describe items belonging to the group. When you assign an item to an item catalog
group, you define values for the descriptive elements that apply to your item. For example, an
item catalog group called mug could have a descriptive element called material. Possible
values for material might be glass or ceramic.
Descriptive Elements
You can define any number of descriptive elements for an item catalog group. You can also
describe whether the descriptive element is required at item definition, and whether the
descriptive element value is included by default in the item catalog description. Descriptive
element values can be concatenated and used to create an item's description. You turn this
feature off or on for each descriptive element in a catalog group. Turn Description Default on
for any element you want included in a concatenated description. You create a concatenated
description when assign an item to an item catalog group.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Deletion Constraints
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Deletion Constraints
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Implementation Considerations
You should set all costing attributes at the organizational level because costing is most
commonly done at organizational level. WIP requires costing at org level to set up WIP
accounting classes. Costing of individual items is specific to individual organizations because
of location and other considerations.
Costing Method
Costing method is chosen and set at the inventory organization level. Within a ledger (set of
books), an enterprise can have multiple cost methods specified at each organization level. For
example, a company may have one average cost org and one standard cost org. Available
costing methods are as follows:
Standard
Average
FIFO
LIFO
e
l
c
a
r
O
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objective
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Child Lots
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Child Lots
A child lot is a subdivision of a lot that you can use if you produce a lot over a period of time,
but still want to group the material as a single lot. Using a child lot maintains the integrity of
the lot, but enables you to consume it in manageable pieces. When you process transactions for
material under child lot control, you enter the child lot as the lot number. The system also
maintains a genealogy relationship between the parent lot and the child lot.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
point, or MRP planning calculations. You also cannot reserve an expired lot. See Oracle
Inventory User's Guide Inventory Attribute Group control.
Grade Control
A grade is a rating that you assign to an item lot for quality control purposes. Grades are
usually based on criteria such as color, size, or quality of the lot. For example, the grade of a
lot of paint could be excellent, average, or poor. A grade is a characteristic of an item lot, and
never a lot location.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Managing Lots
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Managing Lots
Assigning Lot Numbers
You must assign lot numbers when you receive items under lot control. You can also add
quantities to existing lot numbers and split an inventory receipt into several lots, if necessary.
Oracle Inventory uses the default lot number generation method that you entered in the
Organization Parameters window to determine lot numbers so the Lot Prefix and Starting
Number can be generated from either an Organization or Item-specific Prefix, based on the
Organization Parameters setting. Alternatively, if the setting is *User-Defined*, then the
Operator must 'manually' ENTER or SCAN the Lot Number.
If the item is under user-defined expiration date Lot Expiration (shelf life) Control, you must
specify the expiration date for the lot.
You can either use the lot master to generate new lot numbers or assign lot numbers when you
perform transactions. When you create the lot, the system determines the lot origination type. If
you create the lot on the lot master, the origination type is lot master. If you generate the lot
while performing a transaction, the origination type is Inventory. See Item Lots and Assigning
Lots Within Transactions, Oracle Inventory Users Guide for more information.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Expired Lots
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Expired Lots
You can assign lot control shelf life days, or enter a lot expiration date to determine when a lot
expires. The expiration date controls the availability of the lot for transacting and planning
purposes. An expired lot:
Is not considered as on-hand supply when you are performing min-max, reorder point, or
MRP planning calculations.
Cannot be reserved for a date beyond the expiration date.
Can be transacted and is included in on-hand quantities.
Is included in all inquiries and reports, including inventory valuation reports
Is included in a cycle count and count entry and adjustments are allowed
Is included in a physical inventory and tag entry and adjustments are allowed
Lot Expiration Action
A lot expiration action is the action that you perform on a lot when it expires. You can assign a
default lot expiration to an item on the Item Master or when you generate a lot. To associate a
lot expiration action with a lot, you must define shelf life days for the item.
e
l
c
a
r
O
Disabled Lots
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Disabled Lots
Disabling a lot only prevents it from appearing in a list of values when you are performing
receipt transactions. If you type in the lot number, it is valid and accepted even though it was
not in the list of values. Disabling is used only for tailoring this specific instance of the list of
values for lot numbers. A disabled lot:
Is included in available to transact, available to promise, and available to reserve
calculations
Is included as on-hand supply when you are performing min-max, reorder point or MRP
planning calculations
Is included as on-hand in all inquiries and reports, including inventory valuation report
Can be transacted with Inventory functions and the Transaction Open Interface
Can be reserved
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Note: Prefix and Starting Number can be Organization or Item-specific and is determined at
the Serial Control Generation Setting on the Organization Parameters. Alternatively, they can
also be User-Defined. If the Setting is *User-Defined* then the Operator must 'manually'
ENTER or SCAN the Serial Number. The system will not generate the Serial number.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Serial Uniqueness
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Serial Uniqueness
You use the Organization Parameters window to choose a type of serial number uniqueness for
your organization. You can choose to enforce uniqueness Within inventory items, Within an
organization, or Across organizations. The three levels for serial uniqueness are cumulative,
and the definitions are as follows:
Within Inventory Items: Once you assign a serial number to a particular item you cannot
assign the same serial number to the same item regardless of the organization. For
example if you assign serial number SN100 to item A, you cannot assign serial number
SN100 to any other instance of item A in any organization. This also includes CTO items
derived from base model A. However you could receive item B with serial number SN100
in any organization.
Within an Organization: In addition to the Within Inventory Items restrictions, the same
serial number cannot exist twice within the same organization. For example, if you assign
SN100 to item A, you cannot receive item B with the serial number SN100 in the same
organization. You can, however, receive item B with the serial number SN100 in any
other organization.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Lot Genealogy
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Lot Genealogy
Lot genealogy tracks the relationship between lots and provides lot traceability that results
from inventory transactions. This includes all lot splits, merges, and translations. Lot
genealogy also enables you to view where a particular lot is used. For example, one of your
suppliers informs you that they supplied you with contaminated sugar, which needs to be
recalled, and you used this sugar as an ingredient in the production of orange juice. You can
use lot genealogy to find each lot of orange juice that contain the contaminated lots of sugar.
You can use lot genealogy to view the work order details for a WIP job, material and pending
transactions, and quality results for both WIP jobs and process batches. Oracle Process
Manufacturing does not support serial numbers or serial genealogy.
e
l
c
a
r
O
Serial Genealogy
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Serial Genealogy
Serial genealogy tracks the transaction and multilevel composition history of any serialcontrolled item from receipt to customer sale. The composition genealogy is captured through
material transactions in Oracle Work in Process and Oracle Process Manufacturing. The serial
genealogy appears in a graphical display, and you can trace an assembly down through all of
its components or from the component to an assembly. This genealogy tracing enables you to
expedite problem isolation and improve customer response times. Serial genealogy also helps
you to track and regulate supplier performance and quality.
You can view the transaction history of the serial across all organizations within an operating
unit and view the current organization where the serial resides. When issuing serialized
components to serial controlled assemblies, you must associate the component serial number
with the assembly serial number. If the component has a supply type of Push, the association
occurs at WIP Issue. If the component has a supply type of Operation Pull, the association
occurs at WIP Move. If the component has a supply type of Assembly Pull, the association
occurs at WIP Completion. If the item is under lot control, then you can also view the lot
genealogy for the same item. When you view the genealogy of the item, the system lists the
item number, followed by the lot number, and finally the serial number.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Overview
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Transactions
A transaction is an item movement into, within, or out of inventory. A transaction changes the
quantity, location, planning responsibility, or cost of an item. Oracle Inventory supports a
number of predefined and user-defined transaction types. Every material movement has a
corresponding set of accounting transactions that Oracle Inventory automatically generates. All
transactions validate the various controls (revision, locator, lot, dual unit of measure, and serial
number) you enable for your items.
For more information about transaction see Overview of Inventory Transactions, Oracle
Inventory Users Guide.
e
l
c
a
r
O
Inventory Transactions
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Inventory Transactions
Inventory transactions enable you to:
Receive items into your organization.
Issue items out of your organization.
Transfer items from one subinventory in your organization to another subinventory in the
same organization
Transfer items between organizations
e
l
c
a
r
O
Move Orders
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Move Orders
Move orders are requests for the movement of material within a single organization. They
formalize the process to request the movement of material within a warehouse or facility for
purposes like replenishment, material storage relocations, and quality handling. Move orders
are generated manually or automatically depending on the source type. To request a material
transfer between organizations requires an internal requisition.
Move Order Requisitions
A move order requisition is a manually generated request for a move order. It is available for
subinventory transfers and account transfers. Once a requisition has been approved, it becomes
a move order. These requests can optionally go through a workflow-based approval process
before becoming move orders. For more information about move order requisitions see
Generating Move Order Requisitions, Oracle Inventory Users Guide.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transaction Action
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Transaction Action
You use transaction actions with a source type. A transaction action identifies a transaction
type. Oracle Inventory provides the following transaction actions:
Issue from stores
Subinventory transfer
Direct organization transfer
Cycle count adjustment
Physical inventory adjustment
Intransit receipt
Intransit shipment
Cost update
Receipt into stores
Delivery adjustments
WIP scrap
Assembly completion
e
l
c
a
r
O
Assembly return
Negative component issue
Negative component return
Staging Transfer
Ownership Transfer
Logical Issue
Logical Delivery Adjustment
Retroactive Price Adjustment
Logical Receipt
Delivery Adjustment
Lot Split
Lot Merge
Lot Translate
Lot Update Quantity
Logical Expense Requisition Receipt
Planning Transfer
Ownership Transfer
Logical Intercompany Sales
Logical Intercompany Receipt
Logical Intercompany Receipt Return
Logical Intercompany Sales Return
Container Pack
Container Unpack
Container Split
Cost Group Transfer
Logical Intransit Receipt
Logical Intransit Shipment
Retroactive Price Update
Container Transaction
COGS Recognition
Residual Quantity Issue
Residual Quantity Return
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
c
A
e
d
a
Transaction Reasons
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transaction Types
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Transaction Types
A transaction type is the combination of a transaction source type and a transaction action. It is
used to classify a particular transaction for reporting and querying purposes. Oracle Inventory
also uses transaction types to identify certain transactions to include in historical usage
calculations for ABC analysis or forecasting. A number of transaction types are predefined in
Oracle Inventory. You can also create custom transaction types.
You use the Transaction Types window to define additional transaction types to customize
transaction entry. A user-defined transaction type is a combination of a user-defined
transaction source type and a predefined transaction action. For example, if you frequently
donate items to charity, you might want to define a transaction source type called charity and a
transaction type called Issue to Charity. In this case, the transaction action would be Issue from
Stores. You would then use the Miscellaneous Transactions window to actually issue an item
to charity, using the Issue to Charity transaction type. You would also specify the actual charity
to which you are issuing, such as Goodwill, and the expense account that specifies the source
Goodwill. For more information about transaction types see Transaction Types, Oracle
Inventory Users Guide.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Transaction Managers
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Transaction Managers
(N) > Setup > Transactions > Interface Managers.
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
After you create a rule you assign it in the rules workbench. The rule that you created on the
Inventory Picking Rules page appears on the Rules Workbench. The system automatically
assigns a sequence number and return type to the rule. You can modify the sequence number,
but you cannot modify the return type. The return type is a strategy, rule, or value.
You can assign your rule to any combination of criteria the Rules Workbench displays. For
example, if you create a picking rule that allocates material by lot number in ascending order
followed by locator in ascending order, you can assign it to an item in the Rules Workbench.
This means for picking, the system allocates the lowest lot number of the item in the lowest
locator number where the item resides.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Account Aliases
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Aliases
An account alias is an easily recognized name or label representing a general ledger account
number. You can view, report, and reserve against an account alias. During a transaction, you
can use the account alias instead of an account number to refer to the account.
You must create an inventory account alias for each GL account if you wish to use an alias for
that GL account in inventory transactions. Oracle Inventory does not honor GL account aliases.
e
l
c
a
r
O
Accounting Periods
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Accounting Periods
Oracle Inventory uses accounting periods to group material and work in process transactions
for accounting purposes. An accounting period must be open for you to complete a transaction;
that is, the transaction date you enter must fall within the beginning and ending dates you
define for the period.
Closing Accounting Periods
You can close the earliest accounting period with a status of Open or Error. An automatic
general ledger transfer is processed when you close an accounting period.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Shortage Alerts
The shortage alert appears in the window during the transaction with the option to go to the
View Potential Shortages form, showing where the shortage exists. Alerts are automatic once
they are set up. Notifications are optional and can be sent to a prespecified list of individuals.
Sources of Demand
When generating shortage alerts and notifications, the system considers one or more of the
following to be sources of demand:
WIP jobs
WIP schedules
Sales order lines that have been pick released and detailed but for which adequate quantity
was not sourced
Supply Types
The system considers the transaction types you select as supply for the unsatisfied demand.
Shortage alerts and notifications are triggered for system or user defined transaction types with
transaction actions of:
Receipt into stores
Intransit receipt
Direct organization transfer
Assembly completion
Negative component issue
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
You can also specify individuals to be notified if a shortage occurs. To bypass the approval
process and automatically approve move order requisitions, enter 0 days for the Move Order
Timeout Period and select Automatically Approve for the Move Order Timeout Action. The
approval process is also not enabled for organization items without an assigned planner.
Item Transaction Defaults
You can define the item transaction defaults to automatically populate the destination locator
on the move order line from an organization item.
(N) > Setup > Transactions > Item Transaction Defaults.
Move Order Time-Out
Use move order time-out if you want to require approvals for the move orders in your
organization.
Time-out Period
The length of time, in days, you will let your move orders sit in a pending-approval queuing
status.
The following rules apply when you set up time-outs:
After one time-out period, a reminder is sent to the approver.
After two time-out periods, the move order time-out action is performed.
The time-out action is either approved or rejected.
If the time-out period is 0, all move orders are automatically approved.
If the time-out period is left blank, the setting defaults to 0.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Locator Defaults
If a subinventory or item is locator controlled, when you create the move order receipts,
specify a destination locator. If you do not specify a destination locator, the allocating process
uses the item transaction default.
For more information see:
(Help) Oracle Manufacturing Applications > Oracle Inventory > Transactions > Overview of
Move Orders > Setting Up Move Orders
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Implementation Considerations
Answer the following questions to determine which of the following demand sources should be
considered potential shortages.
Which inventory organizations should be checked for shortages?
Which type and statuses of WIP jobs/schedules should be checked for shortages?
Answer the following questions to determine the individuals and the method for delivering
shortage messages.
Should workflow alerts and notifications be generated when actual shortages exist?
Who should be notified?
How frequently should notifications be sent?
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 7
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Module Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Transactions
A transaction is an item movement into, within, or out of inventory. A transaction changes the
quantity, location, planning responsibility, and cost of an item.
Oracle Inventory supports a number of predefined and user-defined transaction types. Every
material movement has a corresponding set of accounting transactions that Oracle Inventory
automatically generates. All transactions validate the various controls (revision, locator, lot
number, serial number and secondary unit of measure) you enable for items.
See Overview of Inventory Transactions, Oracle Inventory Users Guide for more information.
e
l
c
a
r
O
Inventory Transactions
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Inventory Transactions
You can perform the following inventory transactions:
Receive items into your organization from a general ledger account number.
Issue items from your organization to a general ledger account number.
Transfer items from a subinventory in your organization to another subinventory in the
same organization.
Transfer items directly between organizations.
Transfer items between organizations by way of intransit.
Reserve items for a specific account or temporarily prevent the release of items onto the
shop floor.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Miscellaneous Transactions
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Miscellaneous Transactions
Miscellaneous Transactions enable you to issue material to individuals or projects that are not
in inventory, receiving, or work in process. These could include a research and development
group or an accounting department. You can also make manual adjustments to the general
ledger by receiving material from one account to inventory, and then issuing that material from
inventory to another account.
For more information see Performing Miscellaneous Transactions Oracle Inventory Users
Guide
Miscellaneous Transactions Applications
With miscellaneous transactions you can:
Load items when you implement Oracle Inventory
Scrap items by issuing them to scrap accounts
Issue items to individuals, departments, or projects
Receive items that were acquired without purchase orders
Enter adjustments and corrections to system quantities due to theft, vandalism, loss, shelflife expiration, or inaccurate record keeping
e
l
c
a
r
O
Subinventory Transfer
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Subinventory Transfer
Some of the uses of subinventory transfers are:
Transferring between asset and expense subinventories
- Transferring between tracked and non-tracked subinventories
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
The validity of a transfer transaction depends on the controls you have defined in both the
shipping and destination organizations for the items you want to transfer. For example, you can
transfer item A from organization X to organization Y, even though item A is under lot control
only in organization X (you can specify the lot numbers for item A in organization X during
the transfer transaction). You can also transfer item B from organization X to organization Y if
item B is under lot control only in organization Y (you can specify lot numbers for item B in
the destination organization when you perform the receiving transaction).
Unit of Measure Conversions
When you transfer items under dual UOM control between organization, the system honors the
UOM conversion of the destination organization. Consequently, the system could potentially
recalculate the secondary quantity for the item if the conversions differ between the shipping
organization and the destination organization. The system always processes transaction
quantities in the primary UOM.You must define UOM conversions in both the shipping and
destination organization before the system can process the transaction.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Managing Receipts
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Managing Receipts
You can receive both internally and externally sourced shipments and deliver material directly
to inventory, the shop floor, and You can deliver to inventory, shop floor, and expense
destinations. You can also can satisfy the following receiving business needs:
Increased receiving process control
Streamlined receiving throughput
Increased transaction visibility and traceability
A common process for all receipt types
Entering Receipt Information
To process receipts, you select the items to receive and enter the receipt quantities. If you
change the unit of measure, the system adjusts receipt quantity to reflect the new unit of
measure. You can override this value if you are recording a partial receipt or are receiving
more than the expected quantity.
The quantity received on the corresponding purchase order or return material authorization
(RMA) is updated to reflect the received quantity.
e
l
c
a
r
O
Substitutions
You can receive predefined substitute items when you allow suppliers to ship alternatives to
the items that you order. For example, you assign different internal item numbers to mountain
bikes of the same model number but different color. You have an agreement with your
mountain bike supplier that allows him to ship white bikes in place of blue bikes.
Specifying Substitute Receipt Details
You can select a substitute item in the Lines region based on the following restrictions:
You must allow substitute receipts for the shipments you receive.
You have defined substitutes for the items you receive.
When you query in the list of values for the item, the system displays all valid substitutes for
the item you want to receive. All subsequent receipt processing is identical to other standard
and direct receipts.
Supplying Handling of Substitute Items
When you receive a substitute item, the system removes the purchase order supply for the
original item.
If you perform a standard receipt, the system creates receiving supply for the new item.
If you perform a direct receipt, the system increments on-hand balances for the new item.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Direct Receipts
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Standard Receipt
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Inspection Receipt
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Move Orders
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Move Orders
Move orders are requests for the movement of material within a single organization. They
formalize the process to request the movement of material within a warehouse or facility for
purposes like replenishment, material storage relocations, and quality handling.
Move orders are generated manually or automatically depending on the source type used.
Move orders are restricted to transactions within an organization. Transfers between
organizations require an internal requisition.
Move Order Requisitions
A manually generated request, available for subinventory and account transfers.
These requests can optionally go through a workflow based approval process before they
become move orders that are ready to be sourced and transacted.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Once the order line is approved, notices are sent to a notification list that is attached to the
source and destination subinventories to let the subinventory planners know that material will
be moved to or from their areas.
Note: Replenishment and pick wave move orders are pre-approved.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Tracking: Move orders can be transacted through Application Program Interfaces (APIs).
APIs enable you to use mobile devices to transact, giving you better material visibility and
accuracy. Move orders can also be created to cross-dock material to staging locations.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
source (set at the item-subinventory level) is another subinventory. In this case, the min-max or
replenishment count report automatically generates a move order. Replenishment move orders
are pre-approved and ready to be transacted.
The type of move order generated depends on the replenishment source:
If the replenishment source is a supplier, then a move order requisition is created.
If the replenishment source is another inventory organization, then an internal requisition
is created.
If the replenishment source is a subinventory then a replenishment move order is created.
Note that the source subinventory must be set up at the item subinventory level. For the
min-max report to generate a move order, the report must be generated at the subinventory
level.
For kanban to generate a move order, the pull sequence source type must be set to Intra-org.
Pick Wave Move Order
The pick release process generates move orders to bring the material from its source location in
stores to a staging location, which you define as a subinventory in Oracle Inventory. This
transaction is a subinventory transfer.
These move orders are generated automatically by the Oracle Shipping Execution pick release
process.
These orders are pre-approved and ready to transact. Pick slips and other shipping and
inventory reports will also be available with Oracle.
WIP Issue Move Orders
An optional process in Oracle WIP allows you to run pick release for the components of a
range of jobs or schedules. This process creates move orders to either directly issue the
material to WIP, or to move the material to the backflush locator. These orders are
automatically approved, the picking rules are used to allocated material for the job, and pick
slips can be printed for warehouse users.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
in at the line detail level. These details are automatically filled in by Oracle Inventory using the
inventory picking rules and the item-transaction defaults for destination locators or you can
manually fill in the details. You can edit these details prior to transaction.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
balances negative or whether the lot is indivisible. The system honors lot-specific conversions,
process manufacturing quality matches, material status, and preferred grade if you set the
profile option INV: Target Preferred Grade to Yes. The information that appears on this page is
available according to the picking rules you define, and sorted in the order defined on the
allocation rules.
Suggesting a Destination
The picking rules only suggest source locations. If the destination subinventory is locatorcontrolled and no locator is specified on the move order line, Oracle Inventory generates a
suggestion based on the item subinventory locator default you set up for move orders. You can
set up a default locator for each item that you want to move around the warehouse on a move
order. This is not the same default type that you would use for receiving or shipping.
You have two choices in transacting the move orders to transfer the material to the destination
location:
Automatic Pick Confirmation: The move order is transacted instantly after the order is
allocated without any further human intervention. On-hand inquiries will show the
material in staging. You can then perform ship confirmation.
Manual Pick Confirmation: You can confirm the pick of the move order allocation. You
can also update any picking details such as the source locations, lots or serials and to
report shortages or inventory inaccuracies and allow the system to generate more pick
suggestions. Reporting inventory inaccuracies enables you to request a cycle count in the
inventory area where the material was not found if so desired.
Oracle Shipping
Oracle Shipping provides two choices for when and how you can fill in the line details. These
choices are made by setting up an organization parameter but can be overridden at pick release.
Auto allocate: The allocating process is done at pick release instantly after the move
order is created. No more human intervention is needed and the pick slip can be printed
automatically.
Pick release only creates move orders but does not fill in the line details. You must
navigate to the move order form after pick release and click on the Allocate button. This
option allows warehouse managers to determine when to release the pick to the floor and
might be a better solution for implementations running a global order entry with
distributed warehouse management and/or shipping. In these cases, orders can be released
to regional warehouses from the central order management location in advance and
individual warehouses can schedule picks closer to actual ship time.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Allocation
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Allocating Items
Reservation
A reservation is a link between a supply source and a demand source. A reservation creates a
permanent data link between a supply source and a demand source, and represents a guaranteed
allotment of material to a specified demand source.
Pending Transaction
A pending transaction is a transaction that Oracle Inventory expects to occur shortly, but
confirmation of the transaction has not yet been recorded. This is a material pick that has not
yet been completed. Move order line details are an example of the pending transaction. A pick
slip may have already been printed, but the picker has not yet indicated that they have
deposited the material in the destination location.
Neither reserved material nor a pending transaction quantity is included in any availability
calculation for the source location.
You should not allocate a move order line too soon in the business process, because the
allocating process for a move order creates pending transactions and removes that quantity
from an availability picture. Allocating should not be done until you are ready to print the pick
slip and move the material.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Mobile Transactions
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Mobile Transactions
Oracle Mobile Materials Management enables you to use mobile devices to perform receiving,
inventory, and shipping transactions. You can:
Record inspections, deliveries, and material movements during receiving transactions.
Create transactions for material including kanban movement, cycle counting, and
intraorganization replenishment.
Perform pick confirm and ship confirm transactions.
Print labels
Inquire on item and kanban transactions
Subinventory transfer
Transact move order
Inter-Organization Transfer
Perform move orders
Transfer inventory between organizations
Transfer material between subinventories
e
l
c
a
r
O
For more information see Mobile Materials Management, Oracle Mobile Supply Chain
Applications Users Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Managing Shipments
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Managing Shipments
You can review and update intransit shipments between inventory organizations.
Shipment Visibility: You can access all incoming and outgoing shipments associated
with the current organization.
Shipment Header: You can update information pertaining to the shipment header such as
Ship-to Location and Number of Containers. If you change the Expected Receipt Date,
Oracle Purchasing updates Shipment Supply to reflect the new due date.
Shipment Lines: You can update information pertaining to the shipment lines such as
Expected Receipt Date, Receipt Routing, Packing Slip, and Note to Receiver. The receipt
routing that you specify in Maintain Shipments overrides routings specified at the item,
organization, or system levels.
e
l
c
a
r
O
Transactions Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transactions Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transactions Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transactions Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Transactions Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Overview of Reservations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Overview of Reservations
A reservation is a link between a supply source and a demand source. A reservation creates a
permanent data link between a supply source and a demand source, and represents a guaranteed
allotment of material to a specified demand source. Item reservations prevent the allocation of
material you previously set aside for a sales order, account, account alias, inventory allotment,
user-defined source, process batch components or, Oracle Complex Maintenance and Repair
Overhaul work order components. You can also create reservations for different types of
supplies such as on-hand inventory, purchase orders, internal requisitions, discrete jobs, shop
floor jobs, and process manufacturing batches. In addition, you can create reservations for
advanced shipment notices (ASNs) and material in receiving for Oracle Warehouse
Management enabled organizations.
e
l
c
a
r
O
Overview of Availability
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Overview of Availability
To Planning functions, avail = supply - demand for a particular time period
To Inventory, avail = on hand-res-pending transactions
Note
Availability to Inventory is not the same as availability to Planning- Planning looks at
inbound supply in addition to on hand quantity and deducts other demand. Inventory only
looks at what is on hand and subtracts what is committed to other uses (i.e reserved or
about to be moved or issued out the door)
Availability to Inventory depends on what you want to use the material for. For example,
if you have material that is in a non-reserved subinventory, that quantity will not be
available to reserve but it may be available to transact (for miscellaneous issues etc).
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Material Workbench
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Material Workbench
The Material Workbench enables you to view material in receiving, on-hand quantities, and
inbound material. You can also view material across organizations. In addition, you can create
and save queries, create move orders, and request cycle counts, as well as change material
statuses.
You can view item quantity across organizations. You can view only material in organizations
to which you have access. If you do not enter an organization, you must enter an item.
e
l
c
a
r
O
Display Options
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Display Options
The viewing option that you select dictates the information the Material Workbench displays.
The viewing options are:
Location: Location information includes the subinventory and associated locators. You
can also view subinventory quantities, including packed and unpacked quantities. This is
the only view by option that you can use if the material location type is Inbound.
Item: Item information includes the organization, item number, UOM, available quantity,
lot, and serial number. You can use this option only if the material location type is Onhand.
Cost Group: Cost Group information that is assigned to the item. You can use this option
only if the material location type is On-hand.
Status: Status information that includes the statuses assigned to subinventories, locators,
lots, and serials. You can use this option only if the material location type is On-hand.
LPN: If you are in an Oracle Warehouse Management enabled organization, you can view
LPN information for the item. You can use this option if the material location type is Onhand, Receiving, or both.
e
l
c
a
r
O
Serial: Serial information lists the serial numbers that are generated for an organization
and the items that are associated with the serial numbers. You can use this option only if
the material location type is On-hand.
Lot: The system lists the lot numbers that are generated for an organization and the items
that are associated with the lot numbers. You can use this option only if the material
location type is On-hand.
Grade: The system lists the grade and the items that have a particular lot grade. You can
use this option only if the material location type is On-hand.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Available to Promise
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Available to Promise
Available to Promise (ATP) represents the quantity available for sale at any given period. The
basic formula for ATP is ATP quantity = on-hand quantity + supply - demand shortage.
Oracle Inventory enables you to define different rules that govern what is considered supply
and demand. Available to promise process looks at existing supply and demand to determine
availability. For example, you have 100 units on hand on Monday, and 100 units of purchase
orders coming on Tuesday and new orders that you plan to release to execution for 100 units
on Wednesday. Consequently, the available to promise on Monday is 100, Tuesday is 200, and
Wednesday is 300.
Capable to promise
The capable to promise computations will try and create new supplies to compute availability.
If there is a demand for 200 units on Monday, then the system determines whether to move the
availability date to Tuesday when the Purchase orders and on-hand make it 200 units or see if
there is enough capacity and upstream materials (components) to make, procure, or transfer
100 additional units to make the availability for Monday.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Past-Due-Demand Days
The ATP process does not consider any demand scheduled before the past-due-demand time
fence date. The ATP process considers all demand from the beginning of the past-due-demand
time fence date to the current date as demand for the current date.
Past-due-demand time fence = (current date) (past-due-demand days)
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
ATP Demand
ATP demand is the sum of all demand quantities in the supply period. If demand occurs on a
nonworkday, the ATP calculation considers that demand as belonging to the previous workday.
ATP by Demand Class Check Box
If you select the ATP by Demand Class check box, the ATP calculation considers only supply
and demand for a particular demand class. The demand class feature enables you to forecast,
plan, and promise based on subdivisions of your demand. For example, a demand class might
represent a large customer or a group of related customers.
If you select ATP by Demand Class, Oracle Inventory considers only the following sources of
supply:
Discrete MPS
Repetitive MPS
Discrete WIP
Repetitive WIP
Nonstandard WIP
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
ATP Checking
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Reservation Types
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Reservation Types
For on-hand inventory supply, there are two types of reservations, high level reservations, and
low level reservations. High level reservations contain information about the item and the
organization. Low level reservations contain more detailed information about the item such as
revision, lot, subinventory, serial, and locator. You use the Item Reservations window to
create, view, update, transfer, and delete reservation requests.
e
l
c
a
r
O
Supply Types
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Demand Types
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
User-Defined Demand
You can create your own demand types based on transaction source types. For example, you
can create a demand type for consigned material that you receive from a supplier. For more
information about creating transaction source types see Defining and Updating Transaction
Source Types, Oracle Inventory Users Guide.
e
l
c
a
r
O
Reserving Material
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Reserving Material
You can create reservations as high-leveled or as detailed as you would like. You can reserve
material at the subinventory, locator, and if applicable lot and serial level.
You can reserve specific serial number, or reserve multiple serials. You can only enter a serial
for the supply type Inventory using the Reservations window. If you enter a serial number in
the serial column, and the item is uniquely identified in the system, then the quantity and
reserved serial quantity fields default to one, and all other applicable fields such as item, lot,
and LPN default as well. If the item is not uniquely identified, then you must enter the item
number. Once you enter the item number the rest of the information populates automatically. If
you reserve multiple serials, then the column Reserved Serial Quantity displays the amount of
serials you reserved. Though this value can differ from the quantity column, it cannot exceed
the quantity column.
e
l
c
a
r
O
Changes to Supply
If you make changes to supply sources, then the system behaves as follows for the different
supply types:
Purchase Requisition: If you reduce the quantity of, or cancel a purchase requisition that
is reserved against a demand, then the system reduces or the cancels corresponding
reservation.
Purchase Order: If you reduce the quantity of, or cancel a purchase order, that is
reserved against a demand, then the system modifies or cancels the corresponding
reservation. Any other changes to the purchase order that affect the expected quantity also
trigger changes to the associated reservation. Such changes include, changing the
organization, or item, or closing the order line.
Internal Requisition: You cannot modify an approved internal requisition. You can
however, modify the associated internal sales order. When you modify an internal sales
order, the system updates the supply data. If you modify the quantity of an internal sales
order, then the system also modifies corresponding reservations against the internal
requisition.
Advance Shipment Notice: If you cancel a reserved ASN then the reservations engine
checks to see if a reservation against the PO existed before the system transferred it to the
ASN. If a previous reservation exists, then the system transfers the reservation back to the
PO. If a previous reservation against the PO does not exist, then the system cancels any
reservations associated with the ASN.
Process Production Batches and Shop Floor Jobs: If you make a change to a process
production batch or a shop floor job, then the system updates the corresponding
reservations.
Changes to Demand
If you make changes such as canceling or reducing the quantity of a sales order, then Oracle
Order Management modifies corresponding reservations.
If you reserve components for a work order against inventory or a purchase order, and you
modify the demand source, then the system modifies the corresponding reservations.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Material Status
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Setting Up
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Option
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
R12 Replenishment
Fundamentals
y
m
Chapter 10
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Order Planning
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Replenishment Considerations
Before you replenish your inventory, you should consider the following:
Order time
Order size
Planning method
When to Order
Typically, you should order when the on-hand quantity plus incoming supply minus demand is
less than the specified minimum inventory level. On-hand quantity refers to what you currently
have in stock. Supply represents on-hand stock plus inventory coming into the organization.
Demand represents the need for a particular item.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Replenishment Methods
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Forecast Sets
Forecast sets consist of one or more forecasts. Sets group complimenting forecasts into a
meaningful whole. For example, a forecast set could contain separate forecasts by region.
Forecast Rule
Forecast rules define the bucket type, forecast method, and the sources of demand.
Note: You can manually create forecasts using Oracle Inventory or Oracle MRP. There are no
constraints for manually created forecasts. Manually created forecasts can be based on
transaction activity other than historical data. For more information see Defining a Forecast
Rule and Generate a Forecast, Oracle Inventory Users Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Forecast Types
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Forecast Types
Forecast generation uses mathematical algorithms to calculate a prediction of future demand.
You can calculate estimated future demand for items using historical data and focus or
statistical forecasting techniques. You can create multiple forecasts and group complementing
forecasts into forecast sets. Oracle Inventory supports the following forecast types:
Focus
Statistical
Focus forecasting enables you to simulate various methods of calculating demand so you can
select the best forecasting model. Statistical forecasting enables you to use detailed history and
applies weighted factors to exponentially smooth the data. Statistical forecasting also enables
you to apply exponentially weighted trend and seasonality factors to predict demand.
You typically use focus forecasting to produce single period forecasts, whereas you can use
Statistical forecasting to forecast any number of periods into the future.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Safety Stock
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Note
To manually assign: (N) Planning > Safety Stocks
To have the system calculate: (N) Planning > Safety Stock Update
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Providing a Forecast
The reorder-point planning program uses information from the forecast to calculate the
Economic Order Quantity (EOQ) and the reorder-point quantity. The following equations show
each of these calculations:
EOQ = SQRT {[2 (annual demand) (order cost)] / (annual carrying costs)}
Reorder point = safety stock + [(lead time) (average demand)]
Providing On-Order Quantity Information
Oracle uses on-order quantity information to determine when to reorder an item. You should
reorder when the following is true:
(quantity on hand + quantity on-order) < reorder point
Oracle uses the following sources to calculate on-order quantities:
Purchase orders
Requisitions (internal and supplier)
In-transit shipments owned by the organization
Oracle Inventory uses purchase orders, requisitions, and in-transit shipments that are scheduled
to be delivered before the supply cutoff date.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Min-Max Planning
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Min-Max Planning
Recall that Min-max planning is a method of that determines when and how much to order
based on user-defined minimum and maximum inventory levels.
Note: To perform organization-level Min-max planning for an item, you must specify
organization-level minimum and maximum quantities.
Deciding When to Order with Min-max Planning
You should order when the following is true:
(on-hand quantity demand) + (quantity on order) < minimum quantity
Quantity on order is the sum of purchase order quantities, requisition quantities, and in- transit
shipments. It also includes WIP jobs as supply at the organization level. Quantity on order
represents supplies that you have not yet received in your organization.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Note
You can constrain the order quantity by specifying the following order modifiers for an item:
Fixed-lot multiplier
Minimum order quantity
Maximum order quantity
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Replenishment Counting
Replenishment counting enables you to perform counts for non-tracked subinventories and
then direct Oracle Inventory to check these counts against the minimum quantities that you
specified.
A non-tracked subinventory is an expense subinventory for which Oracle Inventory does not
maintain on-hand quantity information. When you move valued material to a non-tracked
subinventory, Oracle Inventory automatically charges the appropriate expense account and
discards that quantity. Non-tracked subinventories typically store items of low value, such as
office stationery. You can also use replenishment counting if you do your own planning. In this
case you may order either a specific quantity or the maximum quantity specified in the MinMax values. Non-tracked subinventories might include hospital storerooms, where there is no
opportunity to record accurate and timely issue-transaction information.
For more information see Overview of Replenishment Counting, Oracle Inventory Users
Guide.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Note
Use the INV: Replenishment Count Requisition Approval profile option to specify the
requisition approval status.
Use the INV: Replenishment Count Line Failure profile option to specify whether the
system should stop or continue processing in case a replenishment count fails.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Subinventories Window
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Order Quantity
The item for which you select this method can be planned using any replenishment planning
method. With the Order Quantity count type, Oracle Inventory generates a requisition for the
quantity that you enter.
Navigation Path
Use the following navigation path to access the Replenishment Count Lines window:
Inventory Responsibility(N) Counting > Replenishment Counts > Counts (B) Lines.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Navigation Paths
Inventory Responsibility(N) Counting > Replenishment Counts > Process Interface.
Inventory Responsibility (N) Counting > Replenishment Counts > Purge.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
PAR Counts
Periodic Automated Replenishment (PAR) counting is a replenishment method that enables
you to perform replenishment count at a locator level. For example, in Oracle Inventory you
can model a hospital storeroom as a subinventory and the shelves and trolleys in the storeroom
as locators. You can define PAR levels for each item stored in these locators. You can
replenish these items every time they go below the PAR level.
In general, the steps for PAR are the same as that of replenishment counting. For a list of these
steps, see Replenishment Planning Steps earlier in this lesson. The following steps are specific
to PAR:
Enable PAR level planning for the subinventories.
Define locators for the subinventories.
Enter the PAR level when you define the item subinventory relationship.
Note: If you have enabled PAR level planning for a subinventory, you cannot perform minmax planning for that subinventory. The PAR level acts as both the minimum and maximum
quantity levels for subinventories that have PAR level planning enabled.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Choose order quantity to generate a replenishment requisition for the quantity that you want to
order. In this case, the quantity denotes the order quantity.
Note: If you have not specified the PAR level, then you can only choose order quantity as the
count type.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Kanban Replenishment
Kanban is a means of supporting pull-based replenishment in manufacturing systems. A
kanban system is a self-regulating pull system that leads to shorter lead times and reduced
inventory. Kanban systems are typically applied to items with relatively constant demand and
medium-to-high production volume.
Kanbans represent replenishment signals that are manual and highly visible, such as a colorcode card that moves with the material, a light that goes on when replenishment is required, or
an empty bin that is moved to the supply location to trigger replenishment.
Kanban systems typically provide support for external devices, such as bar code readers to read
kanban cards and trigger a replenishment signal.
Kanban System Features
Kanban systems include the following characteristics:
Close cooperation between the users and the supply channel
Short re-supply lead times
Relatively small quantities reordered at a time
Relative frequent ordering
e
l
c
a
r
O
For more information see: (Help) Oracle Inventory > Inventory Planning and Replenishment >
Overview of Kanban Replenishment.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Kanban Cards
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Kanban Replenishment
Recall that a kanban system is a self-regulating pull system that leads to shorter lead times and
reduced inventory. Kanban systems are typically applied to items with relatively constant
demand and medium-to-high production volume.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Navigation Path
Inventory Responsibility(N) Kanban > Pull Sequences > (T) Source.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Kanban Cards
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Kanban Cards
Kanban cards are created for an item, subinventory, and locator (optional). They are uniquely
identified by a kanban number. For cards generated from a kanban pull sequence, the number
is automatically generated. For manually defined cards, both replenishable and
nonreplenishable, you can enter an unused kanban number or let the system create the number.
You cannot override the quantity for generated cards, but you can add additional cards or
delete existing cards from the pull sequence to control the inventory in the replenishment
chain.
A supply source defaults from the sourcing rules if a sourcing rule is available for the item and
kanban location. Only the primary supplier, based on the split percentage and ranking, is used.
You can manually override the quantity and supply source on a pull sequence only before the
cards are printed. Changes to the pull sequence are not reflected until the old cards are deleted
and new ones are created. Updates to the sourcing rules apply only to cards created after the
update.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
It is possible to verify that an entry has been made into the table
WIP_JOB_SCHEDULES_INTERFACE.
Run the associated Mass load Concurrent Program (WIP > Discrete > Import Jobs and
Schedules) to ensure that the WIP interface tables have been picked up and processed.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 11
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
ABC Analysis
An ABC analysis determines the relative value of a group of inventory items based on criteria
you define. ABC refers to the rankings you assign your items as a result of this analysis, where
A items are ranked higher than B items, and so on.
You use the ABC analysis you compile to drive cycle counts. You count items of high value
(A items) very frequently, items of lower (B items) value less frequently, and items of lowest
(C items) value very infrequently.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Cycle Counting
Cycle counting is the periodic counting of individual items throughout the course of the year to
ensure the accuracy of inventory quantities and values. Accurate system on-hand quantities are
essential for managing supply and demand, maintaining high service levels, and planning
production. Most effective cycle counting systems require the counting of a certain number of
items every workday with each item counted at a prescribed frequency. You can use cycle
counting along with ABC analysis to count items of greater importance more frequently than
those of less importance. Cycle counting supports scheduled counting based on value or
counting by location, and can be set up at the organization level or the subinventory level.
Benefits of Cycle Counting
Cycle counting enables you to keep inventory records accurate by correcting errors between
the system on-hand (perpetual) and actual on-hand (physical) quantities. Cycle counting can
also be a valuable tool to help identify patterns in the errors found. Analysis of these patterns
can suggest and help to prioritize improvements in training, tools, and processes. Over a period
of time these improvements may increase the average level of inventory record accuracy.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Approval Tolerances
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Approval Tolerances
Oracle Inventory supports two types of cycle count approval tolerances, Quantity Variance
Tolerance and Adjustment Value Tolerance. For each type, you can specify a positive and a
negative limit which can differ from each other. When a particular cycle count entry results in
an adjustment that exceeds any one of these limits, you have a cycle count adjustment that
exceeds approval tolerances. Based on the approval option you choose when you define your
cycle count, this adjustment is either posted automatically or held for approval.
Quantity Variance Tolerance
The Quantity Variance Tolerance is a user-defined limit for the difference between the actual
cycle count quantity and the system tracked on-hand quantity. You express positive and
negative quantity variance tolerances as percentages of the system on-hand quantity.
You enter these percentages when you define your:
Cycle Count Header
Cycle Count Classes
Cycle Count Items
e
l
c
a
r
O
Oracle Inventory uses any percentages you define at the cycle count item level first. If you do
not have any defined for an item, it uses the tolerances defined for that items cycle count class.
If you do not have any defined for the class, it uses the tolerances at the cycle count header
level. If you have no tolerances defined for the header, Oracle Inventory assumes that there is
no limit to the approval tolerance.
Adjustment Value Tolerance
The Adjustment Value Tolerance is a user-defined limit for the total value of a cycle count
adjustment.
The adjustment value is calculated as:
adjusted value = (system on-hand qty actual count qty) * current item cost
The Adjustment Value Tolerance is expressed as positive and negative amounts in your
functional currency. An adjustment value is out of tolerance if it falls outside of these amounts.
You enter these tolerances when you define your cycle count header and cycle count classes.
Oracle Inventory uses the values you define at the cycle count class level first. If you do not
have any defined for an items class, it uses the values at the cycle count header level. If you
have no tolerances defined for the header, Oracle Inventory assumes that there is no limit to the
approval tolerance.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Hit/Miss Tolerance
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Hit/Miss Tolerance
The Hit/Miss Tolerance is a user-defined limit for the difference between the system tracked
on-hand quantity and the actual cycle count quantity. You express positive and negative
hit/miss tolerances as percentages of the system on-hand quantity. A count is considered a hit
if it is within these tolerances, and a miss if it is outside them.
The Hit/Miss Tolerance allows you to evaluate the actual accuracy of your inventory.
You enter Hit/Miss tolerance percentages when you define your cycle count header and when
you define your cycle count classes. Oracle Inventory uses the percentages you define at the
cycle count class level first. If you do not have any defined for an items class, it uses the
tolerances at the cycle count header level. If you have no tolerances defined for the header,
Oracle Inventory assumes that there is no limit to the Hit/Miss tolerance, and all variances are
therefore hits regardless of the size.
Inventory uses these tolerances to generate the Cycle Count Hit/Miss Analysis report which
will be covered later in this course.
e
l
c
a
r
O
Measurement Errors
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Measurement Errors
Negative and positive measurement errors are user-defined limits for the difference between
the cycle count quantity and the system tracked on-hand quantity. Measurement Error limits
are assigned by Item. Inventory does not make any adjustments to an item whose cycle count
quantity differs from the system tracked on-hand quantity by less than the measurement error.
Because of this, measurement errors may implicitly override any approval tolerances you
specify.
You specify measurement errors when you define or update an item at the Master Item or
Organizational Item level. Use measurement errors with extreme caution since they actually
prevent cycle count adjustments from taking place. You would typically use this feature on an
exception basis for items you cannot accurately count. For example, if you visually check the
level of bolts in a bin to estimate the quantity, or you use their weight to approximate the
quantity, you might want to allow for measurement errors. Therefore, if your system tracked
on-hand quantity for the bolts in that bin is within an acceptable range, you do not perform a
cycle count adjustment.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
You manually enter, delete, or update the items you want included/excluded using the Cycle
Count Items window. You may want to use this window to load all your items for a cycle count
or to simply add items as they are defined in the system rather than recompiling your ABC
group and doing a complete reinitialization.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Automatic Scheduling
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Automatic Scheduling
In order for Oracle Inventory to perform automatic scheduling you must do the following:
Set the Cycle Count Enabled item attribute to Yes for the items you want to include in the
cycle count.
Enable automatic scheduling when you define your cycle count.
Request the schedule using the Generate Automatic Schedule Requests window.
- Each time the auto scheduler runs, it schedules counts only for the schedule interval
you defined for the cycle count header. So if your schedule interval is weeks, Oracle
Inventory schedules all items that you need to be counted on all of the workdays in
the current week. If your schedule interval is days, then Oracle Inventory only
schedules those items that are due for counting on the current date.
e
l
c
a
r
O
Manual Scheduling
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Manual Scheduling
You can request counts for specific subinventories, locators, and items, and set the count for
any inventory date. For example, you could enter a request to count item A wherever it can be
found in subinventory X. Or you could request to count all item quantities in subinventory Y,
locator B-100.
Since manually scheduled counts have no impact on automatically scheduled counts, you can
potentially count some items more frequently than you had initially planned.
Physical Location Scheduling
You can use this feature to execute location-based cycle counting. You first need to generate a
schedule for counting each subinventory and locator. You then need to enter the schedule
requests for each locator, specifying the schedule date.
e
l
c
a
r
O
Count Requests
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Count Requests
This process takes the output of the automatic scheduler and your manual schedule entries and
generates a count request for each item number, revision, lot number, subinventory and locator
combination for which on-hand quantities exist. These count requests are ordered first by
subinventory and locator, then by item, revision, and lot. Oracle Inventory assigns a unique
sequence number to each count request that can be used for reporting, querying and rapid count
entry.
As the count requests are derived from the state of on-hand balances at the time the Generate
Cycle count Requests process is run, you should wait to run it until you are ready to count.
Note: When you schedule an item to be counted using manual scheduling, some schedule
requests may have overlapping count requirements. The count request generator does not
create duplicate count requests, but instead cross-references one count request back to each
associated schedule request.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Automatic Recounts
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Automatic Recounts
If you turn on the Automatic Recount option when you define your cycle count, Oracle
Inventory automatically submits recount requests for items that are outside the limits of the
approval tolerances you specify. Oracle Inventory submits recounts as many times as
necessary, limited by the maximum automatic recounts you specify for the cycle count. After
you reach the maximum number of recounts, Oracle Inventory holds the count for approval.
Any count request with the Recount status automatically appears on the next cycle count
listing. You can manually request recounts when you are approving adjustments. This recount
request will be included in the next cycle count listing.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Item Location: View information for subinventory and locator. You can also view the
primary and secondary adjustment UOM, primary and secondary adjustment quantity,
adjustment value, and adjustment percent.
Item Details: View information for a revision, lot number, and serial number. You can
also view the unit of measure and adjustment quantity.
Reason, Reference: View or update the transaction reason and reference information.
You can also view the primary and secondary adjustment UOM, primary and secondary
adjustment quantity, adjustment value, and adjustment percent.
Count: View information for primary and secondary UOM, primary and secondary count
quantity, counter, and count date.
Count Status, Class: View information for the sequence number, count status, and cycle
count class.
Approval: View information for date approved and approver.
Approval Actions and Adjustments Options
For items appearing in the Approval Actions, Adjustments region, you can approve, request a
recount, or reject cycle count entries that are pending approval. You can also approve or reject
any count for which a recount has already been requested. You can reject any cycle count
request that has not yet been counted. You can display count history information or open the
Count Adjustment Approvals window.
Select Approved to approve the selected count entry and post the adjustment to the
transaction manager for processing.
Select Rejected to reject the selected count record. An adjustment is not posted. No further
processing of this count entry takes place.
Select Recount to process a recount request for the selected count request. An adjustment
is not posted.
Select the Count History button to open the Count History window for the current item.
For the current item, this window displays count and variance information for the current,
prior and first counts.
Select the Open button to open the Count Adjustment Approvals window for the current
line. This window is a combination block which you can use to view and enter approval
and adjustment information for the current line instead of using the Count Adjustment
Approvals Summary window.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Physical Inventory
A physical inventory is a periodic reconciliation of system on-hand balances with physical
counts in inventory. You can perform physical inventories whenever you choose to verify the
accuracy of your system on-hand quantities. You can perform a physical inventory for an entire
organization or for particular subinventories within an organization. Physical inventories are
usually performed once every six months or once a year depending on the organization
requirements.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
You can also exclusively use blank tags to perform a physical inventory. If you need to
perform a complete wall-to-wall physical inventory, you can go through your warehouse and
attach blank tags to every item and/or location you see. As you perform the count, you record
the item and stock-keeping unit information along with the actual on-hand quantity.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Inventory Snapshots
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Inventory Snapshots
Before you can generate tags for a physical inventory, you must take a snapshot of all system
on-hand quantities for your items. The snapshot saves all current item on-hand quantities and
costs. Oracle Inventory uses this information as the basis for all physical inventory
adjustments. All tag counts you enter for this physical inventory are compared with these static
quantities. This allows you to resume normal inventory operations after you have entered your
counts but before you have authorized all final physical inventory adjustments. You can
perform your recounts or investigate certain results without holding up transaction processing.
Note: Oracle Inventory does not stop inventory processing during a physical inventory.
Therefore, you must procedurally coordinate the snapshot of your physical inventory with your
actual counting, and ensure that no transaction activity occurs in a particular location until after
you have performed your adjustments.
Note: It is recommended to clear the Pending Transactions and Transactions Open Interface,
before taking a snapshot of inventory quantities.
For example, suppose that at the start of your physical inventory the system on-hand quantity
for item WIDGET in a particular bin is 30. Oracle Inventory saves this information with the
physical inventory snapshot. During the warehouse count, you count a total of 25 units of item
e
l
c
a
r
O
WIDGET in the same bin. Before you approve your counts and perform your adjustments, you
resume normal transaction operations, and consequently, item widget reaches a system on-hand
quantity of 45. At this point, you perform your physical inventory adjustments. Oracle
Inventory computes the adjustment as the difference between the tag count and the snapshot
quantity, NOT the current system quantity of the item that has now reached 45. So in this case,
the adjustment is 25 - 30 = -5 units. When the adjustment is posted, the new system on-hand
quantity becomes 40 units.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Oracle Inventory holds for approval all tags with counts that are outside the limits of the
quantity variance or adjustment value tolerances, If you set your approval option to Required
for all adjustments, Oracle Inventory holds all counts for approval.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Voiding Tags
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Voiding Tags
It is important for auditing purposes to track the status of each physical inventory tag.
Therefore, if you do not use one or more of the tags Oracle Inventory generates, you should
void them in the Physical Inventory Tag Counts window. A voided tag is not reported as a
missing tag in the Physical Inventory Missing Tag Listing.
If you generated blank tags at the beginning of your physical inventory, and ended up not using
all of them, you void the unused tags. When you run the Physical Inventory Missing Tag
Listing for the whole range of tags you generated, the unused tags appear as missing tags.
If you void a default tag, (for example, a tag that identifies a stock-keeping unit for which there
is system on-hand quantity), Oracle Inventory adjusts the quantity in that location to zero. This
indicates that you did not use the tag in question, presumably because the stock-keeping unit
corresponding to the tag did not exist.
e
l
c
a
r
O
Approval Tolerances
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Approval Tolerances
Oracle Inventory supports two types of physical inventory approval tolerances. For each type,
you can specify a positive and a negative limit. When a particular physical inventory tag count
entry results in an adjustment that exceeds any one of these limits, you have a physical
inventory adjustment that exceeds approval tolerances. Based on the approval option you chose
when you defined your physical inventory, this adjustment is or is not held for approval.
If you decide that approval is required for adjustments out of tolerance you must enter at least
one positive or negative value for one type of approval tolerance. The quantity variance
tolerance is a user-defined limit for the difference between the system-tracked on-hand
quantity and the actual tag count quantity. You express positive and negative quantity variance
tolerances as percentages of the system on-hand quantity. You enter these percentages when
defining your physical inventory.
The adjustment value tolerance is a user-defined limit for the total value of a physical
inventory adjustment: adjustment value = (system on-hand qty - actual count qty) x current
cost, where: Current cost is the cost at inventory snapshot. You express positive and negative
adjustment value tolerances as amounts in your ledger currency. You enter these tolerances
when defining your physical inventory.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Accuracy Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Accuracy Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Accuracy Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Accuracy Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Accuracy Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Accuracy Reports
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Profile Options
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objective
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Organization Tables
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Organization Tables
MTL_PARAMETERS: Associated with an organization. Primary key:
ORGANIZATION_ID.
MTL_INTERORG_PARAMETERS: Identifies the receiving organizations linked to a
particular organization. You must define the interorganizational relationship before you
perform any interorganization transfers. Units of measure, distance, transfer charge, and
accounting information are also specified in this table. Primary key:
FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID.
GL_SETS_OF_BOOKS: Stores define set of books data in General Ledger. Each row
includes the set of books name, description, functional currency, and other data.
Corresponds to the Define Set of Books window. Primary key:
GENERAL_LEDGER_UPDATE_CODE.
GL_CODE_COMBINATIONS: Stores valid Accounting Flexfield segment value
combinations for each accounting flexfield structure within your General Ledger. Primary
key: CODE_COMBINATION_ID.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Master
MTL_SYSTEM_ITEMS_B: This table is the definition table for items. This table holds
the definitions for inventory items, engineering items, and purchasing items. The flexfield
code is MSTK. The primary key for an item is the INVENTORY_ITEM_ID and the
ORGANIZATION_ID. The same item could be defined in more than one organization.
Each row represents an item in an organization.
MTL_ITEM_ATTRIBUTES: This table stores the item attributes, their user-friendly
names if the item is maintained at the item or item/organization level, and the kind of
validation required for each attribute. This table is seeded on install or upgrade. The
primary key is ATTRIBUTE_NAME.
MTL_ITEM_TEMPL_ATTRIBUTES: This table stores the attributes and attribute values
for a template. When a template is created, a row is inserted for each available item
attribute. When the template is applied to an item, the enabled attribute values are
propagated to the item. The primary key is TEMPLATE_ID, ATTRIBUTE_NAME.
MTL_ITEM_STATUS_TL: This table is the definition table for a material status code.
The status code is a required item attribute and indicates the item status (for example,
active, pending, or obsolete). You may define as many additional status codes as you
e
l
c
a
r
O
want. The values of the individual status attributes associated with an item status are
stored in MTL_STATUS_ATTRIBUTE_VALUES. The primary key is
INVENTORY_ITEM_STATUS_CODE.
MTL_ITEM_TEMPLATES_B: This table is the definition table for item templates. It
contains the user-defined name and description. When the template is applied to an item,
the enabled item attributes are propagated to the item. The primary key is
TEMPLATE_ID.
MTL_STATUS_ATTRIBUTE_VALUES: This table stores the attribute values associated
with an item status code. One record is created for each of the function-enabling attributes
for each defined item status code. The primary key is
INVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME.
MTL_PARAMETERS: This table is an inventory organization with which an item is
associated. The primary key is the ORGANIZATION_ID.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
- OE Orderable
- Internal Orderable
- Billable
MTL_STATUS_ATTRIBUTE_VALUES: This table stores the attribute values associated
with an item status code. One record is created for each of the function-enabling attributes
for each defined item status code. The primary key is
INVENTORY_ITEM_STATUS_CODE, ATTRIBUTE_NAME.
MTL_ITEM_STATUS_TL: This table is the definition table for a material status code.
The status code is a required item attribute and indicates the item status (for example,
active, pending, or obsolete). You may define as many additional status codes as you
want. The values of the individual status attributes associated with an items status are
stored in MTL_STATUS_ATTRIBUTE_VALUES. The primary key is
INVENTORY_ITEM_STATUS_CODE.
MTL_PENDING_ITEM_STATUS: This table is used to define and store the history of
the item statuses that have been or will be assigned to an item. This table maintains the
status history for each item. This table also stores pending status information. The primary
key is INVENTORY_ITEM_ID, ORGANIZATION_ID, STATUS_CODE,
EFFECTIVE_DATE.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
different categories in different category sets, but can be assigned to only one category
within a category set. The primary key is CATEGORY_SET_ID.
MTL_CATEGORY_SETS_TL: This table is a table holding translated Name and
Description columns for Category Sets. The primary key is CATEGORY_SET_ID,
LANGUAGE.
MTL_CATEGORY_SET_VALID_CATS: This table defines the valid category list for a
particular category set. If category validation is required, the list of valid categories is
stored in this table and is used to restrict category selection for the category set. The
primary key is CATEGORY_SET_ID, CATEGORY_ID.
MTL_DEFAULT_CATEGORY_SETS: This table stores the identifier of the category set
that acts as the default for a particular functional area. This information is used to
determine the mandatory category sets for an item. It is also used to provide a default
category set for forms and reports that require a category set field value or parameter. The
primary key is FUNCTIONAL_AREA_ID, CATEGORY_SET_ID.
MTL_ITEM_CATEGORIES: This table stores the item assignments to categories within a
category set. For each assignment, this table stores the item, category set, and the
category. Items can be assigned to multiple categories and category sets, but can be
assigned to only one category in a given category set. This table is populated through
either the Define Item or the Update Item/Org Attributes forms. It can also be populated
by performing item assignments when a category set is defined. The primary key is
INVENTORY_ITEM_ID, ORGANIZATION_ID, CATEGORY_SET_ID.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
OE-ORDER_LINES_ALL: This table stores information for all order lines in Oracle
Order Management. The primary key is LINE_ID.
GL_CODE_COMBINATIONS: This table stores valid Accounting Flexfield segment
value combinations for each accounting flexfield structure within your General Ledger
application. Available material can be reserved against a valid Accounting Flexfield
combination. The primary key is CODE_COMBINATION_ID.
MTL_GENERIC_DISPOSITIONS: This table stores the user-defined account alias. An
account alias provides a method to use accounting numbers and makes it easier to transact
account issues and receipts. Available inventory can be reserved against an account alias.
The primary key is DISPOSITION_ID, ORGANIZATION_ID.
MTL_MATERIAL_TRANSACTIONS: This table stores a record of every material
transaction or cost update performed in Inventory. An issue transaction to an account
number or account alias can relieve a reservation against the account number or alias. The
primary key is TRANSACTION_ID.
MTL_DEMAND_INTERFACE: This table is the interface point between non-Inventory
applications and the Oracle Inventory demand module. Records inserted into this table are
processed by the Demand Manager concurrent program.
MTL_SYSTEM_ITEMS_B: This table is the definition table for items. This table holds
the definitions for inventory items, engineering items, and purchasing items. The primary
key for an item is the INVENTORY_ITEM_ID and the ORGANIZATION_ID.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A