Fundamentals
y
m
e
d
a
D50091GC10
Edition 1.0
September 2007
D52994
a
r
O
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Author
Pratima Mahtani
Technical Contributors and Reviewers
Order Management QA Team, Karen Zawada, Rahul Sharma
This book was published using:
a
r
O
e
l
c
y
m
oracletutor
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
d
a
Table of Contents
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
Order Entities and Order Flows ....................................................................................................................2-1
Order Entities and Order Flows.....................................................................................................................2-3
Objectives ......................................................................................................................................................2-4
Order to Cash Lifecycle with Standard Items................................................................................................2-5
Practice - Practice - Order to Cash Cycle with Standard Items .................................................................2-18
Solution Order to Cash cycle with Standard Items .................................................................................2-19
Order to Cash Lifecycle with PTO Models and PTO Kits ............................................................................2-29
Practice - Practice - Order to Cash Cycle with PTO Kits ..........................................................................2-31
Solution Order to Cash Cycle with PTO Kits .........................................................................................2-32
Drop Shipments .............................................................................................................................................2-41
Drop Shipments Across Ledgers ...................................................................................................................2-43
Practice - Order to Cash Cycle with Customer Acceptance ......................................................................2-46
Solution Order to Cash Cycle with Customer Acceptance .....................................................................2-48
Back-to-Back Orders .....................................................................................................................................2-52
Guided Demonstration Creating Back to Back Orders ...........................................................................2-53
Sales Agreements ..........................................................................................................................................2-62
Negotiation Agreement..................................................................................................................................2-63
Approve Sales Agreement .............................................................................................................................2-64
Releases Against a Sales Agreement .............................................................................................................2-65
Practice - 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
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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
Overview of Pricing Concepts.......................................................................................................................8-8
Overview of the Pricing Engine ....................................................................................................................8-10
Overview of Pricing Security ........................................................................................................................8-11
Overview of Price Lists .................................................................................................................................8-12
Overview of Pricing Agreements ..................................................................................................................8-14
Overview of Formulas ...................................................................................................................................8-15
Overview of Qualifiers ..................................................................................................................................8-16
Overview of Modifiers ..................................................................................................................................8-17
Overview of Contexts and Attributes ............................................................................................................8-19
Overview of Freight and Special Charges Modifiers.....................................................................................8-20
Overview of Basic Versus Advanced Pricing................................................................................................8-21
Overview of Price Lists .................................................................................................................................8-22
Price List Information....................................................................................................................................8-24
Creating a Price List ......................................................................................................................................8-27
Price List Header ...........................................................................................................................................8-28
Price List Line ...............................................................................................................................................8-30
Secondary Price List......................................................................................................................................8-34
Practice - Creating a Price List ..................................................................................................................8-35
Solution - Creating a Price List..................................................................................................................8-37
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
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
a
r
O
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Preface
Profile
Before You Begin This Course
Prerequisites
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Related Publications
Oracle Publications
Title
Part Number
B28099-01
B25975-01
B31232-01
B31547-02
B31581-01
B31440-01
Additional Publications
Read-me files
Oracle Magazine
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
c
A
e
d
a
Typographic Conventions
Typographic Conventions in Text
Convention
Bold italic
Caps and
lowercase
Courier new,
case sensitive
(default is
lowercase)
Initial cap
Element
Glossary term (if
there is a glossary)
Buttons,
check boxes,
triggers,
windows
Code output,
directory names,
filenames,
passwords,
pathnames,
URLs,
user input,
usernames
Arrow
Brackets
Commas
Graphics labels
(unless the term is a
proper noun)
Emphasized words
and phrases,
titles of books and
courses,
variables
Interface elements
with long names
that have only
initial caps;
lesson and chapter
titles in crossreferences
SQL column
names, commands,
functions, schemas,
table names
Menu paths
Key names
Key sequences
Plus signs
Key combinations
Italic
Quotation
marks
Uppercase
e
l
c
Example
The algorithm inserts the new key.
Click the Executable button.
Select the Cant Delete Card check box.
Assign a When-Validate-Item trigger to the ORD block.
Open the Master Schedule window.
Code output: debug.set (I, 300);
Directory: bin (DOS), $FMHOME (UNIX)
Filename: Locate the init.ora file.
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects
URL: Go to http://www.oracle.com
User input: Enter 300
Username: Log on as scott
Customer address (but Oracle Payables)
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
a
r
O
Element
Oracle Forms
triggers
Column names,
table names
Example
When-Validate-Item
Passwords
SELECT last_name
FROM s_emp;
PL/SQL objects
Lowercase
italic
Uppercase
Syntax variables
e
d
a
c
A
1.
(N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary.
2.
3.
Notations:
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
e
l
c
(I) = Icon
a
r
O
(H) = Hyperlink
(ST) = Sub Tab
Copyright Oracle, 2007. All rights reserved.
y
m
In the navigation frame of the help system window, expand the General Ledger entry.
2.
3.
4.
Review the Enter Journals topic that appears in the document frame of the help system
window.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 1
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
accepts. Within e-Business Suite, you can obtain orders from the online store (iStore of CRM)
or Quoting and use them in Oracle Order Management.
Process Order API is used to receive any entered or imported orders. Process Order API is used
to perform operations like create, update, delete on all the objects (header, line, pricing entities)
of the sales orders window. When an order is captured, Process Order API performs tasks like
Attribute Level Security Check, Attribute Validation, Defaulting, Record Validation, Database
Write, Cross Record and Cross Entity logic to ensure data integrity and consistency.
Order Fulfillment
The Order Fulfillment process enables you to fulfill orders of various types, some of which are
Internal Orders, Back-to-Back Orders, Drop Shipments, Configure to Order etc.
The fulfillment activity is actually a seeded workflow activity (FULFILL_LINE) and it ensures
that the order lines are ready for completion. There are two activities which are considered
fulfillment method activities in the seeded OM workflows. For a standard shippable line the
fulfillment method activity is the shipping activity. For a return line the fulfillment method
activity is the receiving activity. You may define any activity as the fulfillment method activity
in a workflow process. The fulfillment activity must be between the fulfillment method activity
and the invoice interface activity in the respective workflows.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
profile option Personalize Self-Service Defn for the Personalize Page link to display on the
page.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Tasks
1.
2.
Ensure that the Order Management Super User Vision Operations USA responsibility has
the appropriate menu assigned to it.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
3.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
5.
Assign the following responsibilities to your user using (T) Direct Responsibilities:
Responsibility
Order Management Super User, Vision Operations
(USA)
Inventory, Vision Operations (USA)
Receivables Manager
System Administrator
Human Resources, Vision Enterprises
Purchasing Super User, Vision Operations
Revenue Management Super User, Vision Operations (USA)
Security Group
Standard
Standard
Standard
Standard
Standard
Standard
Standard
6.
(I) Save.
7.
Log out of the operations username and login again using your newly created account.
You will be prompted to change your password.
Once you have logged in again, select the System Administrator responsibility again
and navigate to (N) Security > Responsibility > Define.
9.
Query for the Order Management Super User Vision Operations USA responsibility
(F11 and Ctrl-F11).
y
m
e
d
a
10. Please ensure that the appropriate menu (shown below) ADS_OM_SUPERMENU is
assigned to the OM Super User responsibility.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Enable Diagnostics
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.
e
d
a
y
m
Tasks
c
A
1.
Login to the database with the login and password that you created in the previous practice.
2.
Choose the responsibility Order Management Super User, Vision Operations (USA).
3.
Create a folder at the header and line level using the Folder tool.
4.
Enable Diagnostics.
5.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
Choose Responsibility
2.
y
m
e
d
a
4.
5.
Place your cursor on any of the header fields and then select (M) Folder > New or (I)
Folder Tools > (I) New.
e
l
c
a
r
O
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
y
m
6.
e
d
a
Folder - a name for the header level folder, replacing XX with your initials.
Autoquery Never
Public 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
Verify the following: your new folder name, Others tab, Actions button should
be visible on the window
e
l
c
a
r
O
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Copyright Oracle, 2007. All rights reserved.
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.
Autoquery Never
Public selected
Line Tabs block select all the tabbed regions that you wish to see in the
window
Line Details (Regions) select all the regions that you wish to use in the
window (these are accessible by clicking on the
icon at the bottom right of
the window this expands to show the details of the selected region)
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
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
e
l
c
b. Type: Menu
a
r
O
c. Description: wf menu
d. Language: All
Copyright Oracle, 2007. All rights reserved.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
20. Close 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
Find Customer
e
l
c
Workflow Status
a
r
O
Special Menu #
SPECIAL1
SPECIAL2
Price Debug
SPECIAL3
AutoSchedule
SPECIAL4
Copyright Oracle, 2007. All rights reserved.
User Sets
SPECIAL5
Purge
SPECIAL6
SPECIAL7
Item Search
SPECIAL8
SPECIAL9
Debug
SPECIAL10
Apply Holds
SPECIAL11
Mass Change
SPECIAL12
Schedule
SPECIAL14
Audit
SPECIAL15
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 2
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
y
m
e
d
a
1.
Create an order.
2.
3.
4.
5.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
c
A
6. Save your work. The Status on the line should display as Entered.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
e
d
a
8. 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. Close the Workflow Status window to return to the Quick Sales Orders
window.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
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.
e
l
c
15. Click (B) Execute Now to pick release and pick confirm the order.
a
r
O
y
m
Ship Confirmation
e
d
a
c
A
17. The Query Manager window opens. Enter your order number in the fields From Order
Number and To Order Number. Select no value in the Line Status field.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
19. The Shipping Transactions window opens to display your order details with the statuses.
e
l
c
a
r
O
20. Click on the Delivery, Path by Stop and Path by Trip tabs. The delivery and trip should
have been autocreated. If not, use the Actions LOV to Auto-Create Deliveries, AutoCreate Trip.
y
m
21. Navigate to the (T) Delivery tab. Click (B) Ship Confirm.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
d
a
c
A
a
r
O
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.
Order Header Main Tab
Line Status
Booked
Shipped
Additional Line
Information
Delivery Status =
Closed
Picked Status = Shipped
Trip Status = Closed
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Parameters window:
Item Type: OM Order Line
Process Deferred: Yes
Process Timeout: No
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
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.
e
l
c
a
r
O
29. Return to the Quick Sales Orders window. Query for your order by using the F11 key.
Enter your order number and use the Ctrl-F11 keys to get the query results. Though your
order status still displays as Booked, the line status should show up as Closed.
y
m
e
d
a
Run AutoInvoice
c
A
30. Navigate to (N) Receivables > Interfaces > AutoInvoice. Click (B) Submit a New
Request and then select a single request when prompted. The concurrent programs
window opens to enable you to run AutoInvoice.
31. In the Name field select the AutoInvoice Master Program and enter the following
parameters when 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
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
e
d
a
c
A
32. Click Ok and return to the main window. Click Submit to run AutoInvoice. You will be
given a request ID, which you can use to track the status of your request. It should
complete as normal.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
33. (N) Quick Order Organizer. Enter your order number and click (B) Find. When your
order appears in the result list, click (B) Actions > Additional Order Information > (T)
Invoices / Credit Memos.
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
34. Click (B) Invoice Details to view the invoice that has been autocreated from your order.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
y
m
Tasks
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Note: The Template will default the item attributes and statuses. Enter the following elements
of the PTO model to complete the configuration:
e
l
c
a
r
O
Item Template
Item Type
XX-PTO-SMCMODEL
PTO Model
PTO
XX-PTO-Main-OptionItem
Finished Good
Standard
XX-PTO-MainIncluded-Item
Finished Good
Standard
XX-PTO-Class-1
PTO
XX-PTO-Class1Option-Item
Finished Good
Standard
XX-PTO-Class1Included-Item
Finished Good
Standard
XX-PTO-Class-11
PTO
XX-PTO-Class11Option-Item
Finished Good
Standard
XX-PTO-Class11Included-Item
Finished Good
XX-PTO-Class-2
PTO
XX-PTO-Class2Option-Item
Finished Good
Standard
XX-PTO-Class2Included-Item
Finished Good
Standard
XX-PTO-Class-3
PTO
XX-PTO-Class3Option-Item
Finished Good
Standard
Finished Good
Standard
e
l
c
a
r
O
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
XX-PTO-Class3Included-Item
y
m
e
d
a
c
A
Standard
Note: Please check the Returnable flag in the Order Management tab in order to be able
to create returns for these items.
Copyright Oracle, 2007. All rights reserved.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
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.
e
l
c
12. Click (T) Order Management to enter if the item is optional for the bill or not. Usually
included items are not optional.
a
r
O
13. The Quantity (Minimum) should be less than or equal to the Quantity in the Main tab.
y
m
e
d
a
14. Run the (M) Tools > Create Common Bill concurrent program. Select All Organizations
button so that the Bill of Material is available across all inventory organizations.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
15. Use the (M) View > Requests option to view the completion of the Bill of Material.
16. Repeat the same steps for creating a Bill of Material in the following sequence (refer to
the table PTO SMC Model above):
c
A
XX-PTO-Class-1 with the Class1 option item and included item and Class 11
XX-PTO-SMC-Model
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
17. Use the Miscellaneous Receipts window to create quantities for the items. You need to
enter quantities only for finished goods.
e
l
c
a
r
O
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
Quantity = 10
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
21. Save and exit once you have completed entering the quantity for the items.
e
l
c
a
r
O
24. In the Order Lines region, enter the top model XX-PTO-SMC-MODEL in the Ordered
Items field. Enter a Quantity of 10.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
25. 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.
e
l
c
a
r
O
y
m
26. Click (B) Finish. Configurator processes the classes that you have selected to display on
the sales order window. You will get a message indicating that the Configurator
processing is in process. Once the processing is complete, the sales orders window shows
the following PTO Kit information:
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Pick Release
Ship Confirm
AutoInvoice
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Drop Shipments
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Drop Shipments
Drop shipment is a method of fulfilling sales orders by selling products without the order taker
handling, stocking, or delivering them. The seller buys a product and the supplier ships the
product directly to the sellers customer. Drop shipments are used due to the following reasons:
Customer requires an item that is not normally stocked
Customer requires a large quantity of the item which is not available with you
It is more economical when the supplier ships directly to the customer
In the diagram of the drop ship cycle, the seller receives a sales order from the customer and
sends a purchase order to the supplier. The supplier ships directly to the customer. The seller
receives an invoice from the supplier and sends an invoice to the customer.
There are three types of drop shipments:
Full Drop Shipment: The seller sends the purchase order to the supplier for the full
quantity that the customer had ordered
Normal Shipments and Partial Drop Shipment: If the seller has only part of the quantity
available for shipping to the customer, then that quantity is shipped. The user looks at the
availability for the order qty by using the ATP check and if the whole qty is not available
e
l
c
a
r
O
the balance qty is fulfilled using the dropship process. A purchase order is created for the
remaining quantity which the seller was not able to fulfill.
Normal Shipments and Full Drop Shipment: The seller ships some goods from inventory
to the customer, and the other goods are always shipped from an external source (supplier)
Drop shipments are created as sales orders in Order Management, indicated as drop shipments
when their Source Type is entered as External. The Purchase Release concurrent program or
workflow in Order Management creates rows in the Requisition Import tables in the
Purchasing module. Purchasings Requisition Import process creates requisitions. After the
requisition has been approved, it generates a purchase order. The Source Type is entered as
Supplier. The purchase order is sent to the supplier who then arranges for the delivery of the
items to your customer. The supplier notifies you that the items have been shipped to the
customer, via an invoice, EDI document, or an Advance Shipment Notice (ASN). In turn you
generate an invoice to be sent to the customer. Additionally when you receive confirmation of
a drop shipment or the suppliers invoice, you create a receipt for it. This creates inbound and
outbound material transactions in your system for accounting purposes.
When you receive confirmation of a drop shipment or the suppliers invoice, you create a
receipt for it. This creates inbound and outbound material transactions in your system for
accounting purposes. You can now generate an invoice to be sent to the customer.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
y
m
Create an order.
7.
8.
9.
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Sales Orders: Update Acceptance Attributes This allows for updating the
acceptance attributes of Acceptance Name and Acceptance Expire days.
e
l
c
a
r
O
3. Change your responsibility to Revenue Management Super User Vision Operations USA.
4. (N) Revenue Contingencies > Contingency Definition
Copyright Oracle, 2007. All rights reserved.
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:
Days Added to Event Attribute: any number that you want the removal event to
occur
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
Condition: IN
Case Sensitive: No
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
12. Enable the Acceptance-related fields using folder functionality on the sales orders line in
the Others tab:
Acceptance Date
Acceptance Type
Accepted By
Accepted Qty
Acceptance Description
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
y
m
e
d
a
c
A
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.
e
l
c
a
r
O
Item: AS54888
Qty: 2
y
m
e
d
a
c
A
18. Pick Release the order using (N) Shipping > Release Sales Orders > Release Sales
Orders.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
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.
e
l
c
a
r
O
Back-to-Back Orders
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Back-to-Back Orders
The process of creating Back-to-Back orders involves the close linking of sales orders and
purchase orders. Back-to-Back ordering is used as a replenish to order process for items that
you stock in inventory.
To create and use Back-to-Back orders, you need to ensure that the purchasing document
creation is automated, that you always have the latest status of the lines progress, and that you
can peg (or hard reserve) quantities against the order, so that the items are not allocated to
another customer.
The Auto Create Requisition process creates the requisition for the purchase order from the
sales order in Purchasing. The requisition must be identified as CTO. The purchase order is
then created automatically from the requisition and sent to the supplier. After the supplier
receives the purchase order, the items are recorded in inventory and a reservation is
automatically made against the sales order line. The sales order can then be picked, shipped,
and invoiced.
e
l
c
a
r
O
y
m
(T) Order Management Select Customer Ordered box and Assemble to Order
box
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
5. The profile option MRP: Default Sourcing Assignment Set should be set to Null or any
%Supplier% value.
c
A
6. Add the item XX-FG2 to the Corporate pricelist. (N) Pricing > Price List Setup.
Create an order
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
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
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Note: 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.
e
l
c
a
r
O
13. When you progress the order ((B) Actions > Progress Order), the line status is PO
Requisition Requested.
e
d
a
y
m
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
After the concurrent request is processed successfully, the Sales Orders line shows External Req
Open.
e
l
c
a
r
O
16. Clear all fields and enter CTO in the Import Source field. The Requisition Headers Summary
window displays.
y
m
e
d
a
c
A
17. The Approval Status should be Approved. Verify that the line information corresponds to
that in the sales orders window.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
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.
e
l
c
a
r
O
y
m
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
e
d
a
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
28. Note: The line status on the Sales Order is Awaiting Shipping.
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
31. Check the on-hand quantity in the Quick Sales Orders window, it should be 21.
32. Pick Release the order.
e
l
c
a
r
O
Sales Agreements
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Sales Agreements
A Sales Agreement is a suppliers representation of an agreement with a customer for the
supplier to sell and the customer to buy goods or services. Usually the agreement is fulfilled by
executing multiple sales transactions over a period of time. The SA Header includes the
following:
The information that other order headers include (customer, ship to, bill to, version)
Effective dates of the SA
Payment and freight terms between the customer and supplier
Sales Agreement minimum and maximum value
Control flag to determine whether you can exceed the maximum value
Pricing Information like standard price lists, SA specific price lists
The SA line information includes the following:
Items
The minimum/maximum quantity agreed by the customer and supplier
Price including choice of price list
Effective dates
e
l
c
a
r
O
Negotiation Agreement
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Negotiation Agreement
A Sales Agreement can start with either the Negotiation phase or the Fulfillment phase. If the
Sales Agreement starts with the Negotiation phase, it will first follow the Negotiation flow and
then go through the Fulfillment phase.
The Sales Agreement is specified for a given time period, indicated by the Effectivity dates on
the agreement. The product/item categories are also entered in the Sales Agreement. You can
specify the minimum and maximum quantities for the booked sales order. Additionally you can
specify the minimum and maximum amount (in value) for the booked sales order. You can set
up a basic price list and enter the price for the Sales Agreement, and also set up the payment
and freight terms for the Sales Agreement.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
incorporate these enforceable terms. Defaulting Rules need to be modified to use the SA as a
source of information to default information from the SA onto the release.
When you create an order (release) against the Sales Agreement, the system checks the
quantities and amounts entered in the lines. It then updates the quantities and amounts of the
SA line accordingly. Thus the Sales Agreement shows summary level information about the
releases against the sales agreement. The following fields are used for accumulating or
displaying the quantities and amounts:
Released Quantity
Fulfilled Quantity
Remaining Unfulfilled Quantity
Fulfilled Amount
Remaining Unfulfilled Amount
Returned Quantity
Released Amount
Returned Amount
The accumulation of the quantities and amounts occurs when the release line data is entered or
updated. When the release line is saved, the released quantity is updated at the Sales
Agreement header and line. When the release line is fulfilled, the fulfilled quantity on the SA
line is incremented. When a release line is returned and the item is received, the Returned
Quantity is incremented. The Remaining Unfulfilled Quantity may be stored or may be
calculated for display purposes. It should always equal the Ordered Quantity the Fulfilled
Quantity + the Returned Quantity.
You can terminate a Sales Agreement if it is in the fulfillment phase and if it has no open
release lines. Also when the Expiration Date is reached or when the maximum agreed quantity
or amount is reached, the Sales Agreement can be terminated. The Termination date is
defaulted to the system date. Once you terminate a Sales Agreement, you cannot reopen it and
a workflow notification is sent to the appropriate persons, informing them that the Sales
Agreement is terminated.
When a Sales Agreement is terminated and eligible for closure, it must be closed manually.
You cannot manually close an active Sales Agreement; it must be terminated, expired, or lost.
You can reopen an expired Sales Agreement.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
y
m
e
d
a
Tasks
Create a Sales Agreement (SA)
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
1. Business World (1608) has contacted you to place a long-term order for item AS54999. They
wish this to be supplied every week in quantities of 15 for a period of 30 weeks.
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.
e
l
c
a
r
O
2.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
3.
c
A
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
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Note: 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
e
l
c
a
r
O
7.
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.
Create Release against SA
13. (N) Blanket Agreements > Sales Agreement Organizer.
14. In the Find Blanket window that opens, enter the Blanket Number that you wrote in Step 9
and then click (B) Find.
y
m
15. The Blankets Summary window displays your SA. Click (B) Create Releases to create a
sales order against the SA. This will open the Sales Orders window, defaulting most of the
information relevant to the SA.
e
d
a
c
A
Note: Alternatively, you can create a new sales order using the (N) Orders, Returns > Sales
Orders option and refer to the SA in the order header.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
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.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Sales Orders: Update Acceptance Attributes This allows for updating the
acceptance attributes of Acceptance Name and Acceptance Expire days.
e
l
c
a
r
O
23. Change your responsibility to Revenue Management Super User Vision Operations USA.
24. (N) Revenue Contingencies > Contingency Definition
Copyright Oracle, 2007. All rights reserved.
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:
Days Added to Event Attribute: any number that you want the removal event to
occur
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
Condition: IN
Case Sensitive: No
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
32. Enable the Acceptance-related fields using folder functionality on the sales orders line in
the Others tab:
Acceptance Date
Acceptance Type
Accepted By
Accepted Qty
Acceptance Description
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
y
m
e
d
a
c
A
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.
e
l
c
a
r
O
Item: AS54888
Qty: 2
y
m
e
d
a
c
A
38. Pick Release the order using (N) Shipping > Release Sales Orders > Release Sales
Orders.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
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.
e
l
c
a
r
O
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 3
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
ledgers and a default legal context. Information is secured by operating unit for these
applications using responsibilities. Each user can access, process, and report on data only for
the operating units assigned to the MO: Operating Unit or MO: Security Profile profile option.
The MO: Operating Unit profile option only provides access to one operating unit. The MO:
Security Profile provides access to multiple operating units from a single responsibility.
Inventory Organization: An organization for which you track inventory transactions and
balances, and/or an organization that manufactures or distributes products. Examples include
(but are not limited to) manufacturing plants, warehouses, distribution centers, and sales
offices. The following applications secure information by inventory organization: Oracle
Inventory, Bills of Material, Engineering, Work in Process, Master Scheduling/MRP, Capacity,
and Purchasing receiving functions. To run any of these applications, you must choose an
organization that has been classified as an inventory organization.
Subinventory: Subinventories are unique physical or logical separations of material inventory,
such as raw inventory, finished goods, or defective material. All material within an
organization is held in a subinventory therefore, you must define at least one subinventory.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
After entering other information in the window, if you change the operating unit, a message is
displayed indicating that all the fields will be cleared if the operating unit is changed.
You can query in these windows using operating unit as one of the search criteria. If the
operating unit is specified as one of the search criteria, the search results will display only that
data which is from the specified operating unit. If no operating unit is specified, then the search
results will retrieve all the relevant data from all the operating units that the responsibility with
which you logged in has access to.
The Operating Unit parameter is optional in Process Order Public API. You can call the
Process Order Public API, Get Order API and Lock Order API for any of the Operating Units
that you have access to, by specifying an Operating Unit value as a parameter.
For batch processes like Order Import or High Volume Order Import, EDI/XML, the interface
tables also have an Operating Unit field. If no value is specified in the fields, then Order
Import/High Volume Order Import will attempt to process those records for the default
operating unit. In these concurrent programs (Order Import or High Volume Order Import) you
can also set the value of the hidden parameter Process Orders with no Org Specified as
required.
Oracle Order Management concurrent requests are single-org, multi-org or global. For singleorg requests, the Operating Unit parameter is a required field and is populated with the default
operating unit. If you need to run the request for multiple orgs, leave the optional Operating
Unit parameters field blank. Some concurrent programs are classified as global, you can run
them across all operating units. In such programs, the Operating Unit parameter field is
disabled. Similarly, reports can be run for a single org or globally (across operating units).
Defaulting of the operating unit value takes place in the following manner: When MOAC is
enabled, the value of the operating unit for the MO: Security profile option is defaulted based
on the system profile option MO: Default Operating Unit. When MOAC is not enabled, the
value of the operating unit is the default for MO: Operating Unit profile option. For more
details on MOAC in Oracle Order Management, please refer to the Oracle Order Management
Users Guide and Oracle Order Management Implementation Manual.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Setting Up MOAC
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Setting up MOAC
There are various operating unit security scenarios that can exist in an enterprise:
There is only one Operating Unit.
There are multiple Operating Units, but users have access to only one Operating Unit.
There are multiple Operating Units, and users have access to some of the Operating Units.
There are multiple Operating Units, and users have access to all Operating Units.
1. Define Organizations and Relationships: Use the HR responsibility to create organizations
(N) HRMS Management > Work Structures > Organization > Description.
2. Assign Responsibilities: Use the System Administrator responsibility to assign
responsibilities to your user (N) Security > Users > Define.
3. Define Organization Hierarchy (optional): Use the HR responsibility to create a hierarchy
for the organizations that you have created. In addition to a primary reporting hierarchy
used in HR, you can define multiple hierarchies for matrix management, reporting, and for
security.
e
l
c
a
r
O
4. Define Security Profile: Use the HR responsibility to define a security profile (N) HRMS
Management > Security > Profile. You can either define security profiles based on an
organization hierarchy or a list of organizations.
5. Run Security List Maintenance concurrent request: This concurrent program builds a list of
operating units that are associated with the security profile. The list is available so that it
can be used and validated by other module APIs.
6. Set the Security Profile option for each Responsibility: Once the security profiles are
created, you can assign the values to the MO: Security Profile option at the responsibility
level. Use the System Administrator responsibility for this (N) Profile > System.
7. Setup a default operating unit: Use the profile option MO: Default Operating Unit to
default the operating unit in various windows. You can set the profile option at the
responsibility or user level.
8. Run the Setup Validation Report: Use the System Administrator responsibility to check for
any setup-related issues that might have occurred during MOAC setup. The report
parameters are:
Active Responsibilities Only: Select Yes or No to validate only the active
responsibilities on the report. The default value is Yes.
Correct Customer Attributes: Select Yes or No to correct the customer attributes. If
you choose Yes, the report deletes the operating unit-specific data from the
Customer records. The default value is No.
Correct Supplier Attributes: Select Yes or No to correct the supplier attributes. If you
choose Yes, the report deletes the operating unit-specific data from the supplier
records. The default value is No.
For more information on setting up MOAC, please refer to the Oracle Applications Multiple
Organizations Implementation Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
e
d
a
y
m
e
d
a
3. (B) OK
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
5. Click (B) New in the Find window and in the Organizations window, enter the location
(XX-OrgLocation) that you created in the previous steps.
e
l
c
a
r
O
y
m
e
d
a
Enter a Contact
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
o Ship-To Site
o Bill-To Site
o Receiving Site
o Internal Site
o Office Site
7. (M) Save.
e
l
c
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:
a
r
O
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
blank and enter the effective dates for the org.
Org Name
Location
Internal or
External
Organization
Classification
XX-TOP
XX-OrgLocation
Internal
GRE/Legal
Entity
XX-OU1
XX-OU1-Location
Internal
Operating Unit
XX-OU2
XX-OU2-Location
Internal
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
XX-InvOrg1
XX-InvOrg1Location
Internal
XX-InvOrg2
XX-InvOrg1Location
Internal
e
l
c
a
r
O
y
m
e
d
a
c
A
Operating Unit
Inventory
Organization
Inventory
Organization
12. When you save your work, you will be prompted with a flexfield screen to display more
information. Accept all defaults and enter USA for Legislation and USD for Currency.
e
d
a
13. (N) > HRMS Manager > Work Structures > Organization > Hierarchy
14. Enter a hierarchy for your organization structure.
15. In the Name field enter a Name for your hierarchy.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
16. Enter a Version Number and Start Date for the new hierarchy.
y
m
c
A
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.
e
l
c
a
r
O
y
m
e
d
a
18. In the Subordinates sub-region, enter the operating units and click the Down arrow key to
enter a subordinate (Inventory Org) for each operating unit.
19. Save your work and exit the window.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
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.
e
l
c
a
r
O
y
m
e
d
a
27. Run the Security List Maintenance concurrent program. (M) View > Requests > Security
List Maintenance with the following parameters:
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Generate Lists For: All Security Profiles or One Named Security Profile
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
30. When you have created the security profile, you can assign the value to the MO: Security
Profile option at the responsibility level. You can select the same security profile for
multiple responsibilities.
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 4
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objective
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Overview
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Overview
Oracle Inventory treats many different types of things as inventory. Inventory can be:
Finished goods that you sell to customers
Services that you sell to customers
Spare parts for maintenance
Raw materials for manufacturing processes
Inventory you purchase from a supplier on consignment
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Inventory Organizations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Inventory Organizations
An inventory organization is a facility where you store and transact items. 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.
e
l
c
a
r
O
Setting Up Locations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Setting Up Locations
Locations define information that describe the physical locations of employees and
organizations. Locations are shared between Oracle Inventory, Oracle Purchasing, Oracle
Human Resource Management Systems, Oracle Order Management, and Oracle Shipping
Execution. Locations flagged as global locations are available to all business groups. You can
associate each organization with only one location; however, you can associate more than one
organization with the same location.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
2.
3.
4.
(B) Open.
5.
6.
7.
8.
y
m
e
d
a
Verifying Subinventories
9.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
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.
Tasks
If necessary, change your Organization to Seattle (M1).
y
m
Create four subinventories for your team. Create one subinventory for your finished goods (FGI)
stock, a Main Stores (MAIN) subinventory, a Raw Materials (RM) subinventory, and Low Value
(LV) items subinventory. Your Low Value subinventory must be a non-tracked subinventory.
Use the following naming convention to differentiate your team from other teams (XXFGI)
where the pound sign represents your team number.
After completing the lab, answer the following questions.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
1.
2.
e
l
c
a
r
O
e
d
a
2.
Select OK
3.
(B) New
Name:
Description:
Status:
Type:
Locator Control:
XXFGI
Finished Goods Inventory
Active
Storage
Item Level
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
4.
5.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
XXMain
Main Stores
Storage
Active
Dynamic Entry
a
r
O
c
A
y
m
e
d
a
6.
7.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
XXRM
Raw Materials
Active
Storage
None
a
r
O
c
A
y
m
e
d
a
c
A
8.
9.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
12. Does a subinventory called XXFGI exist in M2 Boston Manufacturing? No, you created
your subinventories in M1 Seattle Manufacturing.
13. (N) Change Organization.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
For more information see Interorganization Shipping Networks, Oracle Inventory Users
Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Shipping Method
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Shipping Method
Shipping methods are the way you ship material. When you create a shipping method, you
must enable it before you can use it in a shipping network. If you disable a shipping method
you cannot use it in a shipping network.
e
l
c
a
r
O
Units of Measure
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Units of Measure
You define units of measure for tracking, moving, storing, and counting items.
Primary Unit of Measure
When you define an item you establish a primary unit of measure. The system tracks on-hand
quantity and calculates transactions based on the primary unit of measure.
Secondary Unit of Measure
You can optionally establish a secondary unit of measure (dual unit of measure control) for an
item. If an item is under dual unit of measure control, then the system tracks on-hand quantity
based on both the primary and secondary units of measure. Secondary unit of measure can be
used for cases where you need to track in two units of measure and there is no constant
conversion between the two unit of measures (UOMs). For example, chickens can be tracked
in pounds and eaches.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
2.
3.
4.
5.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
2.
3.
4.
5.
6.
7.
8.
9.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
2.
3.
Name
UOM
Description
Class
XX-Centimeter
XXC
XX Centimeter
XX-Metric
XX-Kilometer
XXK
XX Kilometer
XX-Metric
4.
5.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Tasks
y
m
e
d
a
Define the unit of measure class, Quantity Class with the base unit of measure
Each.
Use your team number (XX) to uniquely identify your unit of measure class.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Define the following units of measure for your class. (Use your team number
(XX) to uniquely identify your units of measure.)
Dozen
Gross
Case
Use your team number to uniquely identify your class from the other teams in the
classroom.
e
l
c
a
r
O
2.
3.
4.
XX-QTY
XX-Quantity Class
XX-Each
XXE
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
6.
c
A
7.
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
8.
9.
c
A
e
l
c
a
r
O
12. Enter the unit of measure conversion information according to the following table:
Unit
XX-Dozen
Class
Conversion
Base Unit
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
What is an Item?
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
What is an Item?
An item is a part or service you:
Purchase
Sell
Plan
Manufacture
Stock
Distribute
Prototype
Items can also be containers for items as well as components you build into other items.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
Defining Items
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Defining Items
Define only the information you need to maintain the item. You cannot define an item at the
organization level. Oracle Inventory automatically switches to the Master Item window when
you define a new item.
e
l
c
a
r
O
Defining Items
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Item Attributes
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Item Attributes
Item attributes are the collection of information about an item.
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
converts the quantity to the second unit of measure and displays both quantities. You
can change the quantity in the secondary unit of measure, without changing the
quantity in the primary unit of measure.
- No Default: The system stores inventory in both the primary and secondary units of
measure. Use this option when the default conversion between the two units of
measure is usually not the same. The system does not automatically display in the
secondary unit of measure when you specify the quantity for the primary unit of
measure. You manually enter the quantity of the secondary unit of measure before
you process a transaction. The secondary quantity can fluctuate from the default
conversion by the factors that you specify in the Deviation + and Deviation attributes.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
For items you do not ship, you may still want to enable OE Transactable if you use the items in
forecasting or planning. The system issues a warning if you change the value of this attribute
when open sales order lines exist for the item. You cannot disable this attribute if demand
exists.
Pick Components: You use this item attribute to indicate whether an item has a bill of
material with options, classes, or included items picked from finished goods inventory. You
must enable this item attribute for pick-to-order items. You must disable this item attribute for
assemble-to-order items and items without a bill of material.
Ship Model Complete: You use this item attribute to indicate whether any configuration
derived from this model can ship only when all required quantities of all configuration
components (options or included items) are available. If you enable this attribute, then the Pick
Components attribute and the profile option OE: Reservations must be Yes; and the BOM
Item Type attribute can be Model or Standard.
Returnable: You use this item attribute to indicate whether customers can return an item. If an
item is returnable, you can enter it on the Returns window in Oracle Order Management. Order
Management uses this item attribute with the item attributes Stockable and Transactable to
determine which authorized returned items you can physically receive into inventory.
RMA Inspection Required: You use this item attribute to indicate whether to require an
inspection on returned items.
Financing Allowed: You use this item attribute to indicate if a customer can finance an item.
Shipping Subinventory: You this item attribute to determine the default subinventory for
shipping.
Default Shipping Organization: This is the primary shipping organization for the item. This
organization appears on the Enter Orders window if the item is the source attribute of the
warehouse object in the standard value rule set for the order. This organization appears on the
Enter Returns window if a receiving warehouse is not defined on the customer or order type.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Validation
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Validation
Oracle Order Management derives the value of item attributes from two different sources: the
item validation organization and the shipping organization. Oracle Order Management uses
item attributes internally or on the sales order line. It categorizes item attributes as only source
and default source.
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
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
- 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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Status
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Status
You can use statuses to provide default values for certain item attributes to control the
functionality of an item. The Item Status attribute has a defined set of yes or no values for the
status attributes. You apply the values to the status attributes when you choose an item status
code when you define an item. For example, in the beginning of a product development cycle
you set the Item Status attribute to Prototype with all of the status attributes defaulted to yes
except for Customer Orders Enabled. When the item is ready, you change the Item Status
attribute to Active to enable all item functions.
You can assign one or more pending statuses for an item, to be implemented on future dates.
These statuses become effective on their assigned effective dates. You can view the status
history of an item if needed.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Control Levels
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Control Levels
Master-Level Control
An attribute you maintain at the master level has identical values across all organizations that
use the item.
Organization-Level Control
An attribute you maintain at the organization level may have different values for each
organization that uses it.
Attribute Control
Some attributes can be maintained at only the master level or the organizational Level. Units of
measure are controlled at the master level. If you are using multiple organizations, then you
should maintain min-max planning at the organization level.
Technical Note
Master-Level Control
For example, suppose you want to ensure that items defined in two organizations are
transactable at the same time in both organizations. If you make the item not transactable in
one organization, you want the same item to become not transactable in the other organization.
e
l
c
a
r
O
Organization-Level Control
Suppose only one of the two organizations in your Oracle Inventory implementation performs
manufacturing operations, while the other organization is strictly a distribution warehouse.
For a finished good item used in both organizations, you would want the flexibility to select the
Build in WIP status attribute check box in the manufacturing organization, and clear the Build
in WIP status attribute check box in the distribution organization.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
2.
3.
4.
5.
Click Apply.
6.
Click Done.
7.
8.
9.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Tasks
Create a Standard Customer
1. Login using the following username and password:
User: mfg
Password: welcome
2. Set up a Customer with the required defaults to process Sales Orders.
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
Bill To
a
r
O
5.
Ship To
Location
Bill To Primary
Accounts Payable
Blank
Selected
Selected
y
m
6.
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)
Payment Terms: 30 Net
Salesperson: Abbott, Rachel
9.
y
m
Create Items
Use the finished goods template to create five items.
XX-ItemXX
XX-Pager
XX-Palm Pilot
XX-Phone
XX-Phone Card
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
d
a
c
A
Note: Use the following naming convention for your items where XX represents either your
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
e
l
c
a
r
O
2.
3.
4.
5.
(B) Apply.
6.
(B) Done
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
7.
8.
9.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
e
d
a
y
m
e
d
a
c
A
11. Repeat steps 2-10 to create the following items: XX-Pager, XX-Palm Pilot, XX-Phone, and
XX-Phone Card.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
12. When you are finished creating the items, save your work and close the window.
Processing Miscellaneous Receipt Transactions
You can use the miscellaneous receipt window to receive material receive material in to
inventory.
13. Navigate to the Miscellaneous Transaction window.
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.
e
l
c
a
r
O
y
m
Item
XX-Pager
XX-Palm Pilot
XX-Phone
XX-Phone Card
e
l
c
Subinventory
FGI
UOM
Ea
Quantity
10000
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
FGI
Ea
10000
FGI
Ea
10000
FGI
Ea
10000
a
r
O
c
A
e
d
a
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Item Relationships
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Item Relationships
You can define relationships between items. This allows you to search for items through these
relationships. Except in Oracle Purchasing, these relationships are for inquiry and reporting
purposes only. For example, you can create an item relationship for substitute items or items
for which you can up-sell.
e
l
c
a
r
O
Customer Items
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Customer Items
A customer item is an alternate name assigned to an item that is specific to a customer site.
You use the Customer Item window to define customer items. You can also create cross
references between customer items and internal system item numbers.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Available to Promise
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Available to Promise
Available to Promise (ATP) represents the quantity available for sale at any given period. The
basic formula for ATP is ATP quantity = on-hand quantity + supply - demand shortage.
Oracle Inventory enables you to define different rules that govern what is considered supply
and demand. 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.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
2.
3.
4.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
5.
6.
e
l
c
ATP_Backward
ATP Backward consumption
Selected
10
User-defined time fence
User Defined
a
r
O
y
m
c
A
e
d
a
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Implementation Considerations
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Implementation Considerations
You should set all costing attributes at the organizational level because costing is most
commonly done at organizational level. 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
e
l
c
a
r
O
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 5
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Note: Order Management operates at the account level only, that is, party information is not
displayed in the user interface. Further, party identification is not entered through any
windows. Parties are created in the background when accounts are saved.
Customer account sites
Party sites used in the context of customer accounts for specific purposes, or uses, for example
ship-to and bill-to account sites.
Locations
Geospatial points, usually defined by an address.
Contacts
People who have a contact or employment relationship with an organization or person.
Contact points
Means of contact, for example, phone and e-mail address.
TCA also includes conceptual functionality that helps you manage and understand your trading
community. For example, you can use relationships to model the roles that parties play with
respect to one another, and classifications to classify entities.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1.
y
m
Deliver to address: 487 Beverly, San Mateo County, Palo Alto, California, 94301
e
l
c
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
5. Account Type: External. Leave all other fields, in the Account Information region, blank.
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
11. Postal Code: 60610. Leave all other fields, in the Account Site Address region, blank.
e
l
c
a
r
O
12. In the Business Purpose region, set Purpose to Bill To and check the Primary check box.
13. (B) Apply.
14. (B) Create Site.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
23. In the Business Purpose region, set Purpose to Deliver To and leave the Primary check box
unchecked.
24. (B) Apply.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
- Freight: The freight account controls the account in your general ledger to which you
post your freight amounts. You can use constant, customer bill-to site, salesperson,
transaction type, and standard item values to specify your freight account.
- Receivable: AutoAccounting uses this value if you derive the Receivable account
from the transaction bill-to site.
- Remitted Bills Receivable: AutoAccounting uses this value if you derive the
Remitted Bills Receivable account from the transaction drawee site. You can enter a
value in this field only if the business purpose for this address is Drawee.
- Revenue: The revenue account controls the account in your general ledger to which
you post your revenue amounts. You can use transaction types, customer bill-to sites,
standard items, salespeople, and constant values to specify your revenue account.
- Tax: The tax account controls the account in your general ledger to which you post
your tax amounts. You can use information from your tax codes, customer bill-to site,
salesperson, transaction type, standard item, and constant values to specify your tax
account.
- Unbilled Receivable: Receivables uses the unbilled receivable account for
transactions that have invoicing and accounting rules. If your accounting rule
recognizes revenue before your invoicing rule bills it, Receivables posts this amount
to your unbilled receivable account.
- Unearned Revenue: Receivables uses the unearned revenue account for transactions
that have invoicing and accounting rules. If your accounting rule recognizes revenue
after your invoicing rule bills it, Receivables posts this amount to your unearned
revenue account.
- Unpaid Bills Receivable: AutoAccounting uses this value if you derive the Unpaid
Bills Receivable account from the transaction drawee site. You can enter a value in
this field only if the business purpose for this address is Drawee.
Segment: Segment names in your Accounting Flexfield Structure are automatically
populated when you select an AutoAccounting Type.
Table: Receivables enables you to use different table names for different accounts. Select
one of the following table names:
- Bill To Site: Used to determine this segment of your revenue, freight, receivable,
AutoInvoice clearing, tax, unbilled receivable, and unearned revenue account.
- 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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Area: APAC
e
l
c
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
30. Save.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
After you define the Invoice Source, it must be assigned to a system parameter or at OM
transaction type level.
To assigning invoice source at the system parameter level:
(N) Setup > System Parameters > Values
If the invoice source referred for invoice auto-numbering to generate invoices with similar
numbering pattern at operating unit level (e.g., Vision Operations), then it is set at the system
parameter level. The defined Invoice source is assigned under the invoicing parameter of the
system parameter.
To assign invoice source at the OM Header/Line Transaction Type level:
(N) Setup > Transaction Type > Define
If the invoice source is referred for invoice auto - numbering at transaction level, then it is
assigned under the Finance tab of the Transaction Type window.
An invoice source assigned at line transaction type level has maximum precedence, followed
by header transaction type, then at the system parameter level.
A Receivables Transaction Type is defined and assigned at the system parameter or transaction
type level for autoinvoice creation.
To define and assign a receivables transaction type:
Define the transaction type: (N) Receivables > Setup > Transactions > Transaction Types
Assign the transaction type to the system parameter: If the invoice transaction type is
referred for autoinvoice generation at the operating unit level (e.g., Vision Operations),
then it is set at the system parameter level. The defined Invoice Transaction Type is
assigned under invoicing parameter of the system parameter. (N) Setup > System
Parameters > Values
Assign the transaction type to the order header/line transaction type: If the Invoice/
Receivables transaction type is referred for AutoInvoice generation, then it is assigned
under the Finance tab of the transaction type. (N) Setup > Transaction Type > Define
Invoice Transaction Type assigned at Line Transaction Type level has maximum
precedence followed by Header Transaction Type, then at the system parameter level.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
7. Select Quota Sales Credit using the list of values in the Sales Credit Type field.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
2.
3.
Find the tax related fields and determine the tax events.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
e
d
a
y
m
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
33. Navigate to the Tax Event field and use the list of values to view the applicable options.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
4.
y
m
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
5.
6.
e
l
c
a
r
O
c
A
e
d
a
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Include Tax
Include Returns
6. Save.
Define Credit Check and Hold
(N) Order Management > Receivables > Customers > Customers
34. Enter your customer name in the Name field.
35. (B) Find.
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
Chapter 6
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
For information on how to set and update profile option values, see the Oracle Applications
System Administrator's Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
For more information see Using Oracle Workflow in Oracle Order Management.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Order or Return. When an order type is assigned to an order, the category determines
whether both order and return lines can go on the order. A category of Mixed enables an
order to have both kinds of lines. For Sales Agreements, select Order. For Order Lines,
the Sales Orders window automatically sets the category to Order. Order Management
seeds defaulting rules to get the appropriate default outbound or inbound line transaction
type from an order type to a line based on its category code.
5. In the Transaction Type Code field, select order or line from the list of values to specify
whether this is an order or line transaction type. Select the value Order for Sales
Agreements.
6. In the Fulfillment Flow field, select a line flow from the list of values. The most
commonly used flows for sales orders are Order Flow - Generic and Order Flow Generic with Header Level Invoice Interface.
7. If a negotiation flow is needed, select it in the Negotiation Flow field from the list of
values. The most commonly used flows are Negotiation Flow - Generic and Negotiation
Flow - Generic with Approval.
8. Enter an effective date for the transaction type in the Effective Dates field.
9. Select the default transaction phase, Fulfillment or Negotiation, in the Default
Transaction Phase field from the list of values. Transaction phase determines where in the
workflow the transaction begins, and can be used in defaulting rules. This field defaults
to Fulfillmenta fulfillment phase must be defined; Negotiation is optional.
10. Enter a value in the Layout Templates field. This field is optional.
11. Enter a value in the Contract Template field. This field is optional.
12. In order for the Quote number to become the Sales Order number, select the Retain
Document Number check box. This is not applicable for Sales Orders or Sales
Agreements. If the transaction type is associated with both a negotiation flow and
fulfillment flow, the document number can be retained when the document transitions to
fulfillment.
On the Main Tab in the Document Region:
13. In the Agreement Type field, select a pricing agreement type from the list of values. This
field is optional. If you enter an agreement type here, you can choose only agreements
with this agreement type when using this order type. Some of the examples of Agreement
Types in the LOV are: Standard Terms and Conditions, Direct Sales Agreement,
Government 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:
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
18. Select the Enforce List Price check box to prevent discounts and overriding the selling
price. If this is selected, you cannot apply discounts to the order line list price when you
use this order type and you cannot override the selling price, unless the profile option
OM: Discounting Privilege is set at the appropriate level.
19. In the Price List field select a price list from the list of values to serve as a defaulting
source. The list of values displays global price lists and price lists defined for the
Operating Unit selected.
20. Enter a minimum margin in the Minimum Margin Percent field. This field is optional.
On the Main Tab in the Credit Check Rule Region:
21. Enter a credit check rule that you have defined for any one or a combination of the
following events: Ordering, Packing, Picking/Purchase Release, Shipping.
22. Select credit check rules to use when performing checking credit at either Booking, Pick
Release and Purchase Release (for drop shipments), Packing, or Shipping within the
corresponding Credit Check Rule fields.
23. You can select a credit check rule for each field within the Credit Check Rule region, or
select combinations that suit your business purposes. For example, you can select a credit
check rule for booking only, or booking and shipping. If you leave any of the Credit
Check Rule fields blank, no credit checking will occur when an order or order line
reaches the corresponding workflow activity within the order or line flow, using the order
or order line type specified.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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
Sales Document Type = Sales Order
Order Category = Order
Transaction Type Code = Line
Effective Dates From = Enter todays date
3.
(T) Shipping.
Scheduling Level = Allow all scheduling actions
4.
(B) OK.
5.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
(I) New. Create a new transaction type for the order level.
y
m
e
d
a
c
A
Note: The following steps create the order transaction type and assign line flows to the order
transaction type.
7.
e
l
c
a
r
O
8.
(T) Shipping.
Scheduling Level = Allow all scheduling actions
9.
(T) Finance
Currency = USD
y
m
e
d
a
Now you will create a document sequence for the transaction type and then assign the document
sequence to the transaction type.
15. (N) Setup > Documents > Define
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
y
m
e
d
a
c
A
1. Create a line transaction type named XX-StandardLine for the order lines.
2. Create an order transaction type named XX-StandardOrder for the order header.
3. Assign line flows to the XX-StandardOrder transaction type.
e
l
c
a
r
O
2.
y
m
e
d
a
3.
(I) Save.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
5.
(T) Main.
Default Order Line Type = XX-StandardLine
6.
(T) Shipping.
Shipping Method = DHL
Freight Terms = Prepaid
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
7.
(T) Finance.
Accounting Rule = Immediate
Invoice Source = Manual
Currency = USD
y
m
e
d
a
8.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
9.
y
m
e
d
a
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Now you will create a document sequence for the transaction type and then assign the document
sequence to the transaction type.
10. Navigate to the Document Sequences window.
e
l
c
a
r
O
y
m
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
e
d
a
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
2.
Within the Main tab, enter the following in the Customer Number field and [TAB] to
populate the other fields:
1608
Use the list of values in the Order Type field to select Mixed.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
11. View the status of the workflow for the sales order and line.
e
l
c
a
r
O
c
A
2.
(I) Find
3.
Within the Order Number field of the Find Orders/Quotes window, enter the sales order
number from the Create and Book a Sales Order, View Workflow Status demonstration.
4.
(B) Find
y
m
e
d
a
5.
e
l
c
(B) Open
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
7.
Scroll down the page to show the activities associated with this workflow.
8.
Within the Search region, disable some of the Activity Types and Activity Status criteria.
9.
(B) Go.
c
A
10. Identify the changes in the Activities region from your customized search.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
e
d
a
y
m
a. Definition
e
d
a
b. Usage
c. Status
d. Notification
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
14. Identify the Search region and each of the search criteria.
y
m
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
d
a
c
A
16. Identify the Workflow Definition and Workflow Attributes regions and the fields within
each.
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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
Category field.
2. Select the Ledger. Enter Manual in the method field if the number sequence is manual,
otherwise enter Null.
3. On the Assignment tab enter the Start Date and the Sequence that you defined for your
order type in the previous step. Note that you cannot change the assignment for an order
type and ledger. To change the assignment you must assign an end date to the existing
assignment and create a new one for the new assignment. You cannot have more than one
assignment for the same date range, document type and ledger.
4. There are additional controls to be considered when a quote transitions to a sales order in
reference to the document number and how the number is generated.
5. If a gapless numbering type is a requirement, then the Retain Document Number check
box should not be selected when using a transaction type for negotiation and fulfillment.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
attribute is Ordered Quantity only, and for recording Audit Trail history when
requiring a reason for an attribute change
- Requires History: You can perform the operation and will not be prompted to enter a
Reason. You still have the option to enter both a Reason and Comment, and if you
do so, the information is recorded. Use the value for enabling Audit Trail history to
be recorded without a reason for an attribute change
4. Select a value for the System Changes field. The value selected in this field determines if
system changes are allowed, despite the constraint. Choose from:
- Always: System changes allowed
- Never after Insert: System changes allowed if the entry has not been saved to the
database
5. Select a value for the User Changes Field:
- Never: The user is always constrained
- Never after Insert: The user is constrained after the entry is saved to the database
The Enabled field indicates whether the current constraint is active. This allows
constraints to be temporarily disabled if necessary.
System check box: If a Constraint has the System check box selected, you cannot update
the constraint definition.
Enter Conditions
6. In the Group Number field, enter a numeric value according to the following principles:
- For conditions that should together evaluate to TRUE (AND conditions), enter the
same group number. The constraint applies if the entity in question meets all of the
conditions defined.
- For conditions that should together evaluate to OR (OR conditions), enter a different
number for each record. The constraint applies if the entity in question meets any
one of the conditions defined.
7. In Scope, if the record set applies to multiple records, indicate the scope of evaluation of
the record set for this condition. An example of a record set that applies to multiple
records is the record set of all of the lines of a sales order. Select one of the following:
- Any: The condition is satisfied if one of the records meets it, for example, the
condition is satisfied if one of the sales order lines is booked
- All: The condition is satisfied if all of the records meet it, for example, the condition
is satisfied if all of the sales order lines are booked
8. In Validation Entity, enter the entity for which the condition is validated. You can enter
the same entity as the constraint (at the top of the Constraints region) or you can enter an
entity related to the constraint. For example, if the constraint is against Order Header,
Validation Entity can be Order Line.
In Record Set, select the record set that corresponds to the entities to which the
constraints process should apply the condition. For example, if you enter the order
line record set Line, the condition is evaluated against the order line in question. If
you enter the order line record set Order, the condition is evaluated against any or all
(depending on the scope) lines of the order in question.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
If Validation Entity is different from Entity (at the top of the form), you can only select
record sets based on the primary key of the validation entity.
9. Select the Not check box (the negative condition modifier) to direct the constraints
processing to evaluate the NOT condition of Validation Template. For example, if you
expect to select Validation Template Booked, selecting NOT creates the condition of not
booked for the constraint.
- In Validation, select a validation template. This item specifies the condition being
evaluated.
- Enabled: The Enabled field indicates whether the current constraint is active. This
allows constraints to be temporarily disabled if necessary.
- System check box:
- If a Constraint has the seeded check box selected, and the constraint condition
check box is also selected, you cannot update the constraint condition.
- If a Constraint has the seeded check box selected, and the constraint condition
check box is not selected, you can update the constraint condition.
10. In User Message, enter the trailing portion of the error message that the constraint
processing should display when the user violates the constraint. For example, if the
constraint was to not allow an update of the item field on the order line if the line has
been previously booked, constraints processing displays the error message You are not
allowed to update the item; the item is booked.
Specify who the Constraint applies to
Select one of the following:
All responsibilities: The constraint applies to all responsibilities.
Authorized responsibilities: The constraint applies to all responsibilities except ones that
you specify. Specify the excepted responsibilities in the untitled lines below your
selection.
Constrained responsibilities: The constraint applies to the responsibilities that you
specify. Specify the excepted responsibilities in the untitled lines below your selection.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
(N) Order Management > Setup > Rules> Security > Processing Constraints
2.
Query in the top of the window (To query, press CNTRL + F11):
Application = Order Management
Entity = Order Header
3.
4.
5.
e
d
a
y
m
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
7.
Enter the sales order header using the following information (all remaining information
defaults in):
Customer = XX-Big City Electronics
Order Type = Order Only
8.
Ordered Item
9.
Quantity
XX- Phone
XX-Palm Pilot
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Note: 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
13. Navigate to the Sales Orders window.
e
l
c
14. Enter the sales order header using the following information (all remaining information
defaults in):
Customer = XX-Big City Electronics
Order Type = Order Only
a
r
O
15. In the Line Items tab, enter the following line items:
Ordered Item
XX- Phone
Quantity
2
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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,
Error, Notified, and Suspended
- Select the activity Result for the condition
- Save your work
- API (validation is completed through an Application Program Interface):
- Select the PL/SQL Package you wish to interface with the constraint condition
- Enter the Procedure name of the API
- Save your work
- TBL (validation is based on the values of database columns on this entity):
- Select the Attribute Column name on the entity for the constraint condition
- Select the Validation Operation for the constraint condition. Select from: =
(Equal To), <> (Not Equal To), Is NULL, Is Not NULL
- Select the Value String you want to validate against the value of the column
Note: You can add more than one attribute, value pair, otherwise all pairs will be
added together in the validation.
Submit Create Validation Packages concurrent program
When you have created new validation templates or record sets, you will need to submit the
Create Validation Packages concurrent program from the Tools menu to submit a
concurrent request to create a validation package for all new or modified validation
templates and record sets that may constitute a permitted validation combination. After the
request completes, all validation templates that processed successfully will be visible in the
list of values in the Processing Constraints window.
For more information see:
(Help) Oracle Manufacturing Applications > Oracle Order Management > Oracle Order
Management Setup> Defining Validation Templates
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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:
(Help) Oracle Manufacturing Applications > Oracle Order Management > Oracle Order
Management Setup> Define Defaulting Conditions
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Sales order entities include groups of related attributes such as Order or Line.
Attributes are the individual fields within a particular entity, such as Warehouse, Ship
To Location, or Agreement.
Note: Changes to defaulting rules take effect for any new orders that use the modified
defaulting rules when you open the Sales Order Header or Lines windows or if you update
an attribute (field) on an order.
y
m
Assumptions
e
d
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.
Tasks
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
1.
2.
3.
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):
Application = Order Management
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
6.
In the Validation Rules region, create two validation rules for the template you added:
---
Group #
Attribute
Validation Operation
Value String
Rule # 1
105
Customer
Rule # 2
106
Currency
USD
7.
8.
y
m
e
d
a
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
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.
e
l
c
a
r
O
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.
Copyright Oracle, 2007. All rights reserved.
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
19. Navigate to the Sales Orders window.
20. In the Order Information tab, Main subtab, enter a sales order:
Customer = XX-Big City*
Order Type = Mixed
Currency = USD*
Note: *These conditions are required for the Freight Terms rule to be applied.
y
m
e
d
a
21. In the Order Information tab, Others subtab: Confirm that the default freight term value in
the Freight Terms field is To Be Determined. If so, then the default sourcing rule was
applied successfully.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Disabling the Defaulting Condition XX-Freight Terms for XX-Big City Electronics
for the Freight Terms Attribute
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.
22. Navigate to the Defaulting Setup Entity Attributes window.
23. Select Attribute = Freight Terms.
e
l
c
24. Click Defaulting Rules to display the Attribute Defaulting Rules window.
a
r
O
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
28. Navigate to the Sales Orders window.
29. On the Order Information tab > Main subtab, enter a sales order for the following customer:
Customer = XX-Big City*
Order Type = Mixed
Currency = USD*
Note: *These conditions are required to see if the Freight Terms rule you created has been
disabled successfully.
30. On the Order Information tab > Others subtab: In the Freight Terms field, notice that the
default Freight Terms value is now Prepaid and not To Be Determined. This means that you
successfully disabled the Freight Terms sourcing condition you previously created, and a
different defaulting rule was applied to derive the Freight Terms value.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
2.
(I) Find.
3.
e
l
c
a
r
O
c
A
4.
y
m
(B) OK.
e
d
a
5.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
a
r
O
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):
Application = Order Management
Entity = Order Header
y
m
e
d
a
c
A
6.
7.
8.
In the Validation Rules region, create two validation rules for the template you added:
--Rule # 1
Rule # 2
9.
(I) Save.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Group #
Attribute
Validation Operation
Value String
105
Customer
106
Currency
USD
a
r
O
y
m
13. (B) Defaulting Rules. The Attribute Defaulting Rules window appears.
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
16. (M) Tools > Generate Defaulting Handler Package. This program generates the defaulting
rules for the attribute.
17. (I) Save.
e
l
c
ra
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
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
e
l
c
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
r
O
y
m
e
d
a
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Note: *These conditions are required to see if the Freight Terms rule you created has been
disabled successfully.
e
l
c
a
r
O
y
m
e
l
c
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
For more information see:
(Help) Oracle Manufacturing Applications > Oracle Order Management > Change
Management> Versioning > Setup
Set Up Audit History
1. Add "View Audit History" menu option to the Order Management menu for those
responsibilities that need to be able to view the new Audit History forms this menu
option will be created through seed data.
2. Set up Processing Constraints to indicate which attributes on the order you want to have
audit trail recorded for. See Define Processing Constraints.
3. Create some new Validation Templates if you have specific conditions to control whether
or not to record audit information. See Defining Validation Templates.
4. Set the OM System Parameter Audit Trail.
Navigate to Order Management > Setup > System Parameters > Values.
1. Select your Operating Unit.
2. Select Generic Parameters from the list of values.
3. For the Audit Trail Parameter, select from the list of values: Enable when Order is
Booked, Enable when Order is Entered, or "Disabled.
5. Enter and process orders as usual.
6. Schedule the Consolidator program to run periodically to make audit information available
to query and report.
7. Run report or execute queries to view audit information.
Note: Based on the processing constraints that have been set up, users will sometimes be
required to input reasons when they make changes to orders.
System Parameter 'Audit Trail' has to be enabled at Operating Unit and the processing
constraint setup should be required to maintain Audit History for that Operating Unit.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Qty Reservable: The on-hand quantity minus the quantity that is already reserved to other
sources of demand.
Request Date: The date on the order line.
Available date: The date that the ordered quantity will be available. It could be the request
date if the order quantity is available on the request date, or it might be a future date when
the order quantity will be available
Error Message: Any error that occurred in calculating ATP. For example, if the Check
ATP flag for the item is not selected then this field will display ATP not applicable.
Substitute Item: If the requested item is not available and the requested quantity for a
defined substitute is available, the substitute item will be displayed.
An additional tab, showing the availability of the substitute item, is also displayed for single
items. A multi-line window displays availability information for sets and models. Clicking the
Global Availability button located at the bottom of the Availability window opens the ATP
window that has the list of warehouses where the item is enabled. You can select the
warehouses for which you want to see the availability, and the system will return the
availability in all the selected warehouses. You can open the ATP Details window from the
Availability window by clicking the ATP Details Button. The ATP Details window displays
how the results were derived.
ATP is calculated automatically during scheduling, and may be calculated manually by
clicking Availability on the Line Items tab of the Sales Order window. There are several steps
required for ATP calculations.
If you are using ASCP, supply/demand is set up at the plan level. See the Oracle ASCP
Implementation Manual. Global Order Promising will only use the infinite time fence specified
on the ATP rule. If you are not using ASCP, ATP rules must be defined to determine the
sources of supply and demand which are included in the calculation. The ATP rules must be
associated with items and/or inventory organizations. Also, the data collection program must
be run. There is a requirement for ATP calculations to be very fast; some customer service
representatives will need to give this information to customers on the phone.
However, considering all the possible sources of supply and demand for an ATP calculation
can be very complex. Therefore, a concurrent process known as data collection must be run to
summarize the supply and demand picture. This program is part of the Oracle Advanced
Planning and Scheduling application. The ATP calculation is then performed on the summary
tables. For details about setting up ATP rules and running the data collection program, see the
setup section Oracle Order Management implementation Guide.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
You have set the following system parameter. Setup-> System Parameters -> Values
Reservation Time Fence = 30
y
m
e
d
a
Tasks
Creating a Sales Order
c
A
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
1.
2.
3.
e
l
c
a
r
O
4.
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.
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.
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
16. In the Line Items tab, Shipping tab: Notice that the Qty Reserved field has been
automatically entered for item XX-Phone Card.
e
l
c
a
r
O
y
m
2.
y
m
e
d
a
3.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
4.
5.
(B) Availability. In the Availability window, confirm that the item quantity you want is
available. If the available quantity is sufficient, you can continue to the scheduling task.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
6.
c
A
7.
(B) OK.
8.
e
d
a
y
m
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
13. (M) Tools > Auto Schedule (Ensure Auto Schedule is selected)
14. (I) New:
Item = XX-Phone Card
Qty = 2
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
You can define a usage rule set for a single currency or multiple currencies
You can choose to assign a global usage rule (all currencies) and then exclude one or
more currencies from the rule set
You can choose to define multiple usage rules for multiple currencies within the usage
rule set
You can choose to add or delete new Currency records for an existing Usage Rule Set
Usage rule sets consist of at least one usage rule/currency combination, and once a rule set is
assigned to an Oracle Entity, the rule set provides processing defaults for determining
credit availability during multiple currency credit checking processing routines.
Define Credit Check Usage Rule Sets
1. Enter a name for your rule set in the Usage Rule Set Name field.
2. Select the Global Exposure box if you wish to enable the Usage Rule Set for global
exposure (across operating units). By default, this box is cleared (do not enable Global
Exposure for the usage rule set). If you are unable to select the Global Exposure check
box, submit the Credit Limit Usages Report. Review the report output and un-assign any
usage rule sets with different Global Exposure options for the same credit profile.
3. Select the value Currency in the Usage Type field.
4. Enter a currency in the Currency field. The Currency field can contain any Currency
Code currently defined. The Currency field may also use the lookup All Currencies to
indicate the usage rule is for all currencies defined.
5. Chose to exclude a specific currency for your usage rule by selecting the Exclude check
box. The default is unchecked, or No.
Note: If the field Currency has value of All, the Exclude check box is non-updateable.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super
User Order Management responsibility.
Tasks
1.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Rule: XX-Credit-Check-Rule
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
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 Tax
Include Returns
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
4. Save.
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Objectives
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Holds
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Holds
Oracle Order Management enables you to hold an order, return, order line, or return line from
continuing to progress through its workflow. Holds are applied manually or automatically
based on a set of criteria that you define. There are also seeded automatic holds provided to
prevent a line or order from progressing if it violates a given business metric, such as a credit
check failure.
e
l
c
a
r
O
Seeded Holds
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Seeded Holds
Seeded holds in Order Management include the following:
Configurator Validation Hold: This hold is a Configurator Validation type that is
automatically applied to order lines that fail configurator validation.
Credit Card Authorization Failure: This hold is an Electronic Payment type that is
automatically applied to orders if credit card authorization request to Oracle Payment fails.
Credit Card High Risk: This hold is an Electronic Payment type that is automatically
applied to orders if the risk score determined by Oracle Payments is greater than the value
of the risk factor threshold.
Credit Check Failure: This hold is a Credit Check type that is automatically applied if the
credit 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.
e
l
c
a
r
O
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.
Promotional Line: This hold is a promotional hold type that is automatically placed on
lines that exceed a soft modifier promotional limit.
Promotional Order: This hold is a promotional hold type that is automatically placed on
orders that exceed a soft modifier promotional limit.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Automatic Holds
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Automatic Holds
(N) Order Management > Setup > Orders > Holds
Holds are defined to halt processing of your sales documents as well as order and return lines.
Because orders and returns are not affected by holds until the holds are applied, you can define
all the holds at one time. You can define holds that are effective only at certain steps of the
order or line workflow and you can defined holds that apply regardless of the stage in the order
flow.
Defining an automatic hold 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.
e
l
c
a
r
O
Optionally, select the user responsibilities that have authorization to execute and dismiss
holds.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Generic Holds
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Generic Holds
(N) Order Management > Setup > Orders > Holds
Generic holds are defined as an automatic hold; however, the generic hold does not contain a
workflow item or workflow activity.
Generic holds are placed at the order level. Order lines are considered on hold for an order that
has a generic hold against it. Hold information is not visible for generic holds at the order line
level, only at the order header.
Within the Holds window, the check box Apply to Order and Line is enabled only if a line
level workflow activity is entered in the hold definition. If the check box is enabled, then the
line level hold is applicable at the header level as well as the line level. Apply to Order and
Line is disabled as the default.
e
l
c
a
r
O
Hold Sources
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Hold Sources
(N) Order Management > Orders, Returns > Order Organizer
Hold sources are defined to apply holds automatically for existing or future single or multiple
orders, returns, and lines for a particular site, item, warehouse, order, and so on.
To define a hold source:
From the Order Organizer window, select Create Hold Source from the Tools menu.
Select a hold name from the list of values.
Select the operating unit applicable to this hold.
Use the list of values to select the criteria for the hold. Choose from:
- Bill to Site
- Ship to Site
- Warehouse
- Item
- Order
- Sales Agreement No. (number)
e
l
c
a
r
O
Use the list of values to select the value of the criterion that you chose.
Enter a date in the Hold Until Date field to specify when the hold is released.
Optionally, enter comments for the hold.
Click Apply Holds.
You can define the hold source to be for a specific order or return. A hold source can also be
the combination of parameters that Oracle Order Management supports. Oracle Order
Management supports hold sources with up to two entities. The combinations of supported
entities include:
Item > Customer
Item > Ship To Site
Item > Bill To Site
Item > Warehouse
Item > Sales Agreement Number
Warehouse > Customer
Warehouse > Ship To Site
Warehouse > Bill To Site
Sales Agreement Number > Ship To Site
Sales Agreement Number > Bill To Site
Sales Agreement Number > Warehouse
Sales Agreement Number > Ship To Site
Sales Agreement Line Number
You can apply your holds to be effective immediately and universally. An automatic hold that
has hold criteria defined can be released for all orders or individual orders.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Scheduling Related
Credit Check
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.
Use Order Management Super User, Vision Operations (USA) or comparable Super User
Order Management responsibility.
y
m
e
d
a
Tasks
3.
1.
2.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
If you are using Vision Operations as your default operating unit, you need to assign another
operating unit to your responsibility.
e
l
c
a
r
O
Choose Responsibility
2.
e
d
a
2. Authorizations region:
Responsibility: Order Management Super User, Vision Operations USA
Authorized Action: Apply Hold
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
y
m
e
d
a
c
A
4. (B) Actions > Apply Holds. Select XX-Book-Hold from the LOV to apply the hold on
your current order.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
5. Save and book the order. The hold XX-Book-Hold will be applied to your order.
e
l
c
a
r
O
y
m
e
d
a
7. To release the hold, select (B) Actions > Release Holds. Provide a reason for releasing
the hold and click (B) Release.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Authorizations region:
Responsibility: Order Management Super User, Vision Operations USA
Authorized Action: Apply Hold
Responsibility: Order Management Super User, Vision Operations USA
Authorized Action: Remove Hold
e
l
c
a
r
O
y
m
e
d
a
c
A
11. Apply the hold XX-Line-Hold to the order. (B) Actions > Apply Holds.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
12. Save and book the order. If the line cannot be scheduled, the hold is applied to the line.
e
l
c
a
r
O
y
m
14. To release the hold, select (B) Actions > Release Holds. Enter a reason for releasing the
hold and click (B) Release.
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
19. In the Profile Amounts tab, ensure that the Credit Limit and Order Credit Limit are
specified for the currency that you use:
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
22. Create a credit check rule using (N) Setup > Credit > Define Credit Check Rule
e
l
c
a
r
O
y
m
e
d
a
24. Select a transaction type that is defaulted for the customer. For the customer XXSYNERGY, the transaction type is Standard.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
c
A
25. In the Main tab, in the Credit Check Rule region, enter your credit check rule XX-CreditCheck-Rule.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
Warehouse: V1
Item: XX-ITEM1
Qty: any quantity whose total amount exceeds the order credit limit specified for
the customer.
e
l
c
a
r
O
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:
Copyright Oracle, 2007. All rights reserved.
e
d
a
y
m
28. You can release the hold by either decreasing the order total in the sales order or by
increasing the order credit limit in the Customers page.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
Purge Sets
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
Purge Sets
(N) Order Management > Orders, Returns > Purge > Order Purge Selection
(N) Order Management > Orders, Returns > Purge > Quote Purge Selection
A purge set contains orders and quotes to be purged based upon criteria that you specify in the
Parameters of the Order Purge Selection or Quote Purge Selection concurrent process.
The Order Purge Selection and Quote Purge Selection concurrent programs enable you to
search for orders and quotes across operating units. By selecting an operating unit as part of the
parameters for the concurrent program, you restrict your quotes and orders to a specific
operating unit.
The following prerequisites are applicable when purging orders and quotes:
An order or quote status must be expired or lost before it can be purged
An order or quote can only be purged if no open activities exist, including open invoices or
open returns
After these conditions are met, the purge checks to see if all user defined prerequisites have
been met. Orders can be purged if there are unpaid invoices for them.
e
l
c
a
r
O
Note: Order and quote purge capability is available to Oracle Order Management Super Users
only.
You create Purge Sets by:
Purge Set Creation, using the Create Purge Set concurrent program
Multi-selection of orders within the Order Organizer window, then invoking the Create Purge
Set Concurrent Program from the Tools menu
Single selection of orders within the Order Organizer window, then invoking the Create Purge
Set Concurrent Program from the Tools menu
You can submit your same purge request on a regular interval for example, weekly or monthly.
To create a purge set:
Select an operating unit.
Enter a unique purge set name.
Optionally, enter a description for the purge set.
Define the following criteria (limit your selection to refine your purge):
Order Number Low
Order Number High
Order Type
Order Category
Customer
Order Date Low
Order Date High
Creation Date Low
Creation Date High
Determine whether or not you want contract terms to be purged (if applicable).
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
c
A
e
l
c
a
r
O
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
c
A
2. The profile option OM: Show Process Messages Flag is used to display the Open
Message box in the Sales Orders window. Set the value of the profile option to Yes to use
the indicator message_exists_flag . The checked value of this field indicates that at least
one message exists for the order.
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
y
m
e
d
a
4. (N) Orders, Returns > Quick Sales Orders. Open an existing order and navigate to the
lines region. Click (B) Actions > View Open Messages (or right-mouse click menu) to
view any messages. If any messages exist, they will be displayed in the Process Messages
window. If there are no messages for that order, a message box indicating that there are
no open messages displays.
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
e
l
c
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
7. You can use the Quick Sales Orders window to Retry Workflow Activities that have
errored out.
Copyright Oracle, 2007. All rights reserved.
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.
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.
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
Summary
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A
y
m
e
d
a
e
l
c
e
l
c
a
r
O ly
& On
l
a e
n
r
s
e
t
U
n
I
a
r
O
c
A