D50091GC20 SG

Student Guide
D50091GC20
Edition 2.0
October 2009
D64408
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS
COMPUTER IS STRICTLY PROHIBITED
Oracle University and Egabi Solutions use only
R12 Oracle Order Management

Fundamentals
Copyright 2009, Oracle. All rights reserved.

Disclaimer
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and
print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way.
Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display,
perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization
of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document, please
report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This document is not
warranted to be error-free.
Restricted Rights Notice
U.S. GOVERNMENT RIGHTS

The U.S. Governments rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Trademark Notice
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective
owners.
Author
Pratima Mahtani
Technical Contributors and Reviewers
Lata Sundar, John Brazier
This book was published using:
oracletutor
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM ONLY. COPYING eKIT MATERIALS FROM THIS
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
Table of Contents
Order Entities and Order Flows ....................................................................................................................2-1

Order Entities and Order Flows.....................................................................................................................2-3
Objectives ......................................................................................................................................................2-4
Order to Cash Lifecycle with Standard Items................................................................................................2-5
Order to Cash Lifecycle with PTO Models and PTO Kits ............................................................................2-18
Drop Shipments .............................................................................................................................................2-20
Drop Shipments Across Ledgers ...................................................................................................................2-22
Back-to-Back Orders .....................................................................................................................................2-25
Sales Agreements ..........................................................................................................................................2-26
Negotiation Agreement..................................................................................................................................2-27
Approve Sales Agreement .............................................................................................................................2-28
Releases Against a Sales Agreement .............................................................................................................2-29
Order to Cash Lifecycle with Customer Acceptance.....................................................................................2-31
Simple Negotiation within Order Management.............................................................................................2-35
Querying on Prices and Availability..............................................................................................................2-36
Summary........................................................................................................................................................2-37
Multiple Organization Access Control Setup................................................................................................3-1
Multiple Organization Access Control Setup ................................................................................................3-3
Objectives ......................................................................................................................................................3-4
Organization Structure in Oracle Applications..............................................................................................3-5
Multi-Org Access Control (MOAC)..............................................................................................................3-7
Using MOAC in Oracle Order Management .................................................................................................3-9
Setting Up MOAC .........................................................................................................................................3-11
Summary........................................................................................................................................................3-13
Oracle Inventory Setup for Oracle Order Management..............................................................................4-1
Oracle Inventory Setup for Oracle Order Management.................................................................................4-3
Objective........................................................................................................................................................4-4
Overview .......................................................................................................................................................4-5
Receipt to Issue Lifecycle..............................................................................................................................4-6
Inventory Organizations ................................................................................................................................4-7
Setting Up Locations .....................................................................................................................................4-8
Inventory Organization Structure ..................................................................................................................4-9
Sample Inventory Organization.....................................................................................................................4-11
Interorganization Shipping Networks............................................................................................................4-12
Shipping Method ...........................................................................................................................................4-14
Units of Measure ...........................................................................................................................................4-15
Uses of Units of Measure ..............................................................................................................................4-16
Unit of Measure Class ...................................................................................................................................4-17
Unit of Measure Conversions ........................................................................................................................4-18
What is an Item? ............................................................................................................................................4-19
Steps to Setup, Define, and Maintain Items...................................................................................................4-20
Defining Items ...............................................................................................................................................4-21
Copyright Oracle, 2009. All rights reserved.
Oracle Order Management Fundamentals Table of Contents
i
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS CLASSROOM
ONLY. COPYING eKIT MATERIALS FROM THIS
Overview of Oracle Order Management .......................................................................................................1-1

Overview of Oracle Order Management .......................................................................................................1-3
Objectives ......................................................................................................................................................1-4
What is Oracle Order Management? .............................................................................................................1-5
Order Capture and Order Fulfillment ............................................................................................................1-7
Oracle Order Management Capabilities ........................................................................................................1-8
Order to Cash Lifecycle.................................................................................................................................1-10
Integration with Other Products.....................................................................................................................1-11
Summary........................................................................................................................................................1-12
Oracle Receivables Setup for Oracle Order Management...........................................................................5-1

Oracle Receivables Setup for Oracle Order Management .............................................................................5-3
Objectives ......................................................................................................................................................5-4
Overview of Trading Community Architecture.............................................................................................5-5
Key Customer Related Concepts in TCA ......................................................................................................5-6
Adding Customers in Order Management .....................................................................................................5-8
Defining Payment Terms...............................................................................................................................5-9
Defining Invoicing and Accounting Rules ....................................................................................................5-10
Defining Auto-Accounting Parameters .........................................................................................................5-11
Defining Territories in Receivables...............................................................................................................5-14
Defining Invoice Sources (Batch Source) Automatic Transaction Numbering ..........................................5-15
Define Salespersons to Assign Sales Credit ..................................................................................................5-17
Using the Resources Window to Create a Salesperson..................................................................................5-18
Tax Setups in Transaction Types Window Receivables and Order Management ......................................5-19
Overview of Credit Checking........................................................................................................................5-20
Defining Credit Checking on the Customers Page Profile Tab ..................................................................5-21
Defining Credit Checking on the Customers Page - Profile Amounts Tab ...................................................5-23
Credit Check Rules........................................................................................................................................5-25
Defining Credit Usage Rule Sets ...................................................................................................................5-26
Defining Credit Check Rules.........................................................................................................................5-28
Summary........................................................................................................................................................5-30
Oracle Order Management Setup Steps........................................................................................................6-1
Oracle Order Management Setup Steps.........................................................................................................6-3
Objectives ......................................................................................................................................................6-4
Order Management Setup Steps ....................................................................................................................6-6
Profile Options and System Parameters.........................................................................................................6-10
Overview of QuickCode or Lookup Types....................................................................................................6-12
Defining QuickCode or Lookup Types .........................................................................................................6-14
Overview of Order Header and Order Line Processing Flows ......................................................................6-15
Overview of Transaction Types Window ......................................................................................................6-16
Workflow in Transaction Types ....................................................................................................................6-19
Overview of Document Sequences for Order Numbering.............................................................................6-21
Defining Order Import Sources .....................................................................................................................6-23
Overview of Processing Constraints..............................................................................................................6-24
Setting up Processing Constraints .................................................................................................................6-26
Defining Validation Templates......................................................................................................................6-29
Defining Defaulting Conditions ....................................................................................................................6-31
Defining Defaulting Rules.............................................................................................................................6-33
ii
Item Master Organization ..............................................................................................................................4-23

Item Validation Organization ........................................................................................................................4-25
Item Attributes...............................................................................................................................................4-26
Unit of Measure Attributes ............................................................................................................................4-27
Order Management Item Attributes...............................................................................................................4-29
Item Validation ..............................................................................................................................................4-33
Item Status .....................................................................................................................................................4-36
Item Statuses and Attributes ..........................................................................................................................4-37
Organization Assignment and Organization Items ........................................................................................4-38
Control Levels ...............................................................................................................................................4-39
Item Relationships .........................................................................................................................................4-41
Customer Items..............................................................................................................................................4-42
What are Supply and Demand? .....................................................................................................................4-43
Available to Promise .....................................................................................................................................4-44
Uses of ATP in Oracle Inventory ..................................................................................................................4-45
Defining an ATP Rule ...................................................................................................................................4-46
Implementation Considerations .....................................................................................................................4-47
Summary........................................................................................................................................................4-48
Oracle Order Management Fundamentals ...................................................................................................7-1

Holds, Order Purge, and Exception Management Setup ...............................................................................7-3
Objectives ......................................................................................................................................................7-4
Holds .............................................................................................................................................................7-5
Seeded Holds .................................................................................................................................................7-6
Automatic Holds............................................................................................................................................7-8
Generic Holds................................................................................................................................................7-10
Hold Sources .................................................................................................................................................7-11
Order and Quote Purge ..................................................................................................................................7-13
Purge Sets ......................................................................................................................................................7-14
Setting Up Exception Management ...............................................................................................................7-16
Summary........................................................................................................................................................7-18
Basic Pricing Setup..........................................................................................................................................8-1
Basic Pricing Setup........................................................................................................................................8-3
Objectives ......................................................................................................................................................8-4
Overview of Pricing in the Order to Cash Process ........................................................................................8-5
Overview of Pricing Integration ....................................................................................................................8-6
Overview of Pricing Concepts.......................................................................................................................8-8
Overview of the Pricing Engine ....................................................................................................................8-10
Overview of Pricing Security ........................................................................................................................8-11
Overview of Price Lists .................................................................................................................................8-12
Overview of Pricing Agreements ..................................................................................................................8-14
Overview of Formulas ...................................................................................................................................8-15
Overview of Qualifiers ..................................................................................................................................8-16
Overview of Modifiers ..................................................................................................................................8-17
Overview of Contexts and Attributes ............................................................................................................8-19
Overview of Freight and Special Charges Modifiers.....................................................................................8-20
Overview of Basic Versus Advanced Pricing................................................................................................8-21
Overview of Price Lists .................................................................................................................................8-22
Price List Information....................................................................................................................................8-24
Creating a Price List ......................................................................................................................................8-27
Price List Header ...........................................................................................................................................8-28
Price List Line ...............................................................................................................................................8-30
Secondary Price List......................................................................................................................................8-34
Copy Price List ..............................................................................................................................................8-35
Price List Maintenance: Overview ................................................................................................................8-36
Manual Price List Updates.............................................................................................................................8-37
Adjust Price List ............................................................................................................................................8-39
Add Items to Price List..................................................................................................................................8-41
Overview of Modifiers ..................................................................................................................................8-43
Creating Modifier Lists .................................................................................................................................8-44
Adding Modifier Lines ..................................................................................................................................8-46
Creating Modifiers Lines...............................................................................................................................8-47
Modifier Line Examples ................................................................................................................................8-49
Modifier Types ..............................................................................................................................................8-50
Discount Modifier..........................................................................................................................................8-51
Price Break Modifiers: Point Breaks .............................................................................................................8-52
Surcharge Modifier........................................................................................................................................8-53
iii
Setting up Versioning and Audit History ......................................................................................................6-35

Overview of Available To Promise (ATP) ....................................................................................................6-37
Overview of Scheduling Levels.....................................................................................................................6-39
Auto-Schedule Profile Option .......................................................................................................................6-41
Internal Requisition Overview.......................................................................................................................6-43
Creating an Internal Order .............................................................................................................................6-45
Internal Requisition or Internal Order Process Flow .....................................................................................6-46
Summary........................................................................................................................................................6-47
Overview of Shipping Execution ....................................................................................................................9-1

Overview of Shipping Execution...................................................................................................................9-3
Objectives ......................................................................................................................................................9-4
Shipping Execution Flow ..............................................................................................................................9-5
Delivery and Delivery Lines..........................................................................................................................9-7
Trips and Stops ..............................................................................................................................................9-8
Delivery Leg..................................................................................................................................................9-9
Containers/LPNs............................................................................................................................................9-10
Pick Release...................................................................................................................................................9-11
Move Orders..................................................................................................................................................9-12
Pick Confirmation..........................................................................................................................................9-13
Ship Confirm .................................................................................................................................................9-14
Automated Shipping Process.........................................................................................................................9-16
One Step Shipping .........................................................................................................................................9-17
Shipping Transactions Form..........................................................................................................................9-19
Query Manager ..............................................................................................................................................9-20
Data Manager ................................................................................................................................................9-21
Quick Ship Window ......................................................................................................................................9-22
Reports and Processes ...................................................................................................................................9-23
Integration With Oracle Order Management .................................................................................................9-24
Integration With Oracle Transportation Management ...................................................................................9-25
Integration With Oracle Warehouse Management.........................................................................................9-26
Integration with Oracle Workflow.................................................................................................................9-27
Summary........................................................................................................................................................9-28
Shipping Execution Setup ...............................................................................................................................10-1
Shipping Execution Setup .............................................................................................................................10-3
iv
Qualifier Overview ........................................................................................................................................8-54

Example of Qualifier Hierarchy ....................................................................................................................8-55
Using Qualifiers with Modifier Lists.............................................................................................................8-57
Freight and Special Charge List Modifier .....................................................................................................8-58
Seeded Freight Charges .................................................................................................................................8-60
Setting Up Freight and Special Charge List Modifiers..................................................................................8-61
Overview of Price Books...............................................................................................................................8-62
Price Book Example 1 ...................................................................................................................................8-64
Benefits of Price Books .................................................................................................................................8-67
Price Book Implementation ...........................................................................................................................8-68
Implementation Steps: Setting Key Profile Options.....................................................................................8-69
Implementation Steps: Setting Key Profile Options......................................................................................8-70
Implementation Steps: Verifying Pricing Parameters....................................................................................8-71
Implementation Steps: Setting Up the Default Printer...................................................................................8-73
Implementation Steps: Setting up Oracle XML Publisher.............................................................................8-74
Creating a Price Book....................................................................................................................................8-75
Creating a Price Book: Defining General Price Book Criteria .....................................................................8-76
Creating a Price Book: Defining Price Calculation Criteria .........................................................................8-77
Creating a Price Book: Selecting Price Book Publishing Options................................................................8-78
Price Book Publishing Templates..................................................................................................................8-79
Price Book Publishing: Document Types......................................................................................................8-80
Generating and Publishing Price Books ........................................................................................................8-81
Viewing Price Book Details Online ..............................................................................................................8-82
Maintaining Price Books ...............................................................................................................................8-84
Republishing Price Books..............................................................................................................................8-85
Viewing Errors ..............................................................................................................................................8-86
Profile Options in Basic Pricing ....................................................................................................................8-87
Summary........................................................................................................................................................8-89
v
Objectives ......................................................................................................................................................10-4
Roles..............................................................................................................................................................10-5
Granting Roles To Users ...............................................................................................................................10-7
Freight Carriers..............................................................................................................................................10-9
Freight Costs..................................................................................................................................................10-11
Transit Times.................................................................................................................................................10-13
Regions and Zones.........................................................................................................................................10-15
Shipping Document Sets ...............................................................................................................................10-17
Document Categories ....................................................................................................................................10-18
XML Publisher Enabled Documents .............................................................................................................10-20
Customizing and Creating Templates............................................................................................................10-22
Document Sequences.....................................................................................................................................10-23
Choosing Printers For Searching Documents and Labels..............................................................................10-25
ITM Adapter Integration ...............................................................................................................................10-27
Delivery Compliance Screening ....................................................................................................................10-28
Shipping Exceptions ......................................................................................................................................10-30
Defining Shipping Exceptions.......................................................................................................................10-32
Logging Shipping Exceptions........................................................................................................................10-34
View and Update Logged Shipping Exceptions ............................................................................................10-36
Purge and Resolve Logged Shipping Exceptions ..........................................................................................10-37
Running Pick Release....................................................................................................................................10-38
Release Sequence Rules ................................................................................................................................10-39
Pick Slip Grouping Rule................................................................................................................................10-41
Release Rules.................................................................................................................................................10-43
Release Rule Order Tab..............................................................................................................................10-44
Release Rule Shipping Tab.........................................................................................................................10-46
Release Rule Inventory Tab........................................................................................................................10-48
Pick Release tab in Shipping Parameters Window ........................................................................................10-50
Auto Allocate.................................................................................................................................................10-52
Autocreate Deliveries ....................................................................................................................................10-53
Auto Pick Confirm.........................................................................................................................................10-54
Release Sales Orders for Picking Window ....................................................................................................10-56
Ship Confirm Rules .......................................................................................................................................10-58
Ship Confirm Rule Ship Options...................................................................................................................10-59
Ship Confirm Rule Trip Options ...................................................................................................................10-61
Ship Confirm Rule Document Set .................................................................................................................10-63
Ship Confirm Rule Shipping Parameters.......................................................................................................10-64
Creating Containers .......................................................................................................................................10-66
Container-Item Relationship..........................................................................................................................10-67
Container Load Details ..................................................................................................................................10-69
Packing Delivery Lines into Containers ........................................................................................................10-71
Packing Workbench.......................................................................................................................................10-73
Delivery Flow - Generic ................................................................................................................................10-75
Trip Flow Generic ......................................................................................................................................10-76
Ship to Deliver Process Workflow ................................................................................................................10-77
Workflow Lookups........................................................................................................................................10-78
Workflow Specific Profile Options ...............................................................................................................10-79
Workflow Specific Shipping and Global Parameters ....................................................................................10-80
Business Events .............................................................................................................................................10-82
Purging Workflows........................................................................................................................................10-84
Oracle Shipping Debugger ............................................................................................................................10-85
Shipping Lookups..........................................................................................................................................10-87
Shipping Parameters ......................................................................................................................................10-88
General Tab In Shipping Parameters Window ..............................................................................................10-89
Profile Options...............................................................................................................................................10-91
Global Parameters General Tab..................................................................................................................10-93
Summary........................................................................................................................................................10-95

vi
Preface
Profile
Before You Begin This Course
Thorough knowledge of Oracle Order Management
Working experience with Oracle Shipping Execution
There are no prerequisites for this course.
How This Course Is Organized

This is an instructor-led course featuring lecture and hands-on exercises. Online demonstrations
and written practice sessions reinforce the concepts and skills introduced.
vii
Prerequisites
Related Publications
Oracle Publications
Part Number
Oracle Order Management Users Guide
B28099
Oracle Order Management Implementation Manual
B25975
Oracle Shipping Execution Users Guide
B31232
Oracle Advanced Pricing Users Guide
B31581
Oracle Advanced Pricing Implementation Guide
B31440
Additional Publications
System release bulletins
Installation and users guides
Read-me files
International Oracle Users Group (IOUG) articles
Oracle Magazine
viii
Title
Typographic Conventions
Typographic Conventions in Text
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
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
Do not save changes to the database.
For further information, see Oracle7 Server SQL Language
Reference Manual.
Enter user_id@us.oracle.com, where user_id is the
name of the user.
Select Include a reusable module component and click Finish.
This subject is covered in Unit II, Lesson 3, Working with
Objects.
Use the SELECT command to view information stored in the

LAST_NAME
column of the EMP table.
Select File > Save.
Press [Enter].
Press and release keys one at a time:
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]
ix
Convention
Bold italic
Typographic Conventions in Code

Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
DROP USER scott

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

FROM emp;
functions
Typographic Conventions in Oracle Application Navigation Paths

This course uses simplified navigation paths, such as the following example, to direct you
through Oracle Applications.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
This simplified path translates to the following:
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
(M) From the menu, select Query then Find.
3.
(B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab
x
Convention
Caps and
lowercase
Lowercase
Typographical Conventions in Oracle Application Help System Paths

This course uses a navigation path convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example
(Help) General Ledger > Journals > Enter Journals
1.
In the navigation frame of the help system window, expand the General Ledger entry.
2.
Under the General Ledger entry, expand Journals.
3.
Under Journals, select Enter Journals.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.
xi
represents the following sequence of actions:

xii
Chapter 1
Overview of Oracle Order Management
Chapter
1 - Page 1 ONLY. COPYING eKIT MATERIALS FROM THIS
THESE eKIT MATERIALS ARE FOR YOUR USE IN THIS
CLASSROOM
Overview of Oracle Order

Management

Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
What is Oracle Order Management?

Oracle Order Management is the central product used to capture and fulfill different types
orders and returns from different sources. Some of the order types that are supported by Oracle
Order Management are: Orders with standard items, orders with service items (warranties),
orders with PTO Models and PTO Kits, orders with ATO Models and Kits, orders with CTO
items, returns, drop shipments, sales agreements with releases, back to back and internal
orders.
Using the Oracle Workflow engine, you can model and execute any order process. You can
customize workflow processes to reflect your business practices.
Order Capture
You can get orders from various sources: Import, EDI/XML, CRM, entry, etc. The Sales
Orders and Quick Sales Orders window enable you to enter, view and search for orders and
returns. The Order Organizer window enables you to search for orders based on multiple
criteria, perform mass updates and scheduling operations on many orders and lines at a time.
Using the e-Commerce (EDI) Gateway and the XML Gateway you can bring in orders from
other legacy systems and with the help of Order Import (Order Import API which in turn calls
Process Order API) you can convert them into the format that Oracle Order Management
Chapter
CLASSROOM
What is Oracle Order Management?
Chapter
CLASSROOM
accepts. Within e-Business Suite, you can obtain orders from the online store (iStore of CRM)
or Quoting and use them in Oracle Order Management.
Process Order API is used to receive any entered or imported orders. Process Order API is used
to perform operations like create, update, delete on all the objects (header, line, pricing entities)
of the sales orders window. When an order is captured, Process Order API performs tasks like
Attribute Level Security Check, Attribute Validation, Defaulting, Record Validation, Database
Write, Cross Record and Cross Entity logic to ensure data integrity and consistency.
Order Fulfillment
The Order Fulfillment process enables you to fulfill orders of various types, some of which are
Internal Orders, Back-to-Back Orders, Drop Shipments, Configure to Order etc.
The fulfillment activity is actually a seeded workflow activity (FULFILL_LINE) and it ensures
that the order lines are ready for completion. There are two activities which are considered
fulfillment method activities in the seeded OM workflows. For a standard shippable line the
fulfillment method activity is the shipping activity. For a return line the fulfillment method
activity is the receiving activity. You may define any activity as the fulfillment method activity
in a workflow process. The fulfillment activity must be between the fulfillment method activity
and the invoice interface activity in the respective workflows.
Order Capture and Order Fulfillment
Chapter
CLASSROOM
Oracle Order Management Capabilities

You can get orders from various sources, process and fulfill them in e-Business suite.
You can manage your orders by restricting the organization(s) your order(s) can be created
and viewed/updated in.
With Pricing and Shipping Execution integration, you can ensure that the order gets
progressed to the state where it can be fulfilled, which means, all the conditions that satisfy the
order completion are met.
The complete Order to Cash flow involves cycles like Order Entry to Fulfillment, and Order
Fulfillment to Invoicing.
Being a part of the e-Business Suite, Oracle Order Management integrates with AOL so that
you can create sub-menus and functions and assign them to an Order Management
responsibility, create and use concurrent request groups pertaining to Order Management,
customize Order Management forms etc.
You can personalize the Order Information Portal (HTML) pages using the following option:
In any of the Order Information Portal pages, click the Personalize Page link and on the entity
(for example: Header, Column Name) click the Personalize icon. You can personalize at any
one of the four levels: Function, Site, Organization, Responsibility. You need to enable the
Chapter
CLASSROOM
Oracle Order Management Capabilities
profile option Personalize Self-Service Defn for the Personalize Page link to display on the
page.
Chapter
CLASSROOM
Order to Cash Lifecycle

A typical order-to-cash cycle is as follows: You can enter orders from diverse sources like
iStore (online store application), EDI, XML or data entry. After you enter an order, the items
on the order are validated in Oracle Inventory; a price is calculated for the items using the
pricing engine; the availability of the items are checked and may be reserved; the items are
then pick released and shipped to the customer. You can record the customers acceptance of
the goods either before the items are billed or after the billing takes place. Customer
Acceptance is optional and you can enable the Customer Acceptance functionality using the
system parameter Enable Fulfillment Acceptance. You can then invoice the customer for the
items shipped, perform cash management and bank reconciliations.
Chapter
CLASSROOM
Order to Cash Lifecycle
Integration with Other Products

Oracle Order Management is closely integrated with the Advanced Pricing, Shipping
Execution, Configurator and Release Management products that are part of the Order
Management suite.
Chapter
CLASSROOM
Integration with Other Products
Summary
Chapter
CLASSROOM
Chapter 2
Order Entities and Order Flows
Chapter
CLASSROOM
Order Entities and Order

Flows

Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Order to Cash Lifecycle with Standard Items

The sales orders window consists of two regions: header region and lines region. You can use
the folder functionality to specify which tabs you want to see on the regions, however the Main
tab in both the regions is mandatory, and is always visible in the window.
The important header information that you would require to enter in the Main tab: Customer
Name or Number, Order Type. Once you enter these values, other values such as Ship-To
Address, Bill-To Address, Shipping Method, Price List default in the window.
Order Numbers are generated (not defaulted) based on the Order Type. A document sequence
is assigned to every Order Type so that a sales order number is generated.
The value in the Operating Unit field is defaulted based on the responsibility that is associated
to your username. The warehouse assigned (in the Others tab) defaults based on the operating
unit.
For more information on defaulting rules, please refer to Module 6.
Required fields for order lines are: Ordered Item and Quantity. Again, based on defaulting
rules and setups in Pricing, Inventory and Shipping, the other values would default on the sales
orders line. If you have entered the item, UOM and Item Description would default.
Chapter
CLASSROOM
A standard item is a finished good that is not an assembled or configured item, a service or a
component. Other item types used in orders are: Assemble to Order (ATO) models, ATO
items, Pick to Order (PTO) models, and kits.
Please note that the sales orders window is used for entering and processing returns. Returns
are processed for standard items, configured items for ATO models and option items for PTO
models.
Chapter
CLASSROOM

Processing Constraints are a security framework where you can define rules in Oracle Order
Management that validate back-end operations such as Create, Update, Delete and Cancel. For
example, you might want to change the order type on the order header, however if your order
has a status of Booked or if lines have been entered for the order, processing constraints
prevent you from updating the order type field. Similarly, you cannot perform a delete
operation on an order line if it has a status of Closed, if it is ship confirmed or invoice
interfaced. An error message is displayed explaining why you cannot perform the operation
(Create, Update, Delete or Cancel).
There are three types of processing constraints user, extensible and system. You cannot
modify system processing constraints.
Process Order API calls the processing constraints framework to validate the order entities
(headers, lines, sales credits, pricing attributes, or price adjustments) in case of create, update,
delete and cancel operations. In case of updates and delete operations, Process Order API also
checks for the values of dependant attributes and clears them or sets them to MISSING value.
Usually dependant attributes are defaulted, so defaulting rules are also called by Process Order
API during order entry.
Chapter
CLASSROOM
Defaulting Rules enable you to speed up data entry by passing values in the window based on
some key values you have entered. For example, in the order header, Ship-To Address and
Bill-To Address values default in the window once you enter the customer name or number. If
you enter an item number, the Unit of Measure and Item Description automatically default on
the order line.
Chapter
CLASSROOM

Basic Pricing is part of Oracle Order Management and Advanced Pricing is part of the Order
Management family. The pricing engine is integrated with Order Management processes and
flows. The pricing engine consists of a search engine and a calculation engine.
When you enter an item on the sales orders line, the pricing engine is called and it calculates
the price on the order line after reading it from the price list associated with the customer/order
type. The price list may contain some modifiers and qualifiers that may be applied to the base
price and the pricing engine calculates these before placing a final value in the Unit Selling
Price field in the order line.
A modifier such as a discount, surcharge or special charge may be applied to the base price and
may alter the value of the item. You can apply a modifier at the list (order) level or the line
level.
A qualifier helps you define who is eligible for a price list or modifier. A qualifier can be a
customer name, a customer class, an order type, or an order amount that can span orders.
Usually you set up a qualifier and associate it to a modifier or price list.
From the header or line, you can use Actions > View Adjustments to see the details of
modifiers that were applied automatically by the pricing engine or to apply manual discounts.
Chapter
CLASSROOM

You can view the progress of the order using the Tools > Workflow Status option. This
provides a visual representation (using the View Diagram button) of the state of the order while
it progresses through different activities like booking, awaiting shipping, pending customer
acceptance.
The Workflow engine enables you to control the processing of various order types quotes,
orders and lines, returns, sales agreements. Though seeded workflows are available with Oracle
Order Management, you can customize a flow to suit your particular business requirements.
Some examples of commonly used flows:
Order Flow Generic: This flow consists of two sub-processes, Book Order Manual and
Close Order. You can use this flow to verify that and order is booked and closed properly.
This flow is normally associated to a transaction type (which is used to setup an order type
in the sales orders window).
Order Flow Generic with Header Level Invoice Interface: When ALL of the lines of the
order are fulfilled, this flow ensures that the order is then ready to be progressed to invoice
interface.
Chapter
CLASSROOM
Line Flow Generic: When you save a line in the sales orders window, this flow initiates
to ensure that an order line is properly entered, scheduled, shipped, fulfilled, invoiced and
closed. It performs these various activities mentioned using sub-processes like Enter
Line, Schedule Line, Ship Line Manual, Fulfill, Invoice Interface Line, Close Line.
Chapter
CLASSROOM

The ATP functionality enables you to inform your customer when goods are available to fulfill
the sales order. The ATP quantity is calculated given the inputs of item, ordered quantity,
ordered quantity unit of measure, and requested date. Using these inputs and the quantity of the
item in Oracle Inventory, the Availability (ATP) window displays the quantity in the
warehouse as well as the total reservable quantity, so that you can determine how much can be
promised to the customer. The Availability window displays the date when the item will be
available. Further, if the item is in scarce supply, substitute item information is also displayed.
The order is booked when all the required fields in both the header and lines are entered and
validated and there are no error messages reported by the processing constraints framework.
The order header status changes to Booked. The workflow activity Book is reached only when
the Book Eligible activity is complete. The order could be incomplete or placed on hold and
the booking activity could be deferred. If the hold applied is a generic order level hold or a
booking specific hold, the order will not be booked.
When you click the Book button on the Quick Sales Orders window, the API OEXUBOKB.pls
checks if the order is eligible for booking. If not, it generates an error message. If it is eligible
for booking, the API calls the workflow to progress the booking activity and sets the Booked
Flag to Y.
Chapter
CLASSROOM

Based on the release criteria you specify, you can pick release order lines. These order lines
can be pick released together on a trip, stop or delivery. With pick release you can move the
items from the warehouse to the staging areas. With pick release you move the items from the
warehouse to the staging area. Along with physically moving the items, you perform a move
order transaction to record the stock movement in Inventory.
You can Pick Release using a one, two, or three-step process.
The one-step process consists of selecting the Auto Allocate box on the Inventory tab and the
Auto Pick Confirm box on the Inventory tab when you run Pick Release, which means that the
Pick Recommendation is automatically created and Pick Confirmed without any manual
intervention.
The two-step process consists of selecting Auto Allocate (not Auto Pick Confirm), which
creates a move order that is automatically detailed. It enables you to view the Pick
Recommendation and provides the opportunity to change quantity, location, and subinventory.
You can report a missing quantity at the Pick Confirmation step in the Transact Move Orders
window. Once you have made your changes, you can transact the move order to Pick Confirm
the inventory.
Chapter
CLASSROOM
The three-step process consists of selecting neither the Auto Allocate or Auto Pick Confirm
check boxes. This creates a move order whose details you can enter manually or automatically
in the Transact Move Orders window. After the details are entered, you can transact the move
order to pick confirm the transaction.
You can pick release the order using the Shipping > Release Sales Orders window to pick
release online or using a concurrent program or SRS Pick Selection List Generation SRS.
You need to specify the Release Rule Name to be able to proceed with the pick release when
using the concurrent program or SRS.
Chapter
CLASSROOM

When you need to confirm that your items have been shipped out of inventory to the customer
as a delivery, use the Ship Confirm window. Perform Run Ship Confirm to indicate that the
items are loaded onto the carrier from the staging location. When you run Ship Confirm, the
system decrements Oracle Inventory and updates the sales order line status. This information is
then transferred through AutoInvoice to Oracle Accounts Receivables for invoicing. Finally,
accounting information can be sent to the general ledger from Oracle Inventory and Oracle
Accounts Receivables.
Chapter
CLASSROOM

From a general viewpoint, AutoInvoice enables you to import various transactions like
invoices, debit memos, credit memos, on-account credits from other Oracle products (Projects,
Order Management, Service, Property Management) or non-Oracle systems like legacy
systems. You can use a SQL Loader (for non-Oracle sources) or Interface programs (for other
Oracle products) to import data into the Invoice Interface tables. Where required, tax is
calculated for the imported lines, and they are validated and passed to the Receivables tables.
AutoInvoice is a concurrent program in Oracle Receivables that performs invoice processing at
both the order and line levels. You can interface orders, returns and charges information to
Receivables to create invoices, credit memos and credits on account, recognize revenue and
manage sales credits. Once an order or line or set of lines is eligible for invoicing, the Invoice
Interface workflow activity interfaces the data to Receivables. Oracle Order Management
inserts records into the following interface tables: RA_INTERFACE_LINES and
RA_INTERFACE_SALES_CREDITS. Please note that Oracle Order Management does not
use RA_INTERFACE_ DISTRIBUTIONS because all account code creation is done by
AutoInvoice based on the AutoAccounting rules you have defined. For customer acceptance,
AR_INTERFACE_CONTS_ALL is populated for all lines that have contingencies attached to
them. This information is interfaced to Receivables for lines and discount lines.
Chapter
CLASSROOM
Use the AutoInvoice concurrent program to create invoices for the processed orders. You
cannot use AutoInvoice to create invoices for the following items:
Where the item attributes Invoice Enabled or Invoiceable Item is set to No; included item or
internal order. If you do use AutoInvoice, the Invoice Interface workflow activity is completed
with a status of Not Eligible.
If the order or lines are on hold, the order details will not be interfaced to Receivables. The
Invoice Interface workflow activity will complete with a status of On Hold. You can either
release the hold manually, or progress the workflow Actions > Progress Order in the Lines tab.
Alternatively you could wait till the hold is re-evaluated after a time period of 12 hours, in
which case if it is eligible for invoicing, the Workflow Background Process activity progresses
the lines to invoice interface.
Chapter
CLASSROOM
Order to Cash Lifecycle with PTO Models and PTO Kits

Oracle Configurator is part of the Order Management suite and is used extensively by Order
Management when orders for Assemble to Order, Pick to Order and Configure to Order
Models, Kits, Hybrid configurations and Items are required by customers.
Pick to Order model consists of:
Model bill of material with optional items and option selection rules
Pick to Order Kit consists of:
Standard bill of material with mandatory included items
Hybrid configurations consist of:
Pick-to-Order models with optional Assemble-to-Order items
Pick-to-Order model containing Assemble-to-Order model
A typical process flow for Pick to Order:
Define Model and Option Class Bills of Material and routings
Enter sales orders for models with options
Perform ATP check to find earliest possible ship date for configuration
Chapter
CLASSROOM
Order to Cash Lifecycle with PTO Models and PTO Kits
Book and schedule the order

Pick Release and Ship Confirm the PTO order
Run AutoInvoice to create an invoice for the order
Chapter
CLASSROOM
Drop Shipments
Drop shipment is a method of fulfilling sales orders by selling products without the order taker
handling, stocking, or delivering them. The seller buys a product and the supplier ships the
product directly to the sellers customer. Drop shipments are used due to the following reasons:
Customer requires an item that is not normally stocked
Customer requires a large quantity of the item which is not available with you
It is more economical when the supplier ships directly to the customer
In the diagram of the drop ship cycle, the seller receives a sales order from the customer and
sends a purchase order to the supplier. The supplier ships directly to the customer. The seller
receives an invoice from the supplier and sends an invoice to the customer.
There are three types of drop shipments:
Full Drop Shipment: The seller sends the purchase order to the supplier for the full
quantity that the customer had ordered
Normal Shipments and Partial Drop Shipment: If the seller has only part of the quantity
available for shipping to the customer, then that quantity is shipped. The user looks at the
availability for the order qty by using the ATP check and if the whole qty is not available
Chapter
CLASSROOM
Drop Shipments
Chapter
CLASSROOM
the balance qty is fulfilled using the dropship process. A purchase order is created for the
remaining quantity which the seller was not able to fulfill.
Normal Shipments and Full Drop Shipment: The seller ships some goods from inventory
to the customer, and the other goods are always shipped from an external source (supplier)
Drop shipments are created as sales orders in Order Management, indicated as drop shipments
when their Source Type is entered as External. The Purchase Release concurrent program or
workflow in Order Management creates rows in the Requisition Import tables in the
Purchasing module. Purchasings Requisition Import process creates requisitions. After the
requisition has been approved, it generates a purchase order. The Source Type is entered as
Supplier. The purchase order is sent to the supplier who then arranges for the delivery of the
items to your customer. The supplier notifies you that the items have been shipped to the
customer, via an invoice, EDI document, or an Advance Shipment Notice (ASN). In turn you
generate an invoice to be sent to the customer. Additionally when you receive confirmation of
a drop shipment or the suppliers invoice, you create a receipt for it. This creates inbound and
outbound material transactions in your system for accounting purposes.
When you receive confirmation of a drop shipment or the suppliers invoice, you create a
receipt for it. This creates inbound and outbound material transactions in your system for
accounting purposes. You can now generate an invoice to be sent to the customer.
Drop Shipments Across Ledgers

A common scenario involves manufacturing facilities in some countries, sales organizations in
others, and financial companies in several others. These entity structures allow multinational
organizations to take advantage of the benefits of each legal environment where they are
organized. They also allow companies to provide products to market quickly and profitably,
taking advantage of regional hub operations that rationalize product demand and control
supply sourcing in a centralized manner.
The ability to drop-ship goods across legal entities and ledgers is a major business requirement.
It is possible to drop ship across operating units and ledgers in Oracle Applications. The
introduction of cross-operating unit drop shipment raises the need for hybrid drop shipments
where the sales order is drop shipped to one, but not both, of the organizations involved in
executing the transaction.
You can model a drop shipment where the source of the goods is another organization. When
purchase release is run, the order line should be visible in the Procurement Organizations
purchasing system (a different operating unit using a separate ledger).
You can view customer addresses across ledgers, and legal entities support the drop ship
practices.
Chapter
CLASSROOM
Chapter
CLASSROOM
You can receive and record an Advanced Shipment Notice (ASN) to facilitate logical receipt of
the goods in the sales organization. The ASN will indicate the quantities, items, shipment
dates, and ship-to location (customer address). The ASN should be created automatically when
the procurement organization processes a logical receipt.
On the basis of internal orders (purchase and sales), intercompany receivables and payables
transactions must be recorded. The procurement organization creates an intercompany
receivables invoice for the goods, and the sales organization generates an intercompany
payables invoice. These transactions are based on prices negotiated between the two
organizations. For the intercompany accounts to stay balanced, the receivables and payables
invoices must be created simultaneously. You can set up intercompany transactions using the
Intercompany Transaction Flows window.
When you receive confirmation of a drop shipment or the suppliers invoice, you create a
receipt for it. This creates inbound and outbound material transactions in your system for
accounting purposes. You can now generate an invoice to be sent to the customer.

This flow supports the central distribution process flow. In this typical scenario, a sales order is
placed against the operating unit associated with the local sales organization, with a shipping
warehouse of the factory.
Upon shipment of the material from the factory, ownership for the material automatically
transfers through the regional distribution entity, then to the local sales organization, and
finally to the customer. In Oracle Applications, this is achieved by having the physical
shipment from the factory to the customer automatically trigger a logical shipment from the
factory to the regional distribution organization. A logical receipt is followed by a logical
shipment in the regional distribution organization, and finally a logical receipt and shipment in
the local sales organization to the customer. These transactions are accounted, but inventory
valuations in the local sales and regional distribution organization are not affected. The factory
then invoices the regional distribution entity, that invoices the local sales organization which in
turn invoices the customer. The internal invoices are done at the transfer price.
Chapter
CLASSROOM
Back-to-Back Orders
The process of creating Back-to-Back orders involves the close linking of sales orders and
purchase orders. Back-to-Back ordering is used as a replenish to order process for items that
you stock in inventory.
To create and use Back-to-Back orders, you need to ensure that the purchasing document
creation is automated, that you always have the latest status of the lines progress, and that you
can peg (or hard reserve) quantities against the order, so that the items are not allocated to
another customer.
The Auto Create Requisition process creates the requisition for the purchase order from the
sales order in Purchasing. The requisition must be identified as CTO. The purchase order is
then created automatically from the requisition and sent to the supplier. After the supplier
receives the purchase order, the items are recorded in inventory and a reservation is
automatically made against the sales order line. The sales order can then be picked, shipped,
and invoiced.
Chapter
CLASSROOM
Back-to-Back Orders
Sales Agreements
A Sales Agreement is a suppliers representation of an agreement with a customer for the
supplier to sell and the customer to buy goods or services. Usually the agreement is fulfilled by
executing multiple sales transactions over a period of time. The SA Header includes the
following:
The information that other order headers include (customer, ship to, bill to, version)
Effective dates of the SA
Payment and freight terms between the customer and supplier
Sales Agreement minimum and maximum value
Control flag to determine whether you can exceed the maximum value
Pricing Information like standard price lists, SA specific price lists
The SA line information includes the following:
Items
The minimum/maximum quantity agreed by the customer and supplier
Price including choice of price list
Effective dates
Chapter
CLASSROOM
Sales Agreements
Negotiation Agreement
A Sales Agreement can start with either the Negotiation phase or the Fulfillment phase. If the
Sales Agreement starts with the Negotiation phase, it will first follow the Negotiation flow and
then go through the Fulfillment phase.
The Sales Agreement is specified for a given time period, indicated by the Effectivity dates on
the agreement. The product/item categories are also entered in the Sales Agreement. You can
specify the minimum and maximum quantities for the booked sales order. Additionally you can
specify the minimum and maximum amount (in value) for the booked sales order. You can set
up a basic price list and enter the price for the Sales Agreement, and also set up the payment
and freight terms for the Sales Agreement.
Chapter
CLASSROOM
Negotiation Agreement
Approve Sales Agreement

You can setup Sales Agreement Types that include or do not include an approval step. Sales
Agreement Types are Transaction Types with a Sales Document Type of Sales Agreement.
The commonly used seeded Negotiation Flows are: Negotiation Flow Generic, Negotiation
Flow Generic with Approval and Negotiation Flow - Simple. Once negotiation with the
customer is complete and all necessary sales agreement information has been entered, selecting
Submit will launch the approval process and change the SA status from Draft to Pending
Internal Approval if the Sales Agreement Type has been setup with an approval step in the
process. If the Sales Agreement Type does not include an approval step, submitting the SA
will progress the SA to the status Pending Customer Acceptance.
The Sales Agreements window contains the Acceptance tab that records the customer
acceptance process. The customer and supplier information are entered here. Clicking
Customer Acceptance confirms that the Sales Agreement status changes to Customer
Accepted.
Chapter
CLASSROOM
Approve Sales Agreement
Releases Against a Sales Agreement

There are two ways that you can enter an order (release) against a Sales Agreement:
Through the Quick Sales Orders window, by directly creating a new order with the Sales
Agreement number
Through the Sales Agreement window by clicking Create Release to create a sales order
against that Sales Agreement
When you enter the Sales Agreement number, all the header information of the Sales
Agreement defaults on the order header.
After you enter the line information, you should enter the appropriate SA line number. If the
line information is valid, then the quantity is consumed from the SA line.
Note: For all this the SA should be in active status. You cannot create sales agreement releases
for SAs during the approval process.
When the Sales Agreement is created, a number of values may be entered which are later
defaulted to the release. For example: with the Enforce Price List box, you can specify whether
a price list is enforceable on the header or line of the release. When you select the Enforce
Price List box, the price list is defaulted to the release, header or line whichever is applicable,
and you cannot select another price list. Both the header and line of the Sales Agreement
Chapter
CLASSROOM
Releases Against a Sales Agreement
Chapter
CLASSROOM
incorporate these enforceable terms. Defaulting Rules need to be modified to use the SA as a
source of information to default information from the SA onto the release.
When you create an order (release) against the Sales Agreement, the system checks the
quantities and amounts entered in the lines. It then updates the quantities and amounts of the
SA line accordingly. Thus the Sales Agreement shows summary level information about the
releases against the sales agreement. The following fields are used for accumulating or
displaying the quantities and amounts:
Released Quantity
Fulfilled Quantity
Remaining Unfulfilled Quantity
Fulfilled Amount
Remaining Unfulfilled Amount
Returned Quantity
Released Amount
Returned Amount
The accumulation of the quantities and amounts occurs when the release line data is entered or
updated. When the release line is saved, the released quantity is updated at the Sales
Agreement header and line. When the release line is fulfilled, the fulfilled quantity on the SA
line is incremented. When a release line is returned and the item is received, the Returned
Quantity is incremented. The Remaining Unfulfilled Quantity may be stored or may be
calculated for display purposes. It should always equal the Ordered Quantity the Fulfilled
Quantity + the Returned Quantity.
You can terminate a Sales Agreement if it is in the fulfillment phase and if it has no open
release lines. Also when the Expiration Date is reached or when the maximum agreed quantity
or amount is reached, the Sales Agreement can be terminated. The Termination date is
defaulted to the system date. Once you terminate a Sales Agreement, you cannot reopen it and
a workflow notification is sent to the appropriate persons, informing them that the Sales
Agreement is terminated.
When a Sales Agreement is terminated and eligible for closure, it must be closed manually.
You cannot manually close an active Sales Agreement; it must be terminated, expired, or lost.
You can reopen an expired Sales Agreement.
Order to Cash Lifecycle with Customer Acceptance

In a number of countries, the accepted trading practice is that an invoice is not raised when the
goods are shipped to the customer. Invoicing is done only when the customer receives and
accepts the goods. Invoicing is done for the quantities that are finally accepted by the customer
with acceptance date being the invoice date. As a result, the revenue recognition process is also
deferred and linked to customers accepting the shipped goods. To implement this practice of
recording customer acceptance and deferring invoicing and revenue recognition, the Customer
Acceptance functionality is used.
Recording Customer Acceptance is optional in Oracle Order Management. You can enable the
Customer Acceptance functionality by setting the system parameter Enable Fulfillment
Acceptance to a value of Yes for the operating unit specified in the system parameters window.
In Oracle Order Management you can record the customers acceptance of the goods explicitly
or implicitly. With explicit acceptance you can use the Order Information Portal to accept or
reject the goods. You can open the Order Information Portal page from the Quick Sales Orders
window using the Actions > Fulfillment Acceptance option. To perform an implicit
acceptance, you need to define a deferral reason in Accounts Receivables and also run the
Implicit Acceptance Request Set (concurrent programs).
Chapter
CLASSROOM
Flow for Post-Billing Acceptance:

Enter sales orders with lines to be accepted
Progress the order book, pick release and ship confirm
The line status will be Pending Post-Billing Acceptance
View/update Acceptance related fields on the order line (Others tab folder enabled)
Line status will be Closed and the line is interfaced to Account Receivables
Perform Acceptance/Rejection explicitly using the Order Information Portal Page or
implicitly using the AR setups and the concurrent request set
View the Acceptance/Rejection on the sales orders line
Revenue Recognition takes place once the acceptance is recorded
Chapter
CLASSROOM
Flow for Pre-Billing Acceptance:

Enter sales orders with lines to be accepted
Progress the order book, pick release and ship confirm
The line status will be Pending Pre-Billing Acceptance
View/update Acceptance related fields on the order line (Others tab folder enabled)
Perform Acceptance/Rejection explicitly using the Order Information Portal Page or
implicitly using the AR setups and the concurrent request set
View the Acceptance/Rejection on the sales orders line
Line status will be Closed and the line is interfaced to Accounts Receivables
Invoice generation and Revenue Recognition happen subsequently

Pre-Billing Customer Acceptance with full explicit acceptance:
Enter and Book the order.
Pick Release and Ship Confirm the order.
Order Lines status is Pending Pre-Billing Acceptance.
Using the Order Information Portal you can mark the lines as accepted for the full quantity
shipped.
Order line proceeds to invoicing and revenue recognition. Acceptance date is passed to
AR as the invoice date.
Pre-Billing Customer Acceptance with full implicit acceptance:
Enter and book the order. Revenue Management is set up to assume acceptance if explicit
acceptance/rejection is not performed within 30 days of shipment.
Pick release and ship confirm the order.
The order line status is Pending Pre-Billing Acceptance.
30 days pass without receiving acceptance or rejection.
Chapter
CLASSROOM
Post-Billing Customer Acceptance with full explicit acceptance:

Enter and book the order.
Invoice interface the order.
Order lines status displays Pending Post-Billing Acceptance.
If you need to record the acceptance, open the Order Information Portal page and mark it
as accepted for the full quantity shipped.
Order line status is Closed.
Post-Billing Customer Acceptance with full implicit acceptance:
Enter and book the order. Revenue Management is set up to assume acceptance if explicit
acceptance/rejection is not performed within 30 days of shipment.
Invoice interface the order.
Order lines status display as Pending Post-Billing Acceptance.
30 days pass without receiving acceptance or rejection.
Acceptance is assumed. Order line closes and revenue recognition takes place.
You can query the order lines and see that an automatic acceptance was generated on the
31st day after shipping.
Chapter
CLASSROOM
Acceptance is assumed. The order proceeds to invoicing and revenue recognition.

To verify this you can query the order lines and see that an automatic acceptance was
generated on the 31st day after shipping.
Simple Negotiation in Oracle Order Management

The sales order processing incorporates the Negotiation phase. The Negotiation phase is started
when a quote is saved. It captures all the steps in the process of negotiating a quote and
converting it into an order.
Chapter
CLASSROOM
Simple Negotiation within Order Management
Querying on Prices and Availability
Chapter
CLASSROOM
Summary
Chapter
CLASSROOM

Chapter
CLASSROOM
Chapter 3
Multiple Organization Access Control Setup
Chapter
CLASSROOM
Multiple Organization Access

Control Setup

Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Organization Structure in Oracle Applications

The classifications that map an organization structure in Oracle Applications are described
below:
Business Group: This refers to the consolidated enterprise, a major division, or an operation
company and has no accounting impact. You need to have at least one business group in your
business hierarchy. Oracle Applications provides a default business group, Setup Business
Group. You can define additional business groups as required for your enterprise.
Set of Books (Ledger): A set of books is a ledger into which journal entries are entered for one
or more operating units for an organization. A set of books is created using the Set of Books
window in General Ledger. You need to specify the 3 Cs that define a set of books: Chart of
Accounts (accounting flexfield structure), Functional Currency and Financial Accounting
Calendar.
Legal Entity: A legal entity is a legal company for which you prepare tax and fiscal reports.
Operating Unit: An organization that uses Oracle subledgers, such as Oracle Cash
Management, Oracle Order Management and Shipping Execution, Oracle Payables, Oracle
Purchasing, Oracle Receivables, and related products. It may be a sales office, a division, or a
department. Operating units are associated with legal entities. Operating units are assigned to
Chapter
CLASSROOM
Organization Structure in Oracle Applications
Chapter
CLASSROOM
ledgers and a default legal context. Information is secured by operating unit for these
applications using responsibilities. Each user can access, process, and report on data only for
the operating units assigned to the MO: Operating Unit or MO: Security Profile profile option.
The MO: Operating Unit profile option only provides access to one operating unit. The MO:
Security Profile provides access to multiple operating units from a single responsibility.
Inventory Organization: An organization for which you track inventory transactions and
balances, and/or an organization that manufactures or distributes products. Examples include
(but are not limited to) manufacturing plants, warehouses, distribution centers, and sales
offices. The following applications secure information by inventory organization: Oracle
Inventory, Bills of Material, Engineering, Work in Process, Master Scheduling/MRP, Capacity,
and Purchasing receiving functions. To run any of these applications, you must choose an
organization that has been classified as an inventory organization.
Subinventory: Subinventories are unique physical or logical separations of material inventory,
such as raw inventory, finished goods, or defective material. All material within an
organization is held in a subinventory therefore, you must define at least one subinventory.
Multi-Org Access Control (MOAC)

MOAC addresses the need to secure data to users that have access to specific operating units
that are assigned to them. It provides the ability to access and process transactions for multiple
operating units under one responsibility. Some key aspects of MOAC:
Multiple Organizations in a single installation: You can define various organizations within a
single installation of Oracle Applications. These organizations can be business groups, legal
entities, operating units, inventory organizations.
Secure Access: You can assign many operating units to a single responsibility using the
security profile MO: Security Profile that is set at site level or responsibility level. You should
have assigned multiple operating units to the security profile so that the responsibility can
access data only in these assigned multiple operating units.
Responsibility determines access to operating unit or units: If MOAC is not enabled, you can
implement security at the operating unit level through the MO: Operating Unit profile option
called, which is set at the site, responsibility or user level. If MOAC is enabled, you can
implement security at the operating unit level using the MO: Default Operating Unit and MO:
Security Profile profile options.
Chapter
CLASSROOM
Multi-Org Access Control (MOAC)
All tables in Purchasing, Payables, Order Management, and Receivables, except vendors and
customers tables, contain an ORG_ID column. When you open a window in these applications,
you are actually looking at a view of the underlying table. The window will show only those
records where the value in the ORG_ID (operating unit) column corresponds to the value of the
profile option for the responsibility you are logged in with.
Inventory Organization Access: You can specify the inventory organizations that are available
to users in each responsibility. The Change Organization window automatically limits
available inventory organizations to those authorized for the current responsibility.
Chapter
CLASSROOM
Using MOAC in Oracle Order Management

Setup windows that have the Operating Unit field: Approvals, Transaction Types, Payment
Types, System Parameters, Shipping Tolerances.
Transaction windows that have the Operating Unit field: Sales Orders, Quick Sales Orders,
(Order Import) Corrections, Pricing and Availability, Processing Messages, Order Organizer,
Retrobilling Organizer, Audit History, Create Hold Sources, Release Holds, Sales Agreements,
Scheduling Organizer, Order Information Portal (HTML pages).
The Operating Unit field is a required field in the above windows. When the window opens,
the Operating Unit field gets its value from the profile option MO: Default Operating Unit,
however it displays as an LOV, so that you can select a different operating unit other than the
default if needed. The Operating Unit field is always displayed in the windows that are not
folder enabled (Transaction Type, System Parameters). The operating unit field is a hidden
field on all folder enabled windows and you can select to display this field in windows like
Sales Order, Quick Sales Orders. When MOAC is enabled, the value of the operating unit
populates from the MO: Default Operating Unit profile option. If you change the value of the
operating unit in the form, the value of the operating unit comes from the MO: Security Profile.
Chapter
CLASSROOM
Using MOAC in Oracle Order Management
Chapter
CLASSROOM
After entering other information in the window, if you change the operating unit, a message is
displayed indicating that all the fields will be cleared if the operating unit is changed.
You can query in these windows using operating unit as one of the search criteria. If the
operating unit is specified as one of the search criteria, the search results will display only that
data which is from the specified operating unit. If no operating unit is specified, then the search
results will retrieve all the relevant data from all the operating units that the responsibility with
which you logged in has access to.
The Operating Unit parameter is optional in Process Order Public API. You can call the
Process Order Public API, Get Order API and Lock Order API for any of the Operating Units
that you have access to, by specifying an Operating Unit value as a parameter.
For batch processes like Order Import or High Volume Order Import, EDI/XML, the interface
tables also have an Operating Unit field. If no value is specified in the fields, then Order
Import/High Volume Order Import will attempt to process those records for the default
operating unit. In these concurrent programs (Order Import or High Volume Order Import) you
can also set the value of the hidden parameter Process Orders with no Org Specified as
required.
Oracle Order Management concurrent requests are single-org, multi-org or global. For singleorg requests, the Operating Unit parameter is a required field and is populated with the default
operating unit. If you need to run the request for multiple orgs, leave the optional Operating
Unit parameters field blank. Some concurrent programs are classified as global, you can run
them across all operating units. In such programs, the Operating Unit parameter field is
disabled. Similarly, reports can be run for a single org or globally (across operating units).
Defaulting of the operating unit value takes place in the following manner: When MOAC is
enabled, the value of the operating unit for the MO: Security profile option is defaulted based
on the system profile option MO: Default Operating Unit. When MOAC is not enabled, the
value of the operating unit is the default for MO: Operating Unit profile option. For more
details on MOAC in Oracle Order Management, please refer to the Oracle Order Management
Users Guide and Oracle Order Management Implementation Manual.
Setting up MOAC
There are various operating unit security scenarios that can exist in an enterprise:
There is only one Operating Unit.
There are multiple Operating Units, but users have access to only one Operating Unit.
There are multiple Operating Units, and users have access to some of the Operating Units.
There are multiple Operating Units, and users have access to all Operating Units.
1. Define Organizations and Relationships: Use the HR responsibility to create organizations
(N) HRMS Management > Work Structures > Organization > Description.
2. Assign Responsibilities: Use the System Administrator responsibility to assign
responsibilities to your user (N) Security > Users > Define.
3. Define Organization Hierarchy (optional): Use the HR responsibility to create a hierarchy
for the organizations that you have created. In addition to a primary reporting hierarchy
used in HR, you can define multiple hierarchies for matrix management, reporting, and for
security.
Chapter
CLASSROOM
Setting Up MOAC
Chapter
CLASSROOM
4. Define Security Profile: Use the HR responsibility to define a security profile (N) HRMS
Management > Security > Profile. You can either define security profiles based on an
organization hierarchy or a list of organizations.
5. Run Security List Maintenance concurrent request: This concurrent program builds a list of
operating units that are associated with the security profile. The list is available so that it
can be used and validated by other module APIs.
6. Set the Security Profile option for each Responsibility: Once the security profiles are
created, you can assign the values to the MO: Security Profile option at the responsibility
level. Use the System Administrator responsibility for this (N) Profile > System.
7. Setup a default operating unit: Use the profile option MO: Default Operating Unit to
default the operating unit in various windows. You can set the profile option at the
responsibility or user level.
8. Run the Setup Validation Report: Use the System Administrator responsibility to check for
any setup-related issues that might have occurred during MOAC setup. The report
parameters are:
Active Responsibilities Only: Select Yes or No to validate only the active
responsibilities on the report. The default value is Yes.
Correct Customer Attributes: Select Yes or No to correct the customer attributes. If
you choose Yes, the report deletes the operating unit-specific data from the
Customer records. The default value is No.
Correct Supplier Attributes: Select Yes or No to correct the supplier attributes. If you
choose Yes, the report deletes the operating unit-specific data from the supplier
records. The default value is No.
For more information on setting up MOAC, please refer to the Oracle Applications Multiple
Organizations Implementation Guide.
Summary
Chapter
CLASSROOM

Chapter
CLASSROOM
Chapter 4
Oracle Inventory Setup for Oracle Order Management
Chapter
CLASSROOM
Oracle Inventory Setup for

Oracle Order Management

Chapter
CLASSROOM
Chapter
CLASSROOM
Objective
Chapter
CLASSROOM
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
Chapter
CLASSROOM
Overview
Receipt to Issue Lifecycle

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.
Chapter
CLASSROOM
Receipt to Issue Lifecycle
Inventory Organizations
An inventory organization is a facility where you store and transact items. When you
implement 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:
Its own location, ledger, costing method, workday calendar, and items.
Share one or more of these characteristics with other organizations.
Chapter
CLASSROOM
Inventory Organizations
Setting Up Locations
Locations define information that describe the physical locations of employees and
organizations. Locations are shared between Oracle Inventory, Oracle Purchasing, Oracle
Human Resource Management Systems, Oracle Order Management, and Oracle Shipping
Execution. 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.
Chapter
CLASSROOM
Setting Up Locations
Inventory Organization Structure

An inventory organization may have one or more subinventories. Subinventories are unique
physical or logical separations of material inventory, such as raw material, finished goods, or
defective goods. All material within an organization is stored in a subinventory. You must
define at least one subinventory for every organization.
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.
Chapter
CLASSROOM
Inventory Organization Structure
Subinventories may consist of one or more locators. You use locators to identify physical areas
within subinventories where you store inventory items. You can track items by locator and
restrict items to a specific locator. Locator control is optional in Oracle Inventory.
Chapter
CLASSROOM
Sample Inventory Organization
Chapter
CLASSROOM
Sample Inventory Organization
Interorganization Shipping Networks

An interorganization shipping network describes the relationships and accounting information
between a shipping organization and a destination organization. You must define a shipping
network between two organizations before you can transfer material between organizations.
When you setup a shipping network you must select a transfer type. The choices are intransit or
direct. If you choose intransit, then Oracle Inventory moves material to an intermediary state
before it reaches the destination organization, and a receipt transaction is required in the
destination organization once the material arrives in order to retrieve it. If you choose direct,
Oracle Inventory moves the material directly to the destination organization. For both however,
you can determine default receipt routing and whether internal orders are required to transfer
material.
If you choose intransit as the transfer type you can determine:
Shipping methods
GL accounts to use in transit
Material ownership during transfers
Planning lead-times
Transfer charges
Chapter
CLASSROOM
Interorganization Shipping Networks
For more information see Interorganization Shipping Networks, Oracle Inventory Users
Guide.
Chapter
CLASSROOM
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.
Chapter
CLASSROOM
Shipping Method
Units 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. If an item is under dual unit of measure control, then the system tracks on-hand quantity
based on both the primary and secondary units of measure. 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.
Chapter
CLASSROOM
Units of Measure
Uses of Units of Measure

Planning Products
- Forecasting and consumption
- Master scheduling
- Material requirements planning
Work in Process
- Shop floor moves
- Resource transaction
- Completion and return transactions
- Inquiries and reports
Bills of Material and Engineering
- Defining bills of material
- Defining engineering items
Chapter
CLASSROOM
Uses of Units of Measure
Unit of Measure Class

Unit of measure classes represent groups of units of measure with similar characteristics. A
unit of measure class contains a base unit of measure. You use the base unit of measure to
perform conversions between units of measure in the class. For this reason, the base unit of
measure should represent the other units of measure in the class, and be one of the smaller
units. For example, quantity is a unit of measure class and each, dozen, and gross are examples
of units of measure within the class. The unit of measure each is the base unit of measure for
this class.
Chapter
CLASSROOM
Unit of Measure Class
Unit of Measure Conversions

A unit of measure conversion is a mathematical relationship between two different units of
measure. For example, 16 ounces = 1 pound, or 2.2 pounds = 1 kilogram. If you want to
transact items in units of measure belonging to classes other than their primary UOM class,
you must define conversions between the base units of measure in different UOM classes.
Chapter
CLASSROOM
Unit of Measure Conversions
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.
Chapter
CLASSROOM
What is an Item?
Steps to Setup, Define, and Maintain Items

The following are the steps for creating and maintaining items:
Define Inventory organization.
Create the item templates.
Use the templates or existing items to define items.
Enter values for additional item attributes.
Assign a status to the item.
Enable the item in organizations.
Update the organizational-level attributes values.
Assign categories to the item (optional)
Assign items to catalog groups (optional)
Define item relationships (optional)
Delete items (optional)
Chapter
CLASSROOM
Steps to Setup, Define, and Maintain Items
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.
Chapter
CLASSROOM
Defining Items
Defining Items
Chapter
CLASSROOM
Item Master Organization

An item master organization is a logical entity that you use to define items. You use the other
organizations to store and transact inventory. After you define an item in the item master, you
can assign it to any number of other organizations.
There is no functional or technical difference between the item master organization and other
organizations; however, it is recommended that you limit the item master to an item definition
organization.
You should also define one item master organization per Oracle Inventory implementation.
You can use the same item master for child organizations across different ledgers. Item masters
are distinct entities with no relationship to each other. You cannot associate items in one item
master organization with another item master organization. You cannot copy items across item
master organizations.
Defining the Item Master Organization
You create the item master organization in the same way that you create other inventory
organizations.
You use the Organization window to create the item master organization
Use the Organization Parameters window to specify the organization as the Item Master.
Chapter
CLASSROOM
Item Master Organization
You assign child organizations to the item master organization.

- Note that the item master uses itself as its item master.
Chapter
CLASSROOM
Item Validation Organization

The item validation organization contains all the items that you sell to customers. You set the
Item Validation Organization parameter in the Parameters window. You must set assign an
item validation organization for each operating unit. You must also define all transactable
items in the item validation organization. Typically, you set the item master organization as the
item validation organization for each operating unit; however, you can set it to any
organization within the operating unit.
Chapter
CLASSROOM
Item Attributes
Item attributes are the collection of information about an item.
Chapter
CLASSROOM
Item Attributes
Unit of Measure Attributes

You use the units of measure attributes to track items in the warehouse. The following are the
unit of measure attributes and their definitions:
Primary Unit of Measure: This is the stocking and selling unit of measure. Any
necessary conversions are based on this unit of measure. The primary unit of measure is
the default for invoices and credit memos entered in Oracle Receivables.
Tracking: The system can track the item in either the primary only or the primary and
secondary unit of measure. If the system tracks the item by the primary and secondary unit
of measure this is called dual unit of measure control.
Pricing: This attribute controls if pricing is based on the primary or secondary unit of
measure
Defaulting: This attribute controls the behavior of dual unit of measure controlled items.
- Fixed: The system stores inventory in both the primary and secondary units of
measure. You can enter an item quantity in one unit of measure, and the system
converts the quantity to the secondary unit of measure and displays both quantities
- Default: The system stores inventory in both the primary and secondary units of
measure. You can enter an item quantity in one unit of measure, and the system
Chapter
CLASSROOM
Unit of Measure Attributes
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.
Chapter
CLASSROOM
Order Management Item Attributes

The following item attributes are specific to Oracle Order Management.
Customer Ordered: You use this attribute to indicate whether an item can be ordered by
external customers. You can add any customer orderable items to price lists in Oracle Order
Management. If you enable this attribute, you can temporarily exclude an item from being
ordered by turning disabling Customer Orders Enabled.
Customer Orders Enabled: You use this attribute to indicate whether a customer can
currently order an item. If you enable this attribute, then you can specify the item in the Sales
Orders window in Oracle Order Management. You can initially define an item with Customer
Ordered Item enabled and Customer Orders Enabled disabled. Consequently, you can define
prices for the item, but you cannot place an order for the item.
Shippable: You use this item attribute to Indicate whether you can ship an item to a customer.
Oracle Shipping Execution uses the pick release program to make these items available for
shipping. A warning is issued if you change the value of this attribute when open sales order
lines exist.
OE Transactable: You use this attribute to indicate whether Oracle Order Management can
place demand for an item. If you enable Shippable, then you usually enable OE Transactable.
Chapter
CLASSROOM
Chapter
CLASSROOM
For items you do not ship, you may still want to enable OE Transactable if you use the items in
forecasting or planning. The system issues a warning if you change the value of this attribute
when open sales order lines exist for the item. You cannot disable this attribute if demand
exists.
Pick Components: You use this item attribute to indicate whether an item has a bill of
material with options, classes, or included items picked from finished goods inventory. You
must enable this item attribute for pick-to-order items. You must disable this item attribute for
assemble-to-order items and items without a bill of material.
Ship Model Complete: You use this item attribute to indicate whether any configuration
derived from this model can ship only when all required quantities of all configuration
components (options or included items) are available. If you enable this attribute, then the Pick
Components attribute and the profile option OE: Reservations must be Yes; and the BOM
Item Type attribute can be Model or Standard.
Returnable: You use this item attribute to indicate whether customers can return an item. If an
item is returnable, you can enter it on the Returns window in Oracle Order Management. Order
Management uses this item attribute with the item attributes Stockable and Transactable to
determine which authorized returned items you can physically receive into inventory.
RMA Inspection Required: You use this item attribute to indicate whether to require an
inspection on returned items.
Financing Allowed: You use this item attribute to indicate if a customer can finance an item.
Shipping Subinventory: You this item attribute to determine the default subinventory for
shipping.
Default Shipping Organization: This is the primary shipping organization for the item. This
organization appears on the Enter Orders window if the item is the source attribute of the
warehouse object in the standard value rule set for the order. This organization appears on the
Enter Returns window if a receiving warehouse is not defined on the customer or order type.
Order Management Item Attributes (cont.)

Check ATP: You use this item attribute to indicate whether to check available to promise or
capable to promise information when placing demand.
ATP Rule: You use this item attribute to indicate an available to promise (ATP) rule. ATP
rules define supply and demand sources, time-fence parameters, and available-to-promise
calculation methods.
ATP Components: You use this item attribute to indicate whether to perform available to
promise checking for components in the bill of material for ATO and PTO items. These
components are included in ATP checking if Check ATP is enabled.
Picking Rule: This item attribute determines the order in which subinventories, locators, lots,
and revisions are picked. This rule will not be employed in Oracle Warehouse Managementenabled organizations.
Default SO Source Type: You use this item attribute to indicate if an item is to be drop
shipped. If the value is internal, the item will not be drop shipped. If the value is external, then
the item will be drop shipped.
Charge Periodicity: This is the the time the system uses to price a persistent or recurring
service or product. The system derives the list of values for this attribute from the profile
Chapter
CLASSROOM
option OM: UOM Class for Charge Periodicity. Each unit of measure (UOM) in this class is a
periodicity value. An item has only one periodicity value, and the default value is null.
Over Shipment: This item attribute determines the amount of the shipment you can exceed at
the time of ship confirmation.
Under Shipment: This item attribute determines the amount of the shipment you can ship
below at the time of ship confirmation.
Over Return: This item attribute determines the amount of the shipment you can exceed at the
time of receiving or receipt creation.
Under Return: This item attribute determines the lower limit of the received quantity to be
considered as full receipt.
Chapter
CLASSROOM
Item Validation
Oracle Order Management derives the value of item attributes from two different sources: the
item validation organization and the shipping organization. Oracle Order Management uses
item attributes internally or on the sales order line. It categorizes item attributes as only source
and default source.
Only Source
- Assemble to Order
- BOM Item Type
- Build in WIP
- Customer Orders Enabled*
- Inventory Item
- Internal Orders Enabled*
- Pick Components
- Primary Unit of Measure
- Ship Model Complete
Chapter
CLASSROOM
Item Validation
Chapter
CLASSROOM
- Serviceable Product Flag

- Service Item Flag
Default Source
- Accounting Rule
- Default Shipping Organization
- Invoicing Rule
- Over Shipment Tolerance
- Under Shipment Tolerance
- Over Return Tolerance
- Under Return Tolerance
- Payment Terms
- Tax Code
* - Also validated in the Shipping Warehouse.
Shipping Warehouse
Only Source
- ATP Components
- ATP Rule
- Check ATP
- Customer Orders Enabled
- Internal Orders Enabled
- Invoice Enabled**
- Invoiceable Item**
- Lot Control
- Purchasable Flag
- Reservations Control
- Returnable
- Revision Control
- Shippable
- Serial Number Control
- Stock Locator Control
- Stockable
- Subinventory Restrictions
- Transactable
- Pricing
- Tracking
- Secondary UOM Code
** - If you do not specify the shipping warehouse on the sales order line, then these attributes
default from the item validation organization.
Default Source
Chapter
CLASSROOM
- Charge Periodicity
- COGS Account
- Default SO Source Type
Bill of Material Item Attributes
- Mutually Exclusive
- Optional
- Include on Shipping Documents
- Required for Revenue
- Required to Ship
Note: All bill of material item attributes are taken from the organization specified in the item
validation organization.
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.
Chapter
CLASSROOM
Item Status
Item Statuses and Attributes

You define an item status by selecting the value check boxes for the status attribute. You can
control status attributes and item status at the item level or organization level.
Chapter
CLASSROOM
Item Statuses and Attributes
Organization Assignment and Organization Items

You can enable an item in all child organizations under your master organization or choose
child organizations where you use the item. Oracle Inventory propagates the item to all
organizations in which you want to enable it. You can enter or change organization-controlled
item attributes. For example, you can choose reorder point planning in one organization and
min-max planning in another organization for the same item.
Chapter
CLASSROOM
Organization Assignment and Organization Items
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 in
one organization, you want the same item to become not transactable in the other organization.
Chapter
CLASSROOM
Control Levels
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.
Chapter
CLASSROOM
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.
Chapter
CLASSROOM
Item Relationships
Customer Items
A customer item is an alternate name assigned to an item that is specific to a customer site.
You use the Customer Item window to define customer items. You can also create cross
references between customer items and internal system item numbers.
Chapter
CLASSROOM
Customer Items
What are Supply and Demand?
Chapter
CLASSROOM
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. The ATP process checks the existing supply and demand to determine
availability. For example, if you have 100 units of on-hand quantity on Monday, 100 units that
you expect to receive on Tuesday, and 100 new orders that you plan to produce on Wednesday,
the available to promise on Monday is 100, on Tuesday is 200, and on Wednesday is 300.
Capable to Promise
Capable to Promise is the process of committing orders against available capacity and available
inventory. For example 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 quantity make
it 200 units or see if there is enough capacity and upstream components to make, procure, or
transfer 100 additional units to make the availability for Monday.
Chapter
CLASSROOM
Available to Promise
Uses of ATP in Oracle Inventory

You can view the earliest available date for a specific quantity of an item or a group of
items and the available quantity of an item for a specific date.
You can view the supply, demand, and ATP item quantities for the periods that fall
between the current date and the end of the ATP horizon.
Chapter
CLASSROOM
Uses of ATP in Oracle Inventory
Defining an ATP Rule

Navigation Path
Inventory Responsibility (N) Setup > Rules > Available to Promise
You can use the following equation to calculate the ATP quantity for each supply period.
Period ATP = (period supply) (period demand)
Chapter
CLASSROOM
Defining an ATP Rule
Implementation Considerations
You should set all costing attributes at the organizational level because costing is most
commonly done at organizational level. 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 ledger, 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
Weighted
Average
FIFO
LIFO
Chapter
CLASSROOM
Implementation Considerations
Summary
Chapter
CLASSROOM
Chapter 5
Oracle Receivables Setup for Oracle Order Management
Chapter
CLASSROOM
Oracle Receivables Setup for


Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Overview of Trading Community Architecture

Order Management integrates with Oracle Trading Community Architecture to access
customer setup information, including party data, account information, account sites,
relationships and contacts. Many attributes of importance to Order Management, such as
preferred warehouse, preferred order type, set preferences, price list and many others, are
stored in the TCA data model at the account and account site level and are used by Order
Management as defaulting sources.
In addition, Order Management, through the Add Customer functionality, enables you to input
new customer accounts, addresses, and contacts. This data is pushed to the TCA schema, using
TCA APIs. Add Customer functions can also be performed through Order Import in Oracle
Order Management.
Trading Community enables you to:
Separate entities you enter into a relationship with, from the business relationship itself
Provide a common location entity that can be shared, enabling greater optimization for
distributed planning
Maintain businesses and people as different entity types
Enables multiple customer relationships to be established for one common entity
Chapter
CLASSROOM
Overview of Trading Community Architecture
Key Customer Related Concepts in TCA

Parties
Entities of type Person or Organization that can enter into business relationships. Parties can
also be of type Relationship. For example, Joe as himself is a party of type Person, but Joe as a
contact for Vision Corporation is a party of type Relationship. Every party in the TCA Registry
has a unique Registry ID.
TCA includes an extensive variety of information for parties, for example party name,
addresses, contacts, and contact points. Joe as a person can have a personal phone number that
differs from the phone number for the relationship of Joe as a contact.
Party sites
Addresses that parties use for specific purposes, or uses.
Customers
Parties with whom you have a selling relationship.
Customer accounts
The business relationships between you and your customers.
Chapter
CLASSROOM
Key Customer Related Concepts in TCA
Chapter
CLASSROOM
Note: Order Management operates at the account level only, that is, party information is not
displayed in the user interface. Further, party identification is not entered through any
windows. Parties are created in the background when accounts are saved.
Customer account sites
Party sites used in the context of customer accounts for specific purposes, or uses, for example
ship-to and bill-to account sites.
Locations
Geospatial points, usually defined by an address.
Contacts
People who have a contact or employment relationship with an organization or person.
Contact points
Means of contact, for example, phone and e-mail address.
TCA also includes conceptual functionality that helps you manage and understand your trading
community. For example, you can use relationships to model the roles that parties play with
respect to one another, and classifications to classify entities.
Adding Customers in Order Management

(N) Order Management > Customers > Standard
Oracle Order Management enables you to add customers and update existing customers
through the use of the Customers page. TCA APIs and the profile option OM: Add Customer
are used to enable customer definition in Order Management.
OM: Add Customer: This profile option determines which users can access the Order
Management Customer window to enter customers, customer addresses, and customer
contact information. Select from:
- All: Users can create new customers, customer addresses, and customer contacts.
- None: User cannot create new customers, customer addresses, and customer contacts.
- Address and Contact only: Users can access the Add Customer window to create both
new customer addresses and/or customer contacts for existing customers only
The default for this profile option is None.
TCA APIs: The TCA Data Sharing and Security (DSS) feature enables you to define rules
that determine who can create, update or delete customer data. For more information see
the Oracle Trading Community Architecture Administration Guide.
Chapter
CLASSROOM
Adding Customers in Order Management
Defining Payment Terms

(N) Receivables > Setup > Transactions > Payments Terms
Oracle Receivables enables you to define standard payment terms for your customers to
specify the due date and discount date for their open items. Payment terms can include a
discount percent for early payment and you can assign multiple discounts to each payment
term line. For example, the payment term 2% 10, Net 30 indicates that a customer is allowed a
two percent discount if payment is received within 10 days; after 10 days, the entire balance is
due within 30 days of the transaction date with no applicable discount.
Receivables displays the active payment terms you define as list of values choices in the
Customers, Customer Profile Classes, and Transactions windows.
Defining payment terms includes defining a unique name and description, as well as enabling
or disabling options such as credit check and billing cycle.
Chapter
CLASSROOM
Defining Payment Terms
Defining Invoicing and Accounting Rules

(N) Order Management > Setup > Transaction Types > Define
Within the Transaction Types window, Finance tab, you define the following:
Invoicing Rule: Order Management assigns standard invoicing rules to standard lines for
orders that you import through AutoInvoice. Invoicing rules are either Advance Invoice or
Arrears Invoice.
Accounting Rule: Accounting rules create revenue recognition schedules for your
invoices. They determine the number of periods and percentage of total revenue to record
in each accounting period. Accounting rules are used with transactions that you import
into Receivables using AutoInvoice and with invoices that you create manually in the
Transaction windows.
Chapter
CLASSROOM
Defining Invoicing and Accounting Rules
Defining Auto-Accounting Parameters

(N) Receivables > Setup > Transactions > AutoAccounting
You set up AutoAccounting to create account segments based on inventory items and
warehouse. For example, define the Product segment of your Revenue account to use Standard
Lines and specify a warehouse name when entering transaction lines.
Defining Auto-Accounting parameters includes the following:
Operating Unit: Select the operating unit from the list of values.
Type: Select from the following:
- AutoInvoice Clearing: AutoInvoice uses the AutoInvoice Clearing account for your
imported transactions. Receivables uses the AutoInvoice clearing account to store any
differences between the specified revenue amount and the price times the quantity for
imported invoice lines.
- Bills Receivable: AutoAccounting uses this value if you derive the Bills Receivable
account from the transaction drawee site.
- Factored Bills Receivable: AutoAccounting uses this value if you derive the Factored
Bills Receivable account from the transaction drawee site.
Chapter
CLASSROOM
Defining Auto-Accounting Parameters
Chapter
CLASSROOM
- Freight: The freight account controls the account in your general ledger to which you
post your freight amounts. You can use constant, customer bill-to site, salesperson,
transaction type, and standard item values to specify your freight account.
- Receivable: AutoAccounting uses this value if you derive the Receivable account
from the transaction bill-to site.
- Remitted Bills Receivable: AutoAccounting uses this value if you derive the
Remitted Bills Receivable account from the transaction drawee site. You can enter a
value in this field only if the business purpose for this address is Drawee.
- Revenue: The revenue account controls the account in your general ledger to which
you post your revenue amounts. You can use transaction types, customer bill-to sites,
standard items, salespeople, and constant values to specify your revenue account.
- Tax: The tax account controls the account in your general ledger to which you post
your tax amounts. You can use information from your tax codes, customer bill-to site,
salesperson, transaction type, standard item, and constant values to specify your tax
account.
- Unbilled Receivable: Receivables uses the unbilled receivable account for
transactions that have invoicing and accounting rules. If your accounting rule
recognizes revenue before your invoicing rule bills it, Receivables posts this amount
to your unbilled receivable account.
- Unearned Revenue: Receivables uses the unearned revenue account for transactions
that have invoicing and accounting rules. If your accounting rule recognizes revenue
after your invoicing rule bills it, Receivables posts this amount to your unearned
revenue account.
- Unpaid Bills Receivable: AutoAccounting uses this value if you derive the Unpaid
Bills Receivable account from the transaction drawee site. You can enter a value in
this field only if the business purpose for this address is Drawee.
Segment: Segment names in your Accounting Flexfield Structure are automatically
populated when you select an AutoAccounting Type.
Table Name: Receivables enables you to use different table names for different accounts.
Select one of the following table names:
- Bill To Site: Used to determine this segment of your revenue, freight, receivable,
AutoInvoice clearing, tax, unbilled receivable, and unearned revenue account.
- Site: Used to determine this segment of your bills receivable, factored bills
receivable, remitted bills receivable, and unpaid bills receivable account.
- Remittance Banks: Used to determine this segment of your factored bills receivable
and remitted bills receivable account.
- Salesreps: Used to determine this segment of your revenue, freight, receivable,
AutoInvoice clearing, tax, unbilled receivable, and unearned revenue account. If you
choose this option for your AutoInvoice clearing, tax, or unearned revenue accounts,
then Oracle Receivables uses the revenue account associated with this salesperson. If
you choose this option for your unbilled receivable account, then Oracle Receivables
uses the receivable account associated with this salesperson. If the transaction has a
line type of LINE with an inventory item of freight (FRT), then AutoAccounting uses
the accounting rules for the freight type account rather than the revenue type account.
Chapter
CLASSROOM
- Standard Lines: Used to determine this segment of your revenue, AutoInvoice

clearing, freight, tax, unbilled receivable, and unearned revenue account. If you
choose this option for your AutoInvoice clearing, freight, tax, unbilled receivable or
unearned revenue accounts, then Oracle Receivables uses the revenue account
associated to this standard memo line item or inventory item. If the transaction has a
line type of LINE with an inventory item of freight (FRT), then AutoAccounting uses
the accounting rules for the freight type account rather than the revenue type account.
- Taxes: Used to use tax codes when determining your tax account.
- Transaction Types: Used to determine this segment of your revenue, freight,
receivable, AutoInvoice clearing, tax, unbilled receivable, and unearned revenue
account, and of your bills receivable, factored bills receivable, remitted bills
receivable, and unpaid bills receivable account. If the transaction has a line type of
LINE with an inventory item of freight (FRT), then AutoAccounting uses the
accounting rules for the freight type account rather than the revenue type account.
Constant: Constant value is used if you want AutoAccounting to use the same value at all
times for this Accounting Flexfield segment. If you do not select a Table, then select a
Constant using the list of values.
Defining Territories in Receivables

(N) Receivables > Setup > Transactions > Territories
Within Oracle Receivables, you define territories and can define multiple customer territory
combinations. You can assign territories to your customers, salespeople, invoices, and
commitments. For example, you can divide your industry class into different types of
businesses and your regions into North, South, East, and West to evaluate growth by location.
The Territories window consists of the following:
Name: A unique name for your territory.
Description: A description of your territory.
Flexfield: Enter a flexfield for your territory.
Active: Enable this check box to activate the territory.
Effective Dates: Enter the start and (optionally) the end date for this territory.
Chapter
CLASSROOM
Defining Territories in Receivables
Defining Batch Sources Automatic Transaction Numbering

(N) Receivables > Setup > Transactions > Sources
Batch sources control the standard transaction type assigned to a transaction and determine
whether Receivables automatically numbers your transactions and transaction batches. Active
transaction batch sources appear as list of values choices in the Transactions, Transactions
Summary, and Credit Transactions windows, and for bills receivable in the Bills Receivable
and Bills Receivable Transaction Batches windows.
Note: A batch source provides default information, which you can optionally change at the
transaction level.
Automatic Transaction Numbering is defined on the Transaction Sources window by enabling
the check box.
Note: For bills receivable transaction batch sources, you must use the Automatic Transaction
Numbering box and Last Number field to number bills receivable generated automatically.
Note: To avoid conflict, ensure that the profile option OM: Invoice Numbering Method is set
to Automatic, even though the Auto Numbering check box is enabled in the Invoice Source.
Chapter
CLASSROOM
Defining Invoice Sources (Batch Source) Automatic Transaction

Numbering
Chapter
CLASSROOM
After you define the Invoice Source, it must be assigned to a system parameter or at OM
transaction type level.
To assigning invoice source at the system parameter level:
(N) Setup > System Parameters > Values
If the invoice source referred for invoice auto-numbering to generate invoices with similar
numbering pattern at operating unit level (e.g., Vision Operations), then it is set at the system
parameter level. The defined Invoice source is assigned under the invoicing parameter of the
system parameter.
To assign invoice source at the OM Header/Line Transaction Type level:
(N) Setup > Transaction Type > Define
If the invoice source is referred for invoice auto - numbering at transaction level, then it is
assigned under the Finance tab of the Transaction Type window.
An invoice source assigned at line transaction type level has maximum precedence, followed
by header transaction type, then at the system parameter level.
A Receivables Transaction Type is defined and assigned at the system parameter or transaction
type level for autoinvoice creation.
To define and assign a receivables transaction type:
Define the transaction type: (N) Receivables > Setup > Transactions > Transaction Types
Assign the transaction type to the system parameter: If the invoice transaction type is
referred for autoinvoice generation at the operating unit level (e.g., Vision Operations),
then it is set at the system parameter level. The defined Invoice Transaction Type is
assigned under invoicing parameter of the system parameter. (N) Setup > System
Parameters > Values
Assign the transaction type to the order header/line transaction type: If the Invoice/
Receivables transaction type is referred for AutoInvoice generation, then it is assigned
under the Finance tab of the transaction type. (N) Setup > Transaction Type > Define
Invoice Transaction Type assigned at Line Transaction Type level has maximum
precedence followed by Header Transaction Type, then at the system parameter level.
Define Salespersons to Assign Sales Credit

(N) Order Management > Setup > Sales > Salespersons
You set up your salespersons and assign sales territories using the Resource window. You can
define multiple salespersons to which you can assign sales credits when entering invoices. If
AutoAccounting depends on salesperson, Receivables uses the general ledger accounts that
you enter here in combination with your AutoAccounting rules to determine the default
revenue, freight, and receivable accounts for your invoices.
If the system option Require Salesperson is set to Yes, and no salesperson is defined at the billto, ship-to, or customer level, then No Sales Credit is the default for the Salesperson field when
you enter transactions.
Note: If AutoAccounting is based on salesperson, then you must query the No Sales Credit
record in the Resource window and enter revenue, freight, and receivable accounting
information. These accounts are required when creating a debit memo reversal or when
entering transactions with No Sales Credit.
Active salespersons appear in the list of values in the Transaction and Customers windows.
You can make a salesperson inactive by specifying an end date for this salesperson.
The Salesperson field, within the Sales Orders window, is a required field.
Chapter
CLASSROOM
Define Salespersons to Assign Sales Credit
Using the Resources Window to Create a Salesperson

(N) Order Management > Setup > Sales > Salespersons
Salespersons are defined by searching for the Resource Name or Number then navigating to
the Receivables tab and completing the following:
Operating Unit: Use the list of values to select the appropriate operating unit.
Salesperson Number: Enter the number that will represent this salesperson.
Sales Credit Type: Use the list of values to select the sales credit type.
Start Date End Date: Enter a start date for the salesperson and optionally enter an end
date.
Territory: Optionally, enter a territory to be associated with this salesperson.
Chapter
CLASSROOM
Using the Resources Window to Create a Salesperson
Tax Setups in Transaction Types Window Receivables and Order Management

On the Finance tab of the Transaction Types window, you can specify a Receivables
Transaction Type and a Tax Event for tax calculation. You must ensure that the Default Tax
Calculation box is enabled, within the Receivables Transaction Type window, to ensure that
the tax code is defaulted in the order line.
Chapter
CLASSROOM
Tax Setups in Transaction Types Window Receivables and

Order Management
Overview of Credit Checking

Credit checking in Oracle Order Management is the process by which orders are validated and
released against credit checking business rules. Using credit checking rules and credit profiles,
Oracle Order Management credit checking verifies that your customer has a sufficient credit
availability with your organization to allow orders to be processed and shipped in advance of
payment.
Order Management enables you to perform credit checks on customer orders or order lines, and
automatically hold orders or lines that violate your credit setup. Using Order Management
credit checking effectively requires a complete understanding of the functional components as
well as a careful consideration of timing and performance factors.
Chapter
CLASSROOM
Overview of Credit Checking
Defining Credit Checking on the Customers Page Profile Tab

(N) Order Management > Receivables > Customers > Customers > (T) Profile
The Profile tab enables you to define credit checking criteria in the Credit and Collection
region using the following fields:
*Collector: The name of the collector for this profile.
Credit Rating: The credit rating of the profile.
Credit Classification: The credit classification of the profile.
Review Cycle: The frequency of the credit review.
Account Status: The current status of the account.
Risk Code: The risk code for the profile.
Tolerance (%): The percentage amount of this customers credit before collections start.
Collectable (%): The percentage amount of this customer's account balance that you
expect to collect regularly.
Credit Check: Enable this check box to initiate a credit check
Credit Hold: Enable this check box to put the profile on credit hold.
Chapter
CLASSROOM
Defining Credit Checking on the Customers Page Profile Tab
Credit Analyst: The analyst for this profile.

Next Credit Review: A date for the next credit review of the profile.
Chapter
CLASSROOM
Defining Credit Checking on the Customers Page Profile Amounts Tab

(N) Order Management > Receivables > Customers > Customers > (T) Profile Amounts
The Profile Amounts tab enables you to define specific currencies and amounts for the
following:
Min Receipt Amount: The minimum amount that you will receive from the customer.
Credit Limit: The limit to the amount of credit given to the customer.
Order Credit Limit: The limit to the amount per order, given to the customer.
Min Statement Amount: The minimum amount before a statement is sent.
Min Dunning Amount: The minimum amount before dunning starts.
Min Dunning Invoice Amount: The minimum amount on an invoice before dunning starts.
The following conditions must exist for automatic credit checking to execute:
Payment terms with Credit Check enabled
Credit check rule defined and assigned to the Order Management transaction type
Profile amounts defined at the customer level
Chapter
CLASSROOM
Defining Credit Checking on the Customers Page - Profile

Amounts Tab
Note: Credit hold holds an order or order line on at the time of booking, every time an order is
entered, regardless of profile values, and so on. Order Management can release orders
individually; however, the source can only be release from the Customer screen. This type of
credit hold is typically applied when the customer viability has not been verified and is often
confused with credit check hold.
Chapter
CLASSROOM
Credit Check Rules

(N) Order Management > Setup > Credit > Define Credit Check Rules
Credit check rules are assigned to transaction types, which are referenced at the order level.
Within the Options tab of the Credit Check Rules window, you assign the Credit Check Level
and Credit Hold Level for the rule.
Within the Exposure tab, various parameters, such as Include Tax, Include Returns, Include
Open Receivables Balance, are enabled or disabled depending on your business needs.
Chapter
CLASSROOM
Credit Check Rules
Define Credit Usage Rule Sets

(N) Order Management > Setup > Credit > Define Usage Rule
The general setup steps for credit checking are as follows:
1. Customer page - specify a) credit check box b) Account Profile
2. Payment Terms form - enable credit checking
3. Create a credit check rule
4. Attach the credit check rule to the transaction types form
5. Define your credit usage rules
6. Define credit profiles
The Define Credit Usage Rules window enables a user to create and maintain credit usage rule
sets that can be assigned to Credit Profiles. Credit Usage Rule Sets define the set of
currencies that will share a predefined credit limit during the credit checking process, and
enable the grouping of currencies for global credit checking. Usage Rules Sets ensure that
if credit checking is enabled, that all transactions for specified currencies go through the
currency conversion process and are summarized by currency prior to the credit checking
process.
Chapter
CLASSROOM
Defining Credit Usage Rule Sets
You can define a usage rule set for a single currency or multiple currencies
You can choose to assign a global usage rule (all currencies) and then exclude one or
more currencies from the rule set
You can choose to define multiple usage rules for multiple currencies within the usage
rule set
You can choose to add or delete new Currency records for an existing Usage Rule Set
Usage rule sets consist of at least one usage rule/currency combination, and once a rule set is
assigned to an Oracle Entity, the rule set provides processing defaults for determining
credit availability during multiple currency credit checking processing routines.
Define Credit Check Usage Rule Sets
1. Enter a name for your rule set in the Usage Rule Set Name field.
2. Select the Global Exposure box if you wish to enable the Usage Rule Set for global
exposure (across operating units). By default, this box is cleared (do not enable Global
Exposure for the usage rule set). If you are unable to select the Global Exposure check
box, submit the Credit Limit Usages Report. Review the report output and un-assign any
usage rule sets with different Global Exposure options for the same credit profile.
3. Select the value Currency in the Usage Type field.
4. Enter a currency in the Currency field. The Currency field can contain any Currency
Code currently defined. The Currency field may also use the lookup All Currencies to
indicate the usage rule is for all currencies defined.
5. Chose to exclude a specific currency for your usage rule by selecting the Exclude check
box. The default is unchecked, or No.
Note: If the field Currency has value of All, the Exclude check box is non-updateable.
Chapter
CLASSROOM
Defining Credit Check Rules

(N) Order Management > Setup > Rules > Credit
(N) Order Management > Setup > Credit > Define Credit Check Rules
Order Management credit check rules enable you to determine what credit checking criteria is
used when determining credit exposure during the credit checking process.
Order Management transaction types determine when credit checking actually occurs and
define your credit checking process when used in conjunction with credit checking rules,.
For example, you can define credit checking rules that utilize pre-calculated exposure
information when comparing a customer's current order amount against their overall
exposure; if the order transaction type utilizes this rule, and the order fails during the credit
check process, it is automatically placed on credit check hold. You can define as many
credit checking rules as you need, and if you inactivate a credit checking rule, you also
must remove it from any order types that use it. Additionally, you can include in or exclude
from your credit check rule some or all of your open accounts receivable balances, and
some or all of your uninvoiced orders.
1. Enter a name for your credit check rule.
Chapter
CLASSROOM
Chapter
CLASSROOM
2. Optionally, enter the Effective Dates for your rule.

3. Select the entity to perform credit checking against for your rule. Select from:
- Sales Order
- Sales Order Line
Note: If you select Sales Order Line as your credit check level, the Use Pre-calculated
Exposure check box will be checked and protected against update. If you choose to
perform credit checking at the Sales Order level, you are limited to the system
generating header level credit holds only. The Credit Hold Level field will default to
Sales Order and is protected against update.
4. Select the Credit Hold Level for your credit rule. Select from:
- Sales Order
- Sales Order Line
- Override Manual Release check box
5. Select the conversion type to use when performing credit checking using your credit
rule.
6. Select the Check Item Categories check box for your credit rule if you wish to perform
credit checking for sales orders by Item Categories defined for Order Management.
7. Select the Send Hold Notifications check box if you wish to send hold notifications
whenever a credit hold is placed for a sales order or order line.
8. Select the Use Pre-Calculated Exposure checkbox to determine the credit exposure for
the customer. Run the Initialize Credit Summaries concurrent program to calculate the
credit exposure after you have defined the Credit Checking Rule.
9. Select the Include External Credit Exposure check box to include external exposure
details imported into Order Management during the credit checking process.
10. Select the Open Receivables Balance check box for your credit rule if you wish to
include open receivables balances.
11. Select the Include Uninvoiced Orders check box if you wish to include uninvoiced
orders for your credit rule.
12. You can now assign the Credit Check Rule to the Transaction Type that you will use in
your Sales Order. (N) Order Management > Setup > Transaction Types > Define.
Summary
Chapter
CLASSROOM
Chapter 6
Oracle Order Management Setup Steps
Chapter
CLASSROOM

Setup Steps

Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Order Management Setup Steps
Chapter
CLASSROOM
Chapter
CLASSROOM
Chapter
CLASSROOM
Chapter
CLASSROOM
Profile Options and System Parameters

During implementation, you set a value for each user profile option to specify how Order
Management controls access to and processes data. Using the System Administrator or
Application Developer responsibility, you can view or update the profile option and at which
level the profile options can be updated. The levels include User, Responsibility, Application,
and Site levels.
System Parameters in the Oracle Order Management Parameters window can be functionally
grouped, and you can define controls as easily as defining profile options. Order Management
System Parameters are grouped in Categories like Generic Approval, Drop Ship, Pricing, and
Scheduling. You can define new parameters and set up values using different sources like SQL
and constant values.
There are a number of profile options that are available in Order Management setup. Profile
options are also categorized, some examples are Configurations, Electronic Messaging, Forms
UI, Pricing, Security. For a list of all Order Management profile options and system parameters,
and for details about the valid values for all profiles, see the Oracle Order Management
Implementation Manual.
Chapter
CLASSROOM
Profile Options and System Parameters
For information on how to set and update profile option values, see the Oracle Applications
System Administrator's Guide.
Chapter
CLASSROOM
Overview of QuickCode or Lookup Types

(N) Order Management > Setup > QuickCodes
QuickCode is the internal name of a value defined in an Oracle Workflow lookup type. A
lookup is a set of values that is populated in an LOV in a window and classified under a
Lookup Type. These values can be seeded or can be user-defined. Attributes are validated by a
lookup type. The lookup code is stored in the attribute, but the code's translated meaning will
be displayed whenever the attribute value is viewed by an end user. A Lookup Type such as
Credit Card has various code values like Amex, MC, Visa, Diners. Lookups can be created by
the user or by the system and can be extensible.
You can create QuickCodes for Order Management. QuickCode types that you can define
include:
Cancellation Codes
Credit Cards
Freight Terms
Hold Types
Note Usage Formats
Chapter
CLASSROOM
Overview of QuickCode or Lookup Types
Chapter
CLASSROOM
Release Reasons
Sales Channels
Shipment Priorities
Cascading Changes: Line attributes that will be updated as a result of header changes. For
example, if you update the value of a field in the header of the sales order, and the value comes
from a lookup, the changes will be cascaded to the line also.
You can create as many quickcodes as needed. You can also disable quickcodes. The Access
Level toggles display whether you can define new lookup codes. You can modify User and
Extensible lookups only. You cannot modify system lookups.
For more information on how to define the payment method associated with the credit card
type see Oracle Receivables Implementation Guide.
For more information on details of validation method see Oracle iPayment Implementation
Guide.
Defining QuickCode or Lookup Types
Chapter
CLASSROOM
Overview of Order Header and Order Line Processing Flows

The most commonly used Order Header flows are:
1. Order Flow - Generic
2. Order Flow - Generic with Header Level Invoice Interface
The most commonly used Line Flows are:
1. Line Flow - Generic
2. Line Flow - Generic, with Header Level Invoice Interface
For more information see Using Oracle Workflow in Oracle Order Management.
Chapter
CLASSROOM
Overview of Order Header and Order Line Processing Flows
Overview of Transaction Types Window

Transaction Types are used to associate workflows for various phases of sales document (sales
orders or sales agreements) processing. You can also associate various values like
transaction phases, layout templates, approvers to a transaction type that become default
values on the sales order or sales agreement. Use Transaction Types to create various order
types like Standard Orders, Returns etc and associate them to various sales document types
like Orders, Quotes, Sales Agreements etc. In the Transaction Types window, you can
assign workflow processes (for headers and lines), price lists, contract templates, etc. You
can setup your Transaction Type for use within a single operating unit or multiple
operating unit.
1. Enter the name of the transaction type in the Transaction Type field.
2. Enter a description in the Description field.
3. In the Sales Document Type field, select Sales Agreement or Sales Order from the list of
values (for Quotes, Returns and Releases, choose Sales Order).
4. In the Order Category field, select a category from the list of values. For Order Types,
you can specify a value of Order, Return, or Mixed. For Line Types you can specify
Chapter
CLASSROOM
Overview of Transaction Types Window
Chapter
CLASSROOM
Order or Return. When an order type is assigned to an order, the category determines
whether both order and return lines can go on the order. A category of Mixed enables an
order to have both kinds of lines. For Sales Agreements, select Order. For Order Lines,
the Sales Orders window automatically sets the category to Order. Order Management
seeds defaulting rules to get the appropriate default outbound or inbound line transaction
type from an order type to a line based on its category code.
5. In the Transaction Type Code field, select order or line from the list of values to specify
whether this is an order or line transaction type. Select the value Order for Sales
Agreements.
6. In the Fulfillment Flow field, select a line flow from the list of values. The most
commonly used flows for sales orders are Order Flow - Generic and Order Flow Generic with Header Level Invoice Interface.
7. If a negotiation flow is needed, select it in the Negotiation Flow field from the list of
values. The most commonly used flows are Negotiation Flow - Generic and Negotiation
Flow - Generic with Approval.
8. Enter an effective date for the transaction type in the Effective Dates field.
9. Select the default transaction phase, Fulfillment or Negotiation, in the Default
Transaction Phase field from the list of values. Transaction phase determines where in the
workflow the transaction begins, and can be used in defaulting rules. This field defaults
to Fulfillmenta fulfillment phase must be defined; Negotiation is optional.
10. Enter a value in the Layout Templates field. This field is optional.
11. Enter a value in the Contract Template field. This field is optional.
12. In order for the Quote number to become the Sales Order number, select the Retain
Document Number check box. This is not applicable for Sales Orders or Sales
Agreements. If the transaction type is associated with both a negotiation flow and
fulfillment flow, the document number can be retained when the document transitions to
fulfillment.
On the Main Tab in the Document Region:
13. In the Agreement Type field, select a pricing agreement type from the list of values. This
field is optional. If you enter an agreement type here, you can choose only agreements
with this agreement type when using this order type. Some of the examples of Agreement
Types in the LOV are: Standard Terms and Conditions, Direct Sales Agreement,
Government Service Agreement. Define agreement types using Order Management
QuickCodes.
14. Select the Agreement Required check box if a pricing agreement is required. This is only
applicable to order transaction types. Some examples are: Return for Credit, Return for
Credit with Receipt, Return for Credit with Approval.
15. In the Default Return Line Type field, select a return line type from the list of values.
16. In the Default Order Line Type field, select an order line type from the list of values.
17. Select the Purchase Order Required check box check to require purchase order numbers
during order entry for orders and returns with this Order type. This is only applicable to
order transaction types.
18.
On the Main Tab in the Pricing Region:
Chapter
CLASSROOM
18. Select the Enforce List Price check box to prevent discounts and overriding the selling
price. If this is selected, you cannot apply discounts to the order line list price when you
use this order type and you cannot override the selling price, unless the profile option
OM: Discounting Privilege is set at the appropriate level.
19. In the Price List field select a price list from the list of values to serve as a defaulting
source. The list of values displays global price lists and price lists defined for the
Operating Unit selected.
20. Enter a minimum margin in the Minimum Margin Percent field. This field is optional.
On the Main Tab in the Credit Check Rule Region:
21. Enter a credit check rule that you have defined for any one or a combination of the
following events: Ordering, Packing, Picking/Purchase Release, Shipping.
22. Select credit check rules to use when performing checking credit at either Booking, Pick
Release and Purchase Release (for drop shipments), Packing, or Shipping within the
corresponding Credit Check Rule fields.
23. You can select a credit check rule for each field within the Credit Check Rule region, or
select combinations that suit your business purposes. For example, you can select a credit
check rule for booking only, or booking and shipping. If you leave any of the Credit
Check Rule fields blank, no credit checking will occur when an order or order line
reaches the corresponding workflow activity within the order or line flow, using the order
or order line type specified.
Workflow in Transaction Types

Negotiation flow and Fulfillment flow
The negotiation flow represents the decision phase of the order process where a sale is
discussed and agreed upon before the sale is confirmed. Once the order terms and conditions
are negotiated, the negotiation moves into the fulfillment phase of the order where scheduling
and shipping occur, resulting in invoicing through Receivables. The distinction between the
two flows is specific to the activities in the seeded flows. The negotiation flow is a header flow
only and all the lines follow that flow: there are no independent line flows during the
negotiation phase. The negotiation flow also has an expiration that is based on the start and end
active date, and will expire if not converted to an order. Only when the transaction transitions
to the fulfillment part of the order process are line flows associated with the lines and can be
managed independently.
Oracle Order Management transaction types determine the workflow processes executed
at header and line levels. Oracle Order Management enables you to define both header and
line level transaction types.
Chapter
CLASSROOM
Workflow in Transaction Types
Oracle Order Management does not provide seeded transaction types. You must create
your own transaction types using the transaction types window in Oracle Order
Management.
The Transaction Type determines the header level process used at the header level on an order.
The combination of transaction type, line type, and item type determines the line workflow.
Please note that the Operating Unit field on the Transaction Types window is a mandatory field
and transaction types are assigned to one or more operating units. You can perform all standard
processing including orders, returns, drop-ship orders, orders for configured items, and orders
for assemble-to-order items using seeded workflows. You can also create your own workflows
if you need additional processes, activities, or notifications.
Chapter
CLASSROOM
Overview of Document Sequences for Order Numbering

Order Management uses the AOL document sequence functionality for numbering orders. You
must define at least one document sequence for your order types which can be used for all
your order types. For instance, you could define an automatic sequence beginning with 1
and assign it to all your order types. Then each new order that you enter will receive the
next number in the sequence. Alternatively, you may define multiple document sequences
and use different ones with different order types. One sequence could be used with your
domestic orders that begins with 1 and another sequence could be used for your
international orders that begin with 10000. The number ranges would be separate and order
types easily identifiable.
Define document sequences for order numbering
(N) Order Management > Setup > Documents > Define
1. You can define the sequence to be Automatic, Gapless or Manual.
- Automatic: The system automatically increment document numbers. Automatic
sequences do not guarantee contiguous numbering.
- Gapless: The system guarantees that the numbers returned are contiguous.
- Manual: The user must specify a unique document number.
Chapter
CLASSROOM
Overview of Document Sequences for Order Numbering
Assigning your order type to a document sequence

(N) Order Management > Setup > Documents > Assign > (T) Document
1. Enter Oracle Order Management in the Application field and the Order Type in the
Category field.
2. Select the Ledger. Enter Manual in the method field if the number sequence is manual,
otherwise enter Null.
3. On the Assignment tab enter the Start Date and the Sequence that you defined for your
order type in the previous step. Note that you cannot change the assignment for an order
type and ledger. To change the assignment you must assign an end date to the existing
assignment and create a new one for the new assignment. You cannot have more than one
assignment for the same date range, document type and ledger.
4. There are additional controls to be considered when a quote transitions to a sales order in
reference to the document number and how the number is generated.
5. If a gapless numbering type is a requirement, then the Retain Document Number check
box should not be selected when using a transaction type for negotiation and fulfillment.
Chapter
CLASSROOM
For all types of numbering, Order Management validates that the number specified by you is
unique for a given order type.
For more information on AOL Document Sequences, see the Oracle Applications System
Administrator's Guide - Configuration, Document Sequences.
2. Enter a name for the document sequence. Specify Oracle Order Management as the
Application.
3. Enter a starting number.
4. Optionally, enter effective dates for the document sequence.
5. Save your work.
Defining Order Import Sources

(N) Order Management > Setup > Orders > Import Sources
You can define Order Import Sources from which to import order information. You can import
orders from legacy systems, orders from external systems like suppliers systems, orders
from other quote or sales systems, and changes to orders. Oracle Order Management
recommends that you define a unique name for each source of order information you are
importing. When you run the Order Import concurrent program, you can enter the source or
sources for each execution. You can run Order Import for multiple sources at one time.
Define Order Import Sources
1. Enter Order Import Source Name and Description.
2. Select Enabled checkbox to activate the Order Import source.
Chapter
CLASSROOM
Defining Order Import Sources
Overview of Processing Constraints

(N) Order Management > Setup > Rules > Security > Processing Constraints
Processing constraints are rules that control changes to the sales order entities (header and
line level). The changes or operations are Create, Update and Delete and Cancel. You can
carry out the changes or operations on various order attributes (Bill-To Address, Price List,
Order Date, Quantity). Some examples of user action that are performed based on these
changes are Not Allowed, Require Reason and Require History, Raise Integration Event.
Processing constraints can prevent certain changes, but can also be set up to perform
actions based on those changes. A simple example:
Operation = UPDATE
Attribute = Order Date
User Action = NOT ALLOWED
Condition = Order Line is Fulfilled.
The processing constraint prevents you from updating the Order Date if the order line has been
fulfilled. Use processing constraints to control certain user actions like update, deleting
values that are dependant on each other. For example a processing constraint prevents you
from deleting a booked order.
Chapter
CLASSROOM
Overview of Processing Constraints
Chapter
CLASSROOM
Processing Constraints Example

To set up a processing constraint that prevents update of the sales order header order type when
there are order lines created or when the order is booked, do the following after navigating
to the Define Processing Constraints window:
1. Query in the top of the form:
- Application: Oracle Order Management
- Entity: Order Header
2. Enter on a new line at top of the Constraints region:
- Operation: Update
- Attribute: Order Type
- User Action: Not allowed
- Leave System Changes, User Changes blank
- Clear System check box
3. Enter in the first line of the Conditions region:
- Group Number: 101 (the group number should be greater than 100 for user-defined
constraints)
- Scope: Any
- Validation Entity: Order Header
- Record Set: Order
- NOT check box: Deselect
- Validation Template: Booked
- System check box: Deselect
- User Message: the order is booked
4. Enter in the second line of the Conditions region:
- Group Number 2
- Scope: Any
- Validation Entity: Order Header
- Record Set: Order
- NOT check box: Deselect
- Validation Template: Lines Exist
- Seeded check box: Deselect
- User Message: The order has lines
Setting up Processing Constraints

(N) Order Management > Setup > Rules > Security > Processing Constraints
Query Application
Query Application for Oracle Order Management and Entity for the entity for which you want
the processing constraint, for example, Order Header or Order Line.
Enter Constraints
1. In Operation, select the operation that you want to constrain.
2. Select an Attribute to constrain, based upon the operation selected.
If you select the value UPDATE for the Operation field and you do not select an
Attribute value, the constraint allows no update to any field of the entity, by any
user.
3. In User Action, select one of the following:
- Not Allowed: You cannot perform the constrained operation
- Require Reason and History: You can perform the operation only if you enter a
reason. Use this with Operation CANCEL, Operation UPDATE if the constrained
Chapter
CLASSROOM
Setting up Processing Constraints
Chapter
CLASSROOM
attribute is Ordered Quantity only, and for recording Audit Trail history when
requiring a reason for an attribute change
- Requires History: You can perform the operation and will not be prompted to enter a
Reason. You still have the option to enter both a Reason and Comment, and if you
do so, the information is recorded. Use the value for enabling Audit Trail history to
be recorded without a reason for an attribute change
4. Select a value for the System Changes field. The value selected in this field determines if
system changes are allowed, despite the constraint. Choose from:
- Always: System changes allowed
- Never after Insert: System changes allowed if the entry has not been saved to the
database
5. Select a value for the User Changes Field:
- Never: The user is always constrained
- Never after Insert: The user is constrained after the entry is saved to the database
The Enabled field indicates whether the current constraint is active. This allows
constraints to be temporarily disabled if necessary.
System check box: If a Constraint has the System check box selected, you cannot update
the constraint definition.
Enter Conditions
6. In the Group Number field, enter a numeric value according to the following principles:
- For conditions that should together evaluate to TRUE (AND conditions), enter the
same group number. The constraint applies if the entity in question meets all of the
conditions defined.
- For conditions that should together evaluate to OR (OR conditions), enter a different
number for each record. The constraint applies if the entity in question meets any
one of the conditions defined.
7. In Scope, if the record set applies to multiple records, indicate the scope of evaluation of
the record set for this condition. An example of a record set that applies to multiple
records is the record set of all of the lines of a sales order. Select one of the following:
- Any: The condition is satisfied if one of the records meets it, for example, the
condition is satisfied if one of the sales order lines is booked
- All: The condition is satisfied if all of the records meet it, for example, the condition
is satisfied if all of the sales order lines are booked
8. In Validation Entity, enter the entity for which the condition is validated. You can enter
the same entity as the constraint (at the top of the Constraints region) or you can enter an
entity related to the constraint. For example, if the constraint is against Order Header,
Validation Entity can be Order Line.
In Record Set, select the record set that corresponds to the entities to which the
constraints process should apply the condition. For example, if you enter the order
line record set Line, the condition is evaluated against the order line in question. If
you enter the order line record set Order, the condition is evaluated against any or all
(depending on the scope) lines of the order in question.
Chapter
CLASSROOM
If Validation Entity is different from Entity (at the top of the form), you can only select
record sets based on the primary key of the validation entity.
9. Select the Not check box (the negative condition modifier) to direct the constraints
processing to evaluate the NOT condition of Validation Template. For example, if you
expect to select Validation Template Booked, selecting NOT creates the condition of not
booked for the constraint.
- In Validation, select a validation template. This item specifies the condition being
evaluated.
- Enabled: The Enabled field indicates whether the current constraint is active. This
allows constraints to be temporarily disabled if necessary.
- System check box:
- If a Constraint has the seeded check box selected, and the constraint condition
check box is also selected, you cannot update the constraint condition.
- If a Constraint has the seeded check box selected, and the constraint condition
check box is not selected, you can update the constraint condition.
10. In User Message, enter the trailing portion of the error message that the constraint
processing should display when the user violates the constraint. For example, if the
constraint was to not allow an update of the item field on the order line if the line has
been previously booked, constraints processing displays the error message You are not
allowed to update the item; the item is booked.
Specify who the Constraint applies to
Select one of the following:
All responsibilities: The constraint applies to all responsibilities.
Authorized responsibilities: The constraint applies to all responsibilities except ones that
you specify. Specify the excepted responsibilities in the untitled lines below your
selection.
Constrained responsibilities: The constraint applies to the responsibilities that you
specify. Specify the excepted responsibilities in the untitled lines below your selection.
Defining Validation Templates

Order Management provides you the ability to define your own validation conditions by the
use of validation templates. A validation template names a condition and defines the
semantics of how to validate that condition. Validation templates can be used in the
processing constraints framework to specify the constraining conditions for a given
constraint. These conditions are based on:
Where the entity is in its workflow
The state of attributes on an entity
Any other validation condition that cannot be modeled using the above methods
API based validation templates are not available if constrained entity is different from the
entity for which the validation template has been defined (or the Validation templates are
not available even if the record set being used is anything other than the primary key record
set).
For example, API based Validation template Pick Released has been set up for entity Order
Line. If you set up a constraint for attribute Ship To on Order Line, the validation template
Pick Released is available but for a constraint on attribute Ship To on Order Header, Pick
Released will not be available.
Chapter
CLASSROOM
Defining Validation Templates
Define Validation Templates

(N) Order Management > Setup > Rules > Security >Validation Template
1. Select Entity to define condition for the Entity field.
2. Enter a Template Name for the condition.
3. Enter a Name in the Short Name field for the condition.
4. Select Validation Type to be performed by the condition. Select from:
- WF: (validation is based on the workflow status of this entity):
- Select the Activity for the condition
- Select the Activity Status for the condition. Select from:Active, Complete,
Error, Notified, and Suspended
- Select the activity Result for the condition
- Save your work
- API (validation is completed through an Application Program Interface):
- Select the PL/SQL Package you wish to interface with the constraint condition
- Enter the Procedure name of the API
- Save your work
- TBL (validation is based on the values of database columns on this entity):
- Select the Attribute Column name on the entity for the constraint condition
- Select the Validation Operation for the constraint condition. Select from: =
(Equal To), <> (Not Equal To), Is NULL, Is Not NULL
- Select the Value String you want to validate against the value of the column
Note: You can add more than one attribute, value pair, otherwise all pairs will be
added together in the validation.
Submit Create Validation Packages concurrent program
When you have created new validation templates or record sets, you will need to submit the
Create Validation Packages concurrent program from the Tools menu to submit a
concurrent request to create a validation package for all new or modified validation
templates and record sets that may constitute a permitted validation combination. After the
request completes, all validation templates that processed successfully will be visible in the
list of values in the Processing Constraints window.
Chapter
CLASSROOM
For attribute Ship To on Order Line, if the constraint condition uses any record set (ATO
Configuration, for example) other than the primary key record set Order Line, the
validation template Pick Released will not be available.
Defining Defaulting Conditions

(N) Order Management > Setup > Rules > Defaulting > Defaulting Condition Templates
The Defaulting Condition Templates window enables you to define defaulting template and
conditions for the application/entity combination displayed on the defaulting rules setup
window.
Define Defaulting Conditions
1. Select or Add Condition Name: Select an existing condition name if you wish to update
the associated validation rules or add a new condition name with associated validation
rules in the Condition Name field.
2. Enter Validation Rules: In the Validation Rules Region, enter the validation rules based
on the attribute values of the above entity. For example, standard orders could have the
order type Standard. Order type = Standard.
3. Enter Group Number: In the Group Number field:
- For conditions that should together evaluate to TRUE (AND conditions), enter the
same group number
Chapter
CLASSROOM
Defining Defaulting Conditions
For conditions that should together evaluate to OR (OR conditions), enter a different
number for each record
4. Select Attribute Name: Select the Attribute name, such as Contact.
5. Select the Validation Operation option:
- (>) Greater Than
- (<) Less Than
- (>=) Greater than or Equal to
- (<=) Less than or Equal to
- (=) Equal
- (!=) Not Equal
6. Enter the Value String of the attribute that you want to validate against.
For more information, please refer to the Order Management Online Help.
Chapter
CLASSROOM
Define Defaulting Rules

(N) Order Management > Setup > Rules > Defaulting > Defaulting Rules
1. Enter a value in the Precedence field to determine the precedence when resolving
multiple TRUE defaulting conditions.
2. Select a Defaulting Condition from the list of values and then enter the defaulting rules to
be used if this defaulting condition is TRUE.
3. Select the Enable check box if you wish to enable the defaulting condition. If this check
box is not selected, the defaulting condition is disabled and the rules and condition
associated with this condition are not used in default possessing.
4. Select priority sequence: Within the Default Sourcing Rules region, select the priority
sequence in which you want to retrieve the default for this attribute.
The defaulting process searches for a default for your attribute by evaluating defaulting rules in
ascending order.
You can default important information based on user entered values. For example, if you enter
a customer in the order, the Ship To and Bill To addresses default without user
intervention.
Chapter
CLASSROOM
Defining Defaulting Rules
Select Defaulting Source Type

Select the defaulting source type. The defaulting source type determines data entry in the
Default Source/Value field.
Select default sources or enter default values
Based on the default source type selected, either select the default sources or enter default
values in the Default Source/Value field.
Chapter
CLASSROOM
Setting up Versioning and Audit History

Version history maintenance is useful for reference and comparison. This is particularly true of
quotes and Sale Agreements (SAs) with a negotiation phase where the transaction
document changes a number of times before it is approved. This may occur with complex
products that are frequently redesigned to meet customer requirements, or with a loyal
customer who negotiates for a long time for the best price with the promise of higher order
quantities over an extended period of time.
Versioning maintains the history of previous versions, when the active version is changed.
However, one can use the previous versions as templates for creating new sales order,
quotes or sales agreements at any time with the copy feature.
Version history maintenance and comparison enables:
Maintenance of transaction history of previous versions
Ability to amend the current version of the transaction
Tracking changes over a period of time and view those changes
Comparison of changes made to transactions across versions
Copy any version of a Quote to a Sales Order
Chapter
CLASSROOM
Setting up Versioning and Audit History
Set Up Audit History

1. Add "View Audit History" menu option to the Order Management menu for those
responsibilities that need to be able to view the new Audit History forms this menu
option will be created through seed data.
2. Set up Processing Constraints to indicate which attributes on the order you want to have
audit trail recorded for. See Define Processing Constraints.
3. Create some new Validation Templates if you have specific conditions to control whether
or not to record audit information. See Defining Validation Templates.
4. Set the OM System Parameter Audit Trail.
Navigate to Order Management > Setup > System Parameters > Values.
1. Select your Operating Unit.
2. Select Generic Parameters from the list of values.
3. For the Audit Trail Parameter, select from the list of values: Enable when Order is
Booked, Enable when Order is Entered, or "Disabled.
5. Enter and process orders as usual.
6. Schedule the Consolidator program to run periodically to make audit information available
to query and report.
7. Run report or execute queries to view audit information.
Note: Based on the processing constraints that have been set up, users will sometimes be
required to input reasons when they make changes to orders.
System Parameter 'Audit Trail' has to be enabled at Operating Unit and the processing
constraint setup should be required to maintain Audit History for that Operating Unit.
Chapter
CLASSROOM
Set Up Versioning
Define Processing Constraint
Define processing constraint for versioning. Select the desired user action from the User
Action field:
Generate Version, Require Reason and Raise Integration Event
Generate Version and Require Reason
Generate Version
Require Reason and Require History
Require History
Apply necessary Validation Templates
Apply necessary validation templates in the Validation Templates window.
Overview of Available To Promise (ATP)

Oracle Order Management enables you to advise your customers when items will be available
based on current on-hand inventory plus the expected incoming supply and outgoing demand.
To calculate ATP, the following values are required: item, order quantity, order quantity unit
of measure and the request date. In general, you enter the item and order quantity on every
order line. The request date and order quantity unit of measure may be defaulted or manually
entered. ATP may be calculated for a single line, a group of lines, or a complete order. The
results for a single line are displayed in a single column in a small window, while the results
for multi-line ATP are displayed in a table. In both formats, the following information is
displayed:
Warehouse: Either the warehouse on the order line or, if the warehouse on the order line
was blank, the best warehouse as selected by the sourcing rules.
Request Date Qty: The quantity that is available on the requested date
Available: The order quantity, if ATP was successful. The available quantity, which will
be less than the order quantity, if ATP was not successful.
On-hand Qty: The quantity that is currently in the warehouse.
Chapter
CLASSROOM
Overview of Available To Promise (ATP)
Chapter
CLASSROOM
Qty Reservable: The on-hand quantity minus the quantity that is already reserved to other
sources of demand.
Request Date: The date on the order line.
Available date: The date that the ordered quantity will be available. It could be the request
date if the order quantity is available on the request date, or it might be a future date when
the order quantity will be available
Error Message: Any error that occurred in calculating ATP. For example, if the Check
ATP flag for the item is not selected then this field will display ATP not applicable.
Substitute Item: If the requested item is not available and the requested quantity for a
defined substitute is available, the substitute item will be displayed.
An additional tab, showing the availability of the substitute item, is also displayed for single
items. A multi-line window displays availability information for sets and models. Clicking the
Global Availability button located at the bottom of the Availability window opens the ATP
window that has the list of warehouses where the item is enabled. You can select the
warehouses for which you want to see the availability, and the system will return the
availability in all the selected warehouses. You can open the ATP Details window from the
Availability window by clicking the ATP Details Button. The ATP Details window displays
how the results were derived.
ATP is calculated automatically during scheduling, and may be calculated manually by
clicking Availability on the Line Items tab of the Sales Order window. There are several steps
required for ATP calculations.
If you are using ASCP, supply/demand is set up at the plan level. See the Oracle ASCP
Implementation Manual. Global Order Promising will only use the infinite time fence specified
on the ATP rule. If you are not using ASCP, ATP rules must be defined to determine the
sources of supply and demand which are included in the calculation. The ATP rules must be
associated with items and/or inventory organizations. Also, the data collection program must
be run. There is a requirement for ATP calculations to be very fast; some customer service
representatives will need to give this information to customers on the phone.
However, considering all the possible sources of supply and demand for an ATP calculation
can be very complex. Therefore, a concurrent process known as data collection must be run to
summarize the supply and demand picture. This program is part of the Oracle Advanced
Planning and Scheduling application. The ATP calculation is then performed on the summary
tables. For details about setting up ATP rules and running the data collection program, see the
setup section Oracle Order Management implementation Manual.
Overview of Scheduling Levels

The scheduling level on the order transaction type determines what type of scheduling is
allowed. The possible values for this are:
ATP Only: You will not be able to schedule or reserve lines on the order. If you have an
order transaction type defined with a scheduling level of ATP Only, then you must not
have the scheduling activity in any of the line level workflow processes. This could be
used for Line Flow Generic, Bill-Only or Line Flow Generic, Bill-Only with Inventory
Interface flows, or possibly for quoting scenarios. For example, you could use the ATP
Only flow for Bill Only lines that you want to omit from a header level set. If you do not
want the Bill Only lines to be scheduled and considered part of the header-level set, you
could make the scheduling level of the line transaction type ATP Only.
No Reservations: You can perform all scheduling functions except for reserving
inventory. You will be able to use ATP items, and schedule all items, but you will not be
able to create reservations from the sales order window.
Allow All Scheduling Actions: All scheduling actions can be performed.
Inactive Demand With Reservations: You can manually enter any schedule date, but the
system does not schedule. The line can be reserved. The schedule date is not visible to
Chapter
CLASSROOM
Overview of Scheduling Levels
MRP / APS. This functionality is only for standard items, and it does not support ship or
arrival sets.
Inactive Demand Without Reservations: You can manually enter any schedule date, but
the system does not schedule. No reservation can be placed on the line. The schedule date
is not visible to MRP/APS. This functionality is only for standard items, and it does not
support ship or arrival sets. If you don't want your order lines to be visible as demand to
the manufacturing applications, do not schedule the lines. Alternatively, you can control
this by setting the scheduling level of the order transaction type.
Chapter
CLASSROOM
Auto-Schedule Profile Option

This profile option determines the default setting for auto scheduling orders, and also controls
the display of the Availability window within the Sales Orders Lines tab.
Please note that auto scheduling orders is only supported for orders that contain standard line
items, not models or kits.
Select from:
Yes: Order lines are scheduled automatically at the time of entry. Automatically display
the Availability window within the Sales Order window when entering order line details.
No or NULL: Order lines are not scheduled automatically at the time of entry. Does not
automatically display the Availability window within the Sales Order window when
entering order line details.
Note: If the item or model is a standard item or has the item ATP flag enabled, ATP inquiry
will automatically be performed on the item or model once it has been entered on an order line
and a user exits the item field.
The Line Flow - Generic workflow process sequences the line scheduling action to occur after
you book the order. However, even if you have set this profile option to No and you indicate
Chapter
CLASSROOM
Auto-Schedule Profile Option
ship set or arrival set on a order line, the order entry processing schedules the line and sets the
Visible Demand Flag.
To group lines into ship sets and arrival sets, order entry processing uses the warehouse,
scheduled shipment date, ship to location, shipment priority, and shipment method. Therefore,
it schedules the order lines with ship set values to obtain scheduled shipment date. If you want
the Line Flow - Generic workflow process to schedule an order line, you cannot specify a ship
set or arrival set for it.
Chapter
CLASSROOM
Internal Requisition Overview

Internal Requisitions enable you to request and transfer material from one inventory
organization to another, even if the organizations belong to a different operating unit, legal
entity, or set of books.
After you create an internal requisition you can optionally send it for approval. You can set up
approval rules specific for the internal requisition. When the requisition is approved,
requisition supply is created for the requesting organization.
Creating an Internal Requisition is a two step process:
Run the Create Internal Order concurrent program from Oracle Purchasing which
populates the interface tables for Order Management
Order Import concurrent program is run from Order Management to pull all the values
from the interface tables and convert them to sales orders
The following are the important features of Internal Requisitions:
Complete Item Sourcing Definition: Use default sourcing options to automatically
determine the correct source type and source for your internal requisition.
Chapter
CLASSROOM
Internal Requisition Overview
Creating On-line Requisitions: Create online internal requisitions for both expense and
inventory destinations using the same windows you use to create purchase requisitions.
Approvals and Controls: Set up the same approvals and controls for internal requisitions
as for purchase requisitions.
Exception Processing: Internal Requisitions enable you to manage exceptions in the
business flow. Order Management automatically backorders your request when you have
insufficient supply to fill the internal order.
Cancellation of Requisitions: Cancel an internal requisition if you have a change in
requirements or if you cannot fulfill a particular order. Using Order Management you can
cancel lines of the internal sales order and complete the cancellation process by canceling
the original requisition line in Purchasing.
Chapter
CLASSROOM
Creating an Internal Order

The Create Internal Sales Order concurrent program is run in Purchasing to send requisition
information from approved, inventory-sourced requisition lines to the Order Management
interface tables. The Order Import process in Order Management then derives the lines from
the interface tables and generates the internal sales order. The Create Internal Sales Order
concurrent program and Order Import concurrent program can be set to run at predefined
intervals.
The Create Internal Order process automatically schedules internal orders by setting the
Scheduled Ship Date on the order to the Need by date from the requisition. If a subinventory is
specified in the internal requisition line, Order Management reserves the goods and uses only
the specified subinventory for allocation of the items.
You must ensure that the order source is Internal for the import process to run successfully.
Also you should run Order Import using a responsibility that corresponds to the operating unit
where the internal order is created.
Order Management does not have specific workflows to manage internal orders, the standard
workflows are used, however, a customer invoice will never be created.
Chapter
CLASSROOM
Creating an Internal Order
Internal Requisition or Internal Order Process Flow
Chapter
CLASSROOM
Summary
Chapter
CLASSROOM
Summary
Chapter
CLASSROOM
Chapter 7
Oracle Order Management Fundamentals
Chapter
CLASSROOM

Fundamentals

Chapter
CLASSROOM
Holds, Order Purge, and Exception Management Setup
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Holds
Oracle Order Management enables you to hold an order, return, order line, or return line from
continuing to progress through its workflow. Holds are applied manually or automatically
based on a set of criteria that you define. There are also seeded automatic holds provided to
prevent a line or order from progressing if it violates a given business metric, such as a credit
check failure.
Chapter
CLASSROOM
Holds
Seeded Holds
Seeded holds in Order Management include the following:
Configurator Validation Hold: This hold is a Configurator Validation type that is
automatically applied to order lines that fail configurator validation.
Credit Card Authorization Failure: This hold is an Electronic Payment type that is
automatically applied to orders if credit card authorization request to Oracle Payment fails.
Credit Card High Risk: This hold is an Electronic Payment type that is automatically
applied to orders if the risk score determined by Oracle Payments is greater than the value
of the risk factor threshold.
Credit Check Failure: This hold is a Credit Check type that is automatically applied if the
Credit Hold option is enabled on the customer record in Oracle Receivables. This hold is
automatically applied if the credit check rule evaluation fails on orders that require credit
checking.
GSA Violation: This hold is a GSA Violation type that is automatically applied to orders
that violate GSA regulations.
Order Administration: You can apply this hold ased on your business processes.
Chapter
CLASSROOM
Seeded Holds
Chapter
CLASSROOM
Denied Parties Hold: This hold is an import / export compliance type. It is applied when
an order fails denied party screening.
ePayment Failure Hold: This hold is an electronic payment type that is used for expected
errors returned by Oracle Payments.
ePayment Server Failure Hold: This hold is an electronic payment type that is used for
unexpected errors returned by Oracle Payments.
Export Compliance Hold: This hold is an import / export compliance hold type that is
applied when an order fails export compliance screening.
Pending Process Payment Hold: This hold is an electronic payment hold type that is
applied when process payments is deferred.
Promotional Line: This hold is a promotional hold type that is automatically placed on
lines that exceed a soft modifier promotional limit.
Promotional Order: This hold is a promotional hold type that is automatically placed on
orders that exceed a soft modifier promotional limit.
Automatic Holds
(N) Order Management > Setup > Orders > Holds
Holds are defined to halt processing of your sales documents as well as order and return lines.
Because orders and returns are not affected by holds until the holds are applied, you can define
all the holds at one time. You can define holds that are effective only at certain steps of the
order or line workflow and you can defined holds that apply regardless of the stage in the order
flow.
Defining an automatic hold consists of the following:
Enter a unique name and description for the hold.
Use the list of values to select a hold type.
Select the workflow item:
- Order Header: For the order header
- Order Line: For the order line
Select the workflow activity, depending on your choice of workflow item.
Optionally, enter effective to and from dates.
Chapter
CLASSROOM
Automatic Holds
Optionally, select the user responsibilities that have authorization to execute and dismiss
holds.
Chapter
CLASSROOM
Generic Holds
(N) Order Management > Setup > Orders > Holds
Generic holds are defined as an automatic hold; however, the generic hold does not contain a
workflow item or workflow activity.
Generic holds are placed at the order level. Order lines are considered on hold for an order that
has a generic hold against it. Hold information is not visible for generic holds at the order line
level, only at the order header.
Within the Holds window, the check box Apply to Order and Line is enabled only if a line
level workflow activity is entered in the hold definition. If the check box is enabled, then the
line level hold is applicable at the header level as well as the line level. Apply to Order and
Line is disabled as the default.
Chapter
CLASSROOM
Generic Holds
Hold Sources
(N) Order Management > Orders, Returns > Order Organizer
Hold sources are defined to apply holds automatically for existing or future single or multiple
orders, returns, and lines for a particular site, item, warehouse, order, and so on.
To define a hold source:
From the Order Organizer window, select Create Hold Source from the Tools menu.
Select a hold name from the list of values.
Select the operating unit applicable to this hold.
Use the list of values to select the criteria for the hold. Choose from:
- Bill to Site
- Ship to Site
- Warehouse
- Item
- Order
- Sales Agreement No. (number)
Chapter
CLASSROOM
Hold Sources
Chapter
CLASSROOM
Use the list of values to select the value of the criterion that you chose.
Enter a date in the Hold Until Date field to specify when the hold is released.
Optionally, enter comments for the hold.
Click Apply Holds.
You can define the hold source to be for a specific order or return. A hold source can also be
the combination of parameters that Oracle Order Management supports. Oracle Order
Management supports hold sources with up to two entities. The combinations of supported
entities include:
Item > Customer
Item > Ship To Site
Item > Bill To Site
Item > Warehouse
Item > Sales Agreement Number
Warehouse > Customer
Warehouse > Ship To Site
Warehouse > Bill To Site
Sales Agreement Number > Ship To Site
Sales Agreement Number > Bill To Site
Sales Agreement Number > Warehouse
Sales Agreement Number > Ship To Site
Sales Agreement Number > Sales Agreement Line Number
You can apply your holds to be effective immediately and universally. An automatic hold that
has hold criteria defined can be released for all orders or individual orders.
Order and Quote Purge

Oracle Order Management enables you to purge closed orders and quotes and the workflow
history associated with them, by determining which documents you want to purge by creating a
Purge Set. Purging data creates space in your database and improves performance of
transactions and maintenance.
After orders and quotes have been selected for purging within a purge set, you can either purge
the entire set, a subset of the set, or cancel the purge.
Note: Orders must be closed before they can be purged and there can be no open activity for
the order, including uninvoiced lines or open returns.
Order Purge is a concurrent process; you enter parameters, such as Operating Unit, Purge Set
Name, Order Number High/Low, Order Type, Creation Date, and so on, to specify the purge.
The profile: OM: Transactions Purged Per Commit determines how many orders can be purged
per commit action. The default is 100.
Chapter
CLASSROOM
Order and Quote Purge
Purge Sets
(N) Order Management > Orders, Returns > Purge > Order Purge Selection
(N) Order Management > Orders, Returns > Purge > Quote Purge Selection
A purge set contains orders and quotes to be purged based upon criteria that you specify in the
Parameters of the Order Purge Selection or Quote Purge Selection concurrent process.
The Order Purge Selection and Quote Purge Selection concurrent programs enable you to
search for orders and quotes across operating units. By selecting an operating unit as part of the
parameters for the concurrent program, you restrict your quotes and orders to a specific
operating unit.
The following prerequisites are applicable when purging orders and quotes:
An order or quote status must be expired or lost before it can be purged
An order or quote can only be purged if no open activities exist, including open invoices or
open returns
After these conditions are met, the purge checks to see if all user defined prerequisites have
been met. Orders can be purged if there are unpaid invoices for them.
Chapter
CLASSROOM
Purge Sets
Chapter
CLASSROOM
Note: Order and quote purge capability is available to Oracle Order Management Super Users
only.
You create Purge Sets by:
Purge Set Creation, using the Create Purge Set concurrent program
Multi-selection of orders within the Order Organizer window, then invoking the Create Purge
Set Concurrent Program from the Tools menu
Single selection of orders within the Order Organizer window, then invoking the Create Purge
Set Concurrent Program from the Tools menu
You can submit your same purge request on a regular interval for example, weekly or monthly.
To create a purge set:
Select an operating unit.
Enter a unique purge set name.
Optionally, enter a description for the purge set.
Define the following criteria (limit your selection to refine your purge):
Order Number Low
Order Number High
Order Type
Order Category
Customer
Order Date Low
Order Date High
Creation Date Low
Creation Date High
Determine whether or not you want contract terms to be purged (if applicable).
Setting Up Exception Management

(N) Order Management > Orders, Returns > Process Messages
You view and correct stored workflow errors in the Process Messages window. Each logged
message has an associated status (seeded values are Open or Closed). The various transaction
windows provide direct navigation to Open errors, and enable you to retry a workflow activity
that failed. If the retry is successful, then open messages are automatically closed.
The workflow error handling process generates an Order Management-specific notification that
uses standard workflow functionality to enable the recipient to retry an activity in error. The
workflow also generates diagnostic information for the problematic order or line automatically.
In some cases it may take you a couple of iterations of fixing errors and retrying the activity to
fix all the issues that are causing an activity to error.
Purging also includes a record of errors and corresponding diagnostic information for Oracle
Support to aid in fixing the problem.
Setting up exception management includes:
Set the profile option OM: Show Process Messages to Yes.
Set the profile OM: Generate Diagnostics for Error Activities to Yes
Chapter
CLASSROOM
Setting Up Exception Management
This enables the Diagnostics: OM Order Information concurrent program to be run

automatically when there is an error in a workflow activity. Exception Management
automatically submits the Diagnostics: OM Order Information concurrent program
through the Order Management Error flow if the profile option OM: Generate
Diagnostics for Error Activities is set to Yes. In the event that activities are retried
and failed multiple times, the concurrent program does not run multiple times as this
could result in performance issues.
Define any custom message statuses desired by editing the seeded lookup type
ONT_MESSAGE_STATUS.
Chapter
CLASSROOM
Summary
Chapter
CLASSROOM
Chapter 8
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup

Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Basic Pricing Setup
Chapter
CLASSROOM
Objectives
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing in the Order to Cash Process

The ordering process leads to:
Shipping of goods
Invoicing of customer
Receipt of cash and reconciling of the bank statement
In Order Management the pricing engine prices the items after the order is entered or booked
(depending on the pricing setup). Once the order is booked, it proceeds through the workflow
process. If it is a shipping item and the quantities are available, the order is processed by
Shipping Execution. During shipping, the freight and special charges can be calculated and the
price of the item is adjusted accordingly.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing in the Order to Cash Process
Overview of Pricing Integration

The following products use Oracle Pricing setup and engine processing:
Complex MRO
Core Contracts
Demand Planning
Financial Services
Inter-company transactions
Logistics
Marketing
Order Capture/Quoting
Order Management
Procurement
Sales for Communications
Service Contracts
Service Core (Via Order Management)
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing Integration
Service for Communications

Trade Management
The following products use Oracle Pricing engine processing only:
iStore
TeleSales
Sales Online
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing Concepts

The pricing engine determines the selling price for products and services. It provides the final
selling price after retrieving the initial price from the price list or customer agreement. If this
order qualifies for any increases or decreases from the initial price, adjustments called
modifiers are applied to the price.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing Concepts (cont.)

When the sales order is entered, the pricing engine is called and reads the relevant price list or
pricing agreement. The appropriate modifiers are then applied to the base price and the final
selling price is sent to the sales order line or the calling application. The Adjustments window
displays the original price, applied modifiers, and the final price.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of the Pricing Engine

The pricing engine, which consists of a search engine and a calculation engine, works through
open APIs to provide the pricing results to the calling application. From the pricing request, the
pricing engine evaluates the appropriate modifiers and price lists, resolves incompatibility
issues, retrieves the list price, and calculates the unit selling price and adjustments. The search
engine receives pricing information from entities like price lists, modifiers, qualifiers,
formulas, products, and pricing attributes.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of the Pricing Engine
Overview of Pricing Security

In Oracle Applications, the basic level of security called functional security is implemented to
control users access to different windows, controls, and reports in the application.
Additionally, Basic Pricing has its own security setup called pricing security that works along
with functional security to provide a secure environment where the user can view, update, or
add pricing entities within a framework of authorizations and permissions. Pricing entities are
price lists, modifiers, and agreements. You can set up pricing security if you have the Oracle
Pricing Administrator responsibility.
Using pricing security, you can assign pricing entities to operating units, assign privileges, and
set security rules for pricing entities.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing Security
Overview of Price Lists

A price list is useful for maintaining the prices and other pricing details of products and
services. It serves as a repository of items with their related pricing details. You can retrieve a
price list and add/edit/delete related items and item categories. You can also use the price list to
define attributes for the products that determine the pricing action.
An item should have a price when it is entered on a sales order line. Once the pricing engine
populates the Unit Price field by deriving the price from the appropriate price list, the order can
be booked.
The header region of the price list consists of fields to store the price list name, the effective
dates of the price list, currency, multi-currency conversion, pricing controls, rounding factor,
and shipping defaults like freight terms and freight carriers.
You can enter one or more pricing lines to the price list. However you may add only one
secondary price list. Pricing attributes can also be used to determine the price in the price list.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Price Lists (cont.)

You can create as many price lists as needed by entering the information or copying existing
price lists. The price lists can be modified to include new items or groups of items. The list
price of the price list lines can be increased or decreased by either an amount or a percentage.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing Agreements

Oracle Pricing enables you to establish agreements with your customers, where you can define
prices, payment terms, and freight terms for items. Two types of agreements can be created:
Standard Agreements or Pricing Agreements.
Standard Agreements use standard price lists. Standard Agreements can be generic or
specific to a customer or customer family.
Pricing Agreements use Agreement Price Lists. These price lists are set up and maintained
through the Agreements window. Special terms and conditions can also be specified in the
Pricing Agreement that can then be defaulted in the sales order.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Pricing Agreements
Overview of Formulas
You can define prices as constant values or create formulas to provide pricing flexibility and
the ability to carry out complex computations. Some of the formulas that are created are based
on the following formula component types:
Factor List: You can apply different factor values for varying item attributes
Numeric Constant: Numeric value
Pricing Context: Grouping of pricing attributes, of which a maximum of 100 can be
incorporated in the formula
Product Context: Which contains only one attribute, item
You can create formulas in the Pricing Formulas window.
Basic Pricing provides seeded formulas, such as the Freight and Special Charges Formulas,
which includes the Cost to Charge Conversion formula and Cost to Charge Markup formula.
These formulas convert freight costs to freight charges.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Formulas
Overview of Qualifiers
A qualifier defines eligibility rules for modifiers and price lists. A qualifier can be a customer
name, a customer class, an order type, or an order amount that can span orders.
Though a qualifier may be set up independently, it comes into effect only when linked to a
modifier or a price list. Thus, the modifier that is set up and linked to a qualifier determines
who the price adjustment will affect as well as the amount that will change.
You can create qualifier groups to apply individual qualifiers as a set. When you group
qualifiers, they become a set, which allows for faster searching and setup.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Qualifiers
Overview of Modifiers
Modifiers determine the adjustments made to the list price. These are dependant on various
business factors such as the type of adjustments to make, the level at which the adjustments are
made, how the modifiers are qualified, how they are applied, etc. You can create three modifier
list types in Oracle Pricing:
Discount List
Surcharge List
Freight and Special Charge List
Modifier Line Types
The following modifier line types are available in Oracle Pricing:
Discount
Surcharge
Freight and Special Charges: Amount applied to the customer invoice for movement of a
shipment to a destination
Price Break: Only point price breaks are allowed in Basic Pricing modifiers. For example,
the following pricing decisions are:
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Chapter
CLASSROOM
If Item Quantity = 0-50, then discount = 5%

If Item Quantity = 50-100, then discount = 7%
If Item Quantity is between 100 and 99999999999, then discount = 10%.
So if the ordered item quantity is 110, then the discount applicable is 10%.
Types of Modifier Controls
A pricing event is a time in the process flow of the calling application at which it makes a call
to the pricing engine (analogous to an Oracle Workflow event); for example, Book Order in
Order Management.
A pricing phase is a user-defined group of modifiers that the search engine considers together
when applying them to pricing requests, for example, Phase 1: Line Adjustments.
Incompatibility: In any given level within the same phase, the system only allows one modifier
to be selected. The pricing engine may retrieve more than one modifier that meets the calling
request and can be applied. There are three methods to resolve incompatibilities within the
modifiers that the pricing engine retrieves:
Precedence
Best price
Exclusivity
Incompatibility Group: Each modifier has an incompatibility level. If there is more than
one modifier line with the same incompatibility level, the pricing engine selects the one
with the highest precedence. If there is more than one modifier with the highest
precedence in an incompatibility level, the pricing engine selects the modifier that
provides the best benefit to the customer.
In Basic Pricing, users cannot add additional phases or events, and incompatibility level and
buckets are defaulted.
Overview of Contexts and Attributes

There are three types of pricing contexts or groups in Basic Pricing:
Product
Pricing
Qualifier
Attributes are fields in the Standard or Quick Sales Orders window that can be used to
determine the price of an item. A context is comprised of a grouping of attributes. However,
the product context type has only one contextitem.
Through attribute management, the pricing engine evaluates all the values defined in the
qualifier and pricing attributes. Basic Pricing allows the creation and linking of only Pricing
contexts with a maximum of 100 attributes or less.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Contexts and Attributes
Overview of Freight and Special Charges Modifiers

Freight and special charges are applied to the customers invoice, charging for the movement
of goods from the supplier to the destination. Freight and special charges can be applied to the
order as a whole or to individual order lines. Costs that are associated with the shipment of
goods can be entered in the Sales Orders window or the Shipping Transaction window. Freight
charges can be automatically derived from the freight cost. The freight charge represents the
amount charged to the customer receiving the shipment. The freight charge can be equivalent
to the freight cost or to a greater amount such as a freight cost plus a markup.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Freight and Special Charges Modifiers
Overview of Basic Versus Advanced Pricing

Oracle offers two levels of pricing functionality: Basic Pricing and the separate enhanced
product, Oracle Advanced Pricing. While both levels of functionality share some similarities,
the licensed Oracle Advanced Pricing application extends the ability to adjust pricing.
Note: Additionally, Oracle Advanced Pricing enables you to derive prices from external
sources. For further information on Oracle Advanced Pricing, see the Oracle Advanced Pricing
User and Implementation Manuals.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Basic Versus Advanced Pricing

Price lists are essential to ordering products because each item entered on an order must have a
price. Price lists, like modifiers, consist of a header region where you can define general
information such as effective dates and currency, and price list lines where you can define item
and item category prices. For price list lines, you can define price breaks, and pricing
attributes.
Pricing sends customer list price, agreement price, and modifier information to orders being
entered manually in Order Management and to orders being entered in other Oracle
applications which can then be either imported or can use an API via Order Capture into Order
Management. Orders can proceed through the Order to Cash flow by being shipped, run
through the AutoInvoice program to Receivables and finally the accounting information can be
transferred to the General Ledger.
Basic Pricing Setup
Chapter
CLASSROOM
Overview of Price Lists (cont.)

The pricing engine receives and processes a pricing request and then supplies the base (initial)
price from the price list or customer agreement. The pricing engine then applies any modifiers,
calculates the selling price, and returns the result to the calling application.
Basic Pricing Setup
Chapter
CLASSROOM
Price List Information

Basic price list header information: Basic information includes the price list name,
effective dates, currency, pricing controls, rounding factor, and shipping defaults such as
freight terms and freight carrier.
Price list lines: Enter a line for each item and unit of measure combination you sell.
Price breaks: If the price of an item varies with the quantity ordered, you can define
bracket pricing or price breaks.
Pricing attributes: Pricing attributes control what is being priced or modified on a price list
or modifier list.
Secondary price list: The pricing engine uses secondary price lists when it cannot
determine the price for an item using the price list assigned to an order. Primary and
secondary price lists have the same currency.
Basic Pricing Setup
Chapter
CLASSROOM
Price List Information (cont.)

Effective dates: Price lists can have starting and ending dates. This allows you to prepare
price lists ahead of when they are valid and to ensure they will not be used until their start
dates.
Inactive price lists: You can temporarily or permanently inactivate a price list using the
Active check box. Once a price list is inactivated, you can still do the following:
- Query the inactive price list: To retrieve only inactive price lists, deselect the Active
check box; to retrieve only price lists that are active, select the Active check box, then
run the query.
- Update it.
- Base a formula on an inactive price list. The pricing engine does select inactive price
lists when doing a pricing request. Other applications can call an inactive price list
and use relevant information.
Currency: Select a base currency for the price list. If you have international sales, you can
use the multicurrency feature so you can have a single price list for multiple currencies.
When you use the multicurrency conversion feature, it is not necessary to create a price
list for each currency. As long as there is a multicurrency conversion list set up for the
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Chapter
CLASSROOM
price list, the currency on the order does not have to match the currency defined in the
price list.
Rounding Factor: You can define the number of places to the right or left of the decimal
point to which the pricing engine rounds prices from price lists and modifiers from
modifier lists:
- A negative rounding number such as -3 rounds the number of characters to the right
of the decimal point. For example, a rounding factor of -3 indicates rounding to the
nearest thousands so 1.1445 rounds to 1.145.
- A positive rounding number such as +2 rounds the number of characters to the left of
the decimal point. A rounding factor of 2 indicates rounding to the nearest hundreds
so 107 rounds to 100.
- If you enter zero, you affect nothing.
Creating a Price List
Basic Pricing Setup
Chapter
CLASSROOM
Price List Header

Order Management Super User, Vision Operations (USA) or Oracle Pricing Manager
responsibility.
(N) Pricing > Price Lists > Price List Setup
The pricing engine requires that all Items, Services, Models, Option Classes, and Options
should be selected and displayed on the price list.
You will need to set up a price list for each currency you use. The pricing engine will only
consider price lists that share the same currency as the pricing request. Therefore a sales order
placed in Yen will have to utilize a Yen-based price list.
The Round to field in the Price List window controls the rounding factor. Entering a positive
number affects positions to the left of the decimal while entering a negative number affects
positions to the right of the decimal. Example, -2 would round to the second decimal point. The
type of currency standard or extended which has to be defaulted on the price list is
determined by the Profile Option: QP: UNIT_PRICE_PRECISION_TYPE.
Secondary Price Lists
As with other areas of pricing, the Basic Pricing license controls available functionality to the
user. Basic Pricing allows one Secondary price list. A secondary price list allows the pricing
Basic Pricing Setup
Chapter
CLASSROOM
Price List Header
Basic Pricing Setup
Chapter
CLASSROOM
engine to look at more that one price list to determine the value of the sales order line. The
Pricing engine will look to the Secondary Price list if the requesting item and unit of measure is
not on the Primary Price list. A secondary price list is a price list you have defined previously.
Any price list has the ability to be used as a secondary price list.
Price Lists and Sales Order Defaults
Fields such as Payment Terms, Freight Terms, and Freight Carrier are available on the Price
List form. By defining the Order Management defaulting rules to use these fields from the
Price List window, you are able to default values directly into the sales order based upon which
price list has been selected for the order. For more information on Defaulting Rules, see the
Order Management Users Guide.
Note: Price Lists cannot be deleted, however a price list is made valid or invalid with the use
of its effective dates. Alternatively, selecting or deselecting the Active box also temporarily or
permanently makes the price list available or unavailable for use.
Price List Line

Order Management Super User, Vision Operations (USA)
(N) Pricing > Price Lists > Price List Setup (T) List Line
The Product Attribute enables you to enter one price per Item number, one price per Item
Category, or one price for All Items. If you have entered all three prices on a Price List, the
pricing engine will always select the Item Numbers price over the Item Categorys and the
Item Categorys over All Items.
The List line UOM is a required element of the validation process. The pricing request is for an
Item/UOM and only price lists that have the same item and unit of measure will be considered.
If you select the Primary UOM and you enter an item/unit of measure combination on a sales
order that is not on a price list, the pricing engine converts the unit of measure on the order to
the items primary UOM and then uses the UOM conversions to calculate the unit price.
Example: Price List setup: BB-2200, $6.00 each, Primary UOM is selected. Sales Order
request: BB-2200 1 dozen. Result: 12*6.00 = $72.00 unit price.
You can use the Precedence column to enter a number that the pricing engine uses to resolve
incompatibilities, for example, if it finds the different prices for the same item). A price list line
Basic Pricing Setup
Chapter
CLASSROOM
Price List Line
with a lower value in the Precedence column will have a higher precedence and will be
selected to price the line; for example a Precedence value of 1 is selected before 2.
You can select product, pricing, or qualifier contexts in the price list and select the
corresponding attributes that determine the pricing action. The product context contains only
one context type Item. The pricing context contains all the pricing attributes that have been
created and linked through the Attribute Management windows. The qualifier context allows
you to link your customer hierarchy to the pricing action and ensure that the customer
attributes also play a part in determining pricing of the item.
Basic Pricing Setup
Chapter
CLASSROOM
Price List Line (cont.)

You can enter an absolute value that represents the unit price of your price list line item. For
service program items you can either enter an absolute value that represents the unit price of
your service program, or you can enter a percentage value that represents the percentage of
another items price. When you are selling a service program on a sales order you are prompted
for the item that the service program will cover. The pricing engine finds the price of the
covered item and calculates the price of the service program by multiplying the percent times
the items unit price. It then takes that amount multiplied by the duration of the coverage.
Example of percent of other price:
Price List setup:
Service Programs item number is set up at 10% per year.
Sales Order request: Customer purchases 1 years worth of coverage for an Item which
sells for 1200.00.
The pricing engine calculates .10 * 1200 * 1 (year) = 120.00.
Formulas can be used to if you need an algebraic expression to calculate the selling price.
Basic pricing supports entering a formula name in the Static Formula field. Static Formulas
require that a concurrent program, Update Formula Prices, be run to populate the List Price
Basic Pricing Setup
Chapter
CLASSROOM
Price List Line
value prior to being used by the pricing engine. The price list supports both positive and
negative values. A negative value enables you to create an item which represent a restocking
fee. Enter this item on your price list with a negative value, then enter this item on your Return
order. When the pricing engine calculates the total value of the return it will subtract the
restocking fee thus lowering the value of the credit memo. The pricing engine evaluates Start
and End dates.
Basic Pricing Setup
Chapter
CLASSROOM
Secondary Price List

A secondary price list enables the pricing engine to look at more that one price list to determine
the value of the sales order line. The pricing engine reads from the secondary price list if the
requesting item and unit of measure cannot be found on the primary price list. (You must have
defined the secondary price list previously.) Any price list can be used as a secondary price list.
The pricing engine evaluates the precedence of the secondary price list along with the product
precedence on the list lines to determine the most eligible price list line.
Note: If you are using a sales agreement with a standard price list (and secondary price list)
attached, the secondary price list is evaluated if the item is not found on the primary price list
for the sales agreement.
Basic Pricing Setup
Chapter
CLASSROOM
Secondary Price List
Copy Price List

(N) > Pricing > Price Lists > Copy Price List
Copying a Price List enables you to create a new price list without adding lines manually to the
price list. You are able to utilize controls within the Copy Price List window to determine
which line items will be copied during the process.
One option is to include the copying of discounts (modifiers) when copying an existing price
list. This option will create new modifiers for each existing modifier that has the original price
list as either a modifier list qualifier or a modifier line qualifier. The new modifiers name will
be a concatenation of the original modifier plus a sequence number and the new price list will
have a modifier list qualifier. When creating the new price list you can specify any applicable
effective dates. Because the pricing engine will not use the new price list until its Effective
Date, you can create price lists before they are required in the application.
Basic Pricing Setup
Chapter
CLASSROOM
Copy Price List
Price List Maintenance: Overview
Basic Pricing Setup
Chapter
CLASSROOM
Manual Price List Updates

Order Management Super User, Vision Operations (USA) or Oracle Pricing Manager
responsibility.
(N) Pricing > Price Lists > Price List Setup (T) List Line
To manually change existing price lists, navigate to the Price List Setup window and find the
price list to maintain.
You can add or update the following:
Add or update Secondary Price List.
Add new list lines to existing Price Lists.
Change list line values.
Note: If you overwrite the existing value with a new one, the previous data is not retained
anywhere.
Maintain Pricing History by manually entering an end date on the list line value that is
being discontinued, then add a new line with the same item number and unit of measure
but with the new value. The new list lines start date must be greater than the end date of
the original line.
Basic Pricing Setup
Chapter
CLASSROOM
Manual Price List Updates
The pricing engine always validates the Price List and List Lines Effective Dates.
Basic Pricing Setup
Chapter
CLASSROOM
Adjust Price List

(N) Pricing > Price Lists > Adjust Price List
Use the Adjust Price List program to mass update your price list values. Note that using the
Adjust Price List program to change values does not create a history record. You will not be
able to recapture the old price. If you need to retrieve expired prices, do not use Adjust Price
List option. This option enables you to increase or decrease the current price by a percent or an
amount.
Elements you can update:
Optionally adjust only a Range of Items.
Optionally adjust only an Item Category. Many companies adjust their Items selling
prices annually or when the product cost has drastically changed. This is often done by
Product Family. If you set up an Item Category to represent the Product Family you can
quickly markup the subset of Price List Lines.
Optionally adjust only Items with a specific Item Status.
Basic Pricing Setup
Chapter
CLASSROOM
Adjust Price List
Any time a new line is added to a price (manually, copy, or Add Items) the system
populates the Creation Date with the system date.
Use the Creation Date to select only items that were added on a given date. This is very
helpful when you have used the Add Items to Price List program to add new items At
Cost. This enables you to markup the new items while leaving the older lines untouched.
Use the Copy program to create as many price list as your business procedures support
and then Adjust the Price List Value by a Percent or an Amount.
Basic Pricing Setup
Chapter
CLASSROOM
Add Items to Price List

(N) Pricing > Price Lists > Add Items to Price List
The Add Items to Price List window enables you to quickly add items to an existing price list.
When using the Add Items to Price list feature, you can use a number of control attributes
within the window to identify which items should be added to the list. These options include
addition by the range of item numbers, item category, and item status. You can only add items
from this window to one list at a time. To add all of the items that have a category of Shippable
to five different price lists, use the Add Items to Price List window five times, to add the
Shippable category to each price list individually.
Using the Set Price Equal to Cost From option, you can retrieve the current cost of the item by
selecting an inventory organization that stores item costs; the current cost retrieved is stored in
the same price list as the item.
Basic Pricing Setup
Chapter
CLASSROOM
Add Items to Price List (cont.)

(N) Pricing > Price Lists > Add Items to Price List
You can use the Add Items to Price List program to add Product Lines to existing price lists.
When new product lines are added to your inventory, assign unique Categories to them, so that
you can add them to your existing price lists using the Add Items feature by Item Category.
If you are in an industry where your selling prices are set at a given Percent over cost, add your
items at cost with a Future Effective Start date; then use the Adjust Price List program to
markup the new items.
Note that the Add Items to Price List program does not overwrite any list lines that have the
same Item Number and Unit of Measure as the Inventory Item Number and its Primary unit of
measure. This means that you cannot accidentally overwrite current valid values.
Basic Pricing Setup
Chapter
CLASSROOM
Use modifiers to adjust the list price. Select from the following modifier types in basic pricing:
Discounts, Surcharges, Point Price Breaks, Freight and Special Charges.
Create Order Level Modifiers to apply modifier to all order lines.
Create Line Level Modifiers to apply modifier to only the current line.
Using qualifiers with modifier lists can improve processing time because the pricing engine
selects only those modifiers that are applicable to the current pricing request. By creating
qualifiers for your modifier list and lines, you can create rules that will be automatically
applied by the pricing engine.
From the order or order line you can use the Action View Adjustments to see the details of
modifiers that were applied automatically by the pricing engine or to apply manual discounts.
Also, if the modifier is overridable, you can use this window to enter new values or override
the pre-defined values.
Basic Pricing Setup
Chapter
CLASSROOM
Creating Modifier Lists

Header level details such as currency are applied to the modifier lines.
Basic Pricing Setup
Chapter
CLASSROOM
Creating Modifier Lists (cont.)

(N ) Pricing > Modifiers > Modifier Setup
The Modifier Type restricts the kinds of lines that can be attached. Basic Pricing supports three
types of Modifier Lists:
Discounts create a negative price adjustment.
Surcharges create a positive price adjustment.
Freight and Special Charges (including Handling charges) create a charge amount.
Elements within the Modifier List window:
The Active check box allows the modifier list to be evaluated by the pricing engine.
The Start and End Dates define when the modifier list is effective.
The currency on the modifier list must match the currency on the pricing request.
Use a combination of qualifiers to establish pricing rules that will be respected by the
pricing engine.
Modifiers can remain price list independent or you can use your price lists as qualifiers.
Basic Pricing Setup
Chapter
CLASSROOM
Adding Modifier Lines

You can select a modifier line type to define the type of price adjustment, benefits, or freight
and special charges that the pricing engine applies to pricing requests. The modifier list type
you select when creating the modifier determines the modifier line types that you can use. For
example, if you select the Freight and Special charge List as the Modifier List Type in the
Modifier List region, you can select only Freight/Special Charge at the modifier line level.
Basic Pricing Setup
Chapter
CLASSROOM
Adding Modifier Lines
Creating Modifier Lines

(N) Pricing > Modifiers > Modifier Setup (T) Modifier Summary
The modifier number is a unique alphanumeric number that identifies a modifier list. Levels
for modifier lines:
If you create an Order Level modifier, the adjustment will be applicable to all lines on the
order. A Freight Charge is applied only once to the Order Header.
Line Level modifiers adjust only the pricing requests line.
Types of modifier lines:
Define Discounts to decrease the price list price.
Define Surcharges to increase the order price.
Create Freight and Special Handling charges to meet your business requirements.
Price Breaks can either be discounts or surcharges. You can create price breaks based on
order quantity or amount.
Elements when defining a modifier line:
Basic Pricing Setup
Chapter
CLASSROOM
Creating Modifiers Lines
Basic Pricing Setup
Chapter
CLASSROOM
The pricing engine uses the Start and End Dates to establish effective dates for the
modifier line.
The Print on Invoice feature is controlled by a profile option: OM: Show Discount Details
on Invoice. If it is selected the discounts will print on your invoices. Otherwise, the net
amount is passed to Receivables.
Select the Automatic check box if you want the pricing engine to apply the modifier to all
qualified orders and order lines.
To create Manual discounts, deselect the Automatic check box.You can use the Action >
View Adjustments in the Sales Orders window to apply manual modifiers.
To avoid changing the Selling Price calculated by the pricing engine, deselect the
Override check box.
Some businesses have such a flexible selling price where they need to overwrite the
calculated price with a new price. To do this, create a modifier line and deselect the
Automatic check box and select the Override check box. Optionally, restrict the modifier
to a specific Item number or item category by using the Product Attribute.
If multiple discounts are eligible to be applied, then the pricing engine applies the modifier that
gives the lowest price to the customer (incompatibility resolution using best price rather than
precedence).
View your Discounts and Surcharges from the Sales Orders Action View Adjustments
menu. View your Freight and Special Handling charges from the Action Charges menu.
Modifier Line Examples

You can create the following pricing modifier line types in Basic Pricing:
Discount: When the seller offers a discount on the list price of the item. The discount can
be a percent, lump sum, amount, or new price.
Surcharge: The price of the item attracts an additional charge. As with discounts, the
surcharge can be a percent, lump sum, amount, or new price.
Freight and Special Charges: These are charges applicable during the shipping of items.
Price Breaks: Price Break modifiers are applied only at the line level. In this type of
modifier, when the quantity or amount falls within a particular price bracket, the
corresponding price is applied.
Basic Pricing Setup
Chapter
CLASSROOM
Modifier Line Examples
Modifier Types
The table shows modifier list types and the line types that can be associated with each modifier
list type: discounts, surcharges, and freight and special charges. The check mark (3) indicates
that the line modifier is available for the list modifier. The (2) indicates that the line modifier is
not available for the list modifier.
Basic Pricing Setup
Chapter
CLASSROOM
Modifier Types
Discount Modifier
A discount can be a percentage of a basic value. For example, a corporate customer can be
offered a 15 percent discount. A discount can also be for a fixed amount. For example, a
discount of $10 can be offered to a customer who spends more than $300.
Scenario 1
If a customer is either a preferred customer or a customer who spends more than $150, they
receive 10 percent off the order.
Scenario 2
For any 10 compact discs purchased by April 2000, the customer receives $2 off.
Basic Pricing Setup
Chapter
CLASSROOM
Discount Modifier
Price Break Modifiers: Point Breaks

Applies a variable discount or surcharge price adjustment to a pricing request that meets the
condition of the specified price break. The example above displays the use of a point break
header: Item A qualifies for a 10 percent discount because the total value of 150 falls between
the 100 to 200 price break bracket.
Basic Pricing Setup
Chapter
CLASSROOM
Price Break Modifiers: Point Breaks
Surcharge Modifier
A Surcharge modifier increases the cost of an item, and can be applied using the following
application methods:
Percent
Amount
Lumpsum
New Price
A surcharge can be used to apply taxes, handling charges, and other special costs in the price.
Scenario 1
Customers in the National Accounts territory who spend less than $1000 per order receive a 2
percent surcharge.
Scenario 2
Any customer placing a rush order (delivery required within two days) has to pay a $50
surcharge for special handling.
Basic Pricing Setup
Chapter
CLASSROOM
Surcharge Modifier
Qualifier Overview
A qualifier consists of one or more conditions that define eligibility for a particular price or
benefit. Qualifiers are an intrinsic part of pricing logic that enable you to create eligibility rules
for modifiers. You can use grouping numbers to create AND and OR conditions between
different qualifier conditions:
If the Grouping Numbers are the same, AND logic is applied.
If the Grouping Numbers are different, OR condition is applied.
If the Grouping Number is 1, then that qualifier is always used with an AND condition
with the other qualifiers. The qualifier with a grouping number of 1 is mandatory and
must be satisfied, irrespective of other qualifiers.
Basic Pricing Setup
Chapter
CLASSROOM
Qualifier Overview
Example of Qualifier Hierarchy

Qualifier attributes represent values that can be compared to values on your sales order. The
pricing engine evaluates these qualifier attributes to determine which modifier list and modifier
lines should be applied to the order. Basic Pricing limits the seeded qualifier contexts for both
the modifier list and the modifier line.
Qualifiers for Modifier Lists
Customer:
- Customer Name
- Bill to
- Ship to
- Customer Class
Modifier List: Price List
Qualifiers for Modifier Lines
Customer:
- Agreement Name
- Agreement Type
Basic Pricing Setup
Chapter
CLASSROOM
Example of Qualifier Hierarchy
Order:
- Customer PO
- Order Type
Note: When a qualifier has a grouping number 1, it implies that the qualifier will be taken as
mandatory in comparison to other qualifiers.
Basic Pricing Setup
Chapter
CLASSROOM
Using Qualifiers with Modifier Lists

Create qualifiers to define eligibility rules for the modifier list or lines.
Qualifier Contexts: Flattened hierarchies where similar qualifying attributes can be
grouped into logical categories. The specificity is indicated by precedence.
Qualifier Attributes: Specific attributes associated with a context that define eligibility
criteria for a benefit or price. For example, the Customer context includes the following
attributes: Customer class (defined in RA customers); Site; and Customer Name.
Value From: Defines the specific value for the selected qualifier attribute. For example,
for the qualifier attribute Customer Name, you could select the customer name XYZ
Corporation (the qualifier value).
Basic Pricing Setup
Chapter
CLASSROOM
Using Qualifiers with Modifier Lists
Freight and Special Charge List Modifier

Use this modifier to apply freight costs to the order total. For example, any customer who
places an order for less than $500 pays a freight charge of 20 percent of the order cost.
Basic Pricing Setup
Chapter
CLASSROOM

Freight and special charges are costs associated with the shipment of goods. You can use
Freight and Special Charge List modifiers to apply different freight charges to an order or line
and thereby, increase the selling price. Additionally, you can enter the freight and shipping
costs in Shipping Execution and have the Freight and Special Charge List modifiers convert
them into charges in Order Management. The freight charge may be equal to the freight cost,
or it could be the freight cost with a markup.
Basic Pricing Setup
Chapter
CLASSROOM
Seeded Freight Charges
Basic Pricing Setup
Chapter
CLASSROOM
Setting Up Freight and Special Charge List Modifiers

Using Freight and Special Charge List modifiers, you can apply charges to sales orders either
automatically or manually. Here is an example of how to set up automatic order level charges
using modifiers:
1. Select Freight and Special Charge List as the type of modifier.
2. In the Modifier Summary tab, enter the modifier lines, specifying that the modifier is to be
applied at the order level.
3. Set up header level qualifiers that will be applicable at the list level. You can define the
qualifier to accept only orders with Freight Terms of Prepay and Add.
4. When you enter an order with Freight Terms of Prepay and Add, the charges are applied
to the order automatically and you can view them in the order window.
Please note that this is only one example of a type of setup, various other ways of setting up
Freight and Special Charges Modifiers are possible.
Basic Pricing Setup
Chapter
CLASSROOM
Setting Up Freight and Special Charge List Modifiers
Overview of Price Books

A price book is a pricing report that displays item list and net prices (for a specific customer)
based on a specific pricing date. Within the price book, you can view details of the list price,
discounts, surcharges, price breaks, and freight and special charges. The price book supports
formula-based prices, and you can view price break and pricing attribute details.
Freight and special charges: Although freight and special charges do not affect the unit selling
price in Basic Pricing, they will affect the net price in the price book.
Pricing buckets: If pricing buckets have been defined for any modifiers, the modifiers will be
displayed in the order of the pricing buckets, with the null bucket modifiers displayed last
From the online view, you can view any price break details or any pricing attributes used in the
price calculation. Pricing errors (such as missing pricing attribute for formula processing or
duplicate prices) are also displayed on a separate page.
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Chapter
CLASSROOM
Price Book Example 1
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Chapter
CLASSROOM
Benefits of Price Books
Basic Pricing Setup
Chapter
CLASSROOM
Price Book Implementation
Basic Pricing Setup
Chapter
CLASSROOM
Implementation Steps: Setting Key Profile Options

QP: E-mail - From Address
You need to set up the profile option QP: E-mail - From Address to specify the sender's e-mail
address for any e-mails that are sent from the price book feature. When the price book is emailed, the recipient can identify and respond to the senders return e-mail address. There is no
default value for the profile option and can be updated at the Site and User level.
Important: Publishing a price book to a printer or as an e-mail attachment and creation of the
View Document (formatted document) is dependent on the availability of the Delivery Server
Component of the Oracle XML Publisher (XDO) product.
QP: External Default Pricing Perspective
This profile option sets the default pricing perspective for all external users. The value defaults
to the Pricing Perspective field in the Create Price Book page. This profile can be set at the site
or user level and the default value is Order Management Order.
Basic Pricing Setup
Chapter
CLASSROOM

QP: Internal Default Pricing Perspective
This profile sets the default value for the pricing perspective for all internal users using the
price book feature. The values can be applications like Oracle Order Management or Oracle
Purchasing that request information from the pricing application. The Pricing Perspective field
in the Create Price Book page displays the default value; however, an internal user can
override this value by selecting a different pricing perspective. This profile can be set at the site
level only and default value is Order Management Order
Note: Oracle Advanced Pricing is not one of the valid values for this profile option.
QP: Pricing Perspective Request Type
This profile option is used for the price book feature to map the Pricing Perspective to the
Request type calling the price book. It can be set at system administrator site and system
administration application levels. The default value at the site level is Order Management
Order.
Note: External users cannot view or change the Pricing Perspective field. The value PO
(Oracle Purchasing) is valid for internal users but not external users.
Basic Pricing Setup
Chapter
CLASSROOM
Implementation Steps: Verifying Pricing Parameters

(N) Oracle Pricing Manager > Setup > Attribute Management > Pricing Transaction Entity
Associations
(N) Oracle Pricing Administrator > Oracle Pricing Administrator Setup : Parameters>
Parameter Values
The next setup step is to verify the values for the pricing parameter Price Book Pricing Events.
Based on the values specified in the profile QP: Pricing Perspective Request Type, each calling
pricing perspective has an associated request type. The Price Book Pricing Events parameter
determines which pricing event or events are used for each request type to call the pricing
engine to generate a price book.
Multiple events may be entered separated by commas; for example, BATCH, BOOK. Seeded
values are:
CMRO: Batch
Order Capture: Batch
FTE: FTE Price Line
Intercompany: IC Batch
Basic Pricing Setup
Chapter
CLASSROOM
Implementation Steps: Verifying Pricing Parameters
Demand Planning: Batch

Contracts: Batch
Contracts for Service: Batch
Order Management: Batch
Purchase Order: PO Batch
Basic Pricing Setup
Chapter
CLASSROOM
Implementation Steps: Setting Up the Default Printer

You have the option of publishing the price book to a printer. The default printer you define in
the configuration is used if no printer name is specified when publishing the price book.
To define the default printer, add the printer for your site to the Oracle XML Publisher
Delivery Manager configuration and specify it as the default entry.
Basic Pricing Setup
Chapter
CLASSROOM
Implementation Steps: Setting Up the Default Printer
Implementation Steps: Setting up Oracle XML Publisher

Using Oracle XML Publisher, you can publish your price books in a variety of formats such as
PDF, RTF, and EXCEL (XLS). The Delivery Server Component of the Oracle XML Publisher
(XDO) product (available with XML Publisher 5.0 and newer versions) is required to send the
price book to a printer or as an e-mail attachment. Use the seeded XML templates to generate
your price books, or create additional templates depending on the desired publishing option (email or print) and the output format [EXCEL (XLS), PDF, RTF]; for example, you may want a
separate template for print versions and another for e-mail.
Note: To send the price book as an e-mail attachment, you also need to configure the e-mail
server in XML Publisher. Oracle XML Publisher is required to create and maintain XML
Publisher templates that define the layout for the published price book.
Basic Pricing Setup
Chapter
CLASSROOM
Implementation Steps: Setting up Oracle XML Publisher
Creating a Price Book

You can create price books to generate prices for a single item, an item category, all items, or
items within a specified price lists. The prices generated in the price book are based on the
pricing perspective. The value for the operating unit defaults from the Multi-Org Access
Control (MOAC) setup.
The pricing perspective mimics the calling application so as to simulate prices coming from an
order, service contract, or purchase order. An internal user can edit the value but an external
cannot view or edit it. These prices are currency specific, but the price book does handle multicurrency (price list) conversions supported in price lists.
Note: All item/UOM combinations will be priced.
You can set the pricing effective date for a past date, current date, or future date. Information
in the Price Calculation Criteria will be input parameters to generate the price book. Currency,
Quantity, and Customer are mandatory fields. The quantity will always default to 1, but can be
updated. You can specify a price list, pricing agreement, or sales agreement as a starting point
for the price book. The pricing engine will always perform a search across all the valid pricing
setups to derive the price.
Basic Pricing Setup
Chapter
CLASSROOM
Creating a Price Book
Creating a Price Book: Defining General Price Book Criteria

Select details about the price book including the name and pricing perspective. The value you
select in the Product Criteria field determines what items will appear in the price book. You
can select a single item, item category, all items, or price list. If price list is selected, all items
and UOM combinations within the price list will get priced, but the final list price may be
derived from a different price list.
Notes:
The Operating Unit value defaults from the Multi-Org Access Control (MOAC) setup.
An internal user can edit the pricing perspective value but an external cannot view or edit
it.
Basic Pricing Setup
Chapter
CLASSROOM
Creating a Price Book: Defining General Price Book Criteria
Creating a Price Book: Defining Price Calculation Criteria

The price calculation criteria includes values such as currency, date, customer, and quantity,
that the pricing engine requires to generate price books. Optionally, you can enter a value in
the Pricing Basis field to give the pricing engine a starting point from which to look for prices.
Currency: Prices are currency specific, but handles multi-currency (price lists) conversions
supported in price lists.
Pricing effective dates: Past date, current date, or future dates.
Pricing Basis: Agreement, sales agreement, or price list.
Additional criteria: Define further qualities for price book such as qualifiers, pricing
attributes. These attributes may determine if a specific price or modifier will be applied. If
you do any formula-based pricing using pricing attributes, enter those attributes here.
Basic Pricing Setup
Chapter
CLASSROOM
Creating a Price Book: Defining Price Calculation Criteria
Creating a Price Book: Selecting Price Book Publishing Options

You can publish the price book using the following options:
Send Email: Specifies the e-mail addresses to which the price book will be sent. You can
enter multiple e-mail addresses, separated by commas.
Send to Printer: Enter the name of the printer where the price book is to be printed. If no
printer is specified, the default printer defined in the XDO configuration file is used.
View Document: Select a Template and Document Type to view the document online.
Note: The e-mail and printer server must be configured properly to use the e-mail and printer
publishing options. For more details on publishing options, please refer to the XML Publishing
documentation.
Basic Pricing Setup
Chapter
CLASSROOM
Creating a Price Book: Selecting Price Book Publishing Options
Price Book Publishing Templates

In XML Publisher, you can create and maintain price book templates. You can select the
following seeded templates to enable output formats of PDF, RTF, and Excel:
Price Book Details report: Shows all the items in their respective categories with list price,
net price, and all modifiers.
Price Book Errors report: Provides information on any pricing error that occurred during
the generation of the price book.
Price Book Summary report: Displays an items list and net price. To generate the View
Document, a template and template type must be selected.
You may need to create multiple templates depending on the desired publishing option (email or print) and the desired output format (Excel, HTML, PDF, RTF).
Basic Pricing Setup
Chapter
CLASSROOM
Price Book Publishing Templates
Price Book Publishing: Document Types
Basic Pricing Setup
Chapter
CLASSROOM
Generating and Publishing Price Books

In the background, two concurrent requests are completed to generate or republish a price
book. The first concurrent request will create the price book header and items. The second
concurrent request calls the pricing engine to get the list price, net price, and associated
modifiers.
Note: The completed price book can be viewed only after this concurrent request is completed.
Basic Pricing Setup
Chapter
CLASSROOM
Generating and Publishing Price Books
Viewing Price Book Details Online

The price book determines all the items to be priced and then displays each item in their
respective item category. If an item belongs in more than one category, then the price book will
display multiple categories. For an item, you will see the price list used to derive the list price.
If there are any line level discounts, surcharges, price breaks, or freight and special charge
modifier, then these will be displayed below the list price line. If pricing buckets have been
defined for any modifiers, the modifiers will be displayed in the order of the pricing buckets,
with the null bucket modifiers displayed last. Although freight and special charges do not
affect the unit selling price in pricing, they will affect the Net Price in the price book.
From the online view, you can view any price break details or any pricing attributes used in the
price calculation. Pricing errors (such as missing pricing attribute for formula processing or
duplicate prices) are also displayed on a separate page.
Basic Pricing Setup
Chapter
CLASSROOM
Basic Pricing Setup
Chapter
CLASSROOM
Maintaining Price Books

Responsibility: Oracle Pricing User
(N) Home > Reports
You can maintain price books on the Price Book Main page > Reports tab.
You can search for price books using the Simple Search. To add additional search criteria,
click the Show More Search Options link. You can sort your search results by Price Book
Name, Customer, or Price Effective Date of the price book. You can also delete one or more
price books.
Basic Pricing Setup
Chapter
CLASSROOM
Maintaining Price Books
Republishing Price Books

If you decide to republish a price book, the price book is not regenerated meaning the data in
the price book will remain the same. All the publishing options (e-mail, print, XML Message,
View Document) are available and this process will override existing documents or templates.
Basic Pricing Setup
Chapter
CLASSROOM
Republishing Price Books
Viewing Errors
Errors in your price book will be indicated in the Search Results and within your price book.
There is also a seeded template to view pricing errors.
Basic Pricing Setup
Chapter
CLASSROOM
Viewing Errors
Profile Options in Basic Pricing

The system administrator sets up the pricing profile options that determine how the application
accesses and controls data. The level at which the profile options can be set are user,
responsibility, application and site. The permissions for setting the profile options are View,
View and Update, No Access. The Required column determines if the profile option requires a
value or not. If it is Required, then you must provide a value. If it is Optional, you may leave it
blank. The Default Value column allows you to provide a default value for the profile. The
following are some common profile options used in Basic Pricing:
Profile Option
Required
Default Value
------------------------------------------QP: Allow Duplicate Modifiers
Required
Yes
QP: Blind Discount Option
Required
Yes
QP: Debug
Optional
Request Viewer Off
QP: Inventory Decimal Precision
Required
10
QP: Item Validation Organization
Required
No Default
QP: Negative Pricing
Required
No Default
Basic Pricing Setup
Chapter
CLASSROOM
Profile Options in Basic Pricing
Blank
Yes
Yes
Off
Blank
Blank
Individual : =
round(list price) +
round(adj)
QP: Set Request Name
Required
Blank
QP: Unit Price Precision Type
Required
Standard
QP: Valueset Lookup Filter
Optional
Yes
QP: Verify GSA Violations
Required
No
Please refer to the Oracle Order Management Implementation Manual for further details.
Basic Pricing Setup
Chapter
CLASSROOM
QP: Price Rounding

Required
QP: Qualify Secondary Price Lists
Optional
No
QP: Return Manual Discounts
Optional
QP: Satisfied Qualifiers Option
Optional
QP: Security Control
Optional
QP: Security Default Maintain Privilege Required
QP: Security Default ViewOnly Privilege Required
QP: Selling Price Rounding Options
Optional
Summary
Basic Pricing Setup
Chapter
CLASSROOM

Basic Pricing Setup
Chapter
CLASSROOM
Chapter 9
Overview of Shipping Execution
Chapter
CLASSROOM
Overview of Shipping
Execution

Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Shipping Execution Flow

After a sales order has been booked, the sales order lines must complete all workflow activities
leading up to the shipping activity. Two typical preceding workflow activities are Schedule Line and Ship - Line, Manual .
Schedule Line
Scheduling the line makes the order lines demand visible to Oracle Inventory for planning.
It also sets the Shipment Schedule Date.
Create Supply
Variety of subflow paths can be taken within Create Supply Line based on the type of item
shipped. They are as follows:
Configurable Items: Configurable items must complete the Create Supply activity which
takes an order line through a build cycle. The final assemblies that are completed out of
Oracle Work in Process are received into Oracle Inventory as Reserved for a specific
customers order.
Drop ship: Drop ship order lines must complete the Create Supply activity too. After a
Purchase Requisition has been passed to Oracle Purchasing the order line advances to the
Shipping Activity.
Chapter
CLASSROOM
Shipping Execution Flow
Chapter
CLASSROOM
Standard Shippable Items: Standard shippable items dont need to perform any of the
Create Supply activities so directly advance to the Shipping activity.
Shipping
What happens when the order line reaches Ship Line workflow activity?
Oracle Order Management calls Oracle Shipping Execution APIs to indicate that a line is
Ready to Release.
The sales order line status is changed to Awaiting Shipping. Order lines that are awaiting
shipping have corresponding records in Oracle Shipping Execution module called
Delivery Lines.
Pick Release process creates move orders to move items to the staging location and create
reservation in Oracle Inventory.
From the staging area shipments are weighed, packed and shipped.
Deliveries are Ship Confirmed out of the staging location.
When a delivery is Ship Confirmed, Oracle Shipping Execution calls OM APIs to
communicate the event, triggering the line flow to move forward.
Delivery and Delivery Lines

Delivery Lines
When sales order lines are booked or scheduled in Order Management, associated delivery
lines are created in Oracle Shipping Execution.
Delivery
You can either manually or automatically group delivery lines to create a delivery. If a delivery
is auto-created, the delivery lines are grouped together by the mandatory default criteria, Ship
From Location and Ship To Location. However, additional grouping criteria can be included
such as:
- Customer
- Freight Terms
- FOB Code
- Intermediate Ship To Location
- Ship Method
Chapter
CLASSROOM
Delivery and Delivery Lines
Trips and Stops

Trips
A trip is an instance of a specific freight carrier departing from a particular location containing
deliveries. A trip is carrier specific and contains at least two stops such as the pick-up stop and
drop-off stop. Trips can be created automatically or manually.
Stops
A stop is a point along the route of a trip where goods are either picked up, dropped off, or
both.
Chapter
CLASSROOM
Trips and Stops
Delivery Leg
A delivery leg is synonymous to bill of lading and consists of at least two stops. A bill of
lading is an agreement between the shipper and carrier acknowledging receipt of goods
shipped. The bill of lading has all the details specifying the terms of delivery. A delivery might
consist of several delivery legs to reach its final destination.
Chapter
CLASSROOM
Delivery Leg
Containers/LPNs
License Plate Numbers (LPNs), also known as containers, are used for packing delivery lines.
You can create containers without assigning them to a delivery. This is useful if you want to
create multiple containers of the same type then pack them with unassigned delivery lines.
Chapter
CLASSROOM
Containers/LPNs
Pick Release
Pick release is the process of finding and releasing eligible delivery lines that meet the release
criteria that you specify. Pick release creates move orders for picking from inventory. The
release criteria is defined based on your business requirements. You customize the release
criteria by defining the following:
Release Rules: The release rules identify which delivery lines should be considered for
pick release and the picking operations that should be performed on the selected lines.
Release Sequence Rules: The release sequence rules define the order in which eligible
picks are allocated inventory.
Pick Slip Grouping Rules: The pick slip grouping rules define how released order lines
are grouped on the pick slips for ease of picking.
Chapter
CLASSROOM
Pick Release
Move Orders
A move order is a request to transfer materials from a subinventory to a staging location. The
pick release process creates move orders pre-approved requests for subinventory transfer. The
move order consists of move order lines that must be moved from the subinventory to the
staging location. To release the move order lines, the lines must be allocated with the materials
from the subinventory. Oracle Inventory picking engine fills in the move order lines with the
transaction details. It also places a high-level reservation on the material if no reservation
previously exists. This process is called allocation.
Staging Location
A staging location is the destination subinventory where the materials are deposited after
picking. Material deposited in the staging location is then in position for its next step, which is
ship confirm. Each organization must designate at least one staging subinventory. In a
warehouse, the staging location is physically located typically near the shipping dock. Staging
subinventories should be reservable. Each pick release batch created at pick release will have
the same destination staging subinventory.
Chapter
CLASSROOM
Move Orders
Pick Confirmation
Pick confirmation is a process that performs the transfer of materials from the source
subinventory location to the staging location. The transfer is performed based on the allocation
made by Oracle Inventory to the move order lines. Pick confirmation automatically transfers
the high level reservation to an allocated reservation (including lots, subinventory, and
locators) in the staging location.
Chapter
CLASSROOM
Pick Confirmation
Ship Confirm
Ship Confirm is the process of confirming that items have been shipped from the staging
location. Delivery lines must be in the Staged/Pick Confirmed status to perform Ship Confirm.
During Ship Confirm you can perform the following actions:
Backordering: Backordering when only a partial quantity of items that were pick released
require shipping. When a delivery line is backordered, the delivery line is split into two
delivery lines. The original line quantity is the detailed quantity. The new line quantity is
the difference between the requested quantity and the detailed quantity.
Consolidating Backorders: Consolidating backorders is an automatic process that
combines several backordered delivery lines having the same source line, back into one
delivery line. Consolidating Backorders is performed during Pick Release, Cycle Count,
or Ship Confirm. When a backorder occurs, Oracle Shipping Execution searches for the
existing backorder delivery lines for a particular source line.
Note: To consolidate backorders the Consolidate Backorder Lines field in the Global
Parameters window must be selected.
Making Items Non-Reservable: Making items non-reservable places a reservation on the
items such that they are not available for other delivery lines. While making the items
Chapter
CLASSROOM
Ship Confirm
non-reservable you must specify the subinventory and stock locator to pick the items
from. If the items are serial controlled, lot controlled, or revision controlled you must
specify the respective details while making items non-reservable.
Models: You can ship Model items non-proportionately, for example:
- You ship all the components but not in the correct proportion
- You do not ship all of the components
Chapter
CLASSROOM
Automated Shipping Process

The automated shipping processes will be useful when the shipping personnel rarely alter or
modify the attributes of the shipment. The automated shipping process can be used to perform
the following automatically:
Pick Release: The pick release process can be automated to perform delivery creation,
pick selection, pick allocation, and pick confirmation.
Packing: You can run Auto-Pack Deliveries - SRS to run the packing process
periodically.
Ship Confirm: You can run Automated Ship Confirm SRS to run the ship confirm
process periodically.
One Step Shipping performs Pick Release, Pack, and Ship Confirm all in one go.
Chapter
CLASSROOM
Automated Shipping Process
One Step Shipping

One step Shipping involves picking and shipping, or picking, packing, and shipping of one or
more deliveries or delivery lines. When you perform one step shipping you achieve the
following:
Auto create deliveries for delivery lines, if delivery lines are not associated with a
delivery.
Pick release and pick confirm all delivery lines assigned to the deliveries. This includes
the deliveries that were autocreated.
Auto pack all delivery lines assigned to the deliveries that are in the Staged/Pick
Confirmed status.
Note: To automatically pack all delivery lines into LPNs,
you must set the autopack level for your organization as Yes
or Autopack Master in the Shipping Transaction tab of
Shipping Parameters window. For more information, see the
lesson titled Shipping Transaction Parameters slide.
Note: Container-load relationship should be defined for the
delivery line items
Chapter
CLASSROOM
One Step Shipping
Ship confirm all delivery lines assigned to the deliveries that are in the Staged status and
which does not require assignment of serial numbers.
Auto create trips, if trips and stops are not manually created for the delivery lines.
Note: If pick, pack, and ship process is not successful for even one delivery line of a delivery,
the one step shipping cannot be performed on the entire delivery.
Note: To ship confirm from the Shipping Transactions form, the organization to which the
sales order belongs should be attached with a ship confirm rule.
Chapter
CLASSROOM
Note: To automatically ship confirm, you must assign a ship

confirm rule to your organization. You can assign the same
in the Shipping Transaction tab of Shipping Parameters
window. For more information, see the lesson titled
Shipping Transaction Parameters slide.
Shipping Transactions Form

(N) Shipping > Transactions > Query Manager (Perform a search in the Query Manager
window. The search results are displayed in the Shipping Transactions form.)
You can use the shipping transaction form to plan, execute, and view all aspects of the
shipping process. The user interface is composed of two elements; the Query Manager and the
Data Manager. You can use extensively the Oracle folder and tree capabilities.
Chapter
CLASSROOM
Shipping Transactions Form
Query Manager
(N) Shipping > Transactions > Query Manager
The Query Manager is a window used to search and save queries created on the shipping
entities. You create customized queries by entering your search criteria and saving them. You
can use the saved query for future searches. The queries are classified into the following:
Personal Query: Queries you save for your personal use. This query is not available to
other users.
Public Query: Queries you save and share with other users. This is very useful if you
want to centrally manage the queries.
Temporary Query: Queries that are not used frequently such as those that you use only
once. These are queries which are not used frequently. Temporary queries are not saved
and are valid for that session only.
Chapter
CLASSROOM
Query Manager
Data Manager
The data manager is a part of the Shipping Transactions form. You can perform the following
using the data manager:
Create or modify data pertaining to shipping entities
Plan shipping entities
Perform shipping operations such as Pick Release and Ship Confirm
Generate reports
Chapter
CLASSROOM
Data Manager
Quick Ship Window

(N) Shipping > Quick Ship
Quick Ship enables you to enter minimum requirements and process a shipment.
The Quick Ship window provides the following features:
Visibility to trips, deliveries, and delivery lines in the same window
Ship confirm multiple deliveries at the same time
Change ship quantities and also specify the inventory controls for each delivery line
View and resolve the shipping exceptions for the delivery, trip and delivery lines
Customization of the display of fields, initial view (delivery or trip), and folder options for
each entity based on your business needs
Chapter
CLASSROOM
Quick Ship Window
Reports and Processes

Oracle Shipping Execution provides you with a variety of flexible and easy-to-use reports to
help you improve productivity and increase control. Text attachments can be used with reports
and documents to print shipping application data: for example, unpacking instructions entered
on a delivery line can be printed on the Packing Slip. You use the Shipping Reports and
Documents window to select the report you want to generate. The Shipping Execution Reports
are displayed based on the report parameters that you enter.
Printers
(N) Shipping > Setup > Documents > Choose Printers
You can assign shipping documents and reports to specific printers. Printers can be assigned at
multiple levels, including the following:
User
Responsibility
Applications
Site
Chapter
CLASSROOM
Reports and Processes
Integration With Oracle Order Management

After a sales order is booked, the sales order lines must complete all workflow activities
leading up to the shipping activity. Two typical preceding workflow activities are Schedule
Line and Ship Line Manual:
Schedule Line:
The Schedule Line subprocess schedules an order line for all order lines that must be
shipped. This activity makes the order lines demand visible to Oracle Inventory for planning.
It also sets the shipment schedule date for the order line.
Ship Line Manual:
The Ship Line Manual enables you to manually initiate shipping for an order line. The Ship
Line Manual process can return one of the following and reaches the end activity:
Over Shipped Beyond Tolerance
Ship Confirm
Non Shippable
Unreserved
Chapter
CLASSROOM
Integration With Oracle Order Management
Integration With Oracle Transportation Management

If Oracle Transportation Management is installed, you can utilize the following functionality in
Oracle Shipping Execution:
Freight Payment and Audit: Enables you to automate in-house auditing of freight
bills, reducing the costs associated with manual freight bill auditing and the costs
of 3rd party audit firms that you might use. Auditing takes place upon receipt of a
freight bill from the carrier after shipment delivery has been completed.
Load Tendering: Enables you to communicate the characteristics of a delivery with your
carriers to facilitate shipment pickup.
Inbound Carrier Selection: Enables you to select preferred carriers for inbound purchase
orders.
Chapter
CLASSROOM
Integration With Oracle Transportation Management
Integration with Oracle Warehouse Management

If Oracle Warehouse Management is installed, it provides the following functionality to Oracle
Shipping Execution
Plan Tasks: The planning tasks of warehouse such as pick, put away, moves and
replenishments are done by Oracle Warehouse Management.
Pick Methodologies: The pick methodologies are determined by Warehouse
Management.
Chapter
CLASSROOM
Integration With Oracle Warehouse Management
Integration with Oracle Workflow

Oracle Shipping Execution enables you to utilize Oracle Workflow to enhance your day-to-day
business. Using Oracle Workflow with Oracle Shipping Execution is optional; however, if you
choose to enable Oracle Workflow with Oracle Shipping Execution, then specific tasks and
output are enabled through the use of customized business objects. For example, the workflow
can be configured so that specific users receive a notification email when an overship or
backorder occurs.
Workflows available in Oracle Shipping Execution include:
Delivery Flow Generic: This process is initiated when a delivery line is assigned to a
delivery and completed when the delivery reaches its final drop off location.
Trip Flow Generic: This process is initiated when a trip is created and completed when the
ultimate drop off stop is closed.
Ship to Deliver Process Workflow: This process models the ship confirm process through
the Order Management and Inventory interfaces.
Chapter
CLASSROOM
Integration with Oracle Workflow
Summary
Chapter
CLASSROOM
Chapter 10
Shipping Execution Setup
Chapter
CLASSROOM

Chapter
CLASSROOM
Chapter
CLASSROOM
Objectives
Chapter
CLASSROOM
Roles
(N) Shipping > Setup > Grants and Role Definitions > Define Roles
Oracle Shipping Execution provides a role to each user that controls the access of Action list
and Tools menu in the various user interfaces.
Defining Roles:
Roles provide data access controls. You can assign the following data access controls to
each role:
- Data Access Edit: This enables you to edit and view data pertaining to shipping
entities
- Data Access View: This enables you to only view data pertaining to shipping entities
- Data Access None: This prevents you from editing and browsing data and
performing actions
You can create your own customized roles by defining the access controls to match
responsibilities of your shipping personnel.
Defining and Copying Shipping Execution Roles
Chapter
CLASSROOM
Roles
Chapter
CLASSROOM
Use the Shipping Execution Role Definition window to define and copy the shipping
roles. The roles can be granted access to functionalities. The functionalities are classified
as follows in the Shipping Execution Role Definition window:
- Trips
- Stops
- Deliveries
- Lines/LPNs
- General
Copying a role is performed from the Edit menu, using the Duplicate option. The
privileges can be updated, name, and new user assignments are available when copying a
role.
Granting Roles To Users

(N) Shipping > Setup > Grants and Role Definitions > Grants
You can use the Shipping Execution Grants window to grant a user a role in one organization
or all organizations for a period of time. The role is assigned to a user by a grant. The grant is
specific to a particular user and defines the roles assigned to the user, the organization where
the grant is effective, the start date and optionally, an end date.
More than one grant can be assigned if the user requires different access controls to more than
one organization. The start and end dates for grants can overlap.
For example, if a user requires full-access privileges to three organizations and view-only
access to a fourth, the user must be assigned four grantsone for each respective organization
(three full-access and one view-only grant). However, if only one grant is assigned, that grant
becomes the default grant for the user.
In addition, the grant has the following requirements:
A grant may or may not have one inventory organization selected.
Many grants can be assigned for each role.
Chapter
CLASSROOM
Granting Roles To Users
A user can have one or more grants. If the user does not have any grant (expired, effective,
or future), the default is view-only access to all organizations. If the user has grants, the
user's access is controlled by the effective grants. If there are overlapping grants in the
same organization or an intersection of grant date ranges, the union of grant privileges
controls the user's access.
A role can be assigned to a user that spans all organizations instead of granting a unique grant
per organization. If an organization is not specified, the grant is applicable to all organizations.
Chapter
CLASSROOM
Freight Carriers
(N) Shipping > Setup > Freight Carriers, Cost Types > Freight Carriers
A freight carrier is a commercial company that transports shipments to and from customers,
suppliers, and internal organizations. A freight carrier can consist of different service levels
and mode of transportation. You must assign a freight carrier to a delivery in order to ship
confirm if Enforce Ship Methods is enabled in Global Shipping Parameters window. You can
classify a freight carrier as follows:
Active: An active carrier is a carrier attached with a vehicle.
Generic: A generic carrier is virtual carrier that is attached to a vehicle. A generic carrier
can be defined to set up the transit time between an origin and destination. Only transit
time information can be specified for a generic carrier. Other information such as rating,
manifesting, load tendering cannot be defined for a generic carrier.
Note: The ship method of the freight carrier can be used by the organization only if the ship
method is assigned to the organization.
Ship Method
Ship method is the concatenation of the following:
Chapter
CLASSROOM
Freight Carriers
Freight Carrier: Name of the freight carrier.

Service Level: The freight carrier can provide different levels of service. For example,
service levels can be door-to-door, next day air, and ground.
Mode: The freight carrier can be provide different modes of service. For example, the
mode of service can be LTL,TL, or parcel.
Example: Freight carrier: Truck
Mode: LTL
Service Level: Ground
Ship method: Truck-LTL-Ground
Note: For a ship method to be used by an organization, it must be assigned to it.
Chapter
CLASSROOM
Freight Costs
(N) Shipping > Setup > Freight Carriers, Cost Types > Freight Cost Types
You can define freight cost types, which can be attached to shipments. You can attach multiple
freight costs to a shipment. You can group freight costs based on the freight cost types.
The prerequisites for defining freight costs are:
Define values for Freight Cost Type lookups
Define pricing modifier and optionally a pricing formula to pass freight costs to Oracle
Order Management and Oracle Accounts Receivable
You can define the freight costs in the Freight Cost Types window. You can define the
following attributes in the Freight Costs Types window:
Name of the Freight Cost
Type of Freight Cost
Currency of Freight Cost
Amount of Freight Cost
Effective period in which the Freight Cost is valid
Chapter
CLASSROOM
Freight Costs

Chapter
CLASSROOM
Transit Times
(N) Shipping > Setup > Freight Carriers, Cost Types > Shipment Transit Times
Transit time is the time taken to ship material using a given ship method from origin to
destination. Transit time can be specified for the shipments between the following:
Organizations
Supplier and Organizations
Supplier and Customers
Third Party Warehouses
Before defining the transit times, you have to define freight carriers and assign them to
organization to get valid ship methods.
You can use the Transit Times window to define the transit time between two locations. You
can define the following in the Transit Times window:
Origin Type: You can select the location type such as
- Internal Location
- External Location
- Region
Chapter
CLASSROOM
Transit Times
Chapter
CLASSROOM
- Zone
From Location: The location from which the shipment is shipped
Destination Type: Select the location type such as
- Internal Location
- External Location
- Region
- Zone
Destination: The location to which the shipment is shipped
You can define the following in the Ship Method regions
- Ship Method: Select a ship method from the list of values
- Intransit Time: The transit time between the origin and destination
- Daily Capacity: The maximum allowable load capacity in terms of weight that can
be shipped using the ship method in a day
- UOM: The unit of measurement used in calculating the Daily Capacity in terms of
weight
- Cost Per Unit: The cost per unit of measurement specified in the UOM field
- Currency: The currency in which the cost is calculated
- Daily Capacity: The maximum allowable load capacity in terms of volume that can
be shipped using the ship method in a day
- UOM: The unit of measurement used in calculating the Daily Capacity in terms of
volume
- Default Method: Select this, if you want this to be the default ship method for the
shipments between the origin and destination
Regions and Zones

You can use Regions and Zones to group by geographical areas and save the effort of setting
up point-to-point transit times. The terms used while defining regions and zones are as follows:
Region: A geographical area, for example, a group of cities, states, provinces, or a
country. You can model regions at different levels of scale. A region can consist of
countries, provinces or states, cities, or postal codes.
Sub-Region: A child of a region. For example, the sub-regions of the region Canada can
be its provinces; the sub region of the region London can be its postal codes
Zone: A collection of regions, for example, a western zone. Zone information is unique to
your business.
Regional Transit Times: The in-transit time for the shipment between ship-from
location, ship-to location, locations, zones, and regions based on the shipping methods.
The advantage of planning shipments in terms of regions and zones are:
Enter and maintain in-transit and sourcing rules information between zones rather than
between every ship-from and ship-to location combination
With less in-transit information Oracle Shipping Execution finds the information faster
Chapter
CLASSROOM
Regions and Zones
The in-transit information automatically applies to the new user also for deciding shipping
quotation, you can compare your inter-zone shipment requirements with of your service
providers available lanes
Note: To work with Regions and Zones you must have Oracle Advanced Planning and
Scheduling Suite
Chapter
CLASSROOM
Shipping Document Sets

(N) Shipping > Setup > Documents > Document Sets
You can group a set of related documents and reports that can be printed during pick release or
ship confirm. You can also define the sequence in which you want the reports to be printed.
For example, you can create document sets, assign the Bill of Lading and Packing Slip and
define the sequence of printing. The shipping document sets at the following places:
You can set the default document set to be printed during pick release in the Pick Release
tab of the Shipping Transaction Parameters window. For more information, see the lesson
titled Pick Release Tab In Shipping Transaction Parameter slide.
You can select the document sets to be printed during ship confirm in the Ship Confirm
window.
Chapter
CLASSROOM
Shipping Document Sets
Document Categories
(N) Shipping > Setup > Documents > Document Categories
You can use the Document Categories functionality to categorize the shipping documents. Use
the Document Categories window to define the document categories.
You can create more than one document category for a document. For example, while printing
the Bill Of Lading (BOL) for a freight carrier, you want the name of the freight carrier to
printed as a suffix in the document, you can define a separate document category for the freight
carrier. When you use different BOL sequence for each carrier, you can identify the carrier by
looking at the BOL.
Document categories can be specified for the following:
Document Types/Ship Method/Carriers: When you specify the document categories for
specific document types, ship method, or carriers, you can identify the document.
Location: A specific location can be attached to the document category. For example, if
you have a freight carrier named Trucking Company and when it has the following
departure:
- From warehouse 1, the bill of lading number is WH1-12345- Trucking Co
Chapter
CLASSROOM
Document Categories
- From warehouse 2, the bill of lading number is WH2-55466-Trucking Co

Note: Location can be attached only to the document category which has the document type as
BOL.
Note: The document category is specific to the application and responsibility from which you
are accessing.
Chapter
CLASSROOM
XML Publisher Enabled Documents

XML Publisher enables you to create customized reports and print them in PDF format using
seeded templates for the following Oracle Shipping Execution reports,
Bill of Lading
Commercial Invoice
Mailing Label
Master Bill of Lading
Packing Slip
Pick Slip
Vehicle Load Sheet Summary
These templates are assigned to document sets and are used when printing the reports.
Multiple templates can be created for each report. If your report has multiple templates, then
you select which template to use when you print.
Enabling PDF Printing: PDF printing must be enabled on the Shipping Document Sets window
or through the use of concurrent requests. The seeded concurrent requests are as follows:
Vehicle Load Sheet Summary PDF
Chapter
CLASSROOM
XML Publisher Enabled Documents
Pick Slip PDF

Bill of Lading PDF
Master Bill of Lading PDF
Mailing Label PDF
Commercial Invoice PDF
Packing Slip PDF
Enabling PDF printing on the Shipping Document Sets window requires that you use the report
name ending in PDF Output and selecting the layout template. If you select a report that is not
PDF Output, then the Layout Template field is not available for update.
Chapter
CLASSROOM
Customizing and Creating Templates

You can customize your templates by:
Adding your company logo
Moving fields
Removing fields
Add new fields
Rearranging the layout
To customize a layout template, you download the seeded template from Oracle XML
Publisher, customize it, and upload it to Oracle XML Publisher. You then include the template
in the Shipping Document Sets.
All creation and customization of templates is performed in Oracle XML Publisher. See Oracle
XML Publisher Users Guide for more information.
Chapter
CLASSROOM
Customizing and Creating Templates
Document Sequences
(N) Shipping > Setup > Documents > Document Sequences
Define document sequences to generate a unique numbering sequence for documents in Oracle
Shipping Execution. Use the Document Sequences window to define the document sequence.
For example, you can specify unique document sequencing for BOL and packing slips in
Oracle Shipping Execution.
You can define the following in the Document Sequence window:
Name: The name of the document sequence
Application: The application to which the document sequence can be applied
From: The start date from which the document sequence is valid
To: The end date till which the document sequence is valid
Type: You can select the following options:
- Automatic
- Manual
- Gapless
Chapter
CLASSROOM
Document Sequences
Message: Select this checkbox to display a message to inform the user sequence and
name.
Initial Value: Initial value of the document sequence
Chapter
CLASSROOM
Choosing Printers For Searching Documents and Labels

(N) Shipping > Setup > Documents > Choose Printers
You can assign shipping documents and selected reports to specific printers for multiple levels.
The levels are:
User
Responsibility
Application
Site
Oracle Shipping Execution will look for a printer at the User level first. If one is not found in
this level, it looks for printer at lower levels until it is found. For example, you can assign pick
slips and pack slips to your warehouse tractor feed printer, your mailing labels to a tractor
printer stocked with blank labels, and other documents to a laser printer in your order entry
office.
Note: Pick slips can be made to print at the Zone/Subinventory levels.
Chapter
CLASSROOM
Choosing Printers For Searching Documents and Labels
The window consists of a Document and a Printer tab: the Documents tab displays all the
documents assigned to a printer, while the Printers tab displays all printers assigned to a
document.
If a user or responsibility is not specified, Shipping Execution uses the printer assigned to the
application.
Chapter
CLASSROOM
ITM Adapter Integration

Oracle Order Management and Oracle Shipping Execution integrates with International Trade
Management (ITM) adapters to perform the following:
Order Compliance: The partner ITM application evaluates the sales order lines for
export compliance request to the ITM adapter.
Delivery Compliance: The export compliance is performed on the deliveries or shipment.
Chapter
CLASSROOM
ITM Adapter Integration
Delivery Compliance Screening

Export compliance Screening can be performed either at delivery creation or at ship
confirmation. The export compliance screening request is submitted to the ITM adapters
interface tables. The ITM adapter generates and transmits the export compliance service
request XML to the partner application. A synchronous acknowledgment is expected from the
ITM application. The export compliance request XML contains all the necessary data elements
required for checking the compliance of the delivery.
The partner ITM application evaluates the delivery for export compliance and responds to
Oracle Applications with the overall pass or fail status. The asynchronous response is received
by Oracle XML gateway and a synchronous acknowledgement is provided to the partner
application. The XML gateway passes the response information to the ITM adapter, which in
turn handles the exception, originally logged against the delivery to prevent from ship
confirmation.
If a delivery is determined to be non compliant, the ITM adapter logs compliance failure
exception against the delivery. You will need to manually cancel these cancel these deliveries
depending upon their business processes. In case, the ITM application is unable to evaluate the
compliance of a delivery programmatically, the ITM application notifies the compliance users
Chapter
CLASSROOM
Delivery Compliance Screening
for a manual compliance review. A response is not communicated back to Oracle Application
until a final compliance determination is made by the compliance user.
Chapter
CLASSROOM
Shipping Exceptions
During shipping and transportation of goods there are many possibilities of encountering a
situation that violates the requirements of a shipper, transportation carrier, or the customer.
These situations are called Shipping Exceptions. The process of handling the exception is
called Handling Shipping Exceptions. Shipping Exceptions enable you to identify and handle
nonconforming operations that violate the requirements of your business or that of your
carriers and customers.
The shipping entities that can incur shipping exceptions are delivery, delivery lines, containers,
trips, and stops. For each shipping entity the shipping exceptions logged against it are
displayed in the Shipping Transactions form and Quick Ship window. If there is any exception
logged against an entity, the Exception check box is enabled. The color of checkbox will
display the level of exception. They are as follows:
Red: This color of the checkbox indicates that there exist at least one exception for this
entity which is an error
Yellow: This color of the checkbox indicates that there exists at least one exception for
this entity which is a warning
Chapter
CLASSROOM
Shipping Exceptions
No Color: If the exceptions checkbox is checked but there is no red or yellow color, then
there exists at least one exception exists for this shipping entity as information only
Shipping Exceptions can be classified as:
Seeded Exceptions: Seeded exceptions are the default exceptions that ship with Oracle
Shipping Execution.
Manual Exceptions: You can create manual exceptions to meet your business
requirements.
Chapter
CLASSROOM
Defining Shipping Exceptions

(N) Shipping > Setup > Define Exceptions
You can define Shipping Exceptions to meet your unique business requirements. For example,
if there is a scenario where the transportation carrier does not deliver the goods to the customer
on time, a shipping exception can be defined for this scenario. You can manually log this
exception within the entity against the transportation carrier.
Define the shipping exceptions in the Define Shipping Exceptions window. Define the
following attributes for the exception in this window:
Exception Type: You can select the exception type to indicate the process of the
exception. You can select the following for the exception type:
- Batch
- Delivery
- Picking
- Trip
Chapter
CLASSROOM
Defining Shipping Exceptions
Exception Behavior: You can select the following to indicate the behavior of the
exception:
- Error: The exception must be handled before the entity can be closed
- Information Only: The exception is provided as information. You can close the entity
and the information only exception will be closed automatically.
- Warning: A warning is displayed but the entity can be closed.
Enabled: Select this check box, to enable the shipping exception
Raise Business Event: Select this check box, to raise a business event that can be shown
in the workflow
Note: You can enable or disable both the manual and seeded shipping exceptions
Chapter
CLASSROOM
Logging Shipping Exceptions

(N) Shipping > Exceptions > [New]
Shipping Exceptions are logged against shipping entities either manually or automatically. Use
the Log Exception window to log shipping exceptions manually. You must enter the following
in the Exception tab of Log Exception window:
Exception Name: Select the exception name to be logged. The values in the field default
based on the definition of the exception name.
Message: Enter the message to be displayed when the exception is raised.
Logging Entity: The entity logging the shipping exception. The logging entity can be
shipper, receiver, or transportation carrier.
Logged At Location: The location at which the shipping exception is logged.
Exception At Location: The location at which the shipping exception has occurred.
In the Trip/Delivery/Container tab, you can define the shipping entity on which the shipping
exception is logged. For example, you can enter the delivery name in the Delivery Name field
Chapter
CLASSROOM
Logging Shipping Exceptions
to indicate that the shipping exception is logged for this specific delivery. You can do the same
for trip and container.
Note: The Log Exception window can also be invoked from the Shipping Transactions form
and Quick Ship window
Chapter
CLASSROOM
View and Update Logged Shipping Exceptions

(N) Shipping > Exceptions
You can view and update the shipping exception logged to a shipping entity. You use the View
Shipping Exception window to view and update the shipping exception. You can update the
following:
Message: Enter a message that must be displayed when the exception is raised
Status: Select any one of the following to change the status of the logged shipping
exception:
- Open: Select this to keep the shipping exception open
- Closed: Select this to manually close the shipping exception
- No Action Required: Select this to carry on with next process, without closing the
shipping exception
Chapter
CLASSROOM
View and Update Logged Shipping Exceptions
Purge and Resolve Logged Shipping Exceptions

To help maintain your shipping exception records and conserve computer storage space, purge
logged shipping exceptions that are no longer required. For example, you might purge shipping
exceptions that are five months old. Use the Resolve/Purge Exceptions parameters window to
resolve or purge shipping exceptions.
Note: Once purged, the shipping exceptions cannot be retrieved.
Chapter
CLASSROOM
Purge and Resolve Logged Shipping Exceptions
Running Pick Release

Online: You can pick release a delivery line immediately using the Release Sales Orders
for Picking window. This eliminates the time spent waiting for the order to process
through the concurrent manager queue. You can run the pick release online in the Release
Sales Orders for Picking window. You can also run the pick release online in the Shipping
Transactions form by selecting Launch Pick Release from the Actions menu.
Concurrent: You can run pick release in the background, enabling you to run multiple
processes at the same time. You can run the pick release concurrently in the Release Sales
Orders for Picking window.
Standard Report Submission (SRS): You can run pick release using the Standard Report
Submission process. Use this to run pick release as a scheduled task. For example, you can
run pick release at a specific time everyday. The delivery lines are selected for pick release
based on the release rule you select for the standard report submission.
Pick Release Application Program API: You can run pick release using Application
Program Interface (API). For more information refer to Oracle Order Management APIs
and Open Interfaces Manual.
Chapter
CLASSROOM
Running Pick Release
Release Sequence Rules

(N) Shipping > Setup > Picking > Define Release Sequence Rules
Define the release sequence rule to specify the order in which the eligible picking lines are
allocated to Oracle Inventory during pick release. You can release the picking lines by
selecting one or more of the following attributes:
Order Number: Release picking lines based on the order number. If you define a priority
for the Order Number you cannot define priority for outstanding invoice value
Outstanding Invoice Value: Release picking lines based on the outstanding invoice
value.
Scheduled Date: Release picking lines based on scheduled date of delivery
Departure Date: Release picking lines based on the departure date of the delivery
Shipment Priority: Release picking lines based on the shipment priority
You can set a priority level to above attributes by assigning a value from 1 to 5. 1 being the
highest priority and 5 being the lowest priority. You can also decide whether the lines must be
picked based on the ascending or descending order.
Chapter
CLASSROOM
Release Sequence Rules
Example:
Attribute
Priority Level
Order
Shipping Priority
1
Ascending
Schedule Date
2
Ascending
According to the above table the order lines with highest shipping priority with earliest
scheduled date will be allocated with the material first.
Chapter
CLASSROOM
Pick Slip Grouping Rule

(N) Shipping > Setup > Picking > Define Pick Slip Grouping Rules
Define the pick slip grouping rule to specify the criteria by which the delivery lines are
grouped together in a pick slip. For example, if you select delivery as a grouping criteria, all
delivery lines for the same delivery are grouped together on a pick slip. Use the Pick Slip
Grouping Rules window to define the pick slip grouping rule. The Pick Slip Grouping Rules
window is divided into three regions: Group By, Common, and Manufacturing. You can select
a combination of these attributes in these regions based on your business requirement.
The attributes you can group by in the Sales Order region include the following:
Order Number
Customer
Ship To
Carrier
Trip Stop
Delivery
Chapter
CLASSROOM
Pick Slip Grouping Rule
Chapter
CLASSROOM
Shipment Priority
The attributes you can group by in the Common region include the following:
Source Subinv
Source Locator
Item
Revision
Destination Subinv
Destination Locator
Project
Task
The attributes you can group by in the Manufacturing region include the following:
Job or Schedule
Operation
Department
Push/Pull
Note: The grouping attributes in the Manufacturing region is available only if Oracle
Warehouse Management system is installed.
Release Rules
(N) Shipping > Setup > Picking > Define Release Rules
Define the release rules to specify the criteria by which the delivery lines are selected for pick
releasing and to determine the picking operations that will be performed on the delivery lines.
Release rules provide a means for defining one time setup for your pick release process. Create
the release rules in the Release Rules window. You can create a customized pick release rule
with its own set of unique parameters for pick releasing. Pick Release Rules are more
convenient to use when you run pick release regularly based on the same set of criteria.
Note: You must have a release rule defined when you pick release using Release Sales Order
SRS or when you use the Auto Pick Pack and Ship features.
Chapter
CLASSROOM
Release Rules
Release Rule Order Tab

(N) Shipping > Setup > Picking > Define Release Rules > (T) Order
Use the Order Tab in the Release Rule window to define a set of criteria specific to the order to
select delivery lines for releasing. The criteria that you can define in this window includes the
following:
Effective Dates: The period of time that the release rule is valid
Orders: The status of the order. The different statuses are:
- Unreleased
- All
- Backordered
Order Number: The sales order number
Ship Set: The ship set
Prior Reservations only: You check this box to pick release only the sales order that
already has items reserved for the line items
Destination Type: You can pick release based on the following destination types:
Chapter
CLASSROOM
Release Rule Order Tab
Chapter
CLASSROOM
- Region
- Zone
- Ship-To Location
Customer: The customer
Item Region: In this region you select the Category Set, Category, and Item Number
Scheduled Ship Dates/ Requested Dates: Define the range of ship dates scheduled or
requested
Order Type: The type of order
Order Dates: You can specify a Start Date and End Date in combination with the Days
field to create a moving pick window when you schedule the concurrent program to run on
a regular basis. The start and end dates are relative to the system date.
Release Rule Shipping Tab

(N) Shipping > Setup > Picking > Define Release Rules > (T) Shipping
Use the Shipping Tab in the Release Rule window to define a set of parameters that you want
to apply in terms of shipping during pick release. The various parameters available are:
Ship Method: Select the ship method. The system will consider all delivery lines that
includes this ship method for pick release.
Shipment Priority: Select the shipment priority. The system will consider all delivery
lines that include this shipment priority for pick release.
Ship From Location: Select the ship from location. The system will consider all delivery
lines that include this ship from location for pick release.
Include Assigned Lines: Enable the checkbox to include all the assigned lines in the pick
release.
Document Set: Select the document set you want to print at pick release.
Release Sequence Rule: Select the release sequence rule you want to apply at pick
release.
Chapter
CLASSROOM
Release Rule Shipping Tab
Chapter
CLASSROOM
Autocreate Deliveries: Select Yes to autocreate deliveries at pick release.

Autocreate Delivery Criteria: Select Across Orders, if you want to create a delivery by
combining delivery lines across orders. Select Within Order, if you want to create delivery
only within an order.
Auto Pick Confirm: Select Yes to auto pick confirm.
Autopack Delivery: Select No if you do not want to use the autopack delivery option,
select Yes to enable autopacking, or select Auto Pack Master to utilize autopacking the
items into a primary container and additionally automate packing the primary container
into a defined master container.
Append Deliveries: Select yes to append delivery lines to existing deliveries.
Note: You must setup the container-item relationship to support the functionality of auto pack
and auto pack master.
Note: You can append deliveries only when the Appending Limit field is set to value other
than Do Not Append in the Shipping Parameters window. Other prerequisites for appending
deliveries is as follows:
Oracle Transportation Planning is not installed
Organization is specified
Autocreate Delivery criteria must be set to Across Orders
Autocreate Delivery must be set to Yes
Auto Pick Confirm must be set to No
Release Rule Inventory Tab

(N) Shipping > Setup > Picking > Define Release Rules > (T) Inventory
Use the Inventory Tab within the Release Rule window to define a set of parameters you want
to apply in terms of inventory management during pick release. The various parameters include
the following:
Warehouse: Select the warehouse. The system will consider all delivery lines that specify
this warehouse for sourcing.
Pick Slip Grouping Rule: Select the Pick Slip Group Rule to determine the criteria that
will be used for grouping delivery lines on the pick slip as part of the pick release process.
Subinventory: Select the subinventory. The system will consider for pick release all
delivery lines that have this subinventory specified on the sales order line.
Project: Select a project. You can select a project only if Oracle Project Manufacturing is
installed.
Plan Tasks: Select either Yes or No to Enable Plan Tasks if Oracle Warehouse
Management is installed and you choose to utilize the Plan Tasks feature.
Chapter
CLASSROOM
Release Rule Inventory Tab
Tasks: Select a task. You can select a task only if Oracle Project Manufacturing is
installed.
Pick From Region: Select the subinventory and locator from which you want to pick the
line items.
Default Stage Region: Select the default staging area to which you want to move the
items.
Chapter
CLASSROOM
Pick Release tab in Shipping Parameters Window

(N) Shipping > Shipping > Setup > Shipping Parameters > (T) Pick Release
Use the Pick Release Tab within the Shipping Parameters window to define the default values
for the pick release parameters including the following:
Release Sequence Rule: Select the release sequence rule that will be displayed by default
in the Release Sequence Rule field during pick release.
Pick Slip Grouping Rule: Select the pick slip grouping rule that will be displayed by
default in the Pick Slip Grouping Rule field during pick release.
Print Pick Slip: You specify when you want to print the Pick Slips. You can set it to
either of the following:
- At the End: The pick slips are printed at the end of pick release.
- Immediate: The pick slips are printed when a specific number of pick slip lines have
been accumulated for printing. You can specify number of pick slip lines that needs
to be accumulated for printing in the Number of Pick Slip Lines field.
Chapter
CLASSROOM
Pick Release tab in Shipping Parameters Window
Chapter
CLASSROOM
Number of Pick Slip Lines: The maximum number of pick slip lines that is grouped in a
Pick Slip. You must specify the value when the Print Pick Slip is set to Immediate.
Default Pick Release Document Set: Select the default pick release document set you
want to print during pick release.
Default Stage Subinventory: Select the default staging subinventory where items needs
to be transferred at the end of the pick release process.
Default Stage Locator: The default staging locator in the subinventory where the items
needs to be transferred at the end of the pick release process.
Autocreate Deliveries: Select one of the following to specify your preference for
autocreating deliveries:
- Selected: Pick release automatically creates deliveries based on the delivery grouping
criteria specified in the Delivery Grouping tab of the Shipping Parameters window.
Delivery lines are then assigned to the created delivery.
- Cleared: Deliveries are not created automatically at pick release
Auto Allocate: You specify the default auto allocate option during pick release. The
options are:
- Selected: During Pick Release move orders are automatically created and allocated
with items.
- Cleared: During Pick Release automatically creates move orders. The move orders
must be allocated with the inventory items manually using the Inventory Transact
Move Orders window.
Enforce Ship Sets and Ship Models: Enable the checkbox to enforce Ship Sets and Ship
Models during pick release. Ship Sets consists of a set related inventory items. When Ship
Sets or Ship Models are enforced, it means that all the items belonging to a ship set or ship
model should be released together, otherwise a warning message will be displayed. This
feature helps to ensure that only complete ship sets and ship models are transferred to the
staging subinventory.
Auto Allocate
Auto allocation is the process by which you can automatically allocate move order lines with
subinventory items based on the Oracle Inventory picking engine. To autoallocate during pick
release you can set the Auto Allocate field in the Inventory tab of Release Sales Order for
Picking window to Yes.
The release sequence rule selected for the pick release determines the order in which the move
orders are allocated with materials. During allocation a high level reservation is placed on the
items.
Allocation of inventory is a prerequisite for printing pick slips. The pick slip grouping rule
selected during pick release determines the grouping criteria for the picked lines in the pick
slip.
You can set the Auto Allocate option to Yes by default by setting the Auto Allocate checkbox
to Yes within the Pick Release tab of the Shipping Parameters window. For more information
refer to Pick Release slide.
Chapter
CLASSROOM
Auto Allocate
Autocreate Deliveries
You can automatically create deliveries for delivery lines that are not assigned to delivery.
During pick release you can check the Auto-Create Deliveries checkbox in the Shipping tab of
Releasing Sales Order for Picking window to autocreate deliveries. The delivery lines are
grouped together to form a delivery based on the parameters set in the Delivery Parameters tab
within the Shipping Parameters window. You can also select a set of delivery lines in the
Query window and autocreate delivery.
Chapter
CLASSROOM
Autocreate Deliveries
Auto Pick Confirm

Auto pick confirm can be set up as the default to occur immediately after the lines are detailed
if an organizations picks rarely deviate from the suggested picking lines or the overhead of
requiring a pick confirmation is unmanageable. Auto pick confirm can be set up to occur by
default by setting the Auto Pick Confirm field to Yes in the Shipping Tab of Release Rule
window. This default option can be overridden during each pick release.
Pick confirmation follows the allocation and reservation of inventory items process
automatically if both Auto Allocate and Auto Pick Confirm options are selected.
When Auto Allocate is set to Yes and Auto Pick Confirm is set to Yes:
When the request is submitted the system automatically creates a move order for all
eligible order lines that meet the picking criteria.
The Release Sequence Rule can be used to sequence the orders for inventory allocation.
Oracle Inventorys Picking Rule can be used to detail the move order with suggested
material.
Pick Slips are printed and can be reprinted if needed later.
Chapter
CLASSROOM
Auto Pick Confirm
The subinventory transfer is executed to move the material from its source location to the
destination staging subinventory.
The delivery line status is changed to Stagged/Pick Confirmed, making it eligible to be
Ship Confirmed.
Note: Auto Pick Confirm is not possible if Auto Allocation is not selected.
Note: Manual Pick Confirmation is required if you have Oracle Warehouse Management
installed.
Chapter
CLASSROOM
Release Sales Orders for Picking Window

(N) Shipping > Release Sales Orders
Use the Release Sales Orders for Picking window to pick release sales order lines. You can
select a set of parameters based on which you want to release sales order lines. You can only
pick release the sales order lines that meet the following prerequisites:
Delivery lines must be in the booked status
Delivery lines must have shippable items
Delivery lines must have shipping workflow activity
In this window you can release sales orders based on existing release rules or define you own
set of criteria to pick release.
For field description refer to Release Rule Order Tab, Release Rule Shipping Tab, and
Release Rule Inventory Tab slide.
Note: You can also run the pick release online in the Shipping Transactions form by selecting
Launch Pick Release from the Actions menu.
Chapter
CLASSROOM
Release Sales Orders for Picking Window

Chapter
CLASSROOM
Ship Confirm Rules

(N) Shipping > Setup > Ship Confirm Rules
You use the Ship Confirm Rules window to define the Ship Confirm Rules based on your
business needs.
Within the Ship Confirm Rules window, there are several options, which are covered next.
Chapter
CLASSROOM
Ship Confirm Rules
Ship Confirm Rule Ship Options

The Ship Options region of the Ship Confirm Rules window enables you to specify the default
action to take when ship confirming. It also enables you to choose what to do when the Action
is Ship Entered Quantities and the quantities are unspecified. The following describes the
default actions:
Action:
- Ship Entered Quantities: This action enables you to ship the quantities entered at ship
confirm time.
- Ship All: This action enables you to ship all lines, regardless of the actual quantity.
Ship All is required if you choose to use a default ship confirm rule.
- Backorder All: This actions enables you to backorder all lines, regardless of the
quantity.
- Cycle Count All: This action enables you to cycle count all line items, regardless of
the quantity.
Unspecified Quantities (only available when the Action is Ship Entered Quantities):
Chapter
CLASSROOM
Ship Confirm Rule Ship Options
- Ship: Ship confirms the quantity of items specified in the Shipped Quantity
field and treats blank values as full quantity (shipped quantity = requested
quantity).
- Backorder: Ship confirms the quantity of items specified in the Shipped
Quantity field and treats blank quantities as full backorders (backorder
quantity = requested quantity).
Note: If a non-zero Stage Quantity exists on a line, it is split from the line and
unassigned from the delivery. If the Create Delivery for Staged Quantities is
enabled, all staged delivery lines are grouped together in a new delivery.
- Cycle Count: Ship confirms the quantity of items specified in the Shipped
Quantity field, treats blank quantities as full backorders (backorder quantity =
requested quantity), and transfers the backorder reservation to cycle
counting.
Chapter
CLASSROOM
- Stage: Leaves the unspecified delivery line quantity as staged and removes it
from the delivery.
Ship Confirm Rule Trip Options

The Trip Options region of the Ship Confirm Rules window enables you to either define a
default ship method or use the trip or delivery default ship method. The Trip Options region
also contains options that enable you to define what actions take place after ship confirm as
completed.
Note: Trip Options are only available if the Ship Option Action is set to Ship Entered
Quantities or Ship All.
Ship Method Default Option:
- Ship Method: Selecting Ship Method enables you to select a valid ship method from
the list of values.
- Default from Trip/Delivery: Selecting Default from Trip/Delivery enables you to
allow Oracle Shipping Execution to use the ship method specified in the trip or
delivery.
Set Delivery In-Transit: This creates a trip and related stops for the delivery and sets
status of delivery to In-transit.
Close Trip: This creates a trip and related stops for the delivery and closes the trip.
Chapter
CLASSROOM
Ship Confirm Rule Trip Options
Defer Interface: This creates a trip and related stops for the delivery, but does not initiate
the Order Management interface and Inventory interface.
Create Bill of Lading: This creates a trip and related stops for the delivery and creates a
bill of lading.
Any of the above options can be combined. For example, you might want to create a trip,
change the status to In-Transit, close the trip, then print the bill of lading. In this case, you
would enable the Set Delivery In-Transit, Close Trip, and Create Bill of Lading options.
Chapter
CLASSROOM
Ship Confirm Rule Document Set

As part of the Ship Confirm rule, you can select a default document set that will print
whenever your rule is used.
Chapter
CLASSROOM
Ship Confirm Rule Document Set
Ship Confirm Rule Shipping Parameters

(N) Shipping > Shipping > Setup > Shipping Parameters > (T) Shipping
Shipping transaction parameters are the default values assigned to ship confirm parameters
during ship confirm. Define the shipping transaction parameters in the Shipping Transaction
tab of Shipping Parameters window. You can define the following in this window:
Default Ship Confirm Document Set: The ship confirm document set that you want to
print on ship confirm.
Ship Confirm Rule: The default ship confirm rule that your organization will use during
auto ship confirm.
Autopack Options: You can select one of the following values:
- No: Autopack option is disabled for your organization. You have to manually select
the deliveries or delivery lines and pack.
- Yes: Autopack option is enabled for you organization. When autopack is run delivery
line items are automatically packed into containers based on the container-item
relationship.
Chapter
CLASSROOM
Ship Confirm Rule Shipping Parameters
Chapter
CLASSROOM
- Autopack Master: Autopack option is enabled for your organization. Select this
option, when you want to pack the delivery line items in a container, and pack the
containers into master container. For example, containers are packed into freight
containers for transportation. The auto packing is done based on the container-item
relationship.
Goods Dispatched Account: Select the default Cost of Goods Sold (COGS) account for
your organization.
Enforce Packing in Containers: Select one of the following options:
- Yes: Select this to enforce packing of delivery line items into containers. When you
select this option, a warning message is displayed during ship confirm to indicate that
you have not packed the delivery line items. You can bypass this message and
proceed.
- No: Select this not to enforce packing of delivery line items into containers.
Note: When you autopack, the delivery lines are grouped based on the delivery grouping rule.
Note: The delivery line details of a packed delivery cannot be modified until you unpack the
delivery.
Creating Containers
Containers, also known as License Plate Numbers (LPNs), are used to pack items. LPNs can be
created at any point in the shipping process. Packing is the process in which the items are
packed into containers. LPNs can be created in the following ways:
Manually: You can create LPNs without assigning them to a delivery. You can use this
method, when you want to create multiple containers of the same type and then pack them
with unassigned delivery lines. This makes packing more flexible because you can plan
and pack ahead of time or as needed.
Automatically: Auto-packing provides a convenient and quick way of automatically
packing delivery lines into LPNs. The delivery lines are packed into the LPNs based on
the Container-item relationship set up in Oracle Shipping Execution or in Oracle
Inventory.
Note: You can pack delivery lines into LPNs regardless of whether they are pick released or
not pick released.
Chapter
CLASSROOM
Creating Containers
Container-Item Relationship
(N) Shipping > Setup > Container Load Details
The container-item relationship defines the container used for packing the delivery lines. When
setting this relationship define the maximum quantity of load items (delivery lines) that can be
packed into a container. For example, when you define 12 items of X that can be packed into
Y, this information is used to calculate the following:
Calculate the number of containers required for delivery lines in a delivery or trip. This
enables you to use the auto-pack function to auto-pack delivery line items into new
containers. The number of containers required to pack the delivery lines is automatically
calculated based on the container-item relationships.
Calculate the fill percentage for containers when the Fill Percentage Shipping parameter is
set to Quantity. For more information refer to General Tab In Shipping Parameters slide.
Note: The container-item relationship is only used for autopacking when the Shipping
Parameter, Percent Fill Basis is set to Quantity.
You can define the container-item relationship in the Container-Item Relationships window.
Container Item: Select the container item from the list of values bag, tote, A2-box
Chapter
CLASSROOM
Container-Item Relationship
Item: Select the load item that you want to pack in the container
Maximum Quantity: Enter the maximum number of items that can be packed in the
container
Preferred Flag: Select this check box if you want the container-item relationship to be
the default for this combination
Note: A container item must be defined as Shippable in Oracle Inventory and assigned to the
organization before it will appear as a value in the Container Item LOV.
Chapter
CLASSROOM
Container Load Details

(N) Shipping > Setup > Container Load Details
Container-Load relationships are used when you use the Auto-Pack and Auto-Pack Master
functionality. The relationship specifies the items that can be automatically packed into
specified containers, and in what quantity.
Your item and container must be defined. Then, you define the maximum quantity of the item
to be loaded.
You could potentially have multiple load-relationships between items and containers. The
Preferred Flag is used to set a preference of a container-load relationship, Auto-Pack and AutoPack Master will use the preferred relationship when packing that item. For example, if you
have two container-load relationships for Item Aone with container A, which is the
preferred LPN/container, and one with Container Bthe maximum load defined in the
relationship with Container A will be used when you select Auto-Pack or Auto-Pack Master
for packing Item A. You must set the Preferred Flag for one of the container-load relationships
you have for an item in order to use Auto-Pack or Auto-Pack Master for that item. If you do
not set the Preferred Flag for one of the relationships for an item, you will receive an error
message.
Chapter
CLASSROOM
Container Load Details

Chapter
CLASSROOM
Packing Delivery Lines into Containers

Delivery lines can be packed into containers either manually or automatically.
Manually Packing Delivery Lines into Containers
You can manually select delivery lines from the Shipping Transactions form and pack them
into existing containers.
Prerequisites
An LPN must be available for packing.
The delivery lines must not be currently assigned to another LPN.
Auto-Packing Delivery Lines into Containers
You can select a set of delivery lines from the Shipping Transactions form and automatically
pack them into containers. The items from the delivery lines are automatically packed into
containers based on the container-item relationship. Auto-Packing has two options of packing:
Auto-Pack: This will pack the items of the delivery lines into containers.
Auto-Pack Master: The Auto-Pack Master functionality enables you to auto-pack
delivery line items into containers, and then auto-pack these containers into master
Chapter
CLASSROOM
Packing Delivery Lines into Containers
containers such as pallets or railway boxcars. The Auto-Pack option is available in the
Actions menu in the Lines/LPNs tab of the Shipping Transactions form.
Note: In order to use the Auto-Pack Master functionality you must define the container-item
relationship for the container into the master container.
Note: Auto-pack will automatically look at Container-Load Relationships set up for the item
and the detail container. If multiple container-item relationships exist for the same item, the
Preferred setting in the Container-Item Relationships window indicates the default containeritem relationship used for that item.
Chapter
CLASSROOM
Packing Workbench
Use the Packing Workbench window to split the delivery lines between containers or to pack
sequentially one container at a time to its full capacity. The Packing Workbench window
consists of the following:
LPNs: This displays the containers and its contents.
Lines: This displays the delivery lines.
Available Capacity: This section displays the available capacity to be filled-in in the
containers.
Item Total: This displays the total weight and volume of the delivery lines in all the
selected containers. As the containers and delivery lines are selected or deselected in the
LPNs and Lines tab respectively, the total net weight and volume in this section is
recalculated.
Note: The item total is calculated only if Product Item field is set to Weight and Volume
in Oracle Inventory.
Packing Mode: The packing of items can be packed into the containers using two
methods. They are as follows:
Chapter
CLASSROOM
Packing Workbench
Note: To prevent unintended splitting of a product item when

packaging by weight/volume, define the items physical
attributes in Oracle Inventory as OM indivisible. For
example, you want to prevent the system from packing 9.5
wallets in a box while packing containers full by weight.
- Equal: You can split delivery lines equally between the selected LPNs so that each of
the container consists of equal number of items. In case of multiple lines being
packed into multiple containers, the lines are equally packed depending on the
number of containers available for packing.
Note: Equal packing method cannot be used for packing serial controlled items.
Chapter
CLASSROOM
- Full: You can fully pack one LPN and then proceed to pack the next LPN. When
packing multiple lines into multiple LPNs, the packing is performed one container at
a time. The first delivery line is packed into the first container until the container is
full or the line is completely packed. If the line is completely packed, then the next
line is packed into the same container until the container is full. If the LPN is fully
packed before the line is completed (in situation where only a partial quantity fits in
the container) then the line is split so that the split line now fills up the first container
and the remaining quantity of the original line is packed into the next container. This
is continued until all the lines packed. The remaining lines are left unpacked. A
warning will be issued to inform you that some lines have been left unpacked.
Delivery Flow Generic

Delivery Flow Generic applies to outbound deliveries. This workflow is not raised for
consolidated deliveries.
Chapter
CLASSROOM
Delivery Flow - Generic
Trip Flow Generic

Trip Flow Generic applies to trips created manually and automatically.
Chapter
CLASSROOM
Trip Flow Generic
Ship to Deliver Process Workflow

Ship to Deliver Process models the ship confirm process through the Order Management and
Inventory interfaces. This workflow is extendable, that is, you can modify or extend the
workflow through the use of Oracle Workflow Builder.
Chapter
CLASSROOM
Ship to Deliver Process Workflow
Workflow Lookups
The following lookups support workflow in Oracle Shipping Execution:
R_DEL_GEN: Used with Delivery Flow Generic, this lookup reflects operations performed
on generic outbound deliveries.
R_SCPOD_C: Used with Ship to Deliver workflow, this lookup performs the operations
between ship confirm and final delivery.
R_TRIP_GEN: Used with Trip Flow Generic, this lookup reflects operations performed on
generic outbound trips.
Chapter
CLASSROOM
Workflow Lookups
Workflow Specific Profile Options

The profile option WSH: Override Ship to Deliver Workflow enables you to bypass the Ship to
Deliver workflow as well as any extensions to the workflow. This enables you to continue
through ship confirm.
Default value is No.
Chapter
CLASSROOM
Workflow Specific Profile Options
Workflow Specific Shipping and Global Parameters

The following parameters are specific to workflow in Oracle Shipping Execution and are on
both the Shipping Parameters and Global Parameters windows:
Shipping Parameters
Enable Workflows: On the General tab of the Shipping Parameters window, use the list of
values to select one of the following:
- Delivery: For use on deliveries only
- Trip: For use on trips only
- Both: For use on deliveries and trips
- None: Do not use workflows
Raise Business Events: Enable this checkbox if you want to utilize business events with
workflow in Oracle Shipping Execution.
Enable Ship to Deliver Workflow: Enable this checkbox if you want to utilize the Ship to
Deliver workflow in Oracle Shipping Execution.
Global Parameters
Chapter
CLASSROOM
Workflow Specific Shipping and Global Parameters
Chapter
CLASSROOM
Enable Workflows: On the General tab of the Shipping Parameters window, use the list of
values to select one of the following:
- Delivery: For use on deliveries only
- Trip: For use on trips only
- Both: For use on deliveries and trips
- None: Do not use workflows
Raise Business Events: Enable this checkbox if you want to utilize business events with
workflow in Oracle Shipping Execution.
Enable Ship to Deliver Workflow: Enable this checkbox if you want to utilize the Ship to
Deliver workflow in Oracle Shipping Execution.
The Enable Workflows parameter on the Global Parameters window must be set to Delivery,
Trip, or Both before you can enable workflows, raise business events, and enable Ship to
Deliver Workflow in the Shipping Parameters window. Enabling the parameters on the
Shipping Parameters window enables the workflow for your organizations.
Business Events
Business events are represented within workflow processes by event activities. By including
event activities in a workflow process, you can model complex processing or
routing logic for business events beyond the options of directly running a predefined function
or sending the event to a predefined recipient.
Business events leverage Oracle Advance Queuing to communicate business events between
systems.
Business events specific to workflow in Oracle Shipping Execution include the following:
Wsh.delivery:
oracle.apps.wsh.delivery.gen.closed: Delivery Closure Event
oracle.apps.wsh.delivery.gen.interfaced: Delivery OM, INV Interface Event
oracle.apps.wsh.delivery.gen.setintransit: Delivery Set to Intransit Event
oracle.apps.wsh.delivery.gen.shipconfirmed: Delivery Ship Confirm Event
oracle.apps.wsh.delivery.itm.submittedscreeningatdelcreate: Delivery Export Screening at
Creation Event
Chapter
CLASSROOM
Business Events
Chapter
CLASSROOM
oracle.apps.wsh.delivery.itm.submittedscreeningatship: Delivery Export Screening at

Confirm Event
oracle.apps.wsh.delivery.pik.pickinitiated: Delivery Pick Initiation Event
oracle.apps.wsh.delivery.gen.create: Delivery Creation Event
oracle.apps.wsh.delivery.gen.open: Delivery Open Event
oracle.apps.wsh.delivery.itm.responsereceivedatShip: Delivery Export Screening
Response
oracle.apps.wsh.delivery.itm.responsereceivedatdelcreate: Delivery Export Screening
Response
Wsh.trip:
oracle.apps.wsh.trip.gen.initialpickupstopclosed: Trip Initial Pickup Stop Closure Event
oracle.apps.wsh.trip.gen.ultimatedropoffstopclosed:Trip Ultimate Drop off Stop Closure
Event
oracle.apps.wsh.trip.gen.create: Trip Creation Event
oracle.apps.wsh.trip.gen.shipconfirmed: Trip Ship Confirm Event
wsh.stop:
oracle.apps.wsh.stop.gen.arrived: Stop Arrival Event
oracle.apps.wsh.stop.gen.closed: Stop Closure Event
oracle.apps.wsh.stop.gen.create: Stop Creation Event
wsh.line:
oracle.apps.wsh.line.gen.backordered: Line Backorder Event
oracle.apps.wsh.line.gen.releasedtowarehouse: Line Release to Warehouse Event
oracle.apps.wsh.line.gen.staged: Line Pick/Stage Event
Business event subscription specific to Shipping Workflow are:
oracle.apps.wsh.delivery.gen.closed: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.delivery.gen.open: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.delivery.gen.interfaced: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.delivery.gen.setintransit: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.delivery.gen.shipconfirmed: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.delivery.pik.pickinitiated: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.trip.gen.initialpickupstopclosed: WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.trip.gen.ultimatedropoffstopclosed:
WSH_WF_STD.Instance_Default_Rule
oracle.apps.wsh.sup.ssro: WSH_WF_STD.Instance_Default_Rule
Purging Workflows
The concurrent program named Purge Obsolete Workflow Runtime Data is used to purge
Shipping Execution workflows. See: Oracle Workflow Administrators Guide for more
information.
Shipping Purge is also used to purge Shipping Execution workflows when deliveries and trips
with related workflows are purged.
Chapter
CLASSROOM
Purging Workflows
Oracle Shipping Debugger

The Oracle Shipping Debugger is a package (WSH_DEBUG_SV) and set of profiles that
enable you to debug the Oracle Shipping Execution application with the help of Oracle
Support.
The Oracle Shipping Debugger enables you to do the following:
Print messages in a concurrent log file or debug log file
Print timing information for API calls
Run PL/SQL profiler
Start Order Management and Inventory debuggers and print Order Management and
Inventory messages to same debug file along with Shipping Execution debug messages
Start and stop the debugger for each session or action in the following ways:
- Within the Shipping Transactions form or Quick Ship window, Tools menu, select
Debug
- Within the Release Sales Orders for Picking window, Tools menu, select Debug
- Log level parameter on Oracle Shipping Execution concurrent programs
The Oracle Shipping Debugger enables you to debug certain areas of Code Flow:
Chapter
CLASSROOM
Oracle Shipping Debugger
Chapter
CLASSROOM
Logging is enabled or disabled in two dimensions:

- Level: A scale specifying the priority of a log message
- Module: Describes which part of the code the log message is in
The level and module of any given log message are defined by the programmer who
makes the logging API call to log the message.
Oracle Shipping Debugger Profile Options
There are 6 profile options specific to the Oracle Shipping Debugger:
WSH: Debug File Prefix: Naming Convention for Debug File is <Debug File Prefix
Profile>_sessionid.dbg. If value of profile is null, naming convention is
wsh_<username>_<sessionid>.dbg. Where: <username> is Application user name. If
application context is not established, it will be defaulted to dbuser: <dbusername>.
<sessionid> is Database session id.
WSH: Debug Enabled: Select from the Debug Enabled LOV either YES or NO to activate the
debug feature. The default is NO.
WSH: Debug Module: The Module describes where to find the log message within the code.
This profile indicates that debug messages from only those modules with names beginning
with the profile value will be logged. The naming convention for Module is: <application short
name>.<directory>.<package>.<routine>. <label> e.g. wsh.plsql.WSH_WV_
UTILS.convert_uom.
WSH: Debug Log Directory: The value entered for this profile option must be specified as a
UTL_FILE parameter value.
WSH: Debug Level: The level is a scale specifying the priority of a log message. The level is
the lowest level for which the user wants to see messages. Select from the Debug Level LOV
one of the following.
Valid Values are (in increasing order of priority):
Performance
Statement
Procedure
Event
Exception
Error
Unexpected Error
WSH: Run PL/SQL Profiler: If this profile option is turned on and you are using PL/SQL,
then it collects the performance statistics for the PL/SQL code.
Shipping Lookups
(N) Shipping > Setup > Lookups
Lookups are how you define selections within a list of values (LOV). The Lookups window
enables you to search for existing lookups, edit existing lookups, and create new lookups.
The following header fields are used when defining a lookup:
Type: This is the internal name used to identify the lookup.
Meaning: This is the meaning of the lookup type.
Application: This is the Oracle application that uses the lookup (Shipping Execution).
Description: This is the description of the lookup.
The body of the Lookups window contains the following:
Code: This is a unique code that is used for each value in the lookup.
Meaning: This is the meaning of the code used for each value.
Description: This is the description of the code used for each value.
Effective Dates To / From: These are the dates that are used for the value.
Enabled: This check box enables the value.
Chapter
CLASSROOM
Shipping Lookups
Shipping Parameters
The values for the parameters you specify in Shipping Parameters window are set as the default
values for the parameters in your successive operation. You must enter an organization before
assigning values to the parameters in this window. The Shipping Parameters window consists
of five tabs, they are General, Pick Release, Shipping Transaction, Delivery, and
Transportation.
Chapter
CLASSROOM
Shipping Parameters
General Tab in Shipping Parameters Window

Use the General tab of the Shipping Parameters window to define values for general
parameters such as Unit Of Measurement (UOM), and percentage fill basis. The parameters in
this tab are as follows:
Weight UOM Class: Select the default unit of measure class used by your organization to
measure weight unit of measure.
Volume UOM Class: Select the default unit of measure class used by your organization
to measure volume unit of measure.
Percent Fill Basis: Select the basis on which the minimum fill percentage for a container
in your organization is calculated. This is set as the default value, which can be changed
during execution. The value you specify for this parameter ensures that the containers are
filled at least with the minimum percentage of its total capacity. You can select the
following options:
- Weight/Volume: The percent fill calculation is done based on containers and items
physical attributes defined in Oracle Inventory.
- Quantity: The percent fill calculation is done based on the container-load relationship
setup, which specifies the maximum quantity of the item that can be filled in the
Chapter
CLASSROOM
General Tab In Shipping Parameters Window
Chapter
CLASSROOM
container. The percent fill basis will not be calculated and the Fill % field for the LPN
will display as Null. You are allowed to pack an infinite amount into the container.
Export Compliance Screening: You can select the following:
- Not Required: Select this option when export compliance screening is not required for
shipments of your organization
- At Delivery Creation: Select this option, when export compliance screening must be
done whenever a delivery is created by your organization.
- At Ship Confirm: Select this option, when export compliance screening must be done
whenever a delivery is ship confirmed by your organization
- At Delivery Creation and Ship Confirm: Select this option when export compliance
screening must be done both at delivery creation and ship confirmation.
Note: Third-Party International Trade Management (ITM) application must be installed to
check Export Compliance Screening.
Profile Options
The following list represents profile options available with Oracle Shipping Execution:
WSH: Express Pick - If this profile is enabled (YES), then the Pick Release process will
skip move order line creation, allocations, and the pick confirm process if the following
conditions are met:
- Prior Reservations Only is checked in the Release Sales Orders window before
submitting pick release request
- Auto Pick Confirm is set to Yes in the Release Sales Orders window before
submitting pick release request
If the above conditions are met then the lines will not be Staged if:
- Organization to which line belongs is WMS enabled OR
- The sales order line does not have detailed reservation OR
- Line is not part of ship set but is part of Model/Kit (which has Ship Model Complete
set to Yes) and the shipping parameter Enforce Ship Sets and Ship
- Models is set to Yes OR
Chapter
CLASSROOM
Profile Options
Chapter
CLASSROOM
- Reservations are detailed up to the locator level or sub inventory reserved require a
locator
WSH: Internet Proxy URL: This enables the system to access UPS servers for United
Parcel Service Integration. This profile can only be set at the System Administrator.
WSH: Overpicking Enabled: You can set the value of this profile option to Yes to
enable overpicking.
WSH: Pick Release Batch Size: This enables you to change the batch size from 3 to
1000. Any value less than 3 is interpreted as 3 and any value greater than 1000 is
interpreted as 1000.
WSH: Quick Ship Default View: This enables you to determine the default view of the
Quick Ship window.
WSH: Retain ATO Reservations: This enables you to avoid the redundancy of rereserving an item. If set to Yes, then the inventory system retains the reservation and the
reservation status changes from Staged to Not Staged, while the delivery line status
changes to Backordered.
WSH: Bulk Batch Size: This profile enables you to specify how many lines are to be
interfaced to Oracle Order Management per call. This enables you to specify the batch size
that is inserted in the Oracle Inventory tables.
WSH: Defer Inventory Process: When this profile option value is set to YES, then
Oracle Inventorys Process Online API call will be deferred. If the value is set to either
NULL or NO, then the process online API will be called in online mode.
Note: No Pick slips can be generated for lines processed as part of Express Pick. The
subinventory where reservation was created (before pick release) will be used for storage of
material and staging. The Staging subinventory and locator entered on the Release Sales Order
window is always ignored.
Global Parameters General Tab

(N) Shipping > Setup > Global Parameters (T) General
Use the Global Shipping Parameters window to define parameters that impact the Oracle
Shipping Execution and Oracle Transportation Execution across all organizations of a
particular instance.
General Tab
Use the General tab on the Global Shipping Parameters form to define miscellaneous
parameters such as whether or not to enforce ship methods, defer interface, consolidate
backorders, allow future ship dates. You also define the Oracle Workflow settings and the
unit of measure(UOM) defaults for all of your organizations.
- Enforce Ship Method: Select this check box to enforce that a ship method is entered
and recorded for each shipment. This is recommended if your business practices
require a record of the ship method/carrier for each shipment.
- Allow Future Ship Date: If select this check box, you can enter a future date as the
Actual Departure Date while Ship Confirming the delivery. If you do not select this
Chapter
CLASSROOM
Global Parameters General Tab
Chapter
CLASSROOM
check box, you cannot enter a future date as the Actual Departure Date while Ship
Confirming the delivery.
- Defer Interface: Select this check box to defer shipping interfaces from initiating
updates to the interface tables. In this case, you must manually run the interface or
schedule the interface to run to update interface tables. For example, if you defer the
Inventory Interface, the inventory tables are not updated until you run the Inventory
Interface in the Shipping Interfaces window. If you do not select this check box the
interfaces are run automatically at Ship Confirmation.
- Consolidate Backordered Lines: Select this checkbox if you want to split delivery
lines to be automatically consolidated as they become backordered. For example, if
you split a line with quantity 10 into 5 lines of quantity 2, then during processing, the
inventory available equals 4 items. In this case, 3 lines will be backordered and
consolidated into 1 line with quantity of 6.
Summary
Chapter
CLASSROOM

Chapter
CLASSROOM

D50091GC20 SG

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

D50091GC20 SG

Transféré par

Droits d'auteur :

Formats disponibles

Student Guide

Oracle University and Egabi Solutions use only

R12 Oracle Order Management

Copyright 2009, Oracle. All rights reserved.

U.S. GOVERNMENT RIGHTS

Oracle University and Egabi Solutions use only

Order Entities and Order Flows ....................................................................................................................2-1

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Overview of Oracle Order Management .......................................................................................................1-1

Oracle Receivables Setup for Oracle Order Management...........................................................................5-1

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Item Master Organization ..............................................................................................................................4-23

Oracle Order Management Fundamentals ...................................................................................................7-1

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Setting up Versioning and Audit History ......................................................................................................6-35

Overview of Shipping Execution ....................................................................................................................9-1

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Qualifier Overview ........................................................................................................................................8-54

Copyright Oracle, 2009. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Oracle University and Egabi Solutions use only

Oracle Order Management Fundamentals Table of Contents

Thorough knowledge of Oracle Order Management

Working experience with Oracle Shipping Execution

There are no prerequisites for this course.

How This Course Is Organized

Copyright Oracle, 2009. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Oracle Order Management Users Guide

Oracle Order Management Implementation Manual

Oracle Shipping Execution Users Guide

Oracle Advanced Pricing Users Guide

Oracle Advanced Pricing Implementation Guide

System release bulletins

Installation and users guides

International Oracle Users Group (IOUG) articles

Copyright Oracle, 2009. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Use the SELECT command to view information stored in the

Copyright Oracle, 2009. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Typographic Conventions in Code

DROP USER scott

CREATE ROLE role

SQL commands and SELECT userid

Typographic Conventions in Oracle Application Navigation Paths

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

(B) Click the Approve button.

Oracle Order Management Fundamentals Table of Contents

Oracle University and Egabi Solutions use only

Typographical Conventions in Oracle Application Help System Paths

Under the General Ledger entry, expand Journals.

Under Journals, select Enter Journals.

Copyright Oracle, 2009. All rights reserved.

Oracle Order Management Fundamentals Table of Contents