Oracle R12 Student Guide PDF

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
R12 Oracle
y ฺ u@
Orderen
d
Management
r e dd s Stu
Fundamentals
w ar 1e- Student
t hi Guide
hes to us
Volume
a
(m nse
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n
D50091GC10
Edition 1.0
September 2007
D52994
Unauthorized reproduction or distribution prohibitedฺ Copyright© 2009, Oracle and/or its affiliatesฺ
Copyright © 2007, Oracle. All rights reserved.
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.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted
by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may
be trademarks of their respective owners.
a
Author
) has
Pratima Mahtani c o m ฺ
ฺ
ail uide
Technical Contributors and Reviewers m
g nt G
u @
d d yฺ tude
rre this S
Order Management QA Team, Karen Zawada, Rahul Sharma
a
h e sw use
This book was published using: oracletutor
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Table of Contents
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
Practice - Practice - Creating a User and Assigning Responsibilities........................................................1-12
Solution – Creating a User and Assigning Responsibilities.......................................................................1-13
Practice - Practice - Customizing the Quick Sales Orders Window ..........................................................1-16
Solution – Customizing the Quick Sales Orders Window .........................................................................1-17
Summary........................................................................................................................................................1-23
a
has
Order Entities and Order Flows ....................................................................................................................2-1
)
Order Entities and Order Flows.....................................................................................................................2-3
m ฺ
ฺ c o
Objectives ......................................................................................................................................................2-4
ail uide
Order to Cash Lifecycle with Standard Items................................................................................................2-5
m
@ g nt G
Practice - Practice - Order to Cash Cycle with Standard Items .................................................................2-18
Solution – Order to Cash cycle with Standard Items .................................................................................2-19
u
yฺ tude
Order to Cash Lifecycle with PTO Models and PTO Kits ............................................................................2-29
d d
rre this S
Practice - Practice - Order to Cash Cycle with PTO Kits ..........................................................................2-31
a
Solution – Order to Cash Cycle with PTO Kits .........................................................................................2-32
h e sw use
Drop Shipments .............................................................................................................................................2-41
( m a
Drop Shipments Across Ledgers ...................................................................................................................2-43
to
di cens e
Practice - Order to Cash Cycle with Customer Acceptance ......................................................................2-46
Solution – Order to Cash Cycle with Customer Acceptance .....................................................................2-48
a
mm ble li
Back-to-Back Orders .....................................................................................................................................2-52
U
Guided Demonstration – Creating Back to Back Orders ...........................................................................2-53
ar fera
Sales Agreements ..........................................................................................................................................2-62
e w
s ans
Negotiation Agreement..................................................................................................................................2-63
h
Ma on-tr
Approve Sales Agreement .............................................................................................................................2-64
Releases Against a Sales Agreement .............................................................................................................2-65
nPractice - Practice - Creating a Sales Agreement ......................................................................................2-67
Solution – Creating a Sales Agreement .....................................................................................................2-68
Order to Cash Lifecycle with Customer Acceptance.....................................................................................2-72
Practice - Order to Cash Cycle with Customer Acceptance ......................................................................2-76
Solution – Order to Cash Cycle with Customer Acceptance .....................................................................2-78
Summary........................................................................................................................................................2-82
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
Guided Demonstration – Setting Up Guided Deomonstration - Setting Up MOAC .................................3-13
Summary........................................................................................................................................................3-23
Oracle Inventory Setup for Oracle Order Management..............................................................................4-1
Oracle Inventory Setup for Oracle Order Management.................................................................................4-3
Objective........................................................................................................................................................4-4
Overview .......................................................................................................................................................4-5
Copyright © Oracle, 2007. All rights reserved.
Oracle Order Management Fundamentals Table of Contents

Unauthorized reproduction or distribution prohibitedฺ
i Copyright© 2009, Oracle and/or its affiliatesฺ
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
Guided Demonstration - Creating Subinventories .....................................................................................4-12
Practice - Creating Subinventories ............................................................................................................4-13
Solution - Creating Subinventories............................................................................................................4-14
Interorganization Shipping Networks............................................................................................................4-21
Shipping Method ...........................................................................................................................................4-23
Units of Measure ...........................................................................................................................................4-24
Uses of Units of Measure ..............................................................................................................................4-25
Unit of Measure Class ...................................................................................................................................4-26
Guided Demonstration - Creating Unit of Measure Classes......................................................................4-27
Unit of Measure Conversions ........................................................................................................................4-29
Guided Demonstration - Defining Unit of Measure Conversions..............................................................4-30
Guided Demonstration - Creating Units of Measure .................................................................................4-31
Practice - Defining Units of Measure ........................................................................................................4-32 a
) has
Solution – Defining Units of Measure .......................................................................................................4-33
What is an Item? ............................................................................................................................................4-37
c o m ฺ
Steps to Setup, Define, and Maintain Items...................................................................................................4-38
ฺ
ail uide
Defining Items ...............................................................................................................................................4-39
m
g nt G
Item Master Organization ..............................................................................................................................4-41
@
Item Validation Organization ........................................................................................................................4-43
u
d d yฺ tude
Item Attributes...............................................................................................................................................4-44
rre this S
Unit of Measure Attributes ............................................................................................................................4-45
a
Order Management Item Attributes...............................................................................................................4-47
h e sw use
Item Validation ..............................................................................................................................................4-51
a to
Item Status .....................................................................................................................................................4-54
( m e
Item Statuses and Attributes ..........................................................................................................................4-55
di cens
a
Organization Assignment and Organization Items ........................................................................................4-56
U mm ble li
Control Levels ...............................................................................................................................................4-57
Guided Demonstration - Defining Items....................................................................................................4-59
ar fera
Practice - Practice - Defining Items ...........................................................................................................4-60
w
h e s ans
Solution - Defining Items ..........................................................................................................................4-62
Ma on-tr
Item Relationships .........................................................................................................................................4-68
Customer Items..............................................................................................................................................4-69
n
What are Supply and Demand? .....................................................................................................................4-70
Available to Promise .....................................................................................................................................4-71
Uses of ATP in Oracle Inventory ..................................................................................................................4-72
Defining an ATP Rule ...................................................................................................................................4-73
Guided Demonstration - Creating an ATP Rule ........................................................................................4-74
Implementation Considerations .....................................................................................................................4-76
Summary........................................................................................................................................................4-77
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
Practice - Creating a Customer ..................................................................................................................5-9
Solution – Creating a Customer.................................................................................................................5-10
Defining Payment Terms...............................................................................................................................5-14
Defining Invoicing and Accounting Rules ....................................................................................................5-15
Defining Auto-Accounting Parameters .........................................................................................................5-16
Defining Territories in Receivables...............................................................................................................5-19

ii Copyright© 2009, Oracle and/or its affiliatesฺ
Practice - Defining a Territory...................................................................................................................5-20
Solution - Defining a Territory ..................................................................................................................5-21
Defining Invoice Sources (Batch Source) – Automatic Transaction Numbering ..........................................5-23
Define Salespersons to Assign Sales Credit ..................................................................................................5-25
Using the Resources Window to Create a Salesperson..................................................................................5-26
Guided Demonstration – Creating a Salesperson ......................................................................................5-27
Tax Setups in Transaction Types Window – Receivables and Order Management ......................................5-28
Practice - Viewing Tax Setups...................................................................................................................5-29
Solution – Viewing Tax Setups .................................................................................................................5-30
Overview of Credit Checking........................................................................................................................5-31
Defining Credit Checking on the Customers Page – Profile Tab ..................................................................5-32
Practice - Defining Credit Check and Hold ...............................................................................................5-34
Solution – Defining Credit Check and Hold..............................................................................................5-35
Defining Credit Checking on the Customers Page - Profile Amounts Tab ...................................................5-37
Credit Check Rules........................................................................................................................................5-39
Summary........................................................................................................................................................5-40
Oracle Order Management Setup Steps........................................................................................................6-1
a
has
Oracle Order Management Setup Steps.........................................................................................................6-3
Objectives ......................................................................................................................................................6-4
)
m ฺ
Order Management Setup Steps ....................................................................................................................6-6
ฺ c o
ail uide
Profile Options and System Parameters.........................................................................................................6-10
m
Overview of QuickCode or Lookup Types....................................................................................................6-12
g nt G
Defining QuickCode or Lookup Types .........................................................................................................6-14
u @
d d yฺ tude
Overview of Order Header and Order Line Processing Flows ......................................................................6-15
Overview of Transaction Types Window ......................................................................................................6-16
rre this S
Guided Demonstration - Setting up Transaction Types.............................................................................6-19
a
h e sw use
Practice - Setting up Transaction Types ....................................................................................................6-22
Solution – Setting Up Transaction Types ..................................................................................................6-23
m a to
Workflow in Transaction Types ....................................................................................................................6-29
(
di cens e
Guided Demonstration – Creating and Booking a Sales Order, Viewing Workflow Status, Viewing Workflow
a
mm ble li
Status .........................................................................................................................................................6-31
Guided Demonstration - Customizing Workflow Associated with an Order ............................................6-33
U
ar fera
Overview of Document Sequences for Order Numbering.............................................................................6-37
w
s ans
Defining Order Import Sources .....................................................................................................................6-39
e
h
Overview of Processing Constraints..............................................................................................................6-40
Ma on-tr
Setting up Processing Constraints .................................................................................................................6-42
nGuided Demonstration - Setting Up a Processing Constraint....................................................................6-45
Defining Validation Templates......................................................................................................................6-48
Defining Defaulting Conditions ....................................................................................................................6-50
Defining Defaulting Rules.............................................................................................................................6-52
Practice - Setting Up a Defaulting Rule.....................................................................................................6-54
Solution - Setting Up a Defaulting Rule ....................................................................................................6-58
Setting up Versioning and Audit History ......................................................................................................6-67
Overview of Available To Promise (ATP) ....................................................................................................6-69
Overview of Scheduling Levels.....................................................................................................................6-71
Practice - Using Scheduling in the Sales Orders Window.........................................................................6-73
Solution - Using Scheduling in the Sales Orders Window ........................................................................6-75
Auto-Schedule Profile Option .......................................................................................................................6-79
Defining Credit Usage Rule Sets ...................................................................................................................6-81
Defining Credit Check Rules.........................................................................................................................6-83
Practice - Defining Credit Check Ruless ...................................................................................................6-85
Solution – Defining Credit Check Rule .....................................................................................................6-86
Summary........................................................................................................................................................6-88
Holds, Order Purge, and Exception Management Setup .............................................................................7-1
Holds, Order Purge, and Exception Management Setup ...............................................................................7-3
Objectives ......................................................................................................................................................7-4

iii Copyright© 2009, Oracle and/or its affiliatesฺ
Holds .............................................................................................................................................................7-5
Seeded Holds .................................................................................................................................................7-6
Automatic Holds............................................................................................................................................7-8
Generic Holds................................................................................................................................................7-10
Hold Sources .................................................................................................................................................7-11
Practice - Creating and Applying Holds ....................................................................................................7-13
Solution - Creating and Applying Holds ...................................................................................................7-14
Order and Quote Purge ..................................................................................................................................7-26
Purge Sets ......................................................................................................................................................7-27
Setting Up Exception Management ...............................................................................................................7-29
Guided Demonstration – Setting up Exception Management....................................................................7-31
Summary........................................................................................................................................................7-35
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
a
has
Overview of Pricing Concepts.......................................................................................................................8-8
Overview of the Pricing Engine ....................................................................................................................8-10
)
m ฺ
Overview of Pricing Security ........................................................................................................................8-11
ฺ c o
ail uide
Overview of Price Lists .................................................................................................................................8-12
m
Overview of Pricing Agreements ..................................................................................................................8-14
g nt G
Overview of Formulas ...................................................................................................................................8-15
u @
d d yฺ tude
Overview of Qualifiers ..................................................................................................................................8-16
Overview of Modifiers ..................................................................................................................................8-17
rre this S
Overview of Contexts and Attributes ............................................................................................................8-19
a
h e sw use
Overview of Freight and Special Charges Modifiers.....................................................................................8-20
Overview of Basic Versus Advanced Pricing................................................................................................8-21
m a to
Overview of Price Lists .................................................................................................................................8-22
(
di cens e
Price List Information....................................................................................................................................8-24
a
mm ble li
Creating a Price List ......................................................................................................................................8-27
Price List Header ...........................................................................................................................................8-28
U
ar fera
Price List Line ...............................................................................................................................................8-30
w
s ans
Secondary Price List......................................................................................................................................8-34
e
h Practice - Creating a Price List ..................................................................................................................8-35
Ma on-tr
Solution - Creating a Price List..................................................................................................................8-37
n
Copy Price List ..............................................................................................................................................8-40
Practice - Copying a Price List ..................................................................................................................8-41
Solution - Copying a Price List..................................................................................................................8-42
Price List Maintenance: Overview ................................................................................................................8-44
Manual Price List Updates.............................................................................................................................8-45
Practice - Manually Updating a Price List.................................................................................................8-47
Solution - Manually Updating a Price List ................................................................................................8-48
Adjust Price List ............................................................................................................................................8-50
Practice - Adjusting a Price List ................................................................................................................8-52
Solution - Adjusting a Price List................................................................................................................8-53
Add Items to Price List..................................................................................................................................8-55
Practice - Adding an Item Category to a Price List ...................................................................................8-57
Solution - Adding an Item Category to a Price List...................................................................................8-59
Overview of Modifiers ..................................................................................................................................8-62
Creating Modifier Lists .................................................................................................................................8-63
Adding Modifier Lines ..................................................................................................................................8-65
Creating Modifiers Lines...............................................................................................................................8-66
Modifier Line Examples ................................................................................................................................8-68
Modifier Types ..............................................................................................................................................8-69
Discount Modifier..........................................................................................................................................8-70

iv Copyright© 2009, Oracle and/or its affiliatesฺ
Practice - Creating a Discount Modifier Using Qualifiers.........................................................................8-71
Solution - Creating a Discount Modifier Using Qualifiers ........................................................................8-74
Price Break Modifiers: Point Breaks .............................................................................................................8-80
Surcharge Modifier........................................................................................................................................8-81
Qualifier Overview ........................................................................................................................................8-82
Example of Qualifier Hierarchy ....................................................................................................................8-83
Using Qualifiers with Modifier Lists.............................................................................................................8-85
Freight and Special Charge List Modifier .....................................................................................................8-86
Seeded Freight Charges .................................................................................................................................8-88
Setting Up Freight and Special Charge List Modifiers..................................................................................8-89
Practice - Creating a Freight and Special Charge List Modifier ................................................................8-90
Solution - Creating a Freight and Handling Charges Modifier..................................................................8-95
Overview of Price Books...............................................................................................................................8-111
Price Book Example 1 ...................................................................................................................................8-113
Benefits of Price Books .................................................................................................................................8-116
Price Book Implementation ...........................................................................................................................8-117 a
Implementation Steps: Setting Key Profile Options.....................................................................................8-118
) has
Implementation Steps: Setting Key Profile Options......................................................................................8-119
c o m ฺ
Implementation Steps: Verifying Pricing Parameters....................................................................................8-120
ฺ
ail uide
Implementation Steps: Setting Up the Default Printer...................................................................................8-122
m
g nt G
Implementation Steps: Setting up Oracle XML Publisher.............................................................................8-123
@
Creating a Price Book....................................................................................................................................8-124
u
d d yฺ tude
Creating a Price Book: Defining General Price Book Criteria .....................................................................8-125
rre this S
Creating a Price Book: Defining Price Calculation Criteria .........................................................................8-126
a
Creating a Price Book: Selecting Price Book Publishing Options................................................................8-127
h e sw use
Price Book Publishing Templates..................................................................................................................8-128
a to
Price Book Publishing: Document Types......................................................................................................8-129
( m e
Generating and Publishing Price Books ........................................................................................................8-130
di cens
a
Viewing Price Book Details Online ..............................................................................................................8-131
U mm ble li
Maintaining Price Books ...............................................................................................................................8-133
Republishing Price Books..............................................................................................................................8-134
ar fera
Viewing Errors ..............................................................................................................................................8-135
w
e s ans
Profile Options in Basic Pricing ....................................................................................................................8-136
h
M a n-tr
Summary........................................................................................................................................................8-138
noof Shipping Execution ....................................................................................................................9-1

Overview
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
Guided Demonstration – Shipping Transaction Form ...............................................................................9-20
Query Manager ..............................................................................................................................................9-21
Data Manager ................................................................................................................................................9-22
Quick Ship Window ......................................................................................................................................9-23
Guided Demonstration – Quick Ship Window ..........................................................................................9-24

v Copyright© 2009, Oracle and/or its affiliatesฺ
Reports and Processes ...................................................................................................................................9-26
Integration With Oracle Order Management .................................................................................................9-27
Integration With Oracle Transportation Management ...................................................................................9-28
Integration With Oracle Warehouse Management.........................................................................................9-29
Integration with Oracle Workflow.................................................................................................................9-30
Summary........................................................................................................................................................9-31
Shipping Execution Setup ...............................................................................................................................10-1
Shipping Execution Setup .............................................................................................................................10-3
Objectives ......................................................................................................................................................10-4
Roles..............................................................................................................................................................10-5
Guided Demonstration - Defining Roles ...................................................................................................10-7
Practice - Defining Roles...........................................................................................................................10-8
Solution - Defining Roles ..........................................................................................................................10-9
Granting Roles To Users ...............................................................................................................................10-14
Guided Demonstration – Granting Access to Roles ..................................................................................10-16
Practice - Granting Access to Roles ..........................................................................................................10-17
Solution -Granting Access to Roles...........................................................................................................10-18
a
has
Freight Carriers..............................................................................................................................................10-19
Guided Demonstration - Defining Freight Carriers ...................................................................................10-21
)
m ฺ
Freight Costs..................................................................................................................................................10-22
ฺ c o
ail uide
Guided Demonstration – Defining Freight Cost Types .............................................................................10-23
m
Transit Times.................................................................................................................................................10-25
g nt G
Regions and Zones.........................................................................................................................................10-27
u @
d d yฺ tude
Shipping Document Sets ...............................................................................................................................10-29
Guided Demonstration – Defining Document Sets....................................................................................10-30
rre this S
Document Categories ....................................................................................................................................10-31
a
h e sw use
XML Publisher Enabled Documents .............................................................................................................10-33
Customizing and Creating Templates............................................................................................................10-35
m a to
Document Sequences.....................................................................................................................................10-36
(
di cens e
Choosing Printers For Searching Documents and Labels..............................................................................10-38
a
mm ble li
ITM Adapter Integration ...............................................................................................................................10-40
Delivery Compliance Screening ....................................................................................................................10-41
U
ar fera
Shipping Exceptions ......................................................................................................................................10-43
w
s ans
Defining Shipping Exceptions.......................................................................................................................10-45
e
h
Logging Shipping Exceptions........................................................................................................................10-47
Ma on-tr
View and Update Logged Shipping Exceptions ............................................................................................10-49
nGuided Demonstration – Viewing Shipping Exceptions ...........................................................................10-50
Purge and Resolve Logged Shipping Exceptions ..........................................................................................10-52
Running Pick Release....................................................................................................................................10-53
Release Sequence Rules ................................................................................................................................10-54
Practice - Defining Release Sequence Rules .............................................................................................10-56
Solution -Defining Release Sequence Rules..............................................................................................10-57
Pick Slip Grouping Rule................................................................................................................................10-58
Practice - Defining Pick Slip Grouping Rules ...........................................................................................10-60
Solution - Defining Pick Slip Grouping Rules ..........................................................................................10-61
Release Rules.................................................................................................................................................10-62
Release Rule – Order Tab..............................................................................................................................10-63
Release Rule – Shipping Tab.........................................................................................................................10-65
Release Rule – Inventory Tab........................................................................................................................10-67
Practice - Defining Release Rules .............................................................................................................10-69
Solution - Defining Release Rules.............................................................................................................10-70
Pick Release tab in Shipping Parameters Window ........................................................................................10-72
Auto Allocate.................................................................................................................................................10-74
Autocreate Deliveries ....................................................................................................................................10-75
Auto Pick Confirm.........................................................................................................................................10-76
Release Sales Orders for Picking Window ....................................................................................................10-78

vi Copyright© 2009, Oracle and/or its affiliatesฺ
Ship Confirm Rules .......................................................................................................................................10-79
Ship Confirm Rule Ship Options...................................................................................................................10-80
Ship Confirm Rule Trip Options ...................................................................................................................10-82
Ship Confirm Rule Document Set .................................................................................................................10-84
Ship Confirm Rule Shipping Parameters.......................................................................................................10-85
Creating Containers .......................................................................................................................................10-87
Container-Item Relationship..........................................................................................................................10-88
Container Load Details ..................................................................................................................................10-90
Guided Demonstration – Defining Container Load Details.......................................................................10-91
Packing Delivery Lines into Containers ........................................................................................................10-93
Packing Workbench.......................................................................................................................................10-95
Delivery Flow - Generic ................................................................................................................................10-97
Trip Flow – Generic ......................................................................................................................................10-98
Ship to Deliver Process Workflow ................................................................................................................10-99
Workflow Lookups........................................................................................................................................10-100
Workflow Specific Profile Options ...............................................................................................................10-101
Workflow Specific Shipping and Global Parameters ....................................................................................10-102
Business Events .............................................................................................................................................10-104a
) has
Purging Workflows........................................................................................................................................10-106
Oracle Shipping Debugger ............................................................................................................................10-107
c o m ฺ
Shipping Lookups..........................................................................................................................................10-109
ฺ
ail uide
Shipping Parameters ......................................................................................................................................10-110
m
g nt G
General Tab In Shipping Parameters Window ..............................................................................................10-111
@
Profile Options...............................................................................................................................................10-113
u
d d yฺ tude
Global Parameters – General Tab..................................................................................................................10-115
rre this S
Summary........................................................................................................................................................10-117
a
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

vii Copyright© 2009, Oracle and/or its affiliatesฺ
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Preface
Profile
Before You Begin This Course
• Thorough knowledge of navigation through the applications
• Working experience with Oracle Order Management
Prerequisites
• There are no prerequisites for this course.
s a
How This Course Is Organized
)h a
m
odemonstrations
This is an instructor-led course featuring lecture and hands-on exercises. Online
and written practice sessions reinforce the concepts and skills introduced. a i l ฺ c
i d eฺ
g m t Gu
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
Ma on-t
n

ix Copyright© 2009, Oracle and/or its affiliatesฺ
Related Publications
Oracle Publications
Title Part Number
Oracle Order Management User’s Guide B28099-01
Oracle Order Management Implementation Manual B25975-01
Oracle Shipping Execution User’s Guide B31232-01
Oracle Inventory User’s Guide B31547-02
Oracle Advanced Pricing User’s Guide B31581-01
Oracle Advanced Pricing Implementation Manual B31440-01
a
Additional Publications
) has
• System release bulletins c o m ฺ
ฺ
ail uide
• Installation and user’s guides
m
g nt G
u @
d d yฺ tude
rre this S
• Read-me files
a
• International Oracle User’s Group
h e sw uarticles
(IOUG) se
( m a to
• Oracle Magazine di ns e
a c e
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

x Copyright© 2009, Oracle and/or its affiliatesฺ
Typographic Conventions
Typographic Conventions in Text
Convention Element Example
Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.
lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the ORD block.
windows Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);
case sensitive directory names, Directory: bin (DOS), $FMHOME (UNIX)
(default is filenames,
lowercase) passwords,
Filename: Locate the init.ora file.
s a
pathnames,
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects )h a
URLs, m
co deฺ
URL: Go to http://www.oracle.com
i l ฺ
ma t Gui
user input,
User input: Enter 300
usernames g
u@ uden
Username: Log on as scott
Initial cap Graphics labels y ฺ
Customer address (but Oracle Payables)
(unless the term is a
r e dd s St
proper noun) a r t h i
w e
Italic Emphasized words
and phrases, a
For hfurthers information,
Do notesave changes
t o u sto the
see
database.
Oracle7 Server SQL Language
titles of books andi (m s
Reference e Manual.
a d Enter c e nuser_id@us.oracle.com,
courses,
m l i
m ble name of the user.
variables
where user_id is the
Quotation r U ra
awith longfeelements
Interface Select “Include a reusable module component” and click Finish.
s w s
he -trthatan only
marks names
a
M on initialhave This subject is covered in Unit II, Lesson 3, “Working with
caps; Objects.”
n lesson and chapter
titles in cross-
references
Uppercase SQL column Use the SELECT command to view information stored in the
names, commands, LAST_NAME
functions, schemas, column of the EMP table.
table names
Arrow Menu paths Select File > Save.
Brackets Key names Press [Enter].
Commas Key sequences Press and release keys one at a time:
[Alternate], [F], [D]
Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

xi Copyright© 2009, Oracle and/or its affiliatesฺ
Typographic Conventions in Code
Convention Element Example
Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER
(OG_GET_LAYER (‘prod_pie_layer’))
Lowercase Syntax variables CREATE ROLE role

italic
a
Uppercase SQL commands and SELECT userid
functions FROM emp; ) has
c o m ฺ
ฺ
ail Paths ide
Typographic Conventions in Oracle Application Navigation m
g nt G u
u @ de to direct you
d d yฺ example,
This course uses simplified navigation paths, such as the following
t u
rre this S
through Oracle Applications.
a
w Queryse> Find (B) Approve
(N) Invoice > Entry > Invoice Batches Summary
h e s(M) u
m a t o
a di (following:
This simplified path translates to the
e n se
m
1. (N) From the Navigator m window,
l e licselect Invoice then Entry then Invoice Batches
Summary. a r U erab
e s w nsf
h From-trthe
2. a(M) a menu, select Query then Find.
M n
3. (B) noClick the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

xii Copyright© 2009, Oracle and/or its affiliatesฺ
Typographical Conventions in Oracle Application Help System Paths
This course uses a “navigation path” convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example—
(Help) General Ledger > Journals > Enter Journals
—represents the following sequence of actions:
1. In the navigation frame of the help system window, expand the General Ledger entry.
2. Under the General Ledger entry, expand Journals.
3. Under Journals, select Enter Journals. a

) h as
4. Review the Enter Journals topic that appears in the document frame of the helpmsystem
o
window.
a ilฺ uideฺ
c
@ gm nt G
d y ฺu tude
r r ed is S
w a e th
s
he to us
a
(m nse
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n

xiii Copyright© 2009, Oracle and/or its affiliatesฺ
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

xiv Copyright© 2009, Oracle and/or its affiliatesฺ
a
) has
c o m ฺ
ฺ
ail uide
m
g ntOrder G
Overview uof@Oracle
Management
d d yฺ tude
a r re this S
e s wChapterse1
a h to u
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Overview of Oracle Order Management

Unauthorized reproduction or distribution prohibitedฺ Copyright©
Chapter 1 - Page 1 2009, Oracle and/or its affiliatesฺ
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

What is Oracle Order Management?
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Oracle
What is
MOracle n - tr Order Management?
noOrder 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

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
a
) has
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
c o m ฺ
ฺ
and the invoice interface activity in the respective workflows.
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order Capture and Order Fulfillment
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Oracle Order Management Capabilities
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-trManagement Capabilities
Oracle
MYou
Order
• o get orders from various sources, process and fulfill them in e-Business suite.
ncan
• 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

profile option Personalize Self-Service Defn for the Personalize Page link to display on the
page.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order to Cash Lifecycle
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
MAatypical
Order to Cash
n - tr Lifecycle
no 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 customer’s 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.

Integration with Other Products
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-with
Integration
MOracle tr Other Products
noOrder Management is closely integrated with the Advanced Pricing, Shipping
Execution, Configurator and Release Management products that are part of the Order
Management suite.

Practice - Practice - Creating a User and Assigning
Responsibilities
Overview
In this practice you will learn how to create a user and assign responsibilities to the user
Assumptions
• You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
• Your instructor will provide login information.

a
• Replace XX with the number provided by your instructor or your initials.
) has
c o m ฺ
ฺ
• Use System Administrator or comparable System Administration responsibility.
ail uide
m
g nt G
Tasks
u @
1. Create a user and assign responsibilities to it. edd
yฺ tude
a rr this S
2. Ensure that the Order Management Super
h e swUseruVision
se Operations USA responsibility has
the appropriate menu assigned to a
it. to
( m e
a di cens
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Solution – Creating a User and Assigning Responsibilities
Login
1. Login to the database.
User Name: operations
Password: welcome
2. Select the System Administrator responsibility.
3. Create a User. (N) Security > User > Define
a
has
Enter the following information:
a. User: <your chosen login name>
)
m ฺ
b. Password: o
<any pwd of your choice; you need to type it twice>
ฺ c
c. Password Expiration: select None
m ail uide
d. Effective Dates: enter dates
@ g nt G
u
yฺ tude
d d
4. (M) File > Save.
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

5. Assign the following responsibilities to your user using (T) Direct Responsibilities:
Responsibility Security Group

Order Management Super User, Vision Operations Standard
(USA)
Inventory, Vision Operations (USA) Standard
Receivables Manager Standard
System Administrator Standard
Human Resources, Vision Enterprises Standard
Purchasing Super User, Vision Operations Standard
Revenue Management Super User, Vision Operations (USA) Standard
6. (I) Save.
a
7.
has
Log out of the operations username and login again using your newly created account.
)
You will be prompted to change your password.
c o m ฺ
ฺ
ail uide
Note: You can use this account for subsequent logins. m
g nt G
u @ e
dyฺ Stud responsibility again
8. Once you have logged in again, select the System Administrator
and navigate to (N) Security > Responsibilitye>dDefine.
a rr this
9. Query for the Order ManagementeSuper
h sw User u e Operations USA responsibility
sVision
(F11 and Ctrl-F11).
( m a to
i ens
dappropriate e
a c menu (shown below) ADS_OM_SUPERMENU is
liUser
mm
10. Please ensure that the
assigned U
r to the OMb l e
Super responsibility.
wa nsfer a
h e s a
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
11. Save your work and close theaResponsibilities
to window.
( m e
a di cens
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Practice - Customizing the Quick Sales Orders Window
Overview
In this practice you will learn how to customize the Quick Sales Orders window.
• Open the Quick Sales Orders window
• Use the Folder Tool
• Enable Diagnostics
• Personalize the Quick Sales Orders window
s a
Assumptions
)h a
• You must have access to an Oracle Application Vision database or comparable
m
co detraining
ฺ
a i l ฺ i
or test instance at your site on which to complete this practice.m
g G u
@ den t
• Your instructor will provide login information. yฺu
r e dd s Stu
• Replace XX with the number provided by
w aryoureinstructor
t hi or your initials.
a h es us
• Use System Administratorm
( to System Administration responsibility.
or comparable
e
a di cens
Tasks
U mm ble li
1. Login w ar database
to the f erawith the login and password that you created in the previous practice.
s s
he -thetraresponsibility
n
2. a
M onChoose Order Management Super User, Vision Operations (USA).
n
3. Create a folder at the header and line level using the Folder tool.
4. Enable Diagnostics.
5. Personalize the Quick Sales Orders window.

Solution – Customizing the Quick Sales Orders Window
Login
• UserName: <your login name>
• Password: <your password>
Choose Responsibility
2. Order Management Super User, Vision Operations (USA) Responsibility is selected.

a
has
Customize the Quick Sales Orders window
)
m ฺ
3. (N) > Orders, Returns > Quick Sales Orders
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
4. Place your cursor on any of the header fields and then select (M) Folder > New or (I)
Folder Tools > (I) New.
5. The following window opens:

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
mm ble li
6. Enter the following:
U
r a
- ar name for the header level folder, replacing XX with your initials.
•a Folderfe
s w s
a he -tran
M on • Autoquery – Never
n
• Open as default – selected
• Public – selected
• Others tab (Others box) – selected
• Configure Buttons block – you need to display the Actions button in the
window, so select the Display box of the Actions entry in the Action Name
column
• Click OK to save and return to the Quick Sales Orders window
• Verify the following: your new folder name, Others tab, Actions button – should
be visible on the window

7. Place your cursor at a line level field and re-open the Quick Sales Orders window: (M)
Folder > New or (I) Folder Tools > (I) New.
Note: Enter the order type and customer name in the header so that you can navigate
to the lines region.
8. Enter the following:
• Folder – enter the folder name, replacing XX with your initials
• Autoquery – Never
• Open as default – selected
• Public – selected
s a
)h
• Line Tabs block – select all the tabbed regions that you wish to see in the a
window m
co deฺ
i l ฺ
a to useuini the
• Line Details (Regions) – select all the regions that you
g mwish t G
u @
ฺ tuicon
window (these are accessible by clicking onythe
n
deat the bottom right of
d d of S
a r e details
the window – this expands to show rthe
h i s the selected region)
e s w se t
a h to u
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

9. Save your work and return to the Quick Sales Orders window.
10. Verify the following: your new folder name, all tabs in the Lines block, Regions –
should be visible on the window.
Personalize the window using Forms Personalization
11. With the Quick Sales Orders window open, navigate to the Personalizations window:
(M) Help > Diagnostics > Custom Code > Personalize
12. If there are seeded personalizations already in the window, do not modify them.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
13. Enter a short description in the Description column, “Workflow Status menu”. Select
the Level as Function and select the Enabled box.
14. (T) Condition: Select the Trigger Event as WHEN-NEW-FORM-INSTANCE with a

processing mode of BOTH.
15. (T) Actions: Enter the following:
a. Seq: 1
b. Type: Menu
c. Description: wf menu
d. Language: All

e. Enabled box: selected
16. Menu Entry: SPECIAL2:
17. Menu Label: Workflow Status
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
ar fera
18. (B) Validate.
e w
s Apply n s
h
19. (B)
r a Now.
Ma20. oClose
n -t
n the Personalizations form and return to the Quick Sales Orders window.
21. Close the Quick Sales Orders window and reopen it. Check if the Workflow Status
menu option is now available in the Tools menu.
Use the Specials Menus to add some menu option to your Quick Sales Order window. The
list is below:
Function Special Menu #
Find Customer SPECIAL1
Workflow Status SPECIAL2
Price Debug SPECIAL3
AutoSchedule SPECIAL4

User Sets SPECIAL5
Purge SPECIAL6
Show Line Details SPECIAL7
Item Search SPECIAL8
Quick Customer Entry SPECIAL9
Debug SPECIAL10
Apply Holds SPECIAL11
Mass Change SPECIAL12 a

) h as
Schedule SPECIAL14
c o m ฺ
ฺ
ail uide
Audit SPECIAL15 m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m G
gandnOrder
t
Order Entities
ฺ u @ e
Flowsddy Stud
a rre 2 this
h e sw use
Chapter
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Order Entities and Order Flows

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order to Cash Lifecycle with Standard Items
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Order to r
Cash aLifecycle with Standard Items
MThe o orders window consists of two regions: header region and lines region. You can use
nsales
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.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order to
MProcessing- tr Lifecycle with Standard Items
no 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.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order
MBasic
to
- tr Lifecycle with Standard Items
o is part of Oracle Order Management and Advanced Pricing is part of the Order
nPricing
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.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order
MYou
to
o view the progress of the order using the Tools > Workflow Status option. This
ncan
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.

• 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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Order to r
MThe o functionality enables you to inform your customer when goods are available to fulfill
nATP
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.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order
MBased
to
noon 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.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Order to r
MWhen
noyou 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.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order
MFrom
to
naogeneral 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.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Practice - Order to Cash Cycle with Standard Items
Overview
In this practice, you will learn how to create orders with a standard item. Please note that you
will be completing an order to cash cycle with a standard item using all the seeded data available
in the environment. Examples of seeded data are: Order Type, Customer, Price List, Item, etc.
Assumptions
• Your instructor will provide login information. a

) h as
• Replace XX with the number provided by your instructor or your initials. m
i l ฺ co deฺ
• Use Order Management Super User, Vision Operations (USA)m oracomparableui Super
User Order Management responsibility. g
@ dent G
y ฺ u
e d d S tu
Tasks r
ar e this
Create an order to cash lifecycle hes
w
a t o us
1. Create an order. di (
m se
m a licen
2. Save and U m theborder.
book le
r a
wa nsfether order.
3.esPick release
h -tra
Ma 4. onShip
n confirm the order.
5. Use AutoInvoice to create an invoice for the order.

Solution – Order to Cash cycle with Standard Items
Create an order
1. Navigate to the Quick Sales Orders window:
2. (N) Orders, Returns > Quick Sales Orders
3. Create an order for Computer Service and Rental:

• Customer: Customer Service and Rental (1006)
• Order Type: Standard
4. Verify the following on the Main tab and Others tab (if the field is not visible on the
window, you can folder-enable it): a
• Operating Unit = should be Vision Operations
• Shipping Method: DHL ) has
c o m ฺ
• Warehouse: V1 ฺ
ail uide
• Price List: Corporate m
g nt G
@
• Ship To and Bill To Address should default depending on the Customer
u
Name/Number field value
d d yฺ tude
a r re this S
5. Enter Order Line Information:
• Ordered Item: AS54888 h e sw use
( m a to
• Qty: 2 e
• Shippingm adi DHL c e ns
m ble li
Method:
6. Save your
U
ar work.feThe
ra Status on the line should display as Entered.
s w s
heBook-the
an
M on tr Order using (B) Book Order.
a
7.
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
8. Note: Click (M) Tools > Workflow Status to seedthe
e d statusSoftthe flow. Click (B) View
Diagram on the Workflow Status HTML page
a r r to see
t isorder processes and activities. A
the
h
w by asbox) e indicates that the activity is in
heswindow
green line around an activity (represented
progress. Close the Workflow a Status
t o u to return to the Quick Sales Orders
m
window.
a di ( cense
U mm ble li
ar thefeorder
Pick Release
w ra
s s
e ran > Release Sales Orders
9.h (N) Shipping
a
M on-t
n
10. In the (T) Order tab, the Orders field should show a value of Unreleased.
11. Enter the order number in the Order Number field.
12. The Customer and Order Type fields get populated based on the Order Number field
value.
13. Click (T) Inventory. Set Auto Allocate to Yes.
14. Click (T) Shipping. Set Auto Pick Confirm and Autocreate Delivery to Yes.
15. Click (B) Execute Now to pick release and pick confirm the order.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
r r e i s S
Ship Confirmation a
w se t h
e s
h to u
m a
a di ( ceTransactions
16. Open the Shipping > Shipping nse window.
mm window l e li
r
17. The Query
a U
Manager
r a b opens. Enter your order number in the fields From Order
e s w andnsTofeOrder Number. Select no value in the Line Status field.
Number
h -tra
Ma18. Click
non Find to find your order.
19. The Shipping Transactions window opens to display your order details with the statuses.

a
) has
c o m ฺ
ฺ
ail andutrip
ideshould
m
nt G Auto-
@g deDeliveries,
20. Click on the Delivery, Path by Stop and Path by Trip tabs. The delivery
u
have been autocreated. If not, use the Actions LOV toฺAuto-Create
y
Create Trip.
e d d S tu
r his
arShip eConfirm.
t
w
hes to us
21. Navigate to the (T) Delivery tab. Click (B)
a
(m nse
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n
22. Accept all other defaults. Click (B) Ok.
23. You will get a message that the delivery was successfully confirmed. Click Ok and close
the Shipping Transactions window.

Verifying Status
24. Open the Quick Sales Orders window to check the status of your order. It should display
as Shipped.
25. Click (M) Tools > Workflow Status to see the current status of your order. Click (B)
View Diagram to see the diagrammatic representation of the order flow. When a
workflow activity (represented by a box) is enclosed with a green line, it implies that the
activity is in progress.
Viewing the Shipping Details from the Quick Sales Orders window
26. Click (B) Actions > Additional Line Information to view the delivery and trip
information and status.
a
Order Header Main Tab Line Status
) has Additional Line
c o m ฺ Information
Booked Shipped ฺ
ail uide
Delivery Status =
m
g nt G Closed
u @ Picked Status = Shipped
d d yฺ tude Trip Status = Closed
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Interfacing to Receivables using the Workflow Background Process concurrent
program
27. From the Quick Sales Orders window, navigate to (M) View > Requests. Click (B)
Submit a New Request (single request) and select the concurrent request Workflow
Background Process. Enter the following as parameters:
• Parameters window:
• Item Type: OM Order Line
• Process Deferred: Yes
• Process Timeout: No
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
28. Click Submit to process your request. You will get a request ID that you can track in the
Find Requests window. Click Find to see your request processed. It should complete as
Normal.

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
29. Return to the Quick Sales Orders window. Query
e d yourSorder
dfor t by using the F11 key.
Enter your order number and use the Ctrl-F11 r
ar keys t
to is the query results. Though your
hget
w e
a hesthetline
order status still displays as Booked,
o
s should show up as Closed.
ustatus
Run AutoInvoice d i (m nse
m a lice
30. Navigate toU(N) mReceivables
b le > Interfaces > AutoInvoice. Click (B) Submit a New
r a
erselect a single request when prompted. The concurrent programs
e s wa opens
Request
s f
and then
n enable you to run AutoInvoice.
a h window
t r a to
n- Namewhen
M 31. Inothe
nparameters
field select the AutoInvoice Master Program and enter the following
the parameters window pops up:
• Parameters for AutoInvoice:
• Organization: All
• Invoice Source: ORDER ENTRY
• Date: your current date
• (Low) Sales Order Number: Look for your sales order number in the LOV and
select it
• (High) Sales Order Number: Look for your sales order number in the LOV and
select it

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
32. Click Ok and m mato the
return l i
maincewindow. Click Submit to run AutoInvoice. You will be
r U
given a request ID,a b le you can use to track the status of your request. It should
which
e s
complete s fer
wa asnnormal.
h a
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
rre this S
Viewing your Invoice details
a
33. (N) Quick Order Organizer. Enter e
h sworderunumber
your se and click (B) Find. When your
m
order appears in the result list,
( aclick (B) tActions
o > Additional Order Information > (T)
di cens
Invoices / Credit Memos. e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

34. Click (B) Invoice Details to view the invoice that has been autocreated from your order.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order to Cash Lifecycle with PTO Models and PTO Kits
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order to
MOracle - tr Lifecycle with PTO Models and PTO Kits
noConfigurator 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

• Book and schedule the order
• Pick Release and Ship Confirm the PTO order
• Run AutoInvoice to create an invoice for the order
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Practice - Order to Cash Cycle with PTO Kits
Overview
In this practice, you will learn how to create orders with PTO Models and Kits. Please note that
you will be completing an order to cash cycle with PTO Models and Kits using all the seeded
data available in the environment. Examples of seeded data are: Order Type, Customer, Price
List.
Assumptions
a
) has
c o m ฺ
ฺ
• Replace XX with the number provided by your instructor or your initials.
ail uide
• Use Order Management Super User, Vision Operations @
m G Super
g or comparable
t
u (USA) n
User Order Management responsibility.
d d yฺ tude
r r e i s S
Tasks a
w se t h
e s
h to u
m a
di ( cense
1. Create a PTO Kit in Inventory.
a
mm bleforlithe PTO Kit.
2. Create a Bill of Material
U
w
3. Enter ar feforrathe items.
quantities
h e s ans
Ma4. Create
n - r order for the PTO Kit.
tan
no

Solution – Order to Cash Cycle with PTO Kits
Create a PTO Configuration
1. (N) Inventory > Items > Master Items
2. Enter the item name: OM-PTO-SMC-MODEL
3. Enter the description: pto smc model
4. (M) Tools > Copy From
5. Template: PTO Model
a
has
6. Click (B) Apply
)
m ฺ
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Note: The Template will default the item attributes and statuses. Enter the following elements
of the PTO model to complete the configuration:

PTO SMC Model:
Item Name Item Template Item Type
XX-PTO-SMC- PTO Model PTO

MODEL
XX-PTO-Main-Option- Finished Good Standard

Item
XX-PTO-Main- Finished Good Standard

Included-Item
a
has
XX-PTO-Class-1 PTO Option Class PTO
Standard m )
co deฺ
XX-PTO-Class1- Finished Good
Option-Item i l ฺ
g ma t Gui
XX-PTO-Class1- Finished Good
y ฺ u@ udStandard
en
Included-Item
r e dd s St
XX-PTO-Class-11 PTOw ar Class
Option
e t hi PTO
e s
hFinished u s
XX-PTO-Class11- m a
( nse t o Good Standard
Option-Item d i
a lice
m
m ble
r U
a fera
XX-PTO-Class11- Finished Good Standard
e w
s ans
Included-Item
h -tr
Ma onXX-PTO-Class-2 PTO Option Class PTO
n
Option-Item

Included-Item
XX-PTO-Class-3 PTO Option Class PTO

Option-Item

Included-Item
Note: Please check the Returnable flag in the Order Management tab in order to be able
to create returns for these items.

Create Bills of Materials
7. Navigate to (N) Bills > Bills
8. Create a bill of material for each container (Item Template = PTO Option Class) in the
table above.
9. Start with the sub-class or the lowest class in the hierarchy so that once it is created it can
be included in the top models or classes.
10. The field Item is the item name as well as the BOM name.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
11. Ensure that the Item Seq is in the order you want the items included in the Bill of
Material. Enter all quantities as appropriate.
12. Click (T) Order Management to enter if the item is optional for the bill or not. Usually
included items are not optional.
13. The Quantity (Minimum) should be less than or equal to the Quantity in the Main tab.

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a
14. Run the (M) Tools > Create Common hesBill
t o us program. Select All Organizations
concurrent
(m nissavailable
button so that the Bill ofi Material
d e across all inventory organizations.
a
m e lic e
U m b l
r a
e s wa nsfer
h a
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
15. Use the (M) View > Requests a o the completion of the Bill of Material.
option to tview
( m e
a
16. Repeat the same stepsdfori creating
c e nasBill of Material in the following sequence (refer to
the table PTOm
m e labove): i
U l
SMC Model
w ar ferab
h e s • XX-PTO-Class-1
a n s with the Class1 option item and included item and Class 11
r
Ma on•-t XX-PTO-Class-2 with the Class2 option item and included item
n
• XX-PTO-Class-3 with the Class3 option item and included item
• XX-PTO-Main-Option-Item and XX-PTO-Main-Included-Item
• XX-PTO-SMC-Model
Enter Quantities for the items
17. Use the Miscellaneous Receipts window to create quantities for the items. You need to
enter quantities only for finished goods.
18. (N) Inventory > Transactions > Miscellaneous Receipts

19. Select Miscellaneous Receipt from the Type LOV. Click (B) Transaction Lines to view
the Type LOV.
20. The Miscellaneous Receipt window opens so that you can specify the subinventory,
account and quantity for the item.
• Subinventory = Stores
• Account = Audit Fee
• Quantity = 10
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
21. Save and exit once you have completed entering the quantity for the items.

22. (N) Orders, Returns > Quick Sales Orders
23. Enter the following in the sales orders window:
• Customer = Computer Service and Rentals
• Order Type= Standard
24. In the Order Lines region, enter the top model XX-PTO-SMC-MODEL in the Ordered
Items field. Enter a Quantity of 10.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n25. Click (B) Configurator and select the classes that should be a part of the PTO model. Use
the Select box to choose the classes. Please note that if you select XX-PTO-Class-1, then
XX-PTO-Class-11 is automatically included as it is a sub-class of XX-PTO-Class-1.

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
edd thatisyou
26. Click (B) Finish. Configurator processes therrclasses Sthave selected to display on
the sales order window. You will get aw a eindicating
th that the Configurator
s message
heprocessinguisscomplete, the sales orders window shows
a
processing is in process. Once the
(m nse
the following PTO Kit information: t o
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n

27. (B)Book the order.
28. Complete the rest of the order to cash cycle:
• Pick Release
• Ship Confirm
• AutoInvoice
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Drop Shipments
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Drop r
Shipmentsa
MDrop o
nshipment 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 seller’s 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

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. Purchasing’s 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
a
has
outbound material transactions in your system for accounting purposes.
)
When you receive confirmation of a drop shipment or the suppliers invoice, you create a
m ฺ
c o
receipt for it. This creates inbound and outbound material transactions in your system for
ฺ
ail uide
accounting purposes. You can now generate an invoice to be sent to the customer.
m
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Drop Shipments Across Ledgers
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
MAacommon t
n -
no 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 Organization’s
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.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
Droph
a n-t r
Shipmentsa Across Ledgers
MThis o supports the central distribution process flow. In this typical scenario, a sales order is
nflow
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.

Practice - Order to Cash Cycle with Customer Acceptance
Overview
In this practice, you will learn how to create orders and record customer acceptance. Please note
that you will be completing an order to cash cycle with customer acceptance using all the seeded
data available in the environment.
Assumptions

) h as
i l ฺ co deฺ
@ dent G
y ฺ u
e d d S tu
Tasks r
ar e this
w
a t o us
m se
m a licen
book le
r a
wa nsfether order .
8.esPick release
h -tra
Ma 9. onShip

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Solution – Order to Cash Cycle with Customer Acceptance
Enable Customer Acceptance in Order Management
1. (N) Orders, Returns > Setup > System Parameters
• Enable Fulfillment Acceptance = Yes
2. Enable function security for the Order Management Super User responsibility for the
following two functions:
• Sales Orders: Fulfillment Acceptance – This ensures that the action attribute
Fulfillment Acceptance is available in the Actions LOV. You can use the folder
functionality to include the Fulfillment Acceptance option in the Actions LOV.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
• Sales Orders: Update Acceptance Attributes – This allows for updating the
acceptance attributes of Acceptance Name and Acceptance Expire days.
Note: These are attached to the sales order menu – ADS_OM_SUPERMENU.
3. Change your responsibility to Revenue Management Super User Vision Operations USA.
4. (N) Revenue Contingencies > Contingency Definition


5. Create a Contingency Rule for pre-billing implicit acceptance. Contingency rules are
terms and conditions that prevent immediate revenue recognition like delivery,
acceptance, government regulations, customer creditworthiness etc.
6. A contingency rule consists of the following that you need to enter:
• Deferral Reason: XX-CA-PREBILL-IMPLICIT
• Start Date: enter a date of your choice
• Related General Policy region: Select the None button
• Define Deferral Reason Removal Event region:
• Removal Event: Invoicing

a
• Event Attribute: Ship Confirm Date ) has
c o m ฺ
• Days Added to Event Attribute: any number that you want a
the ฺ
il removal e to
idevent
occur m
g nt G u
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
7. Click (B) Apply and return to the main page.
8. Click (B) Define Assignment Rules.
9. Enter the following information:
• Rule Name: XX-CA-PREBILL-IMPLICIT-RULE

• Revenue Contingency Name: XX-CA-PREBILL-IMPLICIT
• Parameter: Bill-To Customer
• Condition: IN
• Case Sensitive: No
• Value: Business World
10. You can add one or more parameters for the assignment rule. Click (B) Apply.
Using Pre-Billing Implicit Customer Acceptance
11. Change responsibility to Order Management Super User, Vision Operations USA
a
has
12. Enable the Acceptance-related fields using folder functionality on the sales orders line in
)
the Others tab:
c o m ฺ
ฺ
ail Management
ide
• Acceptance Name (this is known as Deferral Reason in m
g nt G
Revenue u
responsibility) u @
d d yฺ tude
• Acceptance Date
a rre this S
• Acceptance Expire Eventhe
sw use
( m a to
• Acceptance a di Days ns e
Expire
m e li c e
U m
• Acceptance b l
r aType
e s wa nsfer
h • Accepted
a
Ma on-tr
By
n • Accepted Qty
• Acceptance Description
13. Open a default folder, include the above fields in the Others tab using the Show Field
option. Checke the Make as Default box and Use Folder > Save As giving the folder
name as XX-Line-Cust-Accept.
14. The concurrent request set Implicit Acceptance Request set will run for recording implicit
acceptance and updating the above fields.
15. Enter the following in the Quick Sales Orders window:
• Customer Name: Business World (1608)
• Order Type: Mixed

• Item: AS54888
• Qty: 2
16. The default acceptance details will be displayed in (T) Others.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a li
m (B)e Book.
U musing
17. Book the order,
l
w rabusing (N) Shipping > Release Sales Orders > Release Sales
ar thefeorder
h e s ans
18. Pick Release
Ma on-tr
Orders.
19.nShip Confirm the order.
20. Use AutoInvoice to invoice the order. (N) Receivables > Interface > AutoInvoice.
Note: If you require to perform an explicit acceptance, use Actions > Fulfillment
Acceptance to open the Order Information Portal page and record your acceptance
details.

Back-to-Back Orders
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr Orders
Back-to-Back
MThe o of creating Back-to-Back orders involves the close linking of sales orders and
nprocess
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 line’s 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.

Guided Demonstration – Creating Back to Back Orders
Setups for Back-to-Back Orders – Item Attributes
Note: Use Order Management Super User, Vision Operations (USA) or comparable Super User
Order Management responsibility.
1. Create an item using the Inventory > Items > Master Items.
2. Select the Vision Operations (V1) organization if prompted.
3. Setup Item Attributes for a standard item XX-FG2.
4. The item type for the item XX-FG1 should display a value Finished Goods and an Item
Status of Active. Enter the following attributes in each of the tabs indicated below: s a
) h a
m
− (T) Purchasing – Select Purchasable box. Enter a list price in the List
co Priceฺfield.
i l ฺ e
− (T) General Planning – Select Buy in the Make or Buy g ma t Guid
LOV
ฺ u @ den
y
d s Stu
− (T) Work in Process – Select Build in WIPdbox
r e
− (T) Order Management – Select w ar e Ordered
t hi box and Assemble to Order
hes to us
Customer
box a
(m nse
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
d i
5. The profile option MRP: Default
n s e
Sourcing Assignment Set should be set to Null or any
%Supplier% value.
m a lice
U m tobtheleCorporate pricelist. (N) Pricing > Price List Setup.
6. Add the itemr XX-FG2
w a fera
h e s a n s
Ma on-t
Create an r
order
n to the Quick Sales Orders window:
7. Navigate
8. (N) Orders, Returns > Quick Sales Orders. Create a sales order for Business World:
− Customer: Business World (1608)
− Order Type: Standard
− Warehouse: V1
− Operating Unit: Vision Operations
9. Verify the following on the Main tab and Others tab (if the field is not visible on the window,
you can folder-enable it):
− Operating Unit = should be Vision Operations
− Warehouse: V1
− Price List: Corporate
10. Enter Order Line Information:

− Ordered Item: XX-FG1

− Qty: 21
− ATO box should be checked. Use the (M) Folder > Show Field option to display
the ATO check box.
11. Save your work. The Status on the line should display as Entered.
12. Book the Order using (B) Book Order.
Note: The Process Messages window may display with some warnings. Click (B) Continue.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Note: Click (M) Tools > Workflow Status to see the status of the flow. Click (B) View Diagram
on the Workflow Status HTML page to see the order processes and activities. A green line
around an activity (represented by a box) indicates that the activity is in progress. When you
book the order, the line status is Create Supply Eligible.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
r r e i s S
13. When you progress the order ((B) Actionsw a h
t the line status is PO
> Progress Order),
e
Requisition Requested. e s
h to u s
m a
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

14. Close the Workflow Status window to return to the Quick Sales Orders window.
Run Requisition Import
(N) Orders Returns > Requisition Import
− Import Source: CTO
− Group By: Item
− Multiple Distributors: No
− Initiate Approval after re-import: Yes
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
After the concurrent request is processed successfully, the Sales Orders line shows External Req
Open.
Find the PO Requisition
15. (N) Purchasing > Requisitions > Requisition Summary

16. Clear all fields and enter CTO in the Import Source field. The Requisition Headers Summary
window displays.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a i
17. The Approval Status
U mm shouldlebelApproved.
b
Verify that the line information corresponds to
that in the a r
sales ordersra
e window.
s w s f
a he -tran
M
non the Purchase Order
AutoCreate
18. (N) Purchasing > AutoCreate
19. In the Find Requisitions window, click (B) Clear and enter the PO Requsition number you
created in Step ____.
20. In the AutoCreate Documents window that displays, verify the requisition details and click
(B) Automatic to create the purchase order.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
21. Enter the following in the window:
d d yฺ tude
a r re this S
− Supplier: Advanced Network Devices w
− Source: Santa Clara-ERS h e s use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

22. Note: The line status of the sales order is PO Open.
23. (N) Purchasing > Receiving > Receipts
24. (B) Clear. Enter the PO Number and click (B) Find.
25. The Receipts window opens with the PO details.
26. Select the (T) Lines and enter Stores as the Subinventory value. (I) Save.
27. Note: If the value of the Subinventory field is blank, you can populate it by updating the
value of the Subinventory field in the Receiving Transactions window. (N) Purchasing >
Receiving > Receiving Transactions.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
28. Note: The line status on the Sales Order is Awaiting Shipping.
Creating Material Transactions
29. (N) Inventory > Transactions > Material Transactions
30. The following information is displayed:
− Item: XX-FG2

− Source Type: Purchase Order
− Source: 5694
− Transaction Type: PO Received
− Transaction Action: Receipt in Stores
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n the on-hand quantity in the Quick Sales Orders window, it should be 21.
31. Check
32. Pick Release the order.
33. Ship Confirm the order.

Sales Agreements
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Sales
-tr is a supplier’s representation of an agreement with a customer for the
MAaSalesoAgreement
Agreements
n
n
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

Negotiation Agreement
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
MAaSalesoAgreement
-t
Negotiation Agreement
n n 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.

Approve Sales Agreement
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nSales
Approve
MYou - tr Agreement
o setup Sales Agreement Types that include or do not include an approval step. Sales
ncan
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.

Releases Against a Sales Agreement
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nAgainst
Releases
MThere - tr a Sales Agreement
noare 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

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
a
has
• Released Amount
• Returned Amount )
m ฺ
ฺ c o
m ail uide
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
@ g nt G
Agreement header and line. When the release line is fulfilled, the fulfilled quantity on the SA
u
yฺ tude
d
line is incremented. When a release line is returned and the item is received, the Returned
d
rre this S
Quantity is incremented. The Remaining Unfulfilled Quantity may be stored or may be
a
h e sw use
calculated for display purposes. It should always equal the Ordered Quantity – the Fulfilled
Quantity + the Returned Quantity.
( m a to
di cens e
You can terminate a Sales Agreement if it is in the fulfillment phase and if it has no open
a
mm ble li
release lines. Also when the Expiration Date is reached or when the maximum agreed quantity
U
or amount is reached, the Sales Agreement can be terminated. The Termination date is
ar fera
defaulted to the system date. Once you terminate a Sales Agreement, you cannot reopen it and
e w
s ans
a workflow notification is sent to the appropriate persons, informing them that the Sales
h
Ma on-tr
Agreement is terminated.
n
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.

Practice - Practice - Creating a Sales Agreement
Overview
In this practice, you will learn how to create a Sales Agreement and also how to create releases
against this Sales Agreement. In this practice, the SA creation begins in the Negotiation Phase
and the Negotiation Flow selected does not include an approval step.
• Create a Sales Agreement
• Create a release (sales order) against the Sales Agreement
Assumptions
s a
•
)h a
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice. m
co deฺ
i l ฺ
g ma t Gui
• Replace XX with the number provided by your instructor y ฺ u@or uyour
d n
einitials.
r e dd s St
• Use Order Management Super User, Vision
w ar Operations
e t hi (USA) or comparable Super
hes to us
a
Tasks d i (m nse
m a lice
U m ble(SA)
Create a Salesr Agreement
w a fera
h e s
1. Business Worlda n s(1608) has contacted you to place a long-term order for item AS54999. They
Mawishothis
n r
-tot be supplied every week in quantities of 15 for a period of 30 weeks.
n
2. Create a SA for Business World that incorporates all the conditions for a long-term order.
Create a Release against the SA
3. Create one or more sales orders that refer to the SA and track the Released Amount.

Solution – Creating a Sales Agreement
SA Creation
1. Navigate to the Sales Agreements window:
(N) Blanket Agreements > Sales Agreements
2. Create a SA for Business World:

− Customer: Business World (1608)
− Sales Agreement Type: SA without Approvals
− Sales Agreement Name: XX-Blanket Practice
− Activation Date: enter today’s date
− Expiration Date: enter the date 8 months from today a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
3. (T) Pricing in the upper block. Enter the following information:

− Price List: Corporate.
− Check box Enforce Price List should be checked.

4. (B) Price List Setup. In (T) List Lines enter the following information:
− Product Context: Item
− Product Attribute: Item Number
− Product Value: AS18947
− Value: 1500
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Note: The above image shows the SA window, Pricing tab and above that, the Price Lists
window is displayed.
5. Click (I) Save and close the Price Lists window to return to the SA window.
6. In the SA window, in (T) Fulfillment in both the upper and lower regions, enter the
following information:
− Min Quantity Agreed: 15
− Max Quantity Agreed: 30
7. In (T) Fulfillment of the lower region, enter the following information:

− Min Release Quantity: 15
− Max Release Quantity: 30

− Min Release Amount: 1000
− Max Release Amount: 100000
8. In (T) Accounting for both the header and line regions, enter Payment Term of Net30 and
ensure that the Currency is USD.
9. In the lines (lower) region, in (T) Main, enter Item Context as Internal Item Number and
Item as AS18947 with a UOM of Ea.
10. (I) Save and take note of the Status of the SA. It will appear as Draft. Select Submit Draft
from the Actions button to change the status to Pending Customer Acceptance.
11. (B) Actions > Customer Accepted. This will change the Status to Active. Now you can use
the Sales Agreement in an order release.
12. Write the name of the SA here ________________. Save your work and close the window. s a
)h a
Create Release against SA m
co deฺ
i l ฺ
13. (N) Blanket Agreements > Sales Agreement Organizer.
g ma t Gui
y ฺ u@ uthatd en
14. In the Find Blanket window that opens, enter the Blanket
d d Number
S t you wrote in Step 9
and then click (B) Find.
a rre this
15. The Blankets Summary window displays h e sw u
your SA.seClick (B) Create Releases to create a
( m a open the
toSales Orders window, defaulting most of the
sales order against the SA. This
diSA. cens
information relevant toathe
will
e
mm l e li
a r U
Note: Alternatively, you
r a b
can create a new sales order using the (N) Orders, Returns > Sales
Ordersw option andfe
e s
h -tra n s refer to the SA in the order header.
16.aIn (T)n
M Line Items, enter AS18947 with a quantity of 15.
no
17. (I) Save. Close the window and return to the Sales Agreement Organizer. Click (B) Open
Agreement.
18. In the upper region, go to (T) Fulfillment, you will see the release (sales order) amount in
the Summary section in the field Released Amount. The SA is constantly updated to reflect
the latest Released Amount with each order created against it.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order to Cash Lifecycle with Customer Acceptance
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
MInaa number t
n -
no 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).

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
a
has
Flow for Post-Billing Acceptance:
• Enter sales orders with lines to be accepted )
m ฺ
ฺ c o
• Progress the order – book, pick release and ship confirm
m ail uide
• The line status will be Pending Post-Billing Acceptance
@ g nt G
u
yฺ tude
• View/update Acceptance related fields on the order line (Others tab – folder enabled)
d d
rre this S
• Line status will be Closed and the line is interfaced to Account Receivables
a
• Perform Acceptance/Rejection – explicitly using the Order Information Portal Page or
e sw use
implicitly using the AR setups and the concurrent request set
h
( m a to
• View the Acceptance/Rejection on the sales orders line
di cens e
a
• Revenue Recognition takes place once the acceptance is recorded
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCash
Order to
-
MPre-Billing tr Lifecycle with Customer Acceptance
no 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.

• 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.
Post-Billing Customer Acceptance with full explicit acceptance:

• Enter and book the order.
• Pick release and ship confirm 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.
s a
Post-Billing Customer Acceptance with full implicit acceptance:
) h a
• Enter and book the order. Revenue Management is set up to assume acceptance m
co difeexplicit
ฺ
acceptance/rejection is not performed within 30 days of shipment. ailฺ i
• Pick release and ship confirm the order. g m t Gu
y ฺ u@ uden
• Invoice interface the order.
e d St
dAcceptance.
r his
aorr rejection.
• Order lines status display as Pending Post-Billing
t
• 30 days pass without receiving acceptance w
s us e
• Acceptance is assumed. Order a hecloses toand revenue recognition takes place.
( m line
e
a
• You can query the order dilinescand
e nsees that an automatic acceptance was generated on the
mm ble li
31st day after shipping.
U
w ar fera
h e s ans
Ma on-tr
n

Practice - Order to Cash Cycle with Customer Acceptance
Overview
In this practice, you will learn how to create orders and record customer acceptance. Please note
that you will be completing an order to cash cycle with customer acceptance using all the seeded
data available in the environment.
Assumptions

) h as
i l ฺ co deฺ
@ dent G
y ฺ u
e d d S tu
Tasks r
ar e this
w
a t o us
m se
m a licen
book le
r a
e s wa nsfether order .
h -tra
13. Pick release
Ma 14.onShip

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Solution – Order to Cash Cycle with Customer Acceptance
Enable Customer Acceptance in Order Management
21. (N) Orders, Returns > Setup > System Parameters
• Enable Fulfillment Acceptance = Yes
22. Enable function security for the Order Management Super User responsibility for the
following two functions:
• Sales Orders: Fulfillment Acceptance – This ensures that the action attribute
Fulfillment Acceptance is available in the Actions LOV. You can use the folder
functionality to include the Fulfillment Acceptance option in the Actions LOV.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
• Sales Orders: Update Acceptance Attributes – This allows for updating the
acceptance attributes of Acceptance Name and Acceptance Expire days.
Note: These are attached to the sales order menu – ADS_OM_SUPERMENU.
23. Change your responsibility to Revenue Management Super User Vision Operations USA.
24. (N) Revenue Contingencies > Contingency Definition


25. Create a Contingency Rule for pre-billing implicit acceptance. Contingency rules are
terms and conditions that prevent immediate revenue recognition like delivery,
acceptance, government regulations, customer creditworthiness etc.
26. A contingency rule consists of the following that you need to enter:
• Deferral Reason: XX-CA-PREBILL-IMPLICIT
• Start Date: enter a date of your choice
• Related General Policy region: Select the None button
• Define Deferral Reason Removal Event region:
• Removal Event: Invoicing

a
• Event Attribute: Ship Confirm Date ) has
c o m ฺ
• Days Added to Event Attribute: any number that you want a
the ฺ
il removal e to
idevent
occur m
g nt G u
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
27. Click (B) Apply and return to the main page.
28. Click (B) Define Assignment Rules.
• Rule Name: XX-CA-PREBILL-IMPLICIT-RULE

• Revenue Contingency Name: XX-CA-PREBILL-IMPLICIT
• Parameter: Bill-To Customer
• Condition: IN
• Case Sensitive: No
• Value: Business World
30. You can add one or more parameters for the assignment rule. Click (B) Apply.
Using Pre-Billing Implicit Customer Acceptance
31. Change responsibility to Order Management Super User, Vision Operations USA
a
has
32. Enable the Acceptance-related fields using folder functionality on the sales orders line in
)
the Others tab:
c o m ฺ
ฺ
ail Management
ide
• Acceptance Name (this is known as Deferral Reason in m
g nt G
Revenue u
responsibility) u @
d d yฺ tude
• Acceptance Date
a rre this S
• Acceptance Expire Eventhe
sw use
( m a to
• Acceptance a di Days ns e
Expire
m e li c e
U m
• Acceptance b l
r aType
e s wa nsfer
h • Accepted
a
Ma on-tr
By
n • Accepted Qty
• Acceptance Description
33. Open a default folder, include the above fields in the Others tab using the Show Field
option. Checke the Make as Default box and Use Folder > Save As giving the folder
name as XX-Line-Cust-Accept.
34. The concurrent request set Implicit Acceptance Request set will run for recording implicit
acceptance and updating the above fields.
35. Enter the following in the Quick Sales Orders window:
• Customer Name: Business World (1608)
• Order Type: Mixed

• Item: AS54888
• Qty: 2
36. The default acceptance details will be displayed in (T) Others.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a li
m (B)e Book.
U musing
37. Book the order,
l
w rabusing (N) Shipping > Release Sales Orders > Release Sales
ar thefeorder
h e s ans
38. Pick Release
Ma on-tr
Orders.
39.nShip Confirm the order.
40. Use AutoInvoice to invoice the order. (N) Receivables > Interface > AutoInvoice.
Note: If you require to perform an explicit acceptance, use Actions > Fulfillment
Acceptance to open the Order Information Portal page and record your acceptance
details.

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt GAccess
u @
Multiple Organization
ฺ tude
Control d d ySetup
a r re this S
e s wChapterse3
a h to u
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Multiple Organization Access Control Setup

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Organization Structure in Oracle Applications
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-trStructure in Oracle Applications
Organization
MThe o
nclassifications 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 C’s 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

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
a
has
organization is held in a subinventory therefore, you must define at least one subinventory.
)
m ฺ
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Multi-Org Access Control (MOAC)
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nAccess
Multi-Org
MMOAC - tr Control (MOAC)
noaddresses 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.

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 Choose Inventory Organization window automatically
limits available inventory organizations to those authorized for the current responsibility.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Using MOAC in Oracle Order Management
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-trin Oracle Order Management
Using
MSetup
MOAC
nowindows 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 Hold Sources, 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.

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
a
has
can also set the value of the hidden parameter Process Orders with no Org Specified as
required. )
m ฺ
ฺ c o
Oracle Order Management concurrent requests are single-org, multi-org or global. For single-
ail uide
org requests, the Operating Unit parameter is a required field and is populated with the default
m
@ g nt G
operating unit. If you need to run the request for multiple orgs, leave the optional Operating
u
yฺ tude
Unit parameters field blank. Some concurrent programs are classified as global, you can run
d d
rre this S
them across all operating units. In such programs, the Operating Unit parameter field is
a
sw use
disabled. Similarly, reports can be run for a single org or globally (across operating units).
h e
Defaulting of the operating unit value takes place in the following manner: When MOAC is
a
( m e to
enabled, the value of the operating unit for the MO: Security profile option is defaulted based
a di cens
on the system profile option MO: Default Operating Unit. When MOAC is not enabled, the
mm ble li
value of the operating unit is the default for MO: Operating Unit profile option. For more
U
ar fera
details on MOAC in Oracle Order Management, please refer to the Oracle Order Management
w
h e s ans
User’s Guide and Oracle Order Management Implementation Manual.
Ma on-tr
n

Setting Up MOAC
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-MOAC
Setting
MThere
up tr
noare 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.

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
a
parameters are:
) has
c o m ฺ
• Active Responsibilities Only: Select Yes or No to validate only the active
ฺ
ail uide
responsibilities on the report. The default value is Yes.
m
g nt G
• Correct Customer Attributes: Select Yes or No to correct the customer attributes. If
u @
yฺ tude
you choose Yes, the report deletes the operating unit-specific data from the
d
Customer records. The default value is No.
d
a rre this S
• Correct Supplier Attributes: Select Yes or No to correct the supplier attributes. If you
e sw use
choose Yes, the report deletes the operating unit-specific data from the supplier
h
a to
records. The default value is No.
( m
di cens e
For more information on setting up MOAC, please refer to the Oracle Applications Multiple
a
mm ble li
Organizations Implementation Guide.
U
w ar fera
h e s ans
Ma on-tr
n

Guided Demonstration – Setting Up Guided Deomonstration -
Setting Up MOAC
Notes: Enter the following enterprise structure: Top Org with 2 Operating Units. Both Operating
Units have an Inventory Org each.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
ar HRMS
Responsibility:
w f era Management
s s
e rManager
an > Work Structures > Location
(N)a>hHRMS
M on-t
n
1. Enter the following details for some new locations:
Scope: Global
Name: enter a name starting with your intials (e.g. XX-OrgLocation)
Description: any description
(T) Address Details
2. Address flexfield – enter the following:

• Address Line 1: 301 Patriots Road
• City: San Diego
• State: CA
• Zip Code: 92130

• County: San Diego
• Country: United States
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
m e li
3. (B) OK Um l
r
a fer a b
4. e s
(N)
w n
Inventory s> Setup > Organizations > Organizations
h r a
Ma5. Click
o n -t
n (B) New in the Find window and in the Organizations window, enter the location
(XX-OrgLocation) that you created in the previous steps.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
6. (T) Shipping Details:
( m a to
e
• Enter am adi licens
Contact
U m ble
r era Location should default as your location name
•a The Ship-To
s w s f
a he -•traEnsure
n
M on that the following boxes are checked:
n
o Ship-To Site
o Bill-To Site
o Receiving Site
o Internal Site
o Office Site
7. (M) Save.
8. Similarly, create locations for your other orgs: OU1, OU2, InvOrg1, InvOrg2. Select the
Global button for determining the scope of the location. Possible names that you could
use for the locations:

• XX-OU1-Location
• XX-OU2-Location
• XX-InvOrg1-Location
• XX-InvOrg2-Location
9. (N) > HRMS Manager > Work Structures > Organization > Description
10. A Find window pops up prompting you to search for an org. Click (B) New to create a
new org.
11. Create the following orgs in the Organization window one by one. Leave the Type field a
blank and enter the effective dates for the org.
) has
c o m ฺ
ฺ
ail uide
m G
g nt Organization
Org Name Location Internal@ or
u
yฺ tude Classification
e d d
External
S
a r r t h i s
XX-TOP XX-OrgLocation
e s w seInternal GRE/Legal
a h to u Entity
m
( nse
XX-OU1 a diXX-OU1-Location
c e Internal Operating Unit
m l i
m bleXX-OU2-Location Internal
XX-OU2
a r U r a Operating Unit
e s w nsfe
h a
XX-InvOrg1 XX-InvOrg1- Internal Inventory
Ma on-tr Location Organization
n
XX-InvOrg2 XX-InvOrg1- Internal Inventory
Location Organization

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
e d a flexfield
dwith S t screen to display more
12. When you save your work, you will be prompted
r his and USD for Currency.
r for tLegislation
information. Accept all defaults and enteraUSA
w
es us e
a h to> Organization > Hierarchy
13. (N) > HRMS Manager > Work
( m Structures
e
di cens structure.
forayour organization
m ble li
14. Enter a hierarchym
15. In the a
Name
U
r fielderenter
a a Name for your hierarchy.
s w s f
a heEnter-atrVersion
an Number and Start Date for the new hierarchy.
M on
16.
n
17. Using F11 and Ctrl-F11, query for your top organization in the Organization region >
Name field. Please note that if your organization classification is a Business Group it
will not appear in this search result list.

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m enter
18. In the Subordinates sub-region,
n s ethe operating units and click the Down arrow key to
a liceOrg) for each operating unit.
enter a subordinate (Inventory
m
U mand exitb lethe window.
r a
wa nsfer
19. Save your work
e s
h (N) > HRMSa Manager > Security > Profile
Ma on-tr
20.
21.nEnter a Name and a Business Group.
22. Select the Security Type as Secure organizations by organization hierarchy and/or
organization list.
23. Enter your Organization Hierarchy name (you created it in the steps above).
24. Check the Include Top Organization box and the Exclude Business Groups box.
25. Enter Operating Unit in the Classification field and enter the name of your operating unit.
You need to do this for both operating units that you have created.

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
26. Save your work. a hes to us
d i (m nse
27. Run the Securitym aMaintenance
List l i c e concurrent program. (M) View > Requests > Security
U m withbthe
List Maintenance le following parameters:
r a
er Lists For: All Security Profiles or One Named Security Profile
e s w•a Generate
s f
h an
Ma on-tr
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
28. Responsibility: System Administrator
U m b le
r
29. (N) > Profile a
> System
e s wa nsfer
h When-tyou
30. r a have created the security profile, you can assign the value to the MO: Security
Ma Profile
on responsibilities.
option at the responsibility level. You can select the same security profile for
nmultiple

31. Assign a default operating unit to the profile option MO: Default Operating Unit. (N) >
Profile > System.
32. Run the Setup Validation Report to check if the setup steps have been performed
successfully.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g Setupt G for
Oracle Inventory
u @ de n
Oracle d d yฺ tManagement
Order u
a r re this S
e s wChapterse4
a h to u
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Oracle Inventory Setup for Oracle Order Management

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objective
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Overview
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Overview
MOracle
noInventory 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

Receipt to Issue Lifecycle
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Receipt to r a
Issue Lifecycle
MOracle
noInventory 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.

Inventory Organizations
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
MAna inventory
Inventory
n tr
Organizations
-
no 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.

Setting Up Locations
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Setting Up
MLocations tr
a n-Locations
no 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.

Inventory Organization Structure
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
MAna inventory
Inventory
n tr
Organization
- Structure
no 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
User’s Guide.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Sample Inventory Organization
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
Sample Inventory Organization
n

Guided Demonstration - Creating Subinventories
Responsibility: Oracle Order Management Super User, Vision Operations USA
1. (N) Inventory >Setup > Organizations > Subinventories
2. (M) File > New
3. Enter the following subinventory information:

− Name: Raw
− Description: Raw Materials
− Locator Control: Item Level
a
4. (B) Open.
) has
5. Select Storage as the subinventory Type. c o m ฺ
ฺ
ail uide
6. (M) File > Save. m
g nt G
u @
d d yฺ tude
rre this S
7. (M) File > Close Form.
a
h e sw use
( m a to
Verifying Subinventories
di cens e
a
mm ble li
9. (N) Change Organization.
U
r era
aBoston
s
10. Select
e w
M2
n s fManufacturing.
M ah Setup
11. (N) o n -tr>aOrganizations > Subinventories
n
12. (M) View > Find.
13. Enter Raw in the Find Field.
14. Click OK.
15. Note that subinventory Raw is not available in M2.

Practice - Creating Subinventories
Overview
In this practice you will learn how to create two subinventories.
Assumptions
• You are skilled in Oracle navigation.
• Responsibility > Inventory, Vision Operations USA
s a
)h a
m
co deฺ
i l ฺ
Tasks
g ma t Gui
If necessary, change your Organization to Seattle (M1). y ฺ u@ uden
r e dd s St
Create four subinventories for your team. Createaone r subinventory
t hi for your finished goods (FGI)
w e
sa Raw Materials
s (RM) subinventory, and Low Value
stock, a Main Stores (MAIN) subinventory,
a hesubinventory
t o u
( m
(LV) items subinventory. Your Low Value
e must be a non-tracked subinventory.
a di yourcteam
Use the following naming convention ton
e s
differentiate your team from other teams (XXFGI)
U mm ble li
where the pound sign represents number.
w ar the lab,
After completing f a the following questions.
eranswer
s s
hewhich-torganization
an
M on r
1. a In are your new subinventories?
n
2. Determine if XXFGI exists in M2- Boston Manufacturing and why.

Solution - Creating Subinventories
Responsibility = Inventory, Vision Operations USA
1. Change Organization to M1 Seattle.
• (N) Change Organization
• Choose Seattle Manufacturing
• Select OK
2. Navigate to the Sub-inventories window.

a
has
• (N) Setup > Organizations > Subinventories
)
m ฺ
3. (B) New
ฺ c o
− Name: XXFGI
m ail uide
− Description: Finished Goods Inventory
@ g nt G
− Status: Active u
yฺ tude
d d
− Type:
− Locator Control:
Storage
Item Level ar
re this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
r era
aSave
e s w
4. (M) File >
n s f
h -tra
5. a(M) File
M
no−n Name:
> New.
XXMain
− Description: Main Stores
− Type: Storage
− Status: Active
− Locator Control: Dynamic Entry

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
r
>aSave fer
a
s w
6. (M) File
e ran s
a h ->t New
M n
7. (M) File
o
n − Name: XXRM
− Description: Raw Materials
− Status: Active
− Type: Storage
− Locator Control: None

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
r era
aSave
s w
8. (M) File
e >
n s f
M ah n->trNew
9. (M) File
a
no− Name: XXLV
− Description: Low Value Inventory
− Status: Unserviceable: Not Available for Netting, ATP and Reservations
− Type: Storage
− Locator Control: None
− Quantity Tracked: Deselected

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
r era
aClose
e w
10. Savesand
n s f
window.
h tra> Save
Ma• o(M)n-File
n
• (M) File > Close Form
11. In which organization are your new subinventories? M1 Seattle Manufacturing
Verifying Subinventories
12. Does a subinventory called XXFGI exist in M2 Boston Manufacturing? No, you created
your subinventories in M1 Seattle Manufacturing.
13. (N) Change Organization.
• Select M2 Boston Manufacturing.
14. (N) Setup > Organizations > Subinventories.
15. (M) View > Find.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Interorganization Shipping Networks
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n sShipping Networks
h r a
MAna interorganization
-t
Interorganization
n o n 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

For more information see Interorganization Shipping Networks, Oracle Inventory User’s
Guide.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Shipping Method
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nMethod
Shipping
MShipping - tr
no 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.

Units of Measure
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Measure
Units
MYou
of
n - tr
o units of measure for tracking, moving, storing, and counting items.
ndefine
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.

Uses of Units of Measure
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma• Planning
Uses of Units
n - tr of Measure
no 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

Unit of Measure Class
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr Class
Unit
MUnit
of Measure
nofomeasure 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.

Guided Demonstration - Creating Unit of Measure Classes
Responsibility: Order Management Super User, Vision Operations USA
1. (N) Inventory> Setup > Units of Measure > Classes.
2. (M) File > New.
3. Enter the following unit of measure information:

− Name: XX-Metric
− Description: XX-Metric Class
− Base Unit XX-Meter
− UOM: XXM
a
4. (M) File > Save.
) has
c o m ฺ
5. (M) File > Close Form. ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Unit of Measure Conversions
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Unit of
-tr Conversions
MAaunitoofnmeasure
Measure
n 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.

Guided Demonstration - Defining Unit of Measure Conversions
1. (N) Setup > Units of Measure > Conversions
2. (M) File > New.
3. Enter XX-Centimeter in the Unit field.
4. Enter 0.01 in the Conversion field.
5. (M) File > New.
a
has
6. Enter XX-Kilometer in the Unit field.
)
m ฺ
7. Enter 1000 in the Conversion field.
ฺ c o
8. (M) File > Save. m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Guided Demonstration - Creating Units of Measure
1. (N) Inventory> Setup > Units of Measure > Units of Measure.
2. (M) File > New..
3. Use the following information to create two new units of measure:
Name UOM Description Class
a
has
XX-Centimeter XXC XX Centimeter XX-Metric
)
m ฺ
XX-Kilometer XXK XX Kilometer o
XX-Metric
ฺ c
m ail uide
4. (M) File > Save.
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Defining Units of Measure
Overview
In this lab you will be doing the following:
• Defining Unit of Measure Classes
• Defining Units of Measure
• Setting up Unit of Measure Conversions
Assumptions
s a
• You are skilled in Oracle Navigation
)h a
• You must have access to an Oracle Application Vision database or comparable
m
co detraining
ฺ
a i l ฺ i
or test instance at your site on which to complete this practice.m
g G u
u@ uden t
Tasks y ฺ
r e dd s St
1. Define unit of measure class:
w ar e thi
a h es us
• Define the unit of measure
( m e o
class,tQuantity Class with the base unit of measure
Each. i
ad licen s
m
m teambnumber
• UseU
r your
a le (XX) to uniquely identify your unit of measure class.
a fer
2.he sw unit
Define a n s measure:
of
r
Ma on•-t Define the following units of measure for your class. (Use your team number
n
(XX) to uniquely identify your units of measure.)
− Dozen
− Gross
− Case
3. Set up UOM conversions:
• Set up Standard conversion for your units of measure.
• Use your team number to uniquely identify your class from the other teams in the
classroom.
Note: A Gross = 144 each, and a case = 24 each.

Solution – Defining Units of Measure
Responsibility = Order Management Super User, Vision Operations USA
Defining Unit of Measure Classes
1. Navigate to the UOM Classes window.
• (N)Inventory > Setup > Units of Measure > Classes
2. The application prompts you to select an organization if it is a first-time access to the

database. Select M1 Seattle Manufacturing from the list of values.
3. (M) File > New

a
has
− Name XX-QTY
− Description XX-Quantity Class )
m ฺ
− Base Unit XX-Each ฺ c o
− UOM (abbreviation) XXE
m ail uide
@ g nt G
4. (M) File > Save. u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Defining Units of Measure
5. Navigate to the Units of Measure window.
• (B) Units of Measure
6. (M) File > New


7. Enter the units of measure information according to the following table:
Name UOM Description
XX-Dozen XXD XX Dozen UOM
XX Gross XXG XX Gross UOM
XX Case XXC XX Case UOM
Note: Select (M) File > New between each new unit of measure.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
8. (M) File > Save.
9. (M) File > Close form
Setting up Unit of Measure Conversions
10. Navigate to the Unit of Measure Conversions window.
• (B) Setup > Units of Measure > Conversions
11. (M) File > New
12. Enter the unit of measure conversion information according to the following table:
Unit Class Conversion Base Unit
XX-Dozen XX-Qty 12 XX-Each

XX-Gross XX-Qty 144 XX-Each
XX-Case XX-Qty 24 XX-Each
Note: Select (M) File > New between each new unit of measure conversion.
Note: Verify that you are creating a standard unit of measure conversion.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n File > Save.
13. (M)
14. (M) File >Close Form.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

What is an Item?
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
What is r
MAna itemonis-atpart
an Item?
n 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.

Steps to Setup, Define, and Maintain Items
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nSetup,
Steps
MThe
to
- tr Define, and Maintain Items
o
nfollowing 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)

Defining Items
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nItems
Defining
MDefine - tr
noonly 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.

Defining Items
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Item Master Organization
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
MAna itemonmaster
-t organization is a logical entity that you use to define items. You use the other
Item Master Organization
n
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.

• You assign child organizations to the item master organization.
- Note that the item master uses itself as its item master.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Item Validation Organization
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Item r
Validationa Organization
MThe o validation organization contains all the items that you sell to customers. You set the
nitem
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.

Item Attributes
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Item
MItem
Attributes
o
nattributes are the collection of information about an item.

Unit of Measure Attributes
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
Unit h
a n-t
of r
Measure a Attributes
MYou
nuseo 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

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order Management Item Attributes
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Order
MThe
Management Item Attributes
o
nfollowing 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.

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
a
has
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
m ฺ
c o
determine which authorized returned items you can physically receive into inventory.
ฺ
ail uide
RMA Inspection Required: You use this item attribute to indicate whether to require an
m
inspection on returned items. @ g nt G
u
yฺ tude
d
Financing Allowed: You use this item attribute to indicate if a customer can finance an item.
d
rre this S
Shipping Subinventory: You this item attribute to determine the default subinventory for
a
shipping.
h e sw use
a to
Default Shipping Organization: This is the primary shipping organization for the item. This
( m
di cens e
organization appears on the Enter Orders window if the item is the source attribute of the
a
mm ble li
warehouse object in the standard value rule set for the order. This organization appears on the
U
Enter Returns window if a receiving warehouse is not defined on the customer or order type.
ar fera
e w
s ans
h
Ma on-tr
n

Order Management Item Attributes
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Order
MCheck
Management Item Attributes (cont.)
noATP: 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 Management-
enabled 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

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Item Validation
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Item r
Validationa
MOracle
noOrder 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.
Item Validation Organization
• 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

- 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
a
has
* - Also validated in the Shipping Warehouse.
Shipping Warehouse )
m ฺ
ฺ c o
ail uide
• Only Source
- ATP Components m
g nt G
u @
- ATP Rule
d d yฺ tude
rre this S
- Check ATP
a
h e sw use
- Customer Orders Enabled
- Internal Orders Enabled
( m a to
di cens
- Invoice Enabled** e
a
mm ble li
- Invoiceable Item**
U
ar fera
- Lot Control
e w
s ans
- Purchasable Flag
h
Ma on-tr - Reservations Control
n - Returnable
- Revision Control
- Shippable
- Serial Number Control
- Stock Locator Control
- Stockable
- Subinventory Restrictions
- Transactable
- Pricing Quantity Source
- Tracking Quantity Indicator
- 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

- 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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Item Status
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Item
MYou
Status
o use statuses to provide default values for certain item attributes to control the
ncan
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.

Item Statuses and Attributes
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr and Attributes
Item
MYou
Statuses
o an item status by selecting the value check boxes for the status attribute. You can
ndefine
control status attributes and item status at the item level or organization level.

Organization Assignment and Organization Items
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-trAssignment and Organization Items
Organization
MYou o enable an item in all child organizations under your master organization or choose
ncan
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.

Control Levels
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M a Levels
Control
n - tr
no Control
Master-Level
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.

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Guided Demonstration - Defining Items
Responsibility: Oracle Order Management Super User, Vision Operations USA
1. (N) Inventory > Items > Master Items.
2. Define an item using the following information.

− Item: AS18456
− Description: Lap Top Assembly
3. (M) Tools > Copy From.
4. Select the Finished Good template from the LOV.

a
has
5. Click Apply.
)
m ฺ
6. Click Done.
ฺ c o
m ail uide
7. (M) File > Save.
@ g nt G
u
yฺ tude
8. (M) Tools > Organization Assignment.
d d
a r re this S
9. Enable the Item in M1 Seattle.
h e sw use
( m a to
10. (M) File > Save.
di cens e
a
mm ble li
U
w ar fera
h e s ans
Ma on-tr
n

Practice - Practice - Defining Items
Overview
In this practice you will learn how to define items, assign item attributes, and enabled items in
organizations.
Assumptions
• You are skilled in Oracle navigation.
• Responsibility: Oracle Order Management Super User, Vision Operations USA.
• You must have access to an Oracle Application Vision database or comparable training a
) has
c o m ฺ
Tasks ฺ
ail uide
m
g nt G
Create a Standard Customer
u @
d d yฺ tude
1. Login using the following username and password:
• User: mfg a rre this S
• Password: welcome h e sw use
( m a to
2. Set up a Customer with thedirequired e
s to process Sales Orders.
ndefaults
a li c e
U m>mStandard.
l e
ar ferab
• (N) Customers
e w
s CreateanOrganization
s
a h
Find/Enter
- t r window:
M • Organization
non
Name: XX-Big City Electronics (where XX is your initials)
4. (T) Account
− Classification: High Technology
− Account Type: External
− Sales Channel: Commercial
5. (T) Sites
− (B) Create Site
Purpose Location Bill To Primary

Bill To Accounts Payable Blank Selected
Ship To Receiving Dock A Blank Selected
5. (T) Account Profile

− Profile Class: DEFAULT

6. (T) Order Management
− Price List: Corporate
− Free On Board Point: Customer Site
− Freight Terms: Prepaid
− Warehouse: Seattle Manufacturing
7. (T) Addresses
− (B) New
− Country: United States
− Address: 222 W Las Colinas Blvd (suggestion: Add a 2nd address line as an
identifier to use in future practices -- Your Initials)
− Postal Code: 94401 (select San Mateo from the list that appears when you enter the
postal code. The city, county and state should default)
8. (B) Open, (T) Details (repeat steps 7 and 8 for the Bill to and the Ship to)
s a
− Payment Terms: 30 Net
)h a
− Salesperson: Abbott, Rachel m
co deฺ
i l ฺ
9. Save your work and close the window.
g ma t Gui
y ฺ u@ uden
10. Note the Site Number ______________
r e dd s St
Create Items w ar e thi
a h es us
Use the finished goods template tom
( to
create five items.
e
− XX-ItemXX
a di cens
− XX-Pager m m e li
r
− XX-Palm U a
Pilot b l
a fer
−swXX-Phone
h e a n s
Ma on-t − r
XX-Phone Card
n Use the following naming convention for your items where XX represents either your
Note:
initials or the number assigned to you by your instructor. Be sure to enable your items in M1
Seattle and M2 Boston.
Processing Miscellaneous Receipt Transactions
Use the Miscellaneous Transactions window to receive the material in to inventory.

Solution - Defining Items
Responsibility, Oracle Order Management Super User, Vision Operations USA
Create Items
1. Navigate to the Master Items window
• (N) Inventory > Items > Master Items
2. Create the no inventory controls item:

− Name: XX-Item01
− Description Anything you want.
a
has
3. (M) Tools > Copy From
)
m ฺ
4. Enter Finished Goods in the Template field
ฺ c o
m ail uide
5. (B) Apply.
@ g nt G
u
yฺ tude
6. (B) Done
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
7. (M) File > Save
di cens e
a li
mm blAssignment
8. (M) Tools > Organization
U e
w aritem tofetherafollowing inventory organizations:
h e s ans
9. Assign the
−
Ma o−n-Org: tr
Org: M1 Seattle Manufacturing
M2 Boston Manufacturing
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
10. (M) File > Save.
d i (m nse
m a lice
11. Repeat steps 2-10
U m blethe following items: XX-Pager, XX-Palm Pilot, XX-Phone, and
to create
XX-Phone r
a fera
Card.
s w s creating the items, save your work and close the window.
he you
12.aWhen r a n
M on-t
are finished
n Miscellaneous Receipt Transactions
Processing
You can use the miscellaneous receipt window to receive material receive material in to
inventory.
13. Navigate to the Miscellaneous Transaction window.
• (N) Inventory > Transactions > Miscellaneous Transaction
Note: If the organization window appears, select M1-Seattle Manufacturing. Ensure that you
are in M1 (Seattle) organization when you enter the Miscellaneous Receipt. If you still see
organization V1, (N) Change Organization and select M1-Seattle Manufacturing from the
list of values and click OK.
14. Enter the following values:

− Date: Defaults to current date
− Type: Miscellaneous receipt

− Account: 01-580-7740-0000-000 or select Miscellaneous from the Account Aliases
(LOV).
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
15. (B) Transaction Lines.
a rre this S
h e sw use
( m a to
di cens e
a li
Item
U mm bSubinventory
l e UOM Quantity
XX-Pager ar a
s w s f erFGI Ea 10000
a he Pilot
XX-Palm
- t r a n FGI Ea 10000
MXX-Phone
non FGI Ea 10000
XX-Phone Card FGI Ea 10000

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens
17. Save your work and close the window. e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Item Relationships
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Item r a
Relationships
MYou o define relationships between items. This allows you to search for items through these
ncan
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.

Customer Items
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
MAacustomer
Customer
n tr
Items
-
no 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.

What are Supply and Demand?
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Available to Promise
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Available to r a
Promise
MAvailable
no 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.

Uses of ATP in Oracle Inventory
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
ATPtrin Oracle Inventory
Ma• You
Uses of
-
noncan 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.

Defining an ATP Rule
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nan-tATP
Defining
MNavigation r Rule
no 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)

Guided Demonstration - Creating an ATP Rule
Responsibility: Inventory, Vision Operations USA
1. Navigate to the ATP Rules window.
• (N) Inventory Setup > Rules > Available to Promise

− Name: ATP_Backward
− Description: ATP Backward consumption
− Backward Selected
− Past Due Days Demand: 10
− Infinite Supply: User-defined time fence a
− Aggregate Order Promising Time Fence:
) hasUser Defined
c o m ฺ
3. Select the following Demand Sources: ฺ
ail uide
− Sales Orders m
g nt G
− Internal Orders u @
− Discrete WIP
d d yฺ tude
− Repetitive WIP
a rre this S
h e sw use
( m a
4. Select the following Supply Sources:
to
− Discrete WIP i ens e
− Repetitive WIPad
m m e lic
− Internal
r U Reqs
a b l
a fer
− Supplier
wPurchase Reqa
h e s
−
a n s Orders
Ma o−n-On-hand
t r Available
n − Interorg Transfers
5. (M) File > Save
6. (M) File > Close Form

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Implementation Considerations
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr Considerations
Implementation
MYou o set all costing attributes at the organizational level because costing is most
nshould
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

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g ntSetup G
ฺ u @
Oracle Receivables
d e for
Oracle y
ddOrder u
tManagement
r e S
w ar e5 this
hes to us
Chapter
a
(m nse
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n
Oracle Receivables Setup for Oracle Order Management

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Overview of Trading Community Architecture
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nof-trTrading Community Architecture
Overview
MOrder
noManagement 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

Key Customer Related Concepts in TCA
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr Related Concepts in TCA
Key Customer
MParties
no
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.

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 a
has
community. For example, you can use relationships to model the roles that parties play with
)
c o m ฺ
respect to one another, and classifications to classify entities.
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Adding Customers in Order Management
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Customers
Adding
M(N) n - tr in Order Management
no Management > Customers > Standard
Order
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.

Practice - Creating a Customer
Overview
In this practice you will learn how to create a customer in Oracle Order Management
Assumptions
• Replace XX with the number provided by your instructor or your initials. a

h a s
• Use Order Management Super User, Vision Operations (USA) or comparable m ) Super
i l ฺ co deฺ
m a ui
Tasks g
@ dent G
y ฺ u
e
1. Define a new customer named XX-Big Cityrwith d d
two S
sites: tu
w ar e this
a hes Cook
• Bill to address: 102 N. LaSalle,
t o u s Chicago, Illinois, 60610
County,
i
• Deliver to address: ( m Beverly,
s e
a d cen San Mateo County, Palo Alto, California, 94301
487
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Solution – Creating a Customer
Login
Login to the database using the User Name and Password supplied by your instructor.
Order Management Super User, Vision Operations (USA) Responsibility is selected.
Create a Customer
(N) Order Management > Customers > Standard
a
has
1. (B) Create.
2. Organization Name: XX-Big City. Leave Alias, D-U-N-S Number, URL, and m )
o Context
Value.
a il uideฺ
ฺ c
3. Account Description: Enter a description for your customer. @
gm nt G
d y ฺu tude
4. Profile Class: Default.
r r ed is S
w a e th
s
he fields,
5. Account Type: External. Leave all other usthe Account Information region, blank.
in
a
(m nse t o
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
mm ble li
6. Country: United States.
U
w ar 1: 102feN.raLaSalle.
h e s ans
7. Address Line
M a n-tr
8. City: Chicago.
no
9. County: Cook
10. State: Illinois.
11. Postal Code: 60610. Leave all other fields, in the Account Site Address region, blank.

a
)
12. In the Business Purpose region, set Purpose to Bill To and check the Primary check
as
hbox.
c o m ฺ
13. (B) Apply.
ฺ
ail uide
m
g nt G
u @
14. (B) Create Site.
d d yฺ tude
15. Country: United States.
a rre this S
h e sw use
16. Purpose: Deliver To.
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
17. (B) Create Address.
18. Address Line 1: 487 Beverly.

19. City: Palo Alto.
20. County: San Mateo.
21. State: California.
22. Postal Code: 94301.
Leave all other fields, in the Account Site Address region, blank.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
23. In n
the Business Purpose region, set Purpose to Deliver To and leave the Primary check box
unchecked.
24. (B) Apply.

Defining Payment Terms
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nPayment
Defining
M(N) - tr Terms
no
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.

Defining Invoicing and Accounting Rules
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M(N) - tr
a nInvoicing
Defining and Accounting Rules
no Management > Setup > Transaction Types > Define
Order
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.

Defining Auto-Accounting Parameters
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M(N) - tr
a nAuto-Accounting
Defining Parameters
no
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.

- 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
a
account.
) has
c o m ฺ
- Unbilled Receivable: Receivables uses the unbilled receivable account for
ฺ
ail uide
transactions that have invoicing and accounting rules. If your accounting rule
m
recognizes revenue before your invoicing rule bills it, Receivables posts this amount
g nt G
@
to your unbilled receivable account.
u
d yฺ tude
- Unearned Revenue: Receivables uses the unearned revenue account for transactions
d
rre this S
that have invoicing and accounting rules. If your accounting rule recognizes revenue
a
h e sw use
after your invoicing rule bills it, Receivables posts this amount to your unearned
a
revenue account.
( m to
di cens e
- Unpaid Bills Receivable: AutoAccounting uses this value if you derive the Unpaid
a
mm ble li
Bills Receivable account from the transaction drawee site. You can enter a value in
U
this field only if the business purpose for this address is Drawee.
ar fera
e w
• Segment: Segment names in your Accounting Flexfield Structure are automatically
s ans
h populated when you select an AutoAccounting Type.
Ma on-tr
• Table: Receivables enables you to use different table names for different accounts. Select
n 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.
- Drawee 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.

- 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.
a
has
• 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
m ฺ
Constant using the list of values.
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining Territories in Receivables
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M(N) - tr
a nTerritories
Defining in Receivables
no
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.

Practice - Defining a Territory
Overview
In this practice you will learn how to define a territory in Oracle Order Management
Assumptions

) h as
• Use Order Management Super User, Vision Operations (USA) or comparable m Super
o
a ilฺ uideฺ
c
Tasks @ gm nt G
d y ฺu tude
r
1. Define a territory named XX-Territory within the d Pacific
eAsia s Sarea.
a r h i
e s w se t
a h to u
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Solution - Defining a Territory
Login
Define a Territory
(N) Receivables > Transactions > AutoInvoice > Territories
a
has
25. Name: XX-Territory.
)
m ฺ
26. Description: Territory for XX.
ฺ c o
27. Flexfield (list of values): m ail uide
@ g nt G
• Area: APAC
u
yฺ tude
e d d S
a r r h i s
• Country: Your choice
e s w se t
a h to u
• Region: Your choice m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
28. Active: Enable
29. Effective Dates:

• Start: Today’s date
• End: Leave blank
30. Save.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining Invoice Sources (Batch Source) – Automatic Transaction
Numbering
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M a n-tr
no Batch Sources – Automatic Transaction Numbering
Defining
(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.

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
has
A Receivables Transaction Type is defined and assigned at the system parameter or transaction
)
type level for autoinvoice creation.
c o m ฺ
ฺ
ail uide
To define and assign a receivables transaction type:
m
g nt G
• Define the transaction type: (N) Receivables > Setup > Transactions > Transaction Types
u @
d d yฺ tude
• Assign the transaction type to the system parameter: If the invoice transaction type is
rre this S
referred for autoinvoice generation at the operating unit level (e.g., Vision Operations),
a
h e sw use
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
( m a to
Parameters > Values
di cens e
a
• Assign the transaction type to the order header/line transaction type: If the Invoice/
mm ble li
Receivables transaction type is referred for AutoInvoice generation, then it is assigned
U
ar fera
under the Finance tab of the transaction type. (N) Setup > Transaction Type > Define
w
h e s ans
• Invoice Transaction Type assigned at Line Transaction Type level has maximum
Ma on-tr
precedence followed by Header Transaction Type, then at the system parameter level.
n

Define Salespersons to Assign Sales Credit
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Define
M(N)
Salespersons to Assign Sales Credit
no Management > Setup > Sales > Salespersons
Order
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 bill-
to, 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.

Using the Resources Window to Create a Salesperson
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M(N)
the
- tr
a nResources
Using Window to Create a Salesperson
no Management > Setup > Sales > Salespersons
Order
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.

Guided Demonstration – Creating a Salesperson
Responsibility: Order Management Super User, Vision Operations
(USA)
Find an Employee
1. (N) Order Management > Setup > Sales > Salespersons
2. Within the Find Resources window, Resource region, enter the following in the Name field:
− Adams, Mr. Brian
3. (B) Find. Adams, Mr. Brian, employee number 10242 is displayed in the Resource Search
Results window. a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
4. (B) Resource Details
5. (T) Receivables
6. Enter 2118 in the Sales Person Number field.
7. Select Quota Sales Credit using the list of values in the Sales Credit Type field.
8. Accept the default in the Start Date field.
9. Enter an end date that is 1 year from today.
10. Save.

Tax Setups in Transaction Types Window – Receivables and
Order Management
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t r a
M
no in Transaction Types Window – Receivables and Order Management
Tax Setups
(N) Order Management > Setup > Transaction Types > Define
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.

Practice - Viewing Tax Setups
Overview
In this practice you will learn how view tax setups in Oracle Order Management
Assumptions

) h as
• Use Order Management Super User, Vision Operations (USA) or comparable m Super
o
a ilฺ uideฺ
c
Tasks @ gm nt G
d y ฺu tude
d Management.
2. Navigate to the Transaction Types window rineOrder
s S
a r t h i
e s w the tax
s e
a h to u
3. Find the tax related fields and determine events.
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Solution – Viewing Tax Setups
Login
(N) Order Management > Setup > Transaction Types > Define
31. (T) Finance
a
has
32. Navigate to the Receivables Transaction Type field and use the list of values to view the
applicable options.
)
m ฺ
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
33. Navigate to the Tax Event field and use the list of values to view the applicable options.

Overview of Credit Checking
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s Checking
h
a n-t
Overview of r a
Credit
MCredit
nochecking 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.

Defining Credit Checking on the Customers Page – Profile Tab
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a nCredit
Defining
M(N) - tr Checking on the Customers Page – Profile Tab
no Management > Receivables > Customers > Customers > (T) Profile
Order
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 customer’s 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.

• Credit Analyst: The analyst for this profile.
• Next Credit Review: A date for the next credit review of the profile.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Defining Credit Check and Hold
Overview
In this practice you will learn how to create a credit check rule in Oracle Order Management
Assumptions

) h as
• Use Order Management Super User, Vision Operations (USA) or comparable
m Super
o
a ilฺ uideฺ
c
Tasks @ gm nt G
d y ฺu tude
r ed is S
4. Create a credit check rule named XX-CreditCheck-Rule.
r
w a e th
s
he to us
• Credit Check Level: Sales Order
a
m Order
(Sales
• Credit Hold Level:
a d i e n se
m m e lic
r U
• Conversion
a b l Corporate
Type:
a fer
sw Credit
5.heEnable a n s Check and Credit Hold for your customer.
Ma6. oSuspend
n -t r
n the customer’s credit.

Solution – Defining Credit Check and Hold
Login
Create Credit Check Rule
(N) Order Management > Setup > Credit > Define Credit Check Rule
a
has
1. Enter XX-CreditCheck-Rule in the Rule field.
)
m ฺ
2. Use the list of values to select Sales Order in the Credit Check Level field.
ฺ c o
3. Use the list of values to select Sales Order in the Credit Hold Levelm ail uide
field.
@ g nt G
u de
yฺ Typetfield.
u
d
4. Use the list of values to select Corporate in the Conversion
d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
5. On the Exposure tab, enable the following fields:

• Use Pre-Calculated Exposure
• Include Uninvoiced Orders
• Include Freight and Special Charges
• Include Tax
• Include Orders Currently On Hold
• Include Returns
6. Save.
Define Credit Check and Hold

a
(N) Order Management > Receivables > Customers > Customers
) has
c o m ฺ
34. Enter your customer name in the Name field. ฺ
ail uide
m
g nt G
35. (B) Find.
u @
d d yฺ tude
36. Click your company name in the Name column. re
r i s S
a
w icon h
eintthe Details column.
e
37. Within the Accounts tab, click the View
h tos
Detailsu s
m a
38. Open the Account Profiled
a i ( ense
tab.
m m e lic
U
39. Enable Credit Check.
r a b l
w a fer
e s
40. Enable
h Credit n
a s
Hold.
M a n-t r
no the Account Status to Suspended.
41. Change
42. (B) Apply.
43. (B) Save.

Defining Credit Checking on the Customers Page - Profile
Amounts Tab
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M a n-tr
no Credit Checking on the Customers Page – Profile Amounts Tab
Defining
(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

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Credit Check Rules
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr Rules
Credit
M(N)
Check
no Management > Setup > Credit > Define Credit Check Rules
Order
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.

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m G
gManagement
t
Oracle Order u @ n
d
SetupdSteps yฺ tude
a r re this S
e s wChapterse6
a h to u
m
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Oracle Order Management Setup Steps

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order Management Setup Steps
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Profile Options and System Parameters
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M a n-tr and System Parameters
Profile Options
o
Duringnimplementation, 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 Guide, Release 12.

For information on how to set and update profile option values, see the Oracle Applications
System Administrator's Guide.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Overview of QuickCode or Lookup Types
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Overview
M(N) tr
a nof-QuickCode or Lookup Types
no Management > Setup > QuickCodes
Order
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

• 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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining QuickCode or Lookup Types
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Overview of Order Header and Order Line Processing Flows
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Overview
MThe tr Header and Order Line Processing Flows
a nof-Order
o commonly used Order Header flows are:
nmost
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.

Overview of Transaction Types Window
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Overview
M(N) tr
a nof-Transaction Types Window
no Management > Setup > Transaction Types > Define
Order
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

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
a
has
Flow - Generic with Approval.
)
8. Enter an effective date for the transaction type in the Effective Dates field.
m ฺ
ฺ c o
ail uide
9. Select the default transaction phase, Fulfillment or Negotiation, in the Default
m
Transaction Phase field from the list of values. Transaction phase determines where in the
g nt G
@
workflow the transaction begins, and can be used in defaulting rules. This field defaults
u
d yฺ tude
to Fulfillment—a fulfillment phase must be defined; Negotiation is optional.
d
rre this S
10. Enter a value in the Layout Templates field. This field is optional.
a
e sw use
11. Enter a value in the Contract Template field. This field is optional.
h
m a to
12. In order for the Quote number to become the Sales Order number, select the Retain
(
di cens e
Document Number check box. This is not applicable for Sales Orders or Sales
a
mm ble li
Agreements. If the transaction type is associated with both a negotiation flow and
U
ar fera
fulfillment flow, the document number can be retained when the document transitions to
e w
fulfillment.
s ans
h
Ma on-tr
On the Main Tab in the Document Region:
n
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 Sales 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:

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. a
has
23. You can select a credit check rule for each field within the Credit Check Rule region, or
)
o m ฺ
select combinations that suit your business purposes. For example, you can select a credit
c
ฺ
ail uide
check rule for booking only, or booking and shipping. If you leave any of the Credit
m
g nt G
Check Rule fields blank, no credit checking will occur when an order or order line
u @
yฺ tude
reaches the corresponding workflow activity within the order or line flow, using the order
or order line type specified.
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Guided Demonstration - Setting up Transaction Types
Responsibility: Oracle Management Super User, Vision Operations
This guided demo shows you how to create transaction types for both order header and order
line, how to assign line transaction types to an order header, and the subsequent data that defaults
on the Sales Orders window as a result of setting up transaction types correctly.
1. (N) Setup > Transaction Types > Define
2. In the top region of the Transaction Types window, enter the following information:
− Operating Unit = Vision Operations
− Transaction Type = XXStandardTT
− Description = Standard Order Line a
− Sales Document Type = Sales Order a s
− Order Category = Order m )h
− Transaction Type Code = Line i l ฺ co deฺ
− Effective Dates – From = Enter today’s date g ma t Gui
y ฺ u@ uden
3. (T) Shipping.
− Scheduling Level = Allow all scheduling r e dd s St
w ar e thi
actions
4. (B) OK.
a hes to us
d i (m nse
a lice
5. Save your transaction type.
m
U m b le Type for the Order Header
r
Creating an Order
a fer
Transaction
a
e s w n sa new transaction type for the order level.
h
6. (I) a
New. Create
r
MaNote: o n -t
n The following steps create the order transaction type and assign line flows to the order
transaction type.
7. In the top region of the window, enter the following information:

− Transaction Type = XXOrderTT
− Description = Standard Order with order lines
− Sales Document Type = Sales Order
− Order Category = Order
− Transaction Type Code = ORDER
− Fulfillment Flow = Order Flow – Generic. Note: Selecting a fulfillment flow
assigns the workflow to the order header when the sales order is created. This
enables you to save the sales order.
− Effective Dates – From = Enter today’s date

8. (T) Shipping.
− Scheduling Level = Allow all scheduling actions
9. (T) Finance
− Currency = USD
10. (T) Main.

− Default Order Line Type = XXStandardTT.
11. Save your order transaction type. Do not close the window.
12. (B) Assign Line Flows and enter the following information on the window that opens:
− Order Type = XXOrderTT
− Line Type = XXStandardTT
− Process Name = Line Flow – Generic s a
− Start Date = Enter today’s date )h a
c m
o eฺ
i l ฺ
13. (B) OK.
g ma t Guid
14. Save your work and exit the window.
y ฺ u@ uden
r e dItdto the S t
Creating a Document Sequence and Assigning
a r t h is Transaction Type
h e sw u se type and then assign the document

Now you will create a document sequence
sequence to the transaction type.i (m
a for
to
the transaction
d cens e
a li
mm b> lDefine
15. (N) Setup > Documents
U e
r era
afollowing
e w
16. Entersthe
n s f information in the Document Sequences window:
h − Name tra = XXOrderTT Sequence
Ma o−n-Application = Order Management
n − Effective From = Today’s date
− Type = Automatic
− Initial Value = 1000
17. (I) Save. Exit the window.
18. (N) Setup > Documents > Assign
19. (T) Document. (in Sequence Assignments window)

− Application = Order Management
− Category = XXOrderTT
− Ledger = Vision Operations (USA)
20. (T) Assignment.

− Start Date = Today’s date
− Sequence = XXOrderTT Sequence

21. (I) Save and exit the window.
22. Enter an order with the order type as XXOrderTT. The line type defaults to XXStandardTT
and the order number initializes to 1000 due to the Transaction Type setup.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Setting up Transaction Types
Overview
In this practice, you will learn how to set up a transaction type with associated line type and
assign the workflow process.
• Create a line transaction type for the order lines
• Create an order transaction type for the order header
• Assign line flows
• Create a document sequence a

a s
• Assign the document sequence to the order type
m )h
i l ฺ co deฺ
Assumptions
g ma t Gui
• You must have access to an Oracle Application Vision ฺ @ deorncomparable training
udatabase
y tu
ddthis spractice.
e
or test instance at your site on which to complete
r S
w ar e thi
h s to us
• Your instructor will provide logineinformation.
a
• Use Order Management i m User,
(Super seVision Operations (USA) or comparable Super
a d e n
User Order Management
m l lic
m e responsibility.
Tasks wa
r U erab
e s n s f
h -taraline transaction type named XX-StandardLine for the order lines.
Ma1. Create
non
2. Create an order transaction type named XX-StandardOrder for the order header.
3. Assign line flows to the XX-StandardOrder transaction type.
4. Create a document sequence named XX-DocSeq for StandardOrder.
5. Assign XX-DocSeq to the transaction type XX-StandardOrder.

Solution – Setting Up Transaction Types
Creating a Line Transaction Type
Responsibility = Oracle Management Super User, Vision Operations (USA)
1. Navigate to the Transaction Types window:
• (N) Setup > Transaction Types > Define
2. Create a new transaction type by entering the following information:

− Transaction Type = XX-StandardLine
− Description = Standard Line Transaction Type a
− Order Category = Order ) has
c o m ฺ
− Transaction Type Code = Line ฺ
ail uide
− Effective Dates – From = Today’s datem
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
3. (I) Save.

Creating an Order Transaction Type for the Order Header
4. (I) New. Create the order header transaction type.

− Transaction Type = XX-StandardOrder
− Description = Standard Order Transaction Type
− Order Category = Mixed
− Transaction Type Code = ORDER
− Fulfillment Flow = Order Flow – Generic. Note: Selecting a fulfillment flow
assigns the workflow to the order header when the sales order is created. This
enables you to save the sales order.
− Effective Dates – From = Today’s date
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s Default
5. (T) Main.
a n sOrder Line Type = XX-StandardLine
Ma on-t
− r
n
6. (T) Shipping.
− Shipping Method = DHL
− Freight Terms = Prepaid

a
has
7. (T) Finance.
− Accounting Rule = Immediate )
− Invoice Source = Manual c o m ฺ
− Currency = USD
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
8. (B) Assign Line Flows. Enter the following information:

− Order Type = XX-StandardOrder
− Line Type = XX-StandardLine
− Process Name = Line Flow - Generic

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
i m window.
(Types se
d
9. (B) OK. Exit the Transaction
a e n
m mSequence
l e lic and Assigning It to the Transaction Type
r U erab
Creating a Document
a
e
Now you s w nsafdocument sequence for the transaction type and then assign the document
will create
M ah tonthe
sequence - tratransaction type.
no
10. Navigate to the Document Sequences window.
• (N) Setup > Documents > Define
11. Enter the following information in the window:

− Name = XX-DocSeq
− Effective From = Today’s date
− Type = Automatic
− Initial Value = 1

a
12. (I) Save. Exit the window. ) has
c o m ฺ
13. Navigate to the Sequence Assignments window. ฺ
ail uide
m
g nt G
• (N) Setup > Documents > Assign u @
d d yฺ tude
rre this S
14. (T) Document. Enter the following information:
a
h e sw use
− Category = XX-StandardOrder
a
( m e to
a di cens
− Ledger = Vision Operations (USA)
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
15. (T) Assignment. Enter the following information:

− Sequence = XX-DocSeq

16. (I) Save and exit the window.
17. Enter a sales order with the Order Type = XX-StandardOrder. The order number will be 1
and the line type will be defaulted to XX-StandardLine.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Workflow in Transaction Types
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Workflow
MNegotiation r
a nin-tTransaction Types
no 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.

• 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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Guided Demonstration – Creating and Booking a Sales Order,
Viewing Workflow Status, Viewing Workflow Status
(USA)
Create and Book a Sales Order

1. (N) Order Management > Sales Orders
2. Within the Main tab, enter the following in the Customer Number field and [TAB] to
populate the other fields:
− 1608
a
has
− Use the list of values in the Order Type field to select Mixed.
)
m ฺ
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
4. (T) Line Items
5. Enter AS54888 in the Ordered Item field.
6. Enter 2 in the Qty (quantity) field.
7. Save your order.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
8. (B) Book Order.
( m a to
i eyou
dinforming e
ns that the order has been booked.
A Note window is displayeda c
U mm ble li
9. (B) OK ar
s w s f era
he your n order number here _____________
asales
M on-tr
a
Document
n Tools > Workflow Status
10. (M)
11. View the status of the workflow for the sales order and line.

Guided Demonstration - Customizing Workflow Associated with
an Order
(USA)
Find the Sales Order

1. (N) Order Management > Sales Orders
2. (I) Find
3. Within the Order Number field of the Find Orders/Quotes window, enter the sales order
a
has
number from the Create and Book a Sales Order, View Workflow Status demonstration.
)
m ฺ
4. (B) Find
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
5. (B) Open
View and Customize the Workflow

6. (M) Tools > Workflow Status

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
r r e i s S
7. Scroll down the page to show the activities a
wassociatede h
twith this workflow.
e s
h to Activity s
u Types and Activity Status criteria.
m a
di ( cense
8. Within the Search region, disable some of the
a
9. (B) Go.
U mm ble li
w
10. Identify archanges
the f erinathe Activities region from your customized search.
h s
e ran s
M a n
11. (B) View-tDiagram
n o

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
12. Open each of the following tabs:
d d yฺ tude
a rre this S
a. Definition
h e sw use
b. Usage
( m a to
di cens e
a
c. Status
U mm ble li
w ar fera
d. Notification
h e s ans
13.aUsing the
M n - trleft menu, click Participant Responses.
no

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
rre this S
14. Identify the Search region and each of the search criteria.
a
h e sw use
15. Using the left menu, click Workflow Details.
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
16. Identify the Workflow Definition and Workflow Attributes regions and the fields within
each.

Overview of Document Sequences for Order Numbering
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s Sequences for Order Numbering
h
a n-t
Overview of r a
Document
MOrder
noManagement 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.

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.
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 a
Category field.
) has
c o m ฺ
2. Select the Ledger. Enter Manual in the method field if the number sequence is manual,
otherwise enter Null. ฺ
ail uide
m
g nt G
3. On the Assignment tab enter the Start Date and the Sequence that you defined for your
u @
d d yฺ tude
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
rre this S
assignment and create a new one for the new assignment. You cannot have more than one
a
h e sw use
assignment for the same date range, document type and ledger.
a to
4. There are additional controls to be considered when a quote transitions to a sales order in
( m
di cens e
reference to the document number and how the number is generated.
a
mm ble li
5. If a gapless numbering type is a requirement, then the Retain Document Number check
U
ar fera
box should not be selected when using a transaction type for negotiation and fulfillment.
w
h e s ans
Ma on-tr
n

Defining Order Import Sources
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Order
Defining
M(N) n - tr Import Sources
no Management > Setup > Orders > Import Sources
Order
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.

Overview of Processing Constraints
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Overview
M(N) tr
a nof-Processing Constraints
no Management > Setup > Rules > Security > Processing Constraints
Order
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.

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 a
3. Enter in the first line of the Conditions region:
) has
c o m ฺ
- Group Number: 101 (the group number should be greater than 100 for user-defined
constraints) ฺ
ail uide
- Scope: Any
m
g nt G
u @
d yฺ tude
- Validation Entity: Order Header
d
- Record Set: Order
a rre this S
h e sw use
- NOT check box: Deselect
a to
- Validation Template: Booked
( m
di cens e
a
- System check box: Deselect
mm ble li
- User Message: the order is booked
U
ar fera
4. Enter in the second line of the Conditions region:
w
h e s ans
- Group Number 2
Ma on-tr - Scope: Any
n - 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
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M(N)
up
- tr
a nProcessing
Setting Constraints
no Management > Setup > Rules > Security > Processing Constraints
Order
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

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
a
has
- 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
m ฺ
c o
constraints to be temporarily disabled if necessary.
ฺ
m ail uide
• System check box: If a Constraint has the System check box selected, you cannot update
the constraint definition. @ g nt G
u
yฺ tude
Enter Conditions
d d
rre this S
6. In the Group Number field, enter a numeric value according to the following principles:
a
e sw use
- For conditions that should together evaluate to TRUE (AND conditions), enter the
h
a to
same group number. The constraint applies if the entity in question meets all of the
( m
di cens e
conditions defined.
a
mm ble li
- For conditions that should together evaluate to OR (OR conditions), enter a different
U
w ar fera
number for each record. The constraint applies if the entity in question meets any
h e s ans one of the conditions defined.
Ma on-tr
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
n 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.

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 a
has
check box is not selected, you can update the constraint condition.
)
o m ฺ
10. In User Message, enter the trailing portion of the error message that the constraint
c
ฺ
ail uide
processing should display when the user violates the constraint. For example, if the
m
g nt G
constraint was to not allow an update of the item field on the order line if the line has
u @
d d yฺ tude
been previously booked, constraints processing displays the error message You are not
rre this S
allowed to update the item; the item is booked.
a
Specify who the Constraint applies to
h e sw use
Select one of the following:
( m a to
e
• All responsibilities: The constraint applies to all responsibilities.
di cens
a
mm ble li
• Authorized responsibilities: The constraint applies to all responsibilities except ones that
U
you specify. Specify the excepted responsibilities in the untitled lines below your
ar fera
selection.
e w
s ans
h• Constrained responsibilities: The constraint applies to the responsibilities that you
Ma on-tr
specify. Specify the excepted responsibilities in the untitled lines below your selection.
n

Guided Demonstration - Setting Up a Processing Constraint
In this demonstration, you will learn how to set up a processing constraint that prevents a sales
order header from being updated when the order is booked or when there are order lines created.
Processing constraints control who can change what and when they can change it. Processing
constraints can prevent certain changes, but also can perform actions based on those changes
such as requiring a reason for the change, triggering an action in Audit Trail or Versioning, or
raising an Integration Event.
Responsibility: Oracle Management Super User, Vision Operations
1. (N) Order Management > Setup > Rules> Security > Processing Constraints
a
has
2. Query in the top of the window (To query, press CNTRL + F11):
− Application = Order Management )
m ฺ
− Entity = Order Header ฺ c o
m ail uide
3. Create a new line on the Constraints region:
@ g nt G
− Operation = Update u
yฺ tude
− Attribute = Order Type d d S
− User Action = Not Allowed. This means a rrethe constrained
t h i s
s w e operation cannot be
performed.
− Leave System Changes a e
hUser t o usfields blank.
m se
di =(Selected
and Changes
− Enabled checka
m
box
l i c en
U mon thebConditions
le
a r
4. Create a new line
r a tab:
e n s fe = 101
−swGroup Number
h − Scopetra = AnyEntity = Order Header
Ma o−n-Validation
n − Record Set = Order. The record set 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.
− NOT check box = Deselected
− Validation Template = Booked
− Enabled check box = Selected
− User Message = The order is booked.
5. Create a second line on the Conditions tab:

− Group Number = 102
− Scope = Any
− Validation Entity = Order Header
− Record Set = Order
− NOT check box = Deselected

− Validation Template = Lines Exist
− User Message = The order has lines.
Applying the Processing Constraint to a Sales Order (Constraint Based on

Booked Orders)
Responsibility = Order Management Super User, Vision Operations
6. Navigate to the Sales Orders window.
7. Enter the sales order header using the following information (all remaining information
defaults in):
− Customer = XX-Big City Electronics
− Order Type = Order Only
a
8. In the Line Items tab, enter the following line items: ) has
c o m ฺ
ฺ
ail uide
Ordered Item Quantity m
g nt G
u @
XX- Phone 3
d d yฺ tude
XX-Palm Pilot 5
a rre this S
h e sw use
9. Save the sales order.
( m a to
di cens e
a
mm ble li
10. Book the order.
U
ar Information
11. On the Order
s
− w s f e=raDroptab,Shipment
Main subtab, change the order type:
a he -tran
Order Type
M n work.
noyour
12. Save
Note: If the processing constraint condition has been applied successfully, a Message box
alerts you that you cannot update the Order Type because the order is in Booked status.
Applying the Processing Constraint to a Sales Order (Constraint Based on

Existing Lines)
Responsibility = Order Management Super User, Vision Operations
14. Enter the sales order header using the following information (all remaining information
defaults in):
− Order Type = Order Only

15. In the Line Items tab, enter the following line items:
Ordered Item Quantity

XX- Phone 2
16. Save your work.
17. On the Order Information tab, Main subtab, change the order type:
− Order Type = Bill Only
18. Save your work.
Note: You should not be able to save your changes because the second processing constraint
a
condition does not allow you to update the Order Type for orders with existing order lines.
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining Validation Templates
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Validation
Defining
MOrder n - tr Templates
noManagement 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.

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.
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, a
Error, Notified, and Suspended
) has
o m ฺ
- Select the activity Result for the condition
c
- Save your work ฺ
ail uide
m
g nt G
- API (validation is completed through an Application Program Interface):
u @
d yฺ tude
- Select the PL/SQL Package you wish to interface with the constraint condition
d
rre this S
- Enter the Procedure name of the API
a
h e sw use
- Save your work
a to
- TBL (validation is based on the values of database columns on this entity):
( m
di cens e
a
- Select the Attribute Column name on the entity for the constraint condition
U mm ble li
- Select the Validation Operation for the constraint condition. Select from: =
w ar fera (Equal To), <> (Not Equal To), Is NULL, Is Not NULL
h e s ans - Select the Value String you want to validate against the value of the column
Ma on-tr Note: You can add more than one attribute, value pair, otherwise all pairs will be
n 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.
For more information see:
(Help) Oracle Manufacturing Applications > Oracle Order Management > Oracle Order
Management Setup> Defining Validation Templates

Defining Defaulting Conditions
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Defaulting
Defining
M(N) n - tr Conditions
no Management > Setup > Rules > Defaulting > [Defaulting Condition Template]
Order
The Defaulting Condition Template 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

- 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, see:
a
has
Management Setup> Define Defaulting Conditions
)
m ฺ
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining Defaulting Rules
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr Rules
Define
M(N)
Defaulting
no Management > Setup > Rules > Defaulting > Defaulting Rules
Order
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.

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.
Management Setup> Define Defaulting Rules
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Setting Up a Defaulting Rule
Overview
In this practice, you will learn how to set up a defaulting sourcing rule for the Freight Terms
attribute for your customer XX-Big City Electronics. You will then create a sales order to
observe how the sourcing rule provides a defaulting value for Freight Terms on the Sales Orders
window.
In Oracle Order Management, defaulting sourcing rules enable you to automatically default
attribute values into sales order entities:
• Sales order entities include groups of related attributes such as Order or Line.
s a
• a
Attributes are the individual fields within a particular entity, such as Warehouse, Ship
)h
To Location, or Agreement. m
co deฺ
Note: Changes to defaulting rules take effect for any new orders that a i l ฺ i
g m G u
use the modified
defaulting rules when you open the Sales Order Header or Lines windowst or if you update
an attribute (field) on an order. y ฺ u@ uden
r e dd s St
Assumptions w ar e thi
a h es us
• Oracle Management Superm
( toOperations responsibility
User, Vision
e
di cens
• Prior practices m area li Practices build on earlier exercises.
completed.
m l e
• You a r Uhaveeaccess
rab to an Oracle Application Vision database or comparable training
e w must f
s test instance
n s at your site on which to complete this practice.
h or
r a
Ma on-t
n
Tasks
Setting Up a Defaulting Condition Template
Responsibility = Oracle Management Super User, Vision Operations
You will first create a defaulting condition template that defines the conditions when the default
sourcing rule can be applied; for example, apply the defaulting sourcing rule X only if the
customer is Big City Electronics and the Order Type is Mixed (in this case, the conditions are the
specific customer and order type).
Then you can create the defaulting sourcing rule that determines the actual value for the Freight
Terms attribute. (The condition template is attached to the defaulting rule to control how the rule
is applied.)
1. Navigate to the Defaulting Setup – Entity Attributes window.

2. Click Find and select the Order Header entity.
3. Click OK to view the attributes related to the entity.
4. Click the Defaulting Condition Templates button to display the Defaulting Condition
Validation Templates window.
Note: In the header region, ensure the following values are selected for the Application and
Entity values (if you do not see these values, do a query to find them):
− Entity = Order Header
5. In the Validation Templates region, click the New icon to enter a new validation template:
− Condition Name = XX-Freight Terms for XX-Big City Electronics
− Description = Used for Freight Terms for Customer XX-Big City Electronics
s a
)h a
6. In the Validation Rules region, create two validation rules for the template you added:
m
co deฺ
i l ฺ
--- Group # Attribute g ma t GuValue
Validation Operation
i
String
u @ n
Rule # 1 105 Customer
d d yฺ = tude XX-Big City Electronics
Rule # 2 106 Currency
a rre this= S USD
w e
7. Save your work. a hes to us
d i (m nse
m a licValidation
8. Close the Defaulting Condition e Template window.
m ble
r U eraSourcing
Setting Up aaDefaulting Rule for the Freight Terms Attribute
s w s f
he -ttorathen Defaulting Setup – Entity Attributes window.
9. aNavigate
M on
n Attribute = Freight Terms.
10. Select
11. Click Defaulting Rules to display the Attribute Defaulting Rules window.
12. On the Defaulting Conditions region, create a new defaulting condition for the Freight
Terms attribute (select the defaulting condition template you created in previous steps):
− Precedence = 3
− Defaulting Condition = XX-Freight Terms for XX-Big City Electronics
− Enabled = Selected
Note: When defining a set of Conditions and using them in rules, be sure to place the
ALWAYS condition last in the Precedence for Defaulting Conditions.
13. Select the Enabled check box 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 rule processing.

14. On 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.
15. Select the defaulting Source Type = Constant Value. The defaulting source type determines
data entry in the Default Source/Value field.
16. In the Default Source/Value field, enter To Be Determined. This value will display as the
Freight Terms value in the Sales Orders window.
17. Select Tools > Generate Defaulting Handler Package. This program generates the defaulting
rules for the attribute.
18. Click Save.
Viewing the Freight Terms Attribute in the Sales Order Window a

) h as
c o m ฺ
ฺ
ail uide
20. In the Order Information tab, Main subtab, enter a sales order: m
g nt G
− Customer = XX-Big City*
u @
− Order Type = Mixed
d d yฺ tude
− Currency = USD*
a rre this S
Note: *These conditions are required h e sw useTerms rule to be applied.
for the Freight
( m a to
i Others
dtab, e
s Confirm that the default freight term value in
nsubtab:
21. In the Order Information a c e
m is Toe Beli Determined. If so, then the default sourcing rule was
the Freight Terms
U m field
b l
r
applied successfully. a
e s wa nsfer
a h the
Disabling
- t r aDefaulting Condition XX-Freight Terms for XX-Big City Electronics
M
for the o n Terms Attribute
n Freight
Now you will disable the Freight Terms defaulting condition, and create a sales order to confirm
that it has been disabled.
Note: If the Enabled check box for the defaulting condition is not selected, the defaulting
condition is disabled and the rules and condition associated with this condition are not used in
default rule processing.
23. Select Attribute = Freight Terms.
24. Click Defaulting Rules to display the Attribute Defaulting Rules window.
25. Select the Defaulting Condition = XX-Freight Terms for XX-Big City Electronics
− Enabled = Deselected

26. From the Tools menu, select Generate Defaulting Handler Package to update the attribute.
27. Click Save.
Viewing the Freight Terms Attribute in the Sales Order Window
29. On the Order Information tab > Main subtab, enter a sales order for the following customer:
− Currency = USD*
Note: *These conditions are required to see if the Freight Terms rule you created has been
disabled successfully.
s a
30. On the Order Information tab > Others subtab: In the Freight Terms field, notice that a
) hthat
the
default Freight Terms value is now Prepaid and not To Be Determined. Thisomeans
c m ฺ you
ฺ
il created, eand a
ma t Guid
successfully disabled the Freight Terms sourcing condition you previously
different defaulting rule was applied to derive the Freight Termsgvalue.
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
Ma on-t
n

Solution - Setting Up a Defaulting Rule
Setting Up a Defaulting Condition Template
• (N) Order Management > Setup > Rules > Defaulting
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
2. (I)nFind.
3. Select entity = Order Header.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
4. (B) OK.
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
5. (B) Defaulting Condition Templates. The Defaulting Condition Validation Templates

window appears.

Note: In the header region, ensure the following values are selected for the Application and
Entity values (if you do not see these values, do a query to find them):
− Entity = Order Header
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a li
U mminbtheleValidation
6. (I) New (place cursor Templates region).
r eratemplate:
a validation
7. Entersaw
new s f
a he− -Condition
tran Name = XX-Freight Terms for XX-Big City Electronics
M o−n Description = Used for Freight Terms for Customer XX-Big City Electronics
n
8. In the Validation Rules region, create two validation rules for the template you added:
--- Group # Attribute Validation Operation Value String

Rule # 1 105 Customer = XX-Big City Electronics
Rule # 2 106 Currency = USD
9. (I) Save.
10. Close the Defaulting Condition Validation Template window.
Setting Up a Defaulting Sourcing Rule for the Freight Terms Attribute

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
r r e i s S
a
w Rules
13. (B) Defaulting Rules. The Attribute Defaulting
e h
twindow appears.
e s
h to u s
m a
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

14. On the Defaulting Conditions region, select a defaulting condition for the Freight Terms
attribute (use the defaulting condition template you created in previous steps):
− Precedence = 3
− Defaulting Condition = XX-Freight Terms for XX-Big City Electronics
− Enabled = Selected
15. On the Default Sourcing Rules region, create a default sourcing rule for the Freight Terms
attribute. The sourcing rule defines what Freight Terms value is displayed when the
defaulting conditions are met:
− Sequence = 501 (or similar 3-digit value if you cannot use 501)
− Source Type = Constant Value
− Default Source/Value = To Be Determined
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
16. (M) Tools > Generate Defaulting Handler Package. This program generates the defaulting
rules for the attribute.
17. (I) Save.
Viewing the Freight Terms Attribute in the Sales Order Window
• (N) Orders, Returns > Sales Orders
19. (T) Order Information, (T) Main:

20. Enter a sales order for the following customer:
− Currency = USD*
Note: *These conditions are required for the Freight Terms rule to be applied.
21. (T) Order Information, (T) Others.
22. On the Freight Terms field, confirm that the defaulting freight term value is To Be
Determined. If so, then the default rule was applied successfully.
Disabling the Defaulting Condition XX-Freight Terms for XX-Big City Electronics
for the Freight Terms Attribute
a
has
)
m ฺ
ฺ c o
m ail uide
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
25. (B) Defaulting Rules. The Attribute Defaulting Rules window appears.
26. Select the Defaulting Condition = XX-Freight Terms for XX-Big City Electronics
− Enabled = Deselected
Note: If the Enabled check box for the defaulting condition is not selected, the defaulting
condition is disabled and the rules and condition associated with this condition are not used
in default rule processing.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
e
27. (M) Tools > Generate Defaulting Handler
h swPackage.
u se
( m a t o
28. (I) Save. di cens e
a li
m eAttribute
U
Viewing the Freight mTerms b l in the Sales Order Window
r a
e s
29. Navigate ferOrders window.
wato thensSales
h -tra
Ma• o(N)
n n Orders, Returns > Sales Orders
30. (T) Order Information, (T) Main.
31. Enter a sales order for the following customer:

− Currency = USD*
Note: *These conditions are required to see if the Freight Terms rule you created has been
disabled successfully.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
32. (T) Order Information, (T) Others. esw se
a h to u
( m e
a di cens
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

33. In the Freight Terms field, notice that the default Freight Terms value is now Prepaid and
not To Be Determined. This means that you have successfully disabled the Freight Terms
sourcing condition, and a different rule was applied to derive the Freight Terms value.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Setting up Versioning and Audit History
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s and Audit History
h
a n-t
Setting up r a
Versioning
MVersion
no 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

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
• 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.
(Help) Oracle Manufacturing Applications > Oracle Order Management > Change
s a
Management> Versioning > Setup
)h a
m
co deฺ
a i l ฺ
Set Up Audit History
g m G ui
1. Add "View Audit History" menu option to the Order Management
u @ dmenu e n t for those
responsibilities that need to be able to view the new d ฺ
y History
Audit
t u forms – this menu
d S
option will be created through seed data.
a rre this
2. Set up Processing Constraints to indicate
e s w sattributes
which e on the order you want to have
a
audit trail recorded for. See DefinehProcessing
t o uConstraints.
3. Create some new Validation m
i (Templates
seif you have specific conditions to control whether
a d e n
m l e lic See Defining Validation Templates.
minformation.
or not to record audit
r U erParameter
4. Set the OM System
a a b Audit Trail.
s
Navigate
e wto Order
n s fManagement > Setup > System Parameters > Values.
h Select-tyour
ra Operating Unit.
Ma1.2. Select
n
no 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.

Overview of Available To Promise (ATP)
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s To Promise (ATP)
h
a n-t
Overview of r a
Available
MOracle
noOrder 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.

• 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 a
has
warehouses for which you want to see the availability, and the system will return the
)
c o m ฺ
availability in all the selected warehouses. You can open the ATP Details window from the
ฺ
ail uide
Availability window by clicking the ATP Details Button. The ATP Details window displays
how the results were derived. m
g nt G
u @
yฺ tude
ATP is calculated automatically during scheduling, and may be calculated manually by
d
clicking Availability on the Line Items tab of the Sales Order window. There are several steps
d
required for ATP calculations.
a rre this S
e sw use
If you are using ASCP, supply/demand is set up at the plan level. See the Oracle ASCP
h
a to
Implementation Manual. Global Order Promising will only use the infinite time fence specified
( m
di cens e
on the ATP rule. If you are not using ASCP, ATP rules must be defined to determine the
a
mm ble li
sources of supply and demand which are included in the calculation. The ATP rules must be
U
associated with items and/or inventory organizations. Also, the data collection program must
ar fera
e w
be run. There is a requirement for ATP calculations to be very fast; some customer service
s ans
h
representatives will need to give this information to customers on the phone.
Ma on-tr
However, considering all the possible sources of supply and demand for an ATP calculation
n
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 Guide.

Overview of Scheduling Levels
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Overview
MThe tr
a nof-Scheduling Levels
o
nscheduling 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 Bill-Only or 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

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Practice - Using Scheduling in the Sales Orders Window
Overview
In this practice, you will learn how to schedule an order both manually and automatically. Your
customer XX-Big City Electronics wants to order 15 units of item XX-Phone, 45 days from
today’s date.
Assumptions
• Oracle Management Super User, Vision Operations responsibility
• Prior practices are completed. Practices build on earlier exercises.

a
•
has
)
c o m ฺ
ฺ
ail uide
• You have set the following profile option: m
− OM: Auto Schedule = No @ g nt G
u
yฺ tude
d d S Parameters -> Values
• You have set the following system parameter.
a r re Setup->
t h i sSystem
− Reservation Time Fence = 30 w
e s s e
a h to u
m
di ( cense
Tasks
a
mm ble li
Creating a Sales Order
U
w ar = Oracle
Responsibility f eraManagement Super User, Vision Operations
s
he -tran s
M a
non
2. On the Main tab, enter the following sales header information:

− Price List = Corporate
3. On the Line Items tab, enter the following

− Ordered Item = XX-Phone
− Qty = 15
− Request Date = Today’s Date + 45 days
− Line Type = Standard (Header Invoicing)
Checking Item Availability
4. Select the order line for item XX-Phone.

5. Click the Availability button to view whether the quantity is available. If the available
quantity is sufficient, you can continue to the scheduling task.
Scheduling the Order Line
6. From the Tools menu, select Scheduling > Schedule.
7. Click OK.
8. Click the Shipping tab to view the scheduled shipping information and confirm that the
scheduling activity has occurred for the request date.
Reserving the Order Line
9. From the Tools menu, select Scheduling > Reserve.

a
10. Click OK.
) has
c o m ฺ
ฺ
ail uide
11. On the Shipping tab, view the reserved quantity in the Qty Reserved field.
12. Save your work.

m
g nt G
u @
d d yฺ tude
rre this S
Using the Auto Schedule Feature
a
Use the Auto Schedule feature when entering
h e sw
another s
u e on the same order.
line
( m a to check box.
di cens
13. From the Tools menu, select the Auto e
Schedule
a li line:
mm
14. Click New to create
U a newle
order
w f e rab Card
ar = XX-Phone
− Item
e−s Qty =n2s
h
a n-tra
M
no Save.
15. Click
16. In the Line Items tab, Shipping tab: Notice that the Qty Reserved field has been
automatically entered for item XX-Phone Card.

Solution - Using Scheduling in the Sales Orders Window
Creating a Sales Order
• (N) Orders, Returns > Sales Orders
2. (T) Order Information, (T) Main:

− Price List = Corporate a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
3. (T) Line Items, (T) Main:

− Ordered Item = XX-Phone
− Qty = 15
− Request Date = Today’s Date + 45 days
− Line Type = Standard (Header Invoicing)

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
Checking Item Availability h e sw use
( m a to
di XX-Phone.
4. Select the order line for item ns e
a
m e li c e
U
5. (B) Availability.m b l
In the Availability window, confirm that the item quantity you want is
r a
er quantity is sufficient, you can continue to the scheduling task.
e s waIf the
available.
s f
available
h an
Ma on-tr
n
Scheduling the Order Line
6. (M) Tools > Scheduling > Schedule.

7. (B) OK.
8. (T) Line Items, (T) Shipping.
Note: Notice that the schedule ship date has been set to the request date.
a
Reserving the Order Line
) has
c o m ฺ
9. From the Tools menu, select Scheduling > Reserve. ฺ
ail uide
10. Click OK. m
g nt G
u @ de quantity.
d d yฺ treserved
u
rre this S
11. On the Shipping tab note that the Qty Reserved field shows the
a
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
12. (I) Save.
Using the Auto Scheduling Feature
13. (M) Tools > Auto Schedule (Ensure Auto Schedule is selected)
14. (I) New:

− Item = XX-Phone Card
− Qty = 2

15. (I) Save.
16. (T) Line Items, (T) Shipping.
a
Notice that the Qty Reserved field has been automatically entered for item XX-Phone Card.
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Auto-Schedule Profile Option
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s Option
h
a n-t
Auto-Schedule r a
Profile
MThis o option determines the default setting for auto scheduling orders, and also controls
nprofile
the display of the Availability window within the Sales Order Lines window.
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 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 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 Generic workflow process to schedule an order line, you cannot specify a ship set or
arrival set for it.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining Credit Usage Rule Sets
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-trUsage Rule Sets
Define
M(N)
Credit
no Management > Setup > Credit > Define Usage Rule
Order
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.

• 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
a
has
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
m ฺ
ฺ c o
usage rule sets with different Global Exposure options for the same credit profile.
ail uide
3. Select the value Currency in the Usage Type field.
m
@ g nt G
4. Enter a currency in the Currency field. The Currency field can contain any Currency
u
yฺ tude
Code currently defined. The Currency field may also use the lookup All Currencies to
d d
rre this S
indicate the usage rule is for all currencies defined.
a
h e sw use
5. Chose to exclude a specific currency for your usage rule by selecting the Exclude check
box. The default is unchecked, or No.
( m a to
di cens e
Note: If the field Currency has value of All, the Exclude check box is non-updateable.
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Defining Credit Check Rules
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Credit
Defining
M(N) n - tr Check Rules
no Management > Setup > Rules > Credit
Order
(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.
Defining Credit Check Rules
1. Enter a name for your credit check rule.

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
a
has
5. Select the conversion type to use when performing credit checking using your credit
)
rule.
c o m ฺ
ฺ
ail uide
6. Select the Check Item Categories check box for your credit rule if you wish to perform
m
credit checking for sales orders by Item Categories defined for Order Management.
g nt G
u @
d d yฺ tude
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.
a rre this S
8. Select the Use Pre-Calculated Exposure checkbox to determine the credit exposure for
e sw use
the customer. Run the Initialize Credit Summaries concurrent program to calculate the
h
a to
credit exposure after you have defined the Credit Checking Rule.
( m
di cens e
9. Select the Include External Credit Exposure check box to include external exposure
a
mm ble li
details imported into Order Management during the credit checking process.
U
ar fera
10. Select the Open Receivables Balance check box for your credit rule if you wish to
w
h e s ans
include open receivables balances.
Ma on-tr
11. Select the Include Uninvoiced Orders check box if you wish to include uninvoiced
n 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.
(Help) Oracle Manufacturing Applications > Oracle Order Management > Order Management
Setup> Defining Credit Check Rules

Practice - Defining Credit Check Rules
Overview
In this practice you will learn how to create a credit check rule in Oracle Order Management
Assumptions

) h as
• Use Order Management Super User, Vision Operations (USA) or comparable
m Super
o
a ilฺ uideฺ
c
Tasks @ gm nt G
d y ฺu tude
1. Create a Credit Check Rule.
r r ed is S
w a e th
s
he to us
a
(m nse
d i
a lice
m
m ble
r U
a fera
e s w n s
h r a
Ma on-t
n

Solution – Defining Credit Check Rules
Login
Create a Credit Check Rule
(N) Order Management > Setup > Credit > Define Credit Check Rules
a
has
• Rule: XX-Credit-Check-Rule
)
m ฺ
ฺ c o
• Credit Check Level: Sales order m ail uide
@ g nt G
• Credit Hold Level: Sales order
u
yฺ tude
d d
a r re this S
• Conversion Type: Corporate w
h e s use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

2. Click (T) Exposure.
3. Enable the following options (disable any other options that might be enabled by default):
• Pre-Calculated Exposure (the amount in open orders that a customer has based on the
credit check rule)
Note: You will need to run the Initialize Credit Summaries concurrent program if
you are using pre-calculated exposure
• Include Uninvoiced Orders
• Include Freight and Special Charges
• Include Tax
a
• Include Orders Currently On Hold
) has
c o m ฺ
• Include Returns ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
4. Save.

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt and G
Holds, Order u @Purge,
de
Exception
d d yฺ Management
t u
a rre this S
Setup
h e sw use
( m a to 7
Chapter
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
Holds, Order Purge, and Exception Management Setup

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Objectives
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Holds
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h
a n-t
Holds r a
MOracle
noOrder 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.

Seeded Holds
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Holds
Seeded
MSeeded n - tr
noholds 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 check rule evaluation fails on order values that are required to be checked for credit
worthiness and credit limits.
• 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.
• 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.
a
has
• Promotional Line: This hold is a promotional hold type that is automatically placed on
lines that exceed a soft modifier promotional limit. )
m ฺ
c o
• Promotional Order: This hold is a promotional hold type that is automatically placed on
ฺ
ail uide
orders that exceed a soft modifier promotional limit.
m
@ g nt G
u
yฺ tude
d d
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Automatic Holds
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-Holds
Automatic
M(N) tr
no Management > Setup > Orders > Holds
Order
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 source 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.

• Optionally, select the user responsibilities that have authorization to execute and dismiss
holds.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Generic Holds
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a Holds
Generic
M(N) n - tr
no Management > Setup > Orders > Holds
Order
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.

Hold Sources
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Hold
M(N)
Sources
no Management > Orders, Returns > Order Organizer
Order
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)

• 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 a
• Warehouse > Customer
) has
• Warehouse > Ship To Site
c o m ฺ
• Warehouse > Bill To Site ฺ
ail uide
• Sales Agreement Number > Ship To Site
m
g nt G
u @
d yฺ tude
• Sales Agreement Number > Bill To Site
d
rre this S
• Sales Agreement Number > Warehouse
a
h e sw use
• Sales Agreement Number > Ship To Site
a to
• Sales Agreement Line Number
( m
di cens e
a
You can apply your holds to be effective immediately and universally. An automatic hold that
mm ble li
has hold criteria defined can be released for all orders or individual orders.
U
w ar fera
h e s ans
Ma on-tr
n

Practice - Creating and Applying Holds
Overview
In this practice you will learn how to create and apply various types of holds:
• Order Administration Holds
• Scheduling Related
• Credit Check
Assumptions
s a
• a
)h
or test instance at your site on which to complete this practice. m
co deฺ
i l ฺ
g ma t Gui
• Replace XX with the number provided by your instructor y ฺ u@ d
or your e n
initials.
r e dd s Stu
• Use Order Management Super User, Vision
w arOperations
e t hi (USA) or comparable Super User
Order Management responsibility.es
a h to us
Tasks d i (m nse
m a lice
U mand release
1. Create, apply, b le a hold at the order level.
r
a fer a
sw aapply,
2.heCreate, n s and release a hold at the order line level.
M a n-t r
3. Ifn o are using Vision Operations as your default operating unit, you need to assign another
you
operating unit to your responsibility.

Solution - Creating and Applying Holds
Login
• UserName: your login
• Password: your password
2. Order Management Super User, Vision Operations (USA) responsibility is selected.

a
Create, Apply, and Release a Header Level Hold ) has
c o m ฺ
(N) Setup > Orders > Holds ฺ
ail uide
m
g nt G
u @
1. Name: XX-Book-Hold
• Type: Order Administration Hold d d yฺ tude
e S
• Workflow Item: OM Order Headerarr h i s
• Workflow Activity: Book Order
e s w se t
a h to u
2. Authorizations region:di (
m se
a c e n
m m Order
• Responsibility:
l e liManagement Super User, Vision Operations USA
U
ar ferab
• Authorized Action: Apply Hold
e w
s • Responsibility:
n s
h r a
Ma on•-Authorized
t Order Management Super User, Vision Operations USA
Action: Remove Hold
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
3. (N) Orders, Returns >d i Sales
Quick e
nsOrders
a
m e li c e
4. (B) ActionsU>m Apply b l Select XX-Book-Hold from the LOV to apply the hold on
Holds.
r
a order.
yourwcurrent er a
e s n s f
h -and r abook
Ma5. Save t
non
the order. The hold XX-Book-Hold will be applied to your order.

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
6. In the Process Messages window, h e sw(B) Continue.
click u se
( m a to
di (B)cActions e
ns > Release Holds. Provide a reason for releasing
a
7. To release the hold, select
li e
U mm(B)bRelease.
the hold and click
l e
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
Create, Apply, and Release a m
( a Level tHold
Line o
di cens e
a li
U mm Hold
8. Create a Line Level
l e
w f e rab
ar XX-Line-Hold
h e s Type:
Name:
a n s Administration Hold
Ma on-Workflow
t r Order
Item: OM Order Line
n Workflow Activity: Line Scheduling
Authorizations region:
Authorized Action: Apply Hold

Authorized Action: Remove Hold

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
9. (N) Orders, Returns > Quick
( m a Orders
Sales to
di cens e
a
mm ble li
10. Create a sales order.
U
w
11. Apply ather holdfeXX-Line-Hold
ra to the order. (B) Actions > Apply Holds.
e s
h -and n s
abook
Ma12. Save
n t r the order. If the line cannot be scheduled, the hold is applied to the line.
n o

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
13. Click (B) Continue to proceed. y ฺ u@ uden
r e dd s St
a r Holds.
14. To release the hold, select (B) Actions > Release
t h i Enter a reason for releasing the
w e
hold and click (B) Release.
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
Ma on-t
n

Create, Apply, and Release a Credit Check Hold
15. (N) Customers > Standard. The TCA Customers HTML page opens.
16. Select Customer Name: XX-SYNERGY; Customer Number: 6036
17. In the Accounts region, select the Customer and click (I) Details. The Customer
Information page opens. Click (T) Account Profile and select the Credit Check box.
18. Check the values for the Credit Rating and Credit Classification.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
19.nIn the Profile Amounts tab, ensure that the Credit Limit and Order Credit Limit are
specified for the currency that you use:

a
20. (N) Setup > Orders > Payment Terms
) has
o m
ฺ c
l Immediate.
21. Use the F11+Ctrl F11 function keys to search for the Payment Termicalled
a i d eฺ
Ensure that the Credit Check box is selected.
g m t Gu
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a fera
e s w n s
h r a
Ma on-t
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h
22. e s a acredit
Create n s check rule using (N) Setup > Credit > Define Credit Check Rule
Ma on-t r
n • Enter Rule Name: XX-Credit-Check-Rule
• Credit Check Level: Sales Order
• Credit Hold Level: Sales Order
• Conversion Type: Corporate

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
23. (N) Setup > Transaction Typesa> Define.to
d i (m nse
24. Select a transaction a
type thatc isedefaulted for the customer. For the customer XX-
m
m transaction l i
SYNERGY, the
r U a b le type is Standard.
e s wa nsfer
h a
Ma on-tr
n

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
m bCredit
25. In the Main tab,
U in the l e Check Rule region, enter your credit check rule XX-Credit-
r
a fera
Check-Rule.
e s w n s
h r a
Ma on-t
26. Create a sales order with the following information:
n • Customer: XX-SYNERGY (customer number: 6036)
• Warehouse: V1
• Payment Terms: Immediate
• Item: XX-ITEM1
• Qty: any quantity whose total amount exceeds the order credit limit specified for
the customer.
Note: In your previous practices you should have learnt how to create an item and a
customer. Refer to Module 4 (Practice XXXXXX) and Module 5 (Practice XXXXX)
to learn how to create an item and a customer.
27. Save and book your order. It should go on credit check hold as shown below:

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
28. You can release the hold bym
( a decreasing
either to the order total in the sales order or by
di limit e
s Customers page.
nthe
a
increasing the order credit
c ein
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Order and Quote Purge
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Order and
MOracle tr Purge
a n-Quote
noOrder 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.

Purge Sets
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
a n-tr
Purge
M(N)
Sets
no Management > Orders, Returns > Purge > Order Purge Selection
Order
(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.

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. a
• has
Define the following criteria (limit your selection to refine your purge):
)
• Order Number Low
c o m ฺ
• Order Number High ฺ
ail uide
• Order Type
m
g nt G
u @
• Order Category
d d yฺ tude
• Customer
a rre this S
• Order Date Low
h e sw use
• Order Date High
( m a to
di cens e
a
• Creation Date Low
mm ble li
• Creation Date High
U
• ar fera
Determine whether or not you want contract terms to be purged (if applicable).
w
h e s ans
Ma on-tr
n

Setting Up Exception Management
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
M(N)
Up tr
a n-Exception
Setting Management
no Management > Orders, Returns, Process Messages
Order
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

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.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Guided Demonstration – Setting up Exception Management
Setups for Exception Management
Note: Use Order Management Super User, Vision Operations (USA) or comparable Super User
Order Management responsibility.
1. Set the profile option OM: Generate Diagnostics for Error Activities to automatically run
the Diagnostics: OM Order Information concurrent program whenever there is an error in
the workflow activity.
Note: Oracle Support/Development require this during the bug resolution process.
s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
r e dd s St
w ar e thi
a hes to us
d i (m nse
m a lice
U m ble
r
a ferOM: a
e s
2. The w s
profile option
n Show Process Messages Flag is used to display the Open
h Messagetraboxmessage_exists_flag
Ma the
in the Sales Orders window. Set the value of the profile option to Yes to use
n -
no indicator . The checked value of this field indicates that at least
one message exists for the order.

s a
)h a
m
co deฺ
i l ฺ
g ma t Gui
y ฺ u@ uden
3. Set the value of the Lookup ONT_MESSAGE_STATUS
r e dd s toSCUSTOMIZE.
t
w ar e thi
hes to us
(N) Setup > QuickCodes.
a
(mSalesnsOrders.
4. (N) Orders, Returns > Quick
d i e Open an existing order and navigate to the
m a Actions
lines region. Click (B)
l i c e> View Open Messages (or right-mouse click menu) to
U m ble
view any messages. If any messages exist, they will be displayed in the Process Messages
window.a rIf there
e r
area no messages for that order, a message box indicating that there are
e w
nosopen messages
n f
s displays.
h r a
Ma5. Message
o n -t without error:
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
r r e i s S
6. Message with error: a
w se t h
e s
h to u
m a
a di ( cense
U mm ble li
w ar fera
h e s ans
Ma on-tr
n
7. You can use the Quick Sales Orders window to Retry Workflow Activities that have
errored out.

• Navigate to the Sales Orders window.
• Select the Header or Line for which you want to retry the activity.
• Click the right mouse button and select Retry Activities in Error option or
(B)Actions > Retry Activities in Error option.
• Select the Activity you want to retry.
8. You will get a message indicating that the activity completed successfully or not. For
error messages, you need to fix the errors and repeat all the above steps.
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

Summary
a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n

a
) has
c o m ฺ
ฺ
ail uide
m
g nt G
u @
d d yฺ tude
a rre this S
h e sw use
( m a to
di cens e
a
U mm ble li
w ar fera
h e s ans
Ma on-tr
n


Oracle R12 Student Guide PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle R12 Student Guide PDF

Uploaded by

Copyright:

Available Formats

s a

U.S. GOVERNMENT RIGHTS

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

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

noof Shipping Execution ....................................................................................................................9-1

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

• Thorough knowledge of navigation through the applications

• Working experience with Oracle Order Management

• There are no prerequisites for this course.

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Passwords DROP USER scott

Lowercase Syntax variables CREATE ROLE role

(ST) = Sub Tab

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

2. Under the General Ledger entry, expand Journals.

3. Under Journals, select Enter Journals. a

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Oracle Order Management Fundamentals Table of Contents

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management

Copyright © Oracle, 2007. All rights reserved.

Overview of Oracle Order Management