Elshayeboracler12ordermanagement 141215031454 Conversion Gate01

Order Management
Profile Option For New Responsibility

TP:INV Transaction processing mode
Profile Option Name
AP: Use Invoice Batch Controls
AR: Allow Update Of Existing Sales Credits
AR: Cash - Allow Actions
AR: Keep or Replace Existing Profile Amounts
AR: Mask Bank Account Numbers
AR: Use Statement, Dunning, and Late Charges
Site Profiles
Default Country
GL: Data Access Set
HZ: Change Party Name
INV: Item Master Flexfield
OE: Item Validation Organization
QP: Item Validation Organization
Service: Default Operating Unit
HR: Security Profile
HR:User Type
MO: Default Operating Unit
MO: Operating Unit
MO: Security Profile
Sit
e
Applicati
on
Responsibility
No
Yes
Yes
Keep
Mask - First Four Digits
Visible
No
United States
Vision Operations (USA)
Yes
System Items
Vision Operations
Vision Operations
Vision Corporation
HR with Payroll User
Vision Corporation
GL Ledger Name
INV:Override Neg for Backflush
Run Request == Replicate Seed Data

System Administrator> Requests
Vision Operations (USA)

No
https://support.oracle.com/epmos/faces/DocumentDisplay?
_afrLoop=356715836428752&parent=DOCUMENT&sourceId=1101666.1&id=1067402.1&_afr
WindowMode=0&_adf.ctrl-state=qwj6ljmuz_131
How to Setup a Remit-To Address in Release 12 Oracle Receivables (Doc ID 1101666.1)
_afrLoop=190500665481489&parent=DOCUMENT&sourceId=1101855.1&id=1101666.1&_afr
WindowMode=0&_adf.ctrl-state=k0mvht6dq_170
Order Management Setup Stapes

1- Creating a User and Assigning Responsibilities
Overview
In this practice you will learn how to create a user and assign responsibilities to the user
Login
1. Login to the database.
User Name: operations

Password:
welcome
2. Select the System Administrator responsibility.

3. Create a User. (N) Security > User > Define
Enter the following information:
a.User:
<your chosen login name>
b.Password:
<any pwd of your choice; you need to type it twice>
c. Password Expiration: select None
d.Effective Dates: enter dates
4.
(M) File > Save.
5. Assign the following responsibilities to your user using (T) Direct Responsibilities:
Responsibility
Security
Group
Order Management Super User, Vision Operations
Standard
(USA)
Inventory, Vision Operations (USA)
Standard
Receivables Manager
Standard
System Administrator
Standard
Purchasing Super User, Vision Operations
Standard
CRM Administrator, Vision Enterprises
Standard
Oracle Pricing Manager, Global
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.
Note: You can use this account for subsequent logins.
8.
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).
10. Please ensure that the appropriate menu (shown below) ADS_OM_SUPERMENU is assigned to
the OM Super User responsibility.
11. Save your work and close the Responsibilities window.
Guided Demonstration Setting Up

Notes: Enter the following enterprise structure: Top Org with 2 Operating Units. Both
Operating Units have an Inventory Org each.
Responsibility: HRMS Management

(N) > HRMS Manager > Work Structures > Location
1. Enter
the following details for some new locations:

Scope: Global
Name: enter a name starting with your intials (e.g. SH-OrgLocation)
Description: any description
(T) Address Details
2. Address flexfield enter the following:

Address Line 1: 301 Patriots Road
City: San Diego
State: CA
Zip Code: 92130
County: San Diego
Country: United States
3. (B) OK
4. (N) Inventory > Setup > Organizations > Organizations
5. Click (B) New in the Find window and in the Organizations window, enter the location (SHOrgLocation) that you created in the previous steps.
6. (T) Shipping Details:
Enter a Contact
The Ship-To Location should default as your location name
Ensure that the following boxes are checked:
o Ship-To Site
o Bill-To Site
o Receiving Site
o Internal Site
o Office Site
7. (M) Save.
8. Similarly, create locations for your other orgs: OU1, OU2, InvOrg1, InvOrg2. Select the Global
button for determining the scope of the location. Possible names that you could use for the
locations:
SH-OU1-Location
SH-OU2-Location
SH-InvOrg1-Location
SH-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
Organization
External
Classification
SH-TOP
SH-OrgLocation
Internal
GRE/Legal Entity
SH-OU1
SH-OU1-Location
Internal
Operating Unit
SH-OU2
SH-OU2-Location
Internal
Operating Unit
SH-InvOrg1
SH-InvOrg1Internal
Inventory Organization
Location
SH-InvOrg2
SH-InvOrg2Internal
Inventory Organization
Location
When You Define OU Additional Information
When You Define 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.
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.
16.Save your work

17.Enter a Version Number and Start Date for the new hierarchy.
Save Your Work

18.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.
19.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.
20.Save your work and exit the window.

21.(N) > HRMS Manager > Security > Profile
22.Enter a Name and a Business Group.
Business Group = Vision Corporation
Name = SH-Security Profile
23.Select the Security Type as Secure organizations by organization hierarchy and/or organization
list.
24.Enter your Organization Hierarchy name (you created it in the steps above).
25.Check the Include Top Organization box and the Exclude Business Groups box.
26.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.
27.Save your work.

28.Run the Security List Maintenance concurrent program. (M) View > Requests > Security List
Maintenance with the following parameters:
Generate Lists For: All Security Profiles or One Named Security Profile
29.Responsibility: System Administrator

30.(N) > Profile > System
31.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.
32.Assign a default operating unit to the profile option MO: Default Operating Unit. (N) > Profile >
System.
33.Run the Setup Validation Report to check if the setup steps have been performed successfully.
Order Management Setup Validation Report (XML)
Define Inventory Parameter For Inventory Organization

Inventory : Setup -> Organizations -> Organization
Item Master Organization

You define items in one organization. To distinguish it from others, we call it the Item Master
organization .Other organizations (child organizations) refer to the Item Master for item definition. After you define an item
in the Item Master, you can assign it to any number of other organizations.
There is no functional or technical difference between the Item Master organization and other organizations. However, for
simplicity, Oracle recommends that you limit the Item Master to just an item definition organization.
Oracle also recommends that you do not define multiple item masters. This can make item definition and maintenance
confusing. In addition, multiple item masters are distinct entities, with no relationship to each other. You cannot associate
items in one item master organization with another item master organization. You cannot copy items across item
master organizations.
To create the item master:
1. Use the Organization window to create the organization you want to use as the Item Master.
2. Use the Organization Parameters window to specify that organization as the Item Master. This is also where you assign
child organizations to the Item Master. The item master organization uses itself as the Item Master.
You can define and update default inventory and costing parameters for your current organization in the following areas:
1.
Inventory Parameters
2.
Costing Information
3.
Other Account Parameters
4.
Revision, Lot, Serial, LPN Parameters
5.
ATP, Pick, ItemSourcing Parameters
6.
Defining InterOrganization Information
7.
Defining Warehouse Parameters

1. Enter an organization code for which you want to set up the organization parameter.
2. Select an Item Master organization. Oracle Inventory only defines items in the Item Master organization of the
organization from which you enter the Items window.
3. Select a workday calendar. This is required when Oracle Master Scheduling/MRP and Oracle Supply Chain
Planning is installed.
4. Optionally, select a demand class. Demand classes segregate scheduled demand and production into groups,
allowing you to track and consume those groups independently. Oracle Master Scheduling/MRP and Oracle Supply
Chain Planning uses this demand class during forecast consumption, and shipment and production relief.
5. In the Move Order Timeout Period field, enter the number of days a move order requisition can wait for
approval.
The workflow approval process sends a notification to the item planner when a move order requisition requires
approval.
After the first timeout period, if the recipient has not approved or rejected the order, a reminder notice is sent. After
the second timeout period, the order is automatically approved or rejected, depending on whether you select
Approve automatically or Reject automatically in the Move Order Timeout Action field. If you want to bypass the
move order approval process and automatically approve move order requisitions, enter 0 days in the Move Order
Timeout Period field and select Approve automatically in the Move Order Timeout Action field.
6. Select a move order timeout action
Approve automatically: After the second timeout period, move order requisitions are automatically approved. Select
this option and set the Move Order Timeout Period to 0 if you want to bypass the move order approval process and
automatically approve move order requisitions.
Reject automatically: After the second timeout period, move order requisitions are automatically rejected.
7. Select a locator control option:
None: Inventory transactions within this organization do not require locator information.
Prespecified only: Inventory transactions within this organization require a valid, predefined locator for each item.
Dynamic entry allowed: Inventory transactions within this organization require a locator for each item. You can
choose a valid, predefined locator, or define a locator dynamically at the time of transaction.
Determined at subinventory level: Inventory transactions use locator control information that you define at the
subinventory level.
Indicate whether to allow negative balances. Determines whether inventory transactions can drive the inventory
balance of an item negative.
Attention: If insufficient quantity on hand exists in a supply subinventory to satisfy backflush demand, Oracle Work
in Process forces the supply subinventory balance negative, ignoring this option setting.
Auto delete allocation at Move Order cancellation
Indicate whether this organization is an Oracle Warehouse Management enabled organization. You can use WMS
features such as LPNs, task management, warehouse execution rules and cost
groups in this organization. Locator control must be enabled in order to enable WMS. Once this has been enabled and
transactions have been entered in this organization, this box cannot be unchecked.
Indicate whether this organization is enabled for Quality inspection.
Indicate whether this organization is an Oracle Enterprise Asset Management enabled Organization.
Enter a total load weight and unit of measure for this organization.
Enter a total volume and unit of measure for this organization.

8 . Select a Default On-hand Material Status tracking option. This step is optional.
Attention: You cannot update this field for existing organizations. To enable this field, you must submit the Activate
Onhand Level Material Status Tracking concurrent program.
9. Indicate whether locator aliases must be unique across the organization.
1. Costing Organization
2. Costing Method
3. Transfer to GL Indicate whether all transactions are posted in detail to the general ledger.
Caution: Transferring detail transaction distributions to the general ledger increases general ledger posting times due to the
number of records created.
4. Reverse Encumbrance Indicate whether to reverse encumbrance entry upon receipt in inventory.
You normally select this option if you use encumbrances with Oracle Purchasing.
5. Optionally, enter a Cost Cutoff Date
If you leave this field blank, all available transactions will be costed as usual. If you enter a date, all transactions prior to this
date will be costed. All transactions on or later than this date will not be costed.
For interorganization transfers, a standard costing, receiving organization will not cost a receipt if the sending organization
did not already cost the transaction.
The default time is the first instant of the date. You can optionally choose another time.
The standard cost update process can be performed on the cost cutoff date. You can restart cost processing by changing the
cutoff date to blank, or a future date.
6. Default Material Sub element
For standard costing, select a material subelement that this organization uses as a default when you define item costs. For
average costing, the default material subelement you select can be used for cost collection when Project Cost Collection
Enabled is set.
7. Material Over head Sub element
Optionally, select a Default Material Overhead SubElement from the list of values. During the Supply Chain Rollup process,
when costs are merged from another organization, markup and shipping costs will use this value.
The supply chain cost rollup will complete successfully, regardless of whether this field is populated. If the Cost Rollup
identifies an organization with a default material overhead subelement not set up, a corresponding warning message will be
printed in the log file.
8. Default Cost Group
Indicate the default cost group for the organization. This will default into the Default Cost Group field for each subinventory. If
the WMS cost group rules engine fails to find a cost group, this cost group will be used.
9. Valuation Accounts
You choose a default valuation account when you define organization parameters. Under standard costing, these accounts
are defaulted when you define subinventories and can be overridden. Under average costing, these accounts (except for
Expense) are used for subinventory transactions and cannot be updated. For a detailed discussion of cost
elements.
Material An asset account that tracks material cost. For average costing, this account holds your inventory
and intransit values. Once you perform transactions, you cannot change this account.
Material Overhead An asset account that tracks material overhead cost.
Resource An asset account that tracks resource cost.
Overhead An asset account that tracks resource and outside processing overheads.
Outside processing An asset account that tracks outside processing cost.
Expense The expense account used when tracking a nonasset item.
Enter The Following Valuation Account
Account Type
Material
Material Overhead
Resource
Overhead
Outside processing
Expense
Account
01-000-1410-0000-000
01-000-1420-0000-000
01-000-1440-0000-000
01-000-1430-0000-000
01-000-1450-0000-000
01-520-7530-0000-000
Revision, Lot, Serial, LPN Parameters

Enter a starting revision to be the default for each new item.
Lot Number
1. Select an option for lot number uniqueness.
Across items: Enforce unique lot numbers for items across all organizations.
None: Unique lot numbers are not required.
2. Select an option for lot number generation.
Userdefined: Enter userdefined lot numbers when you receive items.
At organization level: Define the starting prefix and lot number information for items using the values you enter in the
Prefix, Zero Pad Suffix, and Total Length fields. When you receive items, this information is used to automatically generate lot
numbers for your items.
At item level: Define the starting lot number prefix and the starting lot number when you define the item. This information is
used to generate a lot number for the item when it is received.
3. Indicate whether to add zeroes to rightjustify the numeric portion of lot numbers (Zero Pad Suffix).
4. Optionally, select an alphanumeric lot number prefix to use for systemgenerated lot numbers when generation is at the
organization level.
5. Optionally, define the maximum length for lot numbers. If you use Oracle Work in Process and you set the WIP parameter
to default the lot number based on inventory rules, then WIP validates the length of the lot number against the length you
define in this field.
Serial Number
1. Select an option for serial number uniqueness.
Within inventory items: Enforce unique serial numbers for inventory items.
Within organization: Enforce unique serial numbers within the current organization.
Across organizations: Enforce unique serial numbers throughout all organizations.
2. Select an option for serial number generation.
At organization level: Define the starting prefix and serial number information for items using the information you enter in
the following fields of this window.
At item level: Define the starting serial number prefix and the starting serial number when you define the item.
3. Optionally, select an alphanumeric serial number prefix to use for systemgenerated serial numbers when generation is at
the organization level.
4. Optionally, enter a starting serial number to use for systemgenerated serial numbers.
If serial number generation is at the organization level you must enter a starting serial number.
5. Indicate whether the system will suggest serial numbers as part of the move order line allocating process. If you do not
select this option, you must manually enter the serial numbers in order to transact the move order.
ATP, Pick, ItemSourcing Parameters

Select a default ATP rule.
ATP rules define the options used to calculate the quantity of an item.
If you are using Oracle Order Management, the default is the ATP rule for the Master organization.
Picking Defaults
Select a default picking rule.
Picking rules define the priority that order management functions use to pick items.
Notes: This rule will not be employed in a WMS enabled organization. The WMS picking rules will be used.
Enter a default subinventory picking order.

This value indicates the priority with which you pick items from a subinventory, relative to another subinventory, in which a
given item resides.
The value you enter here displays as the default when you define a subinventory.
Enter a default locator picking order.
This value indicates the priority with which you pick items from a locator, relative to another locator, where a given item
resides. The value you enter here displays as the default when you define a locator.
Check the Pick Confirmation Required box if you want your pickers to manually pick confirm. If you do not check the box,
pick confirmation will occur automatically.
Item-Sourcing Default
Select a source type for item replenishment.
Inventory: Replenish items internally from another subinventory in the same organization or another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
None: No default source for item replenishment.
Select the organization used to replenish items.
You must enter a value in this field if you selected Inventory in the Type field.
Select the subinventory used to replenish items.
You must enter a value in this field if you selected your current organization in the Organization field. You cannot enter a
value in this field if you selected Supplier in the Type field.
Other Account
Encumbrance: An expense account used to recognize the reservation of funds when a purchase order is approved.
Inventory A/P Accrual : The liability account that represents all inventory purchase order receipts not matched in Accounts
Payable, such as the uninvoiced receipts account.
Purchase Price Variance : The variance account used to record differences between purchase order price and standard
cost. This account is not used with the average cost method.
Invoice Price Variance : The variance account used to record differences between purchase order price and invoice price.
This account is used by Accounts Payable to record invoice price variance.
Cost of Goods Sold: The profit and loss (income statement) account that tracks the default cost of goods sold account.
Sales: The profit and loss (income statement) account that tracks the default revenue account.
Project Clearance Account: When performing miscellaneous issues to capital projects, the project clearance account is
used to post the distributions.
Average Cost Variance: Under average costing with negative quantity balances, this account represents the inventory
valuation error caused by issuing your inventory before your receipts.
Cost Variance Will Appear when you Issue Value from inventory greater than current inventory value
Note: For standard costing, only the Purchase Price Variance, Inventory A/P Accrual, Invoice Price Variance, Expense, Sales
and Cost of Goods Sold accounts are required. The other accounts are used as defaults to speed your set up.
Note: For average costing, only the Material, Average Cost Variance, Inventory A/P Accrual, Invoice Price Variance, Expense,
Sales and Cost of Goods Sold accounts are required. The other accounts are used as defaults or are not required.
Enter The Following Other Account Information:
Account Type
Purchase Price Variance
Invoice Price Variance
Inventory AP Accrual
Encumbrance
Sales
Cost of Goods Sold
Deferred COGS Account
Cost Variance Account
Account
01-520-5210-0000-000
01-520-5220-0000-000
01-000-2220-0000-000
01-520-4110-0000-000
01-450-5110-0000-000
01-450-5110-0000-000
01-000-1410-0000-000
Repeat This Steps Fro To Organization SH 1 And SH 2
Organization Access
Receiving Options
Account Type
Receiving Inventory Account
Clearing Account
Account
01-000-1410-0000-000
01-000-1410-0000-000
Subinventories
Subinventories are unique physical or logical separations of material inventory, such as raw inventory, finished goods, or
defective material. All material within an organization resides in a subinventory. There are two types of subinventories within
Warehouse Management, storage and receiving.
Storage subinventories are intermediate or final put away locations for material. Material that resides in a storage
subinventory appears in on hand quantity, and is tracked by the system. The system can book orders against, and use
manufacturing processes on material that resides in a storage subinventory. You must define at least one storage
subinventory for your implementation.
Receiving subinventories. Optionally, you can create receiving subinventories to track material in the receiving area. You
use receiving subinventories when you want to track the material as soon as it enters the warehouse before an operator puts
it away. Receiving subinventories enable managers to see where the material resides as soon as it enters the warehouse.
Material located in a receiving subinventory does not appear in on hand quantity, and the system cannot reserve the
material.
An operator can also only specify a receiving subinventory if they are using a mobile device to receive the material.
Note: Operators cannot transfer material from a storage subinventory to a receiving subinventory.
All material within an organization is held in a subinventory therefore, you must define at least one subinventory.
Table : MTL_SECONDARY_INVENTORIES
Header
1. Enter a unique alphanumeric name.
2. Indicate the material status of this subinventory, which controls the enabled transactions for all material in this
subinventory. The status is not overridden by the status of any locator, lot or serial, within this subinventory. The statuses of
those objects will be considered when determining transactions that are not enabled. This field is
used if you have Oracle Warehouse Management installed.
3. Indicate the default cost group for this subinventory. If the cost group assignment rules fail to identify a cost group for
newly received material, this cost group will be assigned. This cost group will remain with the material, even through
subinventory transfers, until you perform a cost group change transaction. This feature is available if you have Oracle
Warehouse Management installed, and you are working with a WMS enabled organization.
4. Select the subinventory type from the drop down list. The available choices are as follows:
Storage: Designates the subinventory as a Storage subinventory.
Receiving: Designates the subinventory as a receiving subinventory, and links it to a receiving location. This subinventory
type is used only for receiving material. Material in this type of subinventory cannot be onhand, or reserved.
Null: No subinventory designation
Parameters
Following are the important parameters that we must define
1. Quantity tracked Indicate whether each transaction for this subinventory updates the quantity on hand for the
subinventory (Quantity Tracked).
If you leave this option unchecked, onhand balances are not maintained and you cannot check or update the Asset
Inventory, Include in ATP, Reservable, or Nettable options. You can update this value only if there is no onhand quantity, no
pending transaction, or no uncosted transaction for the subinventory.
2. Asset Subinventory: Indicate whether to maintain the value of this subinventory on the balance sheet (Asset
Subinventory). You can update this value only if there is no onhand quantity for the subinventory.
3. Include in ATP: Indicate whether to include items in this subinventory in ATP calculations.
4. Depreciable: Indicate whether to designate items in this subinventory as depreciable.
This data is needed to support depreciable and location information in the Subinventory Setup from the Oracle Network
Logistics product.
5. Allow Reservation: Indicate whether to include this subinventory when you perform availabletoreserve calculations.
6 Nettable: Indicate whether the planning process uses the onhand balance of these subinventory items as available
inventory (Nettable).
7. LPN Controlled: Indicate if material may be packed into an LPN in the subinventory. If this is unchecked, all LPNs
transacted into this subinventory will be automatically unpacked, and LPNs cannot be packed into this subinventory. This
feature is available if you have Oracle Warehouse Management installed, and you are working with a WMS enabled
organization
8. Select a type of locator control.
You can select an option only if you selected locator control as Determined at subinventory level in the Locator Control field
in the Organization Parameters window. You can only update this option if there is no onhand quantity for the subinventory.
None: Inventory transactions within this subinventory do not require locator information.
Prespecified: Inventory transactions within this subinventory require you to enter a valid predefined locator for each item.
Dynamic entry: Inventory transactions within this subinventory require you to enter a locator for each item. You may
choose a valid predefined locator, or define a locator dynamically at the time of transaction.
Item level: Inventory transactions use locator control information that you define at the item level.
9. Optionally, enter an inactive date for the subinventory.
10. Enter a location for the subinventory. If the Subinventory type is Receiving, this field is mandatory.
Lead times
Optionally, enter preprocessing, processing, and postprocessing lead times for items in this subinventory.
These lead times are used when you use minmax planning at the subinventory level.
Sourcing
Inventory: Replenish items internally, from another organization.
Supplier: Replenish items externally, from a supplier you specify in Oracle Purchasing.
Subinventory: Replenish items internally, from another subinventory in the same inventory organization.Navigate to the
Subinventories Summary folder window. Choose New. The Subinventories window appears.
subinventory account information
Enter the general ledger accounts. The default accounts are those defined for the organization in the Organization
Parameters window. If you are using average costing, you may enter the valuation accounts, but they are not used. Average
costing uses only the Expense and Encumbrance accounts. If you use standard costing, and Oracle Bills of Material is
installed, all asset accounts are required. If you use standard costing, and Oracle Bills of Material is not installed, you are only
required to enter the Material and Material Overhead accounts.
Define Subinventory For Org SH 1
Subinventory
Code
SH FGI
SH Stage
Description
Status
Type
Finished Goods
Inventory
Stage
Active
Storag
e
Storag
Active
Locator
Control
Item Level
Quantity
Tracked
Selected
Dynamic
Selected
SH Main
Main Stores
Active
e
Storag
e
Entry
Dynamic
Entry
Selected
Setting OM System Parameters

Define a territory in Oracle Order Management
Overview
In this practice you will learn how to define a territory in Oracle Order Management
Login
Login to the database using the User Name and Password supplied by your instructor.
Choose Responsibility
Order Management Super User, Vision Operations (USA) Responsibility is selected.
Define a Territory
(N) Receivables > Transactions > AutoInvoice > Territories
1. Name: XX-Territory.
2. Description: Territory for XX.
3. Flexfield (list of values):
Area: APAC
Country: Your choice
Region: Your choice
4. Active: Enable
5. Effective Dates:
Start: Todays date
End: Leave blank
6. Save.
Setting OM System Parameters

Parameters in the Oracle Order Management Parameters window can be functionally grouped, and you can
define controls as easily as defining profile options.
OM System Parameters allows you to define new parameters and setting up the values for the parameters using
different sources like SQL and constant values.
This is step five of the Order Management Setup Steps, page 2-3.
Defining Parameters
Create and define parameters using the following attributes:
Parameter Code: Unique code for the new parameter
Name: Name of the parameter
Description: Description of the parameter
Category: Category the parameter belongs to. The category is controlled using the lookup type
"OM_PARAMETER_CATEGORY." To create a new category, add the lookup code in the lookup type
"OM_PARAMETER_CATEGORY" and then enter that lookup type in your parameter definition window.
Value Set: Value Set associated as the source of values. The possible value sets can have validation types of
NONE or TABLE. For seeded parameters please make sure that you use a value set that begins with "ONT."
Open Orders Check: Provides a control to allow or restrict changes to the parameter value once it is set for a
given operating unit.
Enabled: Controls the availability of the parameter. For seeded parameters this field is active for internal
users.
Seeded: Indicates whether the parameter is seeded or user-defined. This is only active for internal users.
To define Order Management system parameters:

1. Navigate to the Define OM System Parameters window. Order Management >
Setup > System Parameters > Define
Warning: You cannot have any open orders when performing updates to Order Management Parameters.
If open orders are found, a warning message displays. Select the OK button to ignore the Warning or select the
Cancel button to not commit changes.
2. Enter a unique code in the Parameter Code field.
3. Enter a name for the parameter in the Name field.
4. Enter a description of the parameter in the Description field.
5. Select the category from the Category field that the parameter belongs to.
This is controlled with a lookup. To create a new category, add the lookup code in the lookup type
"OM_PARAMETER_CATEGORY" and then enter that lookup type in the parameter definition window.
6. In the Value Set field, enter a value set associated as the source of values.
The possible value sets can have validation types of NONE or TABLE. For seeded parameters, use a value set
that begins with "ONT."
7. Select a value from the Open Orders Check field. This provides a control to allow or restrict changes to the
parameter value once it is set for a given operating unit.
Available options are Allow, Give error, or Give warning.
8. When the Enabled box is selected the parameter is available to use. For seeded parameters this field is active
only for internal users.
9. The Seeded check box indicates if the parameter is a seeded parameter or a user defined parameter. This is
active only for internal users.
10. Save your changes and click OK. To cancel without saving any changes, click
Cancel.
Setting Parameter Values

You can set up parameter values at the operating unit level by specifying following
attributes:
Operating Unit: Select the operating unit from the available list of values for which parameter values are to
be set.
Category: Select the category. On selection all the parameters for the selected category display.
Show All: Check this to see all the parameters of all the categories.
Parameter: Displays the name of the parameter for the selected category.
Value: Parameter value of the parameter. This field shows a list of values based on value set attached with the
parameter definition.
Description: Displays description of the parameter currently selected.
Note: If Multi-Org Access Control is enabled, you can manage System Parameter values across all Operating
Units accessible to you via your
MO: Security Profile.
To set up Order Management system parameter values:

1. Navigate to the Define OM System Parameters window. Order Management >
Setup > System Parameters > Values
2. Select the operating unit from the available list of values.
The Operating Unit field displays your default Operating Unit, however you can pick a different one from the
list of values to manage parameters in it.
3. The Category field identifies the category to which the parameter belongs.
The available parameters and their currently selected values display.
Select the Show All check box to display all the parameters for all categories.
4. In the value field next to the parameter you want to set, select a value.
The Value field displays a list of values available for each respective parameter.
The Description field describes the currently selected parameter.
5. Save your changes and click OK. To cancel without saving any changes, click Cancel.
Generic Parameters
Audit Trail
The audit trail parameter is used in order to capture audit history at either order entry or booking.
You can select either Disable, Enable when Order is Entered or Enable when Order is Booked.
The default is Null - Disabled. When the default is set, then you can also capture cancellation history of entered
orders. Previously, the processing constraint used to maintain a history of cancellations of orders when Require
Reason action was selected.
Customer Relationships
The default value is Single Customer.
Customer Relationship Parameter Setting Examples
The table below lists sample customers, their sites and business purposes.
Sample Customers, Sites, and Business Purpose
Customer
Site
Bill-to
A
X
Yes
B
Y
Yes
B
Z
No
C
W
Yes
Ship-to
Yes
No
Yes
Yes
Deliver-to
Yes
No
Yes
Yes
The table below lists the relationships that exist between these sample customers.
The data within the table will be used to describe how each of the profile option settings control the list of values
for available for order data fields when placing an order.
Relationships Between Sample Customers
Customer
Related To
Customer
A
None
B
A
C
None
Bill To Relationship
Flag
Ship To
Relationship Flag
Yes
Yes
If the parameter for Customer Relationships is set to Single, using the data within the second table, when
placing an order for Customer A:
The eligible Bill To, Ship To, and Deliver To location is Customer A, Site X If the parameter for Customer
Relationships is set to Related Customers, using the data within the second table, when placing an order for
Customer A:
The eligible Ship To and Deliver To locations are Customer A, Site X and Customer B, Site Z
The eligible Bill To locations are Customer A, Site X and Customer B, Site Y If the parameter for Customer
Relationships is set to All Customers, when placing an order for Customer A:
The eligible Ship To, and Deliver To locations are all customers and all of their ship-to sites and deliver-to sites
respectively, within the first table.
The eligible Bill To locations are all customers and all of their Bill To sites within the first table.
Item Validation Organization
In Order Management, the Item Validation Organization parameter indicates the Oracle Manufacturing
organization against which items are validated. Organization is synonymous with warehouse in Order
Management. You set the Item Validation
Organization parameter in the Parameters window, and can only set the value to the operating unit associated
with your current sign on responsibility. You must also define all transactable items in this organization.
Note: Before setting this parameter, you should first setup values for:
HR: Security Profile
HR: Business Group profile options. Valid inventory master organizations will be available based on values of
HRMS profile settings.
Invoicing Parameters
Over Shipment Invoice Basis
This parameter determines whether to invoice the ordered quantity or the shipped quantity for an over
shipment.
This parameter can be overridden for the parameter specific to customers or customer sites by setting a value in
the Customer window.
Default value is Shipped.
Receivables (AR) Required Steps For Order Management

The objective of this document is to provide step by step instructions on the setups required in
Receivables (AR) in order for you to create simple transactions.
If You Have Oracle Support Account You Can See That In URL:
_afrLoop=356715836428752&parent=DOCUMENT&sourceId=1101666.1&id=1067402.1&_afrWindow
Mode=0&_adf.ctrl-state=qwj6ljmuz_131
1. Define Common Accounts Receivable Configuration
Common Accounts configuration pertains to the Accounting Flexfield setup.

This is done in the General Ledger (GL) application. The assumption of this case study is that
you have already defined your accounting flexfield segments, and can create and complete
manual transactions using the Transaction Workbench.
If you need more information on how to set up your Accounting Flexfield, refer to the Oracle
General Ledger Implementation Guide, page 1-33.
Manage Receivables System Options
Realized Gains Account
01-740-7830-0000000
Realized Losses Account
01-740-7840-0000000
Tax Account
01-000-2520-0000000
Unallocated Revenue
Account
Cross Currency Rounding
Account
01-740-7826-0000000
Header Rounding Account
01-740-7827-0000000
The settings in System Options that impact AutoInvoice are in the Trans and Customers tab.
The following screenshot shows recommended settings for fields in the 'AutoInvoice' Section.
Also highlighted is the Grouping rule we defined earlier.

Log file message level = 10 provides the most detailed debug messages, and is useful when
you are debugging or troubleshooting.
Responsibility: Receivables Manager
Navigation: Setup > System > System Options
To see how to Manage Receivable System Options, please refer to Note 1068052.1, How To
Manage Receivables System Options For AutoInvoice.
Additional information on the Tuning Segments, refer to the Oracle Receivables User's Guide,
page 2-210.
14. Manage Receivables Accounting Periods
Open or close periods in your accounting calendar to control the recording of accounting
information for these periods. Since the objective of AutoInvoice is to create new transactions,
the goal is to have these transactions impact open GL periods.
Ensure that the GL_DATE value you provide in the next task is within an open period.
Navigation: Control > Accounting > Open/Close periods
To see how to Manage Receivable Accounting Periods, please refer to Note 1069057.1, How To
Manage Receivables Accounting Periods.
2. Manage Receivables Descriptive Flexfields
Oracle Receivables uses the transaction flexfields to uniquely identify each transaction line
that is imported though AutoInvoice.
AutoInvoice is capable of using information from four types of transaction flexfields:
Line Transaction Flexfield
Link-to Transaction Flexfield
Reference Transaction Flexfield
Invoice Transaction Flexfield
More details on each of these types is available in Note 1068344.1, Setting Up Receivables
Descriptive Flexfields.
For this case study, you need to setup a Line Transaction Flexfield as shown below.
Click on the segments button to create the following rows. The values in the field Column are
not shown completely, they are INTERFACE_LINE_ATTRIBUTE1 and
INTERFACE_LINE_ATTRIBUTE2 respectively.
3. Manage Receivables Profile Options
Several Profile options impact the behavior of AutoInvoice.

Please refer to Note 1069294.1, Setting Up System Profile Options For AutoInvoice for details.
4. Manage Transaction Types
The data you insert into the interface table will be associated to a particular transaction type.
Create an invoice transaction type which will be used when we insert data into the Interface
table.
Navigation: Setup > Transactions > Transaction Types
Name
Account
Receivable Account
01-000-1210-0000-000
Revenue Account
01-000-4504-0000-000
Unbilled Receivable Account
01-000-1210-0000-000
Clearing Account
01-000-1222-0000-000
Tax Account
01-000-2510-0000-000
Unearned Revenue Acct.
01-000-1210-0000-000
Note: If you also want to run a test case to import a Credit memo, create a Credit Memo
transaction type as shown below, otherwise you don't need to create a Credit Memo
transaction type.
To see more details on how to create new transaction types, please refer to Note 1067797.1,
Setting Up Transaction Types In Receivables.
Please note that if you want to use the AutoAccounting functionality (next task), and some of
the segments of the Account are sourced from the transaction type, then you must define GL
accounts in the Accounts tab.
5. Manage AutoAccounting Rules

AutoAccounting enables you to create default accounts for revenue, receivable, freight, tax,
unearned revenue, unbilled receivable, late charges, bills receivables accounts, and
AutoInvoice clearing (suspense) accounts.
In the following screen, the source for the third segment is 'Transaction Types'. When the
default accounting is generated for the Receivable account, the accounting flexfield will pull
the third segment from the Receivables account defined for the transaction type. If we crossreference this to the screenshot from the previous task, the value for the third segment is
1210, coming from 01-000-1210-0000-000 defined for Receivables account.
Navigation: Setup > Transactions > AutoAccounting
During AutoInvoice, you are interfacing data with the intention of creating complete
transactions automatically. Hence, you are advised to complete the setup for AutoAccounting
so that AutoInvoice can determine the GL accounts to use for your interfaced transactions,
and process them completely without errors and without the need for manual intervention.
To see how to manage and setup AutoAccounting, please refer to Note 1069052.1, Setting Up
AutoAccounting Rules In Receivables.
6. Manage AutoInvoice Line Ordering Rules

If you want the data in your interface table to be created in a particular sort order, define Line
Ordering Rules.
The following screenshot shows a Line Ordering Rule, that references the same fields we used
in the Line transaction flexfield defined in Task 2 above.
Navigation: Setup > Transactions > AutoInvoice > Line Ordering Rules
To see how to manage and setup AutoInvoice Line Ordering Rules, please refer to Note
1067965.1, How to Manage Line Ordering When Using Autoinvoice To Import.
7. Manage AutoInvoice Grouping Rules
Grouping rules specify attributes that must be identical for lines to be created as one
transaction. Grouping rules always include the mandatory attributes, and to this is added
optional attributes that you define in your grouping rule.
The following screenshot shows a Grouping Rule that uses the Line Ordering Rule defined
in Task 6 above.
Navigation: Setup > Transactions > AutoInvoice > Grouping Rules
To see how to manage and setup AutoInvoice Grouping Rules, please refer to Note 1067993.1,
How To Use Grouping Rules With AutoInvoice.
8. Manage Receivables Payment Terms
Payment terms let you define the due date to be calculated for transactions. When you
interface data, it is mandatory to provide either a TERM_ID or a TERM_NAME in the
RA_INTERFACE_LINES_ALL table (depending on how you have set up your transaction batch
source). Although there is a defaulting mechanism for payment term when entering
transactions manually in the form, this is defaulting is not available during AutoInvoice,
because it would significantly slow down the performance of the process.
The following screenshot shows a Payment term we will use in our interface data.
Navigation: Setup > Transactions > Payment Terms
To see how to manage and setup Payment Terms, please refer to Note 1069049.1, How To
Define Transaction Payment Terms In Receivables.
9. Manage Transaction Sources

Batch sources define default information such as transaction type and automatic numbering.
There are two types available: Manual and Imported.
AutoInvoice requires a batch of type Imported.
The following screenshot shows a Transaction source we will use to interface data via
AutoInvoice.
Highlighted below is the transaction type we created earlier, here we are associating it to this
Imported Batch Source.
Navigation: Setup > Transactions > Sources
Following screenshots show the sub-tab for the Transaction Sources form:
The AutoInvoice Options tab highlights the Grouping rule created earlier. The setup indicates
this batch will group data as specified in this grouping rule.
The following screenshots show the rest of the sub-tabs of this form, including Customer,
Accounting, Salescredit and other information. You need to define whether the data you will
interface provides the Value or the ID so that AutoInvoice can validate the data.
Customer Information tab:
Accounting Information tab:
Other Information tab:
Sales Credit Validation tab:
To see how to manage and setup Transaction Sources, please refer to Note 1068008.1,
Creating Transaction Sources Used For AutoInvoice.
10. Manage Receipt Classes and Methods

To default a payment method to the transactions you interface via AutoInvoice, you need to
define a Receipt Class and Method for your transaction to use.
Navigation: Setup > Receipts > Receipt Classes
To see how to manage and setup Receipt Classes and Methods, please refer to Note
1071284.1, Setting Up Receipt Class And Method For AutoInvoice.
11. Manage Receivables Customer Profile Classes

Oracle Receivables provides a profile class DEFAULT.
If necessary, you can define different customer profile classes to categorize your customers.
You can associate Customer Profile classes to customer records you create later.
By using a profile class you default certain attributes/fields into the customer records to make
customer maintenance more efficient.
The following screenshot defines a new customer profile class, to which we associate the
Payment Term from Task 8 and the grouping rule from Task 7.
Navigation: Customers > Profile Classes
To see how to manage and setup Customer Profile Classes, please refer to Note 1071218.1,
How To Define Customer Profile Classes For AutoInvoice.
Remit-To Address Setup

1. Setting Up a Remit-To Address
Define remit-to addresses to let your customers know where to send payment for their
invoices.
Receivables uses the addresses that you define in the Remit To Addresses window to provide
default remit-to information when you enter transactions.
Note: Receivables does not provide default remit-to information when you enter credit memos.
A. Define System Options and Profile Options
Navigation: Setup > System > System Options
Select the Miscellaneous Tab and enter values for the following:
If you check the Print Remit-To Address box in the System Options window, Receivables prints the
remit-to address that you define here on your dunning letters and statements. The width and height
(in characters) of your customer's remit-to address in your printed dunning letters is 8 characters
(height) by 30 characters (width)
Responsibility: System Administrator
Navigation: Profile > System
You can only enter information in the alternate name field when defining a Remit-to Address if the
profile option
AR: Customers - Enter Alternate Fields is Yes.
Receivables also uses the alternate name to sort customer names in certain reports if the profile
option AR: Sort Customer Reports by Alternate Fields is Yes.
B. Navigate to the Remit-To Address Form

Navigation: Setup > Print > Remit To Address > Create Remit-To Address
C. Select the Country

Default: Country defaults from the System Options Window
Impact: If you have implemented flexible address formats and the country you enter has an address
style assigned to it, Receivables opens a window in which you can enter address information in the
style most appropriate for that country.
Notice in the screenshot below, we change the country to Canada and the "Province" field is now
displayed.
d. Enter an Alternate Name
Enter an Alternate Name for this address (optional). This field is used in some reports. See step 1a
for more information.
The 'Alternate Address Name' is not rendered by default in Release 12. Users can use Forms
Personalization to personalize the address block by setting the Render flag to True for Alternate
Address Name field. See Bug BUG:8571973
e. Enter a remit-to Address
Note: The release 12 Receivables Implementation Guide incorrectly refers to an obsolete Postal Code
field on the Receivables System Options. This setup is no longer used in Release 12. Internal
Documentation Bug 9715200 will correct this in a future version of the manual.
Verify that your Remit-To address is associated with the proper Operating Unit
Once you have completed the address, select "Apply"

f. Re-Query the Remit-To Address
After you apply and save you will be returned ot the Remit-To Address search window. Enter the
country name and select Go.
g. Identify the Customer Addresses that will use this Remit-To
Select the radio button next to the address created in step 1e and then select "Create"
Optionally Enter a State and/or range of Postal Codes for each country. You can define multiple
assignments for a remit-to address that has the same country or state, but different postal code
ranges.
In the example below we first created a range that covers the western United States.
Next we created a range for the same Remit-To address that covers the entire country of Canada.
In this scenario one address could be used for all remittance in both areas.
1st Range:
2nd Range:
After adding both ranges the Remit-To will show as follows:
2. Assigning a Default Remit-To Address
Define default remit-to addresses to ensure that:
Receivables is able to provide a default remit-to address when you enter transactions
AutoInvoice will not reject invoices because it is not able to determine a remit-to address
You can only have one default remit-to address for each country or Country + State
combination.
In the example from step 1g, the address is the Default Remit-To address for Canada.
If we wished to also make this the default Remit-To address for the United States we could
create a third combination and fill in only the country of United States.
Note: It is a best practice to set up a default remit-to address even if you do not anticipate requiring
this value. If for example you have a default remit-to for the United States, you can also define
alternate remit-to address to be used with different zip-code ranges which take priority over the
default due to their more granular definitions.
3. Troubleshooting
Refer to Note 1101855.1 Troubleshooting Receivables Remit To Address Errors
Perform Oracle Inventory Setup

Perform all setup steps required for Oracle Inventory, then perform the following.
Set up internal locations for Human Resources for your Inventory Organizations
Map inventory organizations to internal locations
Organizations
Define at least one of the following:
Item validation organization
Organization as inventory source for internal orders
Organization for receiving purposes, if you use drop ship orders Your item validation organization can be the
same as your inventory source or your logical receiving organization, but you cannot use one organization for all
three purposes.
Note: If you change the location of your organization, after delivery details have been created, then the new
location will not take effect as the ship from location until new transactions are created.
Each delivery detail needs to be updated with the new location if the ship from location needs to be changed on
current deliveries.
Pick Confirmation
The Pick Confirmation Required check box affects the behavior of the picking process in
Shipping Execution. Navigate: Oracle Shipping > Set up > Organization Parameters >
ATP, Picking, Item- Sourcing tab.
If the Pick Confirmation Required check box is selected, then the system requires you to navigate to Inventory
forms or Pick Confirm using a mobile device to perform a manual pick confirmation of the move order that was
generated as a result of the Pick Release process.
The pick confirmation process acknowledges the transfer of the item being picked from its source location to the
default staging location.
If the Pick Confirmation Required check box is deselected (the default) for new installs, the system performs the
pick confirmation process automatically based on sourcing rules set up in Oracle Inventory.
Organization Parameters Window - ATP, Pick, Item-Sourcing Tab
Staging Subinventory
Create at least one staging subinventory for each organization. Move orders record the movement of pick
released material to staging subinventories. Staging subinventories should be Reservable .
Defining Shipping Document Sets

You can group related shipping documents and other reports in a set that can be printed at pick release or ship
confirm. You can include a variety of shipping documents in a set such as a Bill of Lading and Packing Slip Report
and determine the print sequence.
Shipping Execution provides three pre-defined (seeded) document sets:
All Pick Release documents: You can set the default Pick Release Document Set in the Pick Release tab of the
Shipping Parameters window
Ship Confirm documents: You can set the default in the Document Set field of the ship confirm window
Pack Slip only (at ship confirm): You can set the default in the Document Set field of the ship confirm window
Note: You can create additional document sets based on your business needs.
To define document sets:

1. Navigate to the Shipping Document Sets window.
Shipping Document Sets Window
2. Enter a Name and Description for the new document set.

3. Select the Usage for the document set:
Pick Release: For printing at pick release

Ship Confirm: For printing at ship confirm
4. Optionally, enter the Effective Dates for the document set.
5. The default Printing Method is parallel. This submits the reports for printing separately, each with a different
request ID.
If one of the reports in the document set fails to print, the other reports will print.
6. Enter a Sequence number.
7. Select Shipping Execution as the Application.
8. Select the Report Name to be included in the document set.
Selecting a report with PDF Output enables you to select a layout template.
If you select a report without PDF Output, then the Layout Template field is not updatable.
9. If you selected a report with PDF Output, then use the list of vales to select a Layout Template for your report.
Oracle XML Publisher enables you to extend various Oracle Shipping Execution reports to suit your business
needs.
The following list represents those seeded Oracle Shipping Execution report layout templates within Oracle
XML Publisher:
Bill of Lading
Commercial Invoice
Mailing Label
Master Bill of Lading
Packing Slip
Pick Slip
Vehicle Load Sheet Summary
10. Enter the number of Copies that you want.
If number of copies for a document is specified in the document set form, then copy count is used. If it is not
specified (that is, it is null), then the profile option Concurrent: Report Copies is used.
If the profile option Concurrent: Report Copies is also null, then 1 copy is printed.
11. Save your work.
To Edit document sets:

1.
2.
3.
4.
Navigate to the Shipping Document Sets window.

Query an existing document set.
Edit the existing Effective Dates, Sequence of documents, or documents contained within the document set.
Save your work.
Defining Pick Slip Grouping Rules

You can create grouping rules to organize how picking lines for released sales orders are grouped on to pick
slips.
For example, if you select Delivery as a grouping criteria, all picking lines for the same delivery are grouped
together on a pick slip. If there are multiple deliveries, multiple pick slips are created.
You can also define your grouping criteria further by selecting additional grouping attributes.
For example, if you select Delivery and Carrier as grouping criteria, picking lines for the same delivery and
carrier are grouped together on a pick slip.
Defining Release Sequence Rules

You can define release sequence rules to specify the order in which eligible picking lines are allocated to
Inventory during pick release.
You can release the picking lines by:
Order number
Outstanding Invoice Value
Scheduled Date
Departure Date
Shipment Priority
You can assign a priority level to one or more attributes with 1 being the highest priority and 5 being the lowest.
You can also define whether you want the picking lines released in ascending or descending order.
For example, if you select the Ascending button for Order, picking lines are released by ascending order
number--Order 1 is released first, then Order 2, Order 3, and so on.
If the Descending button is selected, the picking lines are released by descending Order number from highest to
lowest--Order 4 is released first, then Order 3, Order 2, and Order 1.
Note: You can define either the Outstanding Invoice Value attribute or the Order attribute for the release
sequence rule, but you cannot select both for the same rule. No two attributes can be given the same priority.
You can edit existing release sequence rules, but you cannot change the name of an existing release sequence
rule.
To define release sequence rules:
1. Navigate to the Release Sequence Rules window.

Release Sequence Rules Window
In the Rule field, enter a name for your rule.

Enter a Description.
Enter the Effective Dates for the rule.
Within the Release Priority region, specify a Priority (1, 2, 3, 4, or 5 where 1 is the highest priority and 5 is the
lowest) for one or all of the following attributes:
Order Number: Releases picking lines based on order number.
If you define a priority for the Order Number attribute, you cannot define a priority for the Outstanding Invoice
Value attribute.
Outstanding Invoice Value: Releases picking lines based on the outstanding invoice value.
If you define a priority for the Outstanding Invoice Value attribute, you cannot define a priority for the Order
Number attribute.
Scheduled Date: Releases picking lines based on scheduled date.
Departure Date: Releases picking lines based on departure date.
Shipment Priority: Releases picking lines based on shipment priority.
6. Select the Ascending or Descending toggle next to each attribute.
If you select the Ascending toggle next to the Scheduled Date attribute, for example, the picking lines with the
earliest Scheduled Date are released first.
If you select the Descending toggle, the picking lines with the most recent Scheduled Date are released last.
7. Save your work.
2.
3.
4.
5.
Defining Release Rules

Define the order in which picking lines are allocated to inventory.
You can create default pick release rules that are applied at pick release in the Release Sales Orders window.
Each rule can be set up with its own set of unique pick release parameters depending on the pick release criteria
required.
When pick release is run, the pick release is performed based on the parameters set up in the selected pick
release rule.
For example, you can create a specific rule that pick releases only backordered lines.
Note: Although you can also enter the pick release criteria at pick release time without creating a rule, creating
a rule is more efficient if you frequently run the same pick release.
Also, note that it is required when releasing using SRS or when using the Auto Pick Pack and Ship features.
To define release rules:
1. Navigate to the Release Rules window.

Release Rules Window - Order Tab
2. Enter a Rule name and the Effective dates.
Within the Order tab, select one or more of the following criteria for your query.
Select only the criteria that you want for the pick release:
3. Select the Orders and Order Types that you want included in the pick release:
Unreleased: The rule is applied to unreleased lines.
All: The rule applies to all lines not pick released.
Backordered: The rule applies only to backordered lines.
4. Enter the Order Number.
5. Select the Ship Set.
6. Optionally, select the Prior Reservations Only check box if you only want to pick release already reserved
quantity for lines.
This is allowed only for the allocation method of Inventory Only.
7. Select the Destination Type:
Region
Zone
Ship-To Location
8. Select the Customer and the Ship-To location for the customer.
9. Within the Item region select a Category Set, Category, and Item Number
10. Select the range of Scheduled Ship Dates and/or Requested Dates.
You can indicate whether you want the system to look at the scheduled ship date or the requested date.
You can then enter the number of days in the past or future, as well as the time, relative to current system
date that you want included in the release criteria.
This means that it is possible to set up a desired release window in terms of number of days rather than only
static dates.
If your organization has a calendar assigned, then the release rule will honor non-working days (for example,
Saturday, Sunday) to select delivery lines for pick release.
If the rule shown were applied to Organization V1 and that Organization has Saturday and Sunday as nonworking days on their organization calendar, then the following would occur:
If pick release is run on Thursday, the delivery lines for Thursday, Friday, Monday, and Tuesday (system date
+ 3 working days) are selected for pick release.
A negative value may be used in the Days field to include past dates which enables backordered lines to be
considered for pick release.
Alternatively, you can create a pick release rule using static dates by selecting the options Start On and End
On in the Scheduled Ship Dates region and the Requested Dates region.
Release Rules Window - Shipping Tab
Select the Ship Method to pick release by a certain ship method.

Select the Shipment Priority, and Ship From location.
Enable the Include Assigned Lines box if you want to include assigned lines in the pick release.
Select a Document Set to be printed during pick release.
Select a Release Sequence Rule if required.
From the list of values, select either Yes or No to Autocreate Deliveries.
If you selected Yes to Autocreate Deliveries, then in the Autocreate Delivery Criteria field select either Across
Orders or Within an Order.
18. Select either Yes or No in the Auto Pick Confirm field. Auto pick confirm is not allowed for the allocation
method of Cross Dock.
19. From the Autopack Deliveries list of values, select No if you do not want to utilize autopacking, select Yes to
enable autopacking, or
select Auto Pack Master if you want to utilize autopacking the item into its primary container and additionally
automatically packing the primary container into a defined master container.
You must setup container-item relationships to support the functionality for auto pack or auto pack master.
See: Oracle Inventory User's Guide.
20. Select a Ship Confirm Rule, if you want to utilize auto ship confirming.
21. Select Yes or No to Append Deliveries (consolidate delivery lines.)
Note: The appending limit must be defined as a value other than Do Not Append in the Shipping Parameters
window before you can append deliveries within a release rule.
Additional prerequisites for setting Append Deliveries flag include:
Oracle Transportation Planning is not installed
Organization must be specified
Autocreate Delivery Criteria must be Across Orders
Autocreate Delivery must be Yes
Auto Pick Confirm must be No
11.
12.
13.
14.
15.
16.
17.
Release Rules Window - Inventory Tab
22. Select the Warehouse (organization code) and default Pick Slip Grouping Rule for grouping the pick slips.
23. Optionally, enter a specific Subinventory for your rule.
This value determines which lines are considered for picking based on the subinventory name assigned to
the sales order line.
24. If Oracle Project Manufacturing is installed, specify a Project and Task for your rule.
25. If Oracle Warehouse Management is installed, then you can select an Allocation Method to be used:
Inventory Only: (Default) If you select this allocation method, then pick release allocates inventory
materials only.
Cross Dock Only: If you select this allocation method, then pick release allocates cross docking materials
only.
Prioritize Inventory: If you select this allocation method, then pick release checks for inventory availability
before all other sources, then allocates material from other sources if needed.
Prioritize Cross Dock: If you select this allocation method, then pick release checks for material available
for cross docking from all other sources other than Inventory, then allocates materials from Inventory if
needed.
The Allocation Method field cannot be updated unless Oracle Warehouse Management is installed.
See: Oracle Warehouse Management User's Guide and Oracle Warehouse Management Implementation
Guide for more information.
26. If Oracle Warehouse Management is installed and if you selected Cross Dock Only or Prioritize Cross Dock in
the Allocation Method,
then select a Cross Dock Criteria.
Enables a rule to be named, which limits the cross docking criteria. This field is disabled if the organization is
not WMS Enabled, or the Allocation Method is Inventory Only.
See: Oracle Warehouse Management User's Guide and Oracle Warehouse Management Implementation
Guide for more information.
27. Select Auto Allocate if you want to allocate the order lines automatically at pick release.
If Auto Allocate is selected, order lines are automatically allocated and reserved.
If not selected, you must allocate the lines and create reservations using the Inventory Transact Move Orders
window.
28. Select either Yes or No to Enable Plan Tasks if Oracle Warehouse Management is installed and you choose to
utilize the Plan Tasks feature.
29. Enter a Task Priority.
30. In the Pick From region, select the Subinventory and Locator of the default picking location.
Pick From Subinventory determines where the line items are picked/allocated from.
31. In the Default Stage region, select the Subinventory and Locator of the default staging area.
32. Save your work.
Shipping Parameters
You define the default values for basic shipping information such as units of measurement, pick release rules,
weight and volume calculations, and delivery grouping rules.
Shipping parameters are organization specific.
The parameters are arranged into the following tabbed regions in the Shipping Parameters window:
General: You can define the shipping weight and volume unit of measure classes, criteria for calculating
percent fill basis like weight, volume, or quantity, and shipping events at which export compliance screening will
be performed.
(Screening is only applicable if Oracle Shipping Execution is integrated with a third party ITM partner
application).
Pick Release: You can define Release Sequence rules and Pick Slip Grouping rules, limiting the number of
lines in the pick slip, printing behavior, document set to be printed at pick release, default staging subinventory,
locator, and decision points to autocreate delivery, auto allocation, enforcing ship sets and ship models, and task
planning at the time of pick release.
Shipping Transaction: You can define document sets to be printed at the time of ship confirm, ship confirm
rule, auto-pack options, goods dispatched (COGS) account and whether to enforce packing in containers.
Delivery: You can define the attributes forming the basis of delivery grouping for the organization.
You can also specify if delivery grouping is limited to lines within the same sales order or across orders. For
consolidation of deliveries, you specify the event at which appending will stop for the appending of delivery lines
to the delivery stops.
Transportation: If Oracle Transportation Execution is installed, you specify whether or not to Apply Routing
Rules automatically, define Freight Payment and Audit related parameters, and define Freight Rating parameters.
Defining Shipping Parameters

On the General tab, you define general Shipping Execution parameters such as weight and volume unit of
measure (UOM) class parameters, criteria for percent fill basis calculations, International Trade Management
(ITM) screening generation, and Oracle Workflow settings.
To define shipping parameters:
1. Navigate to the Shipping Parameters window.
Shipping Parameters Window - General Tab

2. Select the General tab.
3. Select the default Weight UOM Class from the valid UOM classes.
4. Select the Volume UOM Class from the valid UOM classes.
Note: The seeded values shown in the UOM class are created in Oracle Inventory.
5. Select the default unit of measure for the Percent Fill Basis of a container.
You can select Weight, Volume, or Quantity.

Percent Fill Basis is used to determine if containers have met their minimum fill percentage requirements.
If you select Weight or Volume, the calculation uses the item and container physical attributes in Oracle
Inventory.
If you select Quantity, the calculation uses the Container Load Relationship details to determine the maximum
number of items that will fit into the container.
6. In the Export Compliance Screening field, select one of the following: (Requires ITM Partnership Integration)
Not Required: Use this option if ITM Partner Integration is not used
At Delivery Creation: Use this option if Export Compliance Screening is to be enforced when the delivery is
created
At Ship Confirm: Use this option if Export Compliance Screening is to be enforced at ship confirm
At Delivery Creation and Ship Confirm: Use this option if Export Compliance Screening is to be enforced when
the delivery is created and at ship confirm
7. Enable Workflows by selecting whether you want Delivery workflows or None of the workflows enabled.
Specific tasks and output are enabled through the use of customized business objects. For example, the
workflow can be configured so that specific users receive a notification email when an overship or backorder
occurs.
8. Depending on your business needs, select the Raise Business Events check box.
Business events are optional. Individual Business Events can be enabled via the Business Events definition
window.
See: Shipping Execution Workflows and Oracle Workflow User's Guide.
9. Save your work.
Defining Pick Release Parameters

You can define default picking criteria that is used at pick release. You can also select the default settings for
auto-detailing and auto-creating deliveries.
To define pick release parameters:

Shipping Parameters Window - Pick Release Tab
2. Select the Pick Release tab.

3. Select the Release Sequence Rule.
During pick release, this rule determines the order in which delivery lines are allocated to inventory.
It appears as the default release sequence rule in the Release Sales Order window.
Note: It is recommended that you select the most frequently used release sequence rule; although it becomes
the default, you can change it any time you launch pick release.
4. Select the Pick Slip Grouping Rule.
This rule dictates how the released delivery lines are grouped on pick slips and how the pick slip number is
generated by pick release.
It appears as the default pick slip grouping rule in the Release Sales Order form.
Note: It is recommended that you select the most frequently used pick slip grouping rule; although it becomes
the default, you can change it any time you launch pick release.
5. From the Print Pick Slip list of values, select when you want the pick slips printed.
If you select At the End, pick slips will be generated when the pick release process has completed.
If you select Immediate, you specify the number of lines per pick slip.
Whenever this threshold is reached, a pick slip document is submitted for printing. Every time the threshold is
reached, another pick slip document will be submitted for printing. This continues until all lines meeting the
release criteria for a batch have been pick released. For example, if there are 20 custom defined lines, all pick
slips belonging to these 20 lines are printed in a single pick slip report. The number of pick slips printed depends
on the pick slip grouping rule and the custom defined lines. This choice has more impact on system resources.
6. Enter the Number of Pick Slip Lines to print on each pick slip.
If Print Pick Slip is Immediate, enter the maximum Number of Pick Slip Lines to print on each pick slip.
For example, if Number of Pick Slip Lines is 25 and pick release selects 40 lines, it prints two pick slips, one with
25 lines and the other with 15 lines.
7. Select the Default Pick Release Document set to be printed at pick release.
8. Select the Default Stage Subinventory.
The process of Pick Confirmation transfers move orders to this staging subinventory. The list of values displays
all subinventories in the organization. Staging subinventories should be reservable.
9. Select the Default Stage Locator.
Move orders move material to this locator. The list of values displays all locators in the Default Stage
Subinventory.
10. Select the Autocreate Deliveries option to specify your preference for delivery creation. You can override this
preference at pick release execution.
Selected: Pick release automatically creates deliveries based on the delivery grouping rules and assigns
delivery lines to them.
When pick releasing, the Autocreate Deliveries check box in the pick release form defaults to this parameter
setting if you enter a warehouse.
If you do not enter a warehouse, pick release uses this parameter setting from the organization of the
warehouse on each sales order line.
Cleared: Pick release does not automatically create deliveries.
Note: There are six descriptive flex field defaulting types supported when auto-creating deliveries:
SQL Statement (Not having references to:$FLEX$.<VALUE_SET_NAME> and:block.field),Constant, Current Date,
Current Time, Previous Segment, and Profile Option value.
11. Select Auto Allocate to automatically allocate delivery lines at pick release.
Selected: Pick release creates move orders and automatically allocates them.
Cleared: Pick release creates move orders.
You must manually allocate the order lines using the Inventory Transact Move Orders window.
12. Select Enforce Ship Sets and Ship Models to enforce that all lines in the Ship Set or Ship Model are released
together.
If you do not select the Enforce Ship Sets and Ship Model's check box, delivery lines for ship sets and ship
models are not validated during picking even if the ship set is specified on order lines.
Note: Depending on your business needs, you must set up the Enforce Ship Sets and Ship Models parameter for
each warehouse.
If you select the Enforce Ship Sets and Ship Models check box, delivery lines for ship sets and ship models are
validated during picking.
All order lines in ship sets are either released completely or auto-backordered during pick release.
If any portion is not available, then all lines in the entire ship set are backordered.
When you create the order, you must specify if you want to retain (or not retain) the ship set for the backordered lines.
You can do this in the Sales Order window in Order Management.
Note: Ship sets for non-transactable delivery lines are validated during ship confirm.
However, a ship set for non-transactable delivery lines is not validated during pick release because the item(s)
are not picked from inventory.
13. Select Plan Tasks if Oracle Warehouse Management is enabled within your organization.
See: Oracle Warehouse Management User's Guide.
Defining Shipping Transaction Parameters

You can define parameters for your shipping transactions such as default ship confirm document set, ship
confirm rule, auto-pack options, goods dispatched account and whether to enforce packing into containers.
To define shipping transaction parameters:

Shipping Parameters Window - Shipping Transaction Tab
2. Select the Shipping Transaction tab.

3. Select the Default Ship Confirm Document Set that prints as part of the ship confirm process.
The list of values displays the valid delivery document sets. See: Defining Shipping Document Sets .
4. Select a Ship Confirm Rule that your organization will use as a default for auto ship confirming.
Note: If you want to define a default ship confirm rule, then you must select Ship All as your option when you
define your ship confirm rules in the Ship Confirm window.

5. Select your Autopack Options. From the list of values, select either No, Yes, or Autopack Master.
No: Autopack will not be enabled
Yes: Autopack will be enabled and delivery line items will be systematically packed into LPNs based on
container-item relationships
Autopack Master: Autopack will be enabled and delivery line items will be systematically packed into LPNs
based on container-item relationships and the container will then be packed into another container, such as a
freight container for transport.
You can autopack delivery lines for a delivery into LPNs (containers).
When you autopack a delivery, the delivery lines are grouped together by shared attributes such as the Ship To
location, and are packed into LPNs based on the delivery grouping rules.
Once a delivery is packed, the delivery line information cannot be changed until you unpack the delivery.
The weight and volume is calculated at ship confirm automatically.
6. Select a default Goods Dispatched Account.
Use the Cost of Goods Sold (COGS) account for this organization.
The sales order issue transaction uses this account if the Oracle Order Management workflow cannot determine
one.
7. Select a value for Enforce Packing in Containers:
If you select Yes, ship confirm displays a warning when confirming a delivery or trip with unpacked delivery line
items.
You can bypass the warning and complete the shipment.
If you select No, ship confirm does not display the warning.
8. Save your work.
Defining Delivery Parameters

Delivery parameters enable you to define how to group delivery lines for a delivery.
The mandatory default attributes are Ship From Location and Ship To Location;
however, you can select additional optional grouping parameters that include:
Customer
Freight Terms
FOB Code
Intermediate Ship To location
Ship Method
The delivery attributes determine how delivery lines are grouped into deliveries when auto-creating deliveries.
For example, if the grouping attribute Customer is selected, the delivery lines are grouped into deliveries by
customer: for example, deliveries for Customer A are grouped into Delivery A, deliveries for Customer B are
grouped into Delivery B.
You can select more than one grouping attribute to refine your grouping criteria further: for example, if you
select Customer and Ship Method as grouping criteria, delivery lines with the same customer and carrier criteria
are grouped into deliveries.
If each optional grouping attribute is checked, the delivery's corresponding field cannot be updated if delivery
lines are assigned to the delivery. This ensures that the delivery lines' grouping criteria is not broken by a
different attribute value:
for example, if someone tries to select a different ship method.
If each optional grouping attribute is unchecked, its field in the delivery record can be updated until the ship
confirm stage.
For example, if you want to change the Ship Method in the delivery and do not need to enforce it as a grouping
attribute, you can deselect Ship Method.
Do not change these options if you have deliveries that are not ship confirmed.
To define delivery parameters:

Shipping Parameters Window - Delivery Tab
2. Select the Delivery tab.
3. Choose the attributes for grouping the delivery lines.

4. Optionally, select Autocreate Delivery Criteria if you enabled the Autocreate Delivery option on the Pick
Release tab.
Select Within An Order to autocreate deliveries whose lines all belong to the same sales order and match on
the Delivery Grouping Attributes.
Select Across Orders to autocreate deliveries across orders.
All selected delivery lines that match on the Delivery Grouping Attributes are eligible to appear on one delivery.
5. Select an Appending Limit.
The appending limit enables you to indicate the point at which you want to stop the system from adding lines to
a delivery (the point that ends the ability to merge deliveries).
You must set the appending limit to a value other than Do Not Append in order to use the Append Deliveries
option within Release Rules and the Process Deliveries SRS. The Appending Limits include:
Do Not Append
Start of Staging
End of Staging
Start of Packing (Oracle WMS enabled organizations only)
Start of Shipping (Oracle WMS enabled organizations only)
6. Save your work.
Ship Confirm Rule

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

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

Oracle Order Management enables you to advise your customers when items will be available based on current
on-hand inventory plus the expected incoming supply and outgoing demand. Calculating ATP requires as input
the item, the order quantity, the order quantity unit of measure and the request date.
In general the user will enter the item and order quantity on every order line. The request date and order
quantity unit of measure may be defaulted or manually entered.
ATP may be calculated for a single line, a group of lines, or a complete order. The results for a single line are
displayed in a single column in a small window. The results for multi-line ATP are displayed in a table. In both
formats, the following information is displayed:
Warehouse: Either the warehouse on the order line or, if the warehouse on the order line was blank, the best
warehouse as selected by the sourcing rules.
Request Date Qty: The quantity that is available on the requested date
Available: The order quantity, if ATP was successful. The available quantity, which will be less than the order
quantity, if ATP was not successful.
On-hand Qty: The quantity that is currently in the warehouse.
Qty Reservable: The on-hand quantity minus the quantity that is already reserved to other sources of demand.
Request Date: The date on the order line.
Available date: The date that the ordered quantity will be available.
It could be the request date if the order quantity is available on the request date, or it might be a future date
when the order quantity will be available
Error Message: Any error that occurred in calculating ATP.
For example, if the Check ATP flag for the item is not selected then this field will display ATP not applicable.
Substitute Item: If the requested item is not available and the requested quantity for a defined substitute is
available, the substitute item will be displayed. An additional tab, showing the availability of the substitute item,
is also displayed. 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.
The ATP Details window can also be opened from the Availability window by pressing 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 of this
document.
Responsibility: Inventory, Vision Operations USA

1. Navigate to the ATP Rules window.
(N) Inventory Setup > Rules > Available to Promise
2.
3.
Name:
ATP_Backward
Description:
ATP Backward consumption
Backward
Selected
Past Due Days Demand:
10
Infinite Supply:
User-defined time fence
Aggregate Order Promising Time Fence:
User Defined
Select the following Demand Sources:
4.
Sales Orders
Internal Orders
Discrete WIP
Repetitive WIP
Select the following Supply Sources:
5.
6.
Discrete WIP
Repetitive WIP
Internal Reqs
Supplier Reqa
Purchase Orders
On-hand Available
Interorg Transfers
(M) File > Save
(M) File > Close Form
Responsibility: CRM Administrator
Find Employee Number
(B) Search
(B) Start Import
(B) Save Resource

(B) Details
Responsibility: Order Management Super User, Vision Operations (USA)

Find an Employee
1.
2.
(N) Order Management > Setup > Sales > Salespersons

Within the Find Resources window, Resource region, enter the following in the Name field: Ahmed
Elshayeb,
(B) Find. Ahmed Elshayeb, employee number 10242 is displayed in the Resource Search Results
window.
Oracle Pricing
Overview
Adding items to a price list is a prerequisite for pricing items in a sales order. In this practice, you will
create a new price list (header) and then add price list lines that define the items and their list prices.
Price lists relate a selling price to a product. Price lists consist of price list lines, pricing attributes, and
a secondary price list and include information such as the price list name, effective dates, currency,
rounding factor, and shipping defaults such as freight
terms and freight carrier.
You may default a price list based on any one of the following:
An agreement
The sold-to organization
The ship-to organization
The bill-to organization
Order type
You can create multiple price lists. Alternatively, you may enter a specific price list on the order
header or at the order line level. For each price list, you can also assign a secondary price list, which
the pricing engine searches when it cannot find an item on
the primary list. Only one secondary price list will be searched for each primary list.
Creating General Information for the Price List
Responsibility = Oracle Pricing Manager, Vision Operations
Change Profile Option : QP: Item Validation Organization = Your Master Organization = SH MST
1. Navigate to the Price Lists window.
2.
(N) Pricing > Price Lists > Price List Setup
Enter the following price list header information:

Name = SH-Price List 1 (XX is a unique identifier)
Active = Selected
Description = Base price list
Currency = USD
Round To = -2 (defaults)
Effective Dates = Use todays date for start date. Leave end date blank.
Freight Terms/Freight Carrier = Leave blank
Payment Terms = 30 Net
3.
(B) Save.
Creating Price List Lines

4. Enter the first price list line using the following data:
In the Product region:
5.
Product Context = Item

Product Attribute = Item Number
Product Value = XX-Palm Pilot
Product Description = Defaults
UOM = EA (Each)
Primary UOM = Deselected
Line Type = Price List Line
Application Method = Unit Price
Value = $700
Start Date = Current date
Precedence = Defaults
Add the following items, one item at a time, to the price list.
Product
Context
Item
Item
Item
Product
Attribute
Item Number
Item Number
Item Number
Item Number
Product
Value
XX-Pager
XX- Phone
XX-Phone
Card
AS54888
Item
Item
Item Number
AS92888
UOM
Ea.
Ea.
Ea.
Primary
UOM
Deselected
Deselected
Deselected
Valu
e
$700
$500
$100
Ea.
Deselected
Ea.
Deselected
$159
9
$230
0
6.
(I) Save.
Overview
You can quickly create a new price list by copying an existing price list. Only active price list lines
(those with an effective end date later than the current date) can be copied. In this practice you will
copy your existing price list named XX-Price List 1.
Copying a Price List
Oracle Management Super User, Vision Operations
1. Navigate to the Copy Price List window.
(N) Oracle Management Super User > Pricing > Price Lists > Copy Price List
2.
Enter the following Copy From information:
3.
Price List = XX-Price List 1

Retain Effective Dates = Selected
Enter the following information in the Copy To region:
Price List = SH-Price List 2
Description = Adjusted by 10%
Global check box = Selected
4.
Submit the request
5.
Confirm that the request completed normally.
6.
(M) View > Requests
Repeat the preceding steps to copy the following price list from XX-Price List 1:
Copy To: Price List Name

SH-Price List 2
7.
Description
Manually updating a price list.
Query your XX-Price Lists to confirm that they were copied successfully.
Overview
You can quickly adjust list prices (such as a 10 percent increase) for selected items or all items on a
price list using the Adjust Price List window. In this practice, you will increase all prices on XX-Price
List 2 by 10 percent.
Adjusting a Price List
Responsibility = Oracle Management Super User, Vision Operations
1. Navigate to the Adjust Price List window.
2.
(N) Pricing > Price Lists > Adjust Price List

Adjust By = Percent
Value = 10
3.
4.
(B) Submit.
Verify that the request completed normally.
(M) View > Requests
5.
Query your XX-Price List 2 to confirm that the prices were adjusted successfully.
Overview
In this practice, you will learn how to add an item category to a price list.
Creating a Price List
1. Navigate to the Price Lists window.
2.
Enter the following information in the price list header using (all remaining information defaults
in):
Name = SH-Price List 4
Description = Accessories price list.
Round To = -2 (defaults from multicurrency list)
Effective Date = Todays Date
3.
(I) Save.
Adding an Item Category to a Price List

4. Navigate to the Add Items to Price List window.
5.
(N) Pricing > Price Lists > Add Items to Price List
Enter the following data:

Item Category Set = Inv.Items
Item Category = ELECTRONIC.ACCESSORY
Item Status = Active
Set List Price Equal to Cost From check box = Selected
Inventory Organization = SH1
6.
7.
8.
(B) Submit.
Record the Request ID number: __________.
Review the request status to ensure the concurrent request completed successfully.
(M) View > Requests
9.
Find your price list SH-Price List 4.
(I) Find > SH-Price List 4
10. Verify that many items have been added to your price list, including the item cost from M1
inventory organization.
Define Order Management transaction types to classify sales documents.

As an example, for each order type, you can assign a default price list, defaulting rules, order lines, return lines,
line types, workflow assignments, payment terms, and freight terms.
This is step twenty-two of the Order Management Setup Steps, page 2-3.
Note: You must first define any OM Line Transaction Types so that they can be assigned when defining your OM
Order transaction types.
Overview
In this practice, you will learn how to set up a transaction type with associated line type and assign
the workflow process.
Create a line transaction type for the order lines

Create an order transaction type for the order header
Assign line flows
Create a document sequence
Assign the document sequence to the order type
Creating a Line Transaction Type

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

Operating Unit = Vision Operations
Transaction Type = SH-StandardLine
Description = Standard Line Transaction Type
Sales Document Type = Sales Order
Order Category = Order
Transaction Type Code = Line
Effective Dates From = Todays date
3. (I) Save.
4. Create a new transaction type by entering the following information:
Transaction Type = SH-StandardReturn
Description = Standard Return Line
Order Category = Return
Transaction Type Code = Line
Creating an Order Transaction Type for the Order Header

4. (I) New. Create the order header transaction type.
Transaction Type = SH-Mixed
Description = Mixed Order Transaction Type
In the Sales Document Type field, select Sales Agreement or Sales Order from the list of
values (for Quotes, Returns and Releases, choose Sales Order).
Order Category = Mixed
Transaction Type Code = ORDER
Fulfillment Flow = Order Flow - Generic
. Note: Selecting a fulfillment flow assigns the workflow to the order header when the sales
order is created. This enables you to save the sales order.
5.
(T) Main.
Default Return Line Type = SH-StandardReturn
Default Order Line Type = SH-StandardLine
6.
(T) Shipping.
Shipping Method = DHL
Freight Terms = Prepaid
7.
(T) Finance.
Accounting Rule = Immediate
Invoice Source = ORDER ENTRY
Receivable Transaction Type = Inv-Hdwre-East
COGS Account = 01-740-7610-0000-000

Currency = USD
8.
(B) Assign Line Flows. Enter the following information:

Order Type = SH-StandardOrder
Line Type = SH-StandardLine , SH-StandardReturn
Process Name = Line Flow - Generic
Start Date = Todays date
Order Type = SH-StandardOrder
Line Type = SH-StandardReturn
Process Name = Line Flow - Return with Receipt Only, No Credit
9.
(B) OK. Exit the Transaction Types window.
Tax Calculation
You can calculate tax by selecting a Tax Date to base your tax rates on, choosing the tax, the tax schedule,
requested, promise, and system dates. You cannot set a value for the Tax Date field within the Sales Order
window, but you can decide to change or update the existing seeded Defaulting Rule for Tax Date.
Tax calculation in Order Management can occur at one of the following events:
Entry
Booking
Invoicing
Tax calculation for the above events can only be controlled at the order level (not at the order line level).
You specify when to calculate the tax for an entire order when you create Order Types within the Order
Management Transaction Types window.
The default value for Tax Calculation Event Code is null.
Null Tax Calculation Event is same as Entry.
For payment verification purposes (to include tax in the total authorized amount), specify Entry or Booking as
your Tax Event.
Note: The Copy Order functionality does not copy tax amounts; tax is recalculated for the new order.
For return orders (referenced or non-referenced returns), tax calculation occurs at the tax event defined for the
associated Order Management transaction type.
To calculate tax at any time, select Calculate Tax from the Actions button menu within the Sales Order or Order
Organizer windows.
Tax amounts are displayed:
Within the Sales Orders window, Main Tab. This is value is the current total order tax
Within the Sales Orders Lines window, Pricing tab.
This tax value is for each taxable order line Additionally, tax is always recalculated when tax-dependent
attributes change on the order line.
Tax Calculation at Entry

With tax calculation at Entry, tax is calculated as each order line is entered. This tax calculation is used, for
example, in businesses that requires the user performing order entry to view the total of the order, including tax,
so it can be quoted to a customer.
To include tax in Commitment Applied Amount, set the tax event to Entry.
Tax Calculation at Booking

When tax calculation occurs at Booking, tax is calculated on each of the booked order lines. This tax calculation
option is used, for example, in business that require tax visibility for booked orders, but who want to increase
order entry input times by not calculating tax at entry.
Tax Calculation at Invoicing

When tax calculation occurs at Invoicing, no tax calculations will occur within Order Management. Tax calculation
will occur in Oracle Receivables when the order or order line is invoiced.
For maximum performance, set the Tax Event as Invoicing.
Inclusive Taxes
When you create your tax codes, you can specify that the taxes are inclusive taxes (the tax amounts are already
included in the price of the item).
When the Tax Engine is called to calculate taxes, it will return inclusive taxes as well as exclusive taxes.
Any inclusive taxes returned are not added to the extended amount of the order line or displayed within the Tax
column of an order line. Order Management displays the estimated tax amount based on the tax date on the
order line. However, inclusive taxes are displayed when you View Tax Details from the Action button menu within
the Sales Orders Lines window.
You can perform a credit check including or excluding the estimated tax amount.
Overview
In this practice you will learn how view tax setups in Oracle Order Management
Tasks
1.
Navigate to the Transaction Types window in Order Management.
2.
Find the tax related fields and determine the tax events.
(N) Order Management > Setup > Transaction Types > Define
7. (T) Finance
8. Navigate to the Receivables Transaction Type field and use the list of values to view the applicable
options.
9. Navigate to the Tax Event field and use the list of values to view the applicable options.
Define Document Sequences for Order Numbering

Order Management uses AOL Document Sequence functionality for order numbering.
This is step eleven of the Order Management Setup You can define document sequences that automatically
generate numbers for your sales documents as you enter them. You can define a single document sequence to
assign unique consecutive numbers to all your sales documents, or you can define multiple document
sequences that are assigned to different order types. In the latter case, an order or return is uniquely identified
by its type and its number, since sales documents of different types may share numbers.
Note. Sales document numbers cannot contain alphabetic characters.
Gapless Order Number Source

Many countries have legal and audit requirements for order numbers to be contiguous.
You can set up a document sequence as gapless through the Define Documents Sequences window.
You can set up a gapless sequence for quotes, sales orders and Sales Agreements.
In addition, Order Management prevents deletion of orders that have been numbered using the gapless
numbering sequence.
The application uses locks to ensure gapless numbering.
If you are using gapless sequences, please save your changes frequently to minimize lock contention issues.
Note: Transactions may be gapless, however if all quotes do not become orders, the order numbers will not
appear gapless.
Manual Order Numbers

Order Management enables you to enter the order numbers for certain types of orders.
You can define a document sequence as manual and assign it to a desired order type.
This order type can be used on orders that you want to manually enter order numbers.
When an order number is specified for such an order, Order Management validates that it is unique for a given
order type.
Prerequisites
Set the profile option Sequential Numbering to Partially Used at the Order Management Application level.
Set your document sequences to Automatic, Gapless, or Manual.
To define document sequences for order numbering:

1. Navigate to the Document Sequences window. Order Management > Setup >Documents > Define.
Order Management Document Sequences Window

2. You can define the sequence to be Automatic, Gapless or Manual.
Automatic: The system automatically increment document numbers.
Automatic sequences do not guarantee contiguous numbering.
Gapless: The system guarantees that the numbers returned are contiguous.
Manual: The user must specify a unique document number.
For all types of numbering, Order Management validates that the number specified by you is unique for a given
order type.
For more information on AOL Document Sequences,
see the Oracle Applications System Administrator's Guide - Configuration, Document Sequences.
3. Enter a name for the document sequence. Specify Oracle Order Management as the Application.
4. Enter a starting number.
5. Optionally, enter effective dates for the document sequence.
6. Save your work.
Note: When sales document Types are defined, a corresponding Document Sequence Category will
automatically be created for order types and not for line types. The category created has the same name as the
order type.
You must navigate to the AOL Assign Document Sequence window to assign a sequence to the newly created
category.
If the Document Descriptive Flexfield is enabled, you need to specify the governing ledger.
The Document Method code should be left blank.
Creating a Document Sequence and Assigning It to the Transaction Type

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.
(N) Setup > Documents > Define
11. Enter the following information in the window:

Name = SH-STD-Order
Application = Order Management
Effective From = Todays date
Type = Automatic
Initial Value = 1
12. (I) Save. Exit the window.

13. Navigate to the Sequence Assignments window.
(N) Setup > Documents > Assign
14. (T) Document. Enter the following information:

Category = SH-Mixed
Ledger = Vision Operations (USA)
15. (T) Assignment. Enter the following information:

Sequence = SH-STD-Order
16. (I) Save and exit the window.
17. Enter a sales order with the Order Type = SH-Mixed.

The order number will be 1 and the line type will be defaulted to SH-StandardLine.
Overview
In this practice you will learn how to create a customer in Oracle Order Management
Tasks
3.
Define a new customer named XX-Big City with two sites:
Bill to address: 102 N. LaSalle, Cook County, Chicago, Illinois, 60610
Deliver to address: 487 Beverly, San Mateo County, Palo Alto, California, 94301
Create a Customer
SELECT
PROFILE_CLASS_ID,CURRENCY_CODE,min_fc_balance_percent,min_fc_balance_overdue_type,a
a.*
FROM hz_cust_prof_class_amts aa
WHERE 1=1
and PROFILE_CLASS_ID=0
and CURRENCY_CODE='EGP'
and min_fc_balance_percent IS NOT NULL
AND min_fc_balance_overdue_type IS NULL;
(N) Order Management > Customers > Standard
10.(B) Create.
11.Organization Name: SH-Big City. Leave Alias, D-U-N-S Number, URL, and Context Value.
12.Account Description: Enter a description for your customer.
13.Profile Class: Default.
14.Account Type: External. Leave all other fields, in the Account Information region, blank.
15.Country: United States.

16.Address Line 1: 102 N. LaSalle.
17.City: Chicago.
18.County: Cook
19.State: Illinois.
20.Postal Code: 60610. Leave all other fields, in the Account Site Address region, blank.
21.In the Business Purpose region, set Purpose to Bill To and check the Primary check box.
22.(B) Save And Add Detail.
23.(B) Create Site.
24.In the Business Purpose region, set Purpose to Deliver To and leave the Primary check box
unchecked.
25.(B) Apply.
A freight carrier is a commercial company that transports shipments to and from customers, suppliers, and
internal organizations.
You must set up each carrier's information as a party in Oracle Shipping Execution before shipping goods; you
should assign a carrier to each delivery. You also must associate a general ledger account with each carrier to
collect associated costs.
Before you set up the carriers:
Collect general information about each carrier
Determine the types of services that your carriers offer and that you use

(N) Shipping > Setup > Freight Carriers, Cost Types > Freight Carriers
1. (N) Shipping > Setup > Freight Carriers, Cost Types > Freight Carriers
2. Enter the following information:
3.
Name:
SH-Freight
Short Name:
SH-F
Enter the following in the Services tab
4.
Service Level:
Select a Service Level from the LOV
Mode:
Select the mode of transport from the LOV
(B) Organization Assignments
5.
Select Assigned check box for the Organization SH 1 and click Done.
Select Assigned to assign the ship method to the organization(s) that use it.
You can assign the ship method to more than one organization.
Note: If you want to assign the ship method to all of your organizations, click Assign All to have all organizations'
Assigned field selected. If you want to begin again with your assignments, click Unassign All to have all
organizations' Assigned field cleared.
6.
(M) File > Save.
Defining Freight Costs

You can define allowable freight costs and suggested amounts for shipments.
These amounts are applied at ship confirm or once a delivery line is planned.
You can add multiple freight costs to a shipment from the list of allowable freight cost types that you define.
Note: If necessary, you can override the freight costs and suggested freight amounts at ship confirm.
You can also define multiple freight costs for a specific freight cost type.
For example, if you want to track different types of insurance, you can create different insurance costs under the
insurance freight cost type such as liability insurance or shipping insurance.
When you add freight costs at ship confirmation for a foreign currency order, you can use either your functional
currency or the order's foreign currency.
If you use your functional currency, the freight charges are converted to the order currency through Oracle
Receivables.
Note: You should define all your freight costs in your functional currency for uniformity.
You can then modify the currency to match the order, and modify the amount on the Confirm Shipments window,
as necessary.
Prerequisites
Define your Freight Cost Type Lookups.
To pass freight costs to Order Management and Accounts Receivable so that the customer is invoiced
(for example, freight terms = Prepay and Add), then a pricing modifier and pricing formula are required.
To define freight costs:
1. Navigate to the Freight Cost Types window.
1.
(N) Shipping > Setup > Freight Carriers, Cost Types > Freight Cost Types
Freight Cost Types Window
2.
3.
4.
5.
Enter a Name for the freight cost.

Select the Type of freight cost.
Select a Currency for the freight cost.
Enter the Amount for the freight cost.
You can change this amount during ship confirmation. You can enter 0 as the amount.
6. Optionally, enter Effective dates for the freight cost.
7. Save your work.
Overview
In this practice, you will learn how to set up a defaulting sourcing rule for the Freight Terms attribute
for your customer XX-Big City Electronics.
You will then create a sales order to observe how the sourcing rule provides a defaulting value for
Freight Terms on the Sales Orders window.
In Oracle Order Management, defaulting sourcing rules enable you to automatically default attribute
values into sales order entities:
Sales order entities include groups of related attributes such as Order or Line.
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.
Setting Up a Defaulting Condition Template
Responsibility = Oracle Management Super User, Vision Operations (USA)
1. Navigate to the Defaulting Setup Entity Attributes window.
2.
3.
(N) Order Management > Setup > Rules > Defaulting
(I) Find.
Select entity = Order Header.
4.
(B) OK.
5.
(B) Defaulting Condition Templates. The Defaulting Condition Validation Templates window
appears.
Note: In the header region, ensure the following values are selected for the Application and Entity
values (if you do not see these values, do a query to find them):
Entity = Order Header
6.
7.
(I) New (place cursor in the Validation Templates region).

Enter a new validation template:
8.
Condition Name = SH-Freight Terms for SH-Big City Electronics

Description = Used for Freight Terms for Customer XX-Big City Electronics
In the Validation Rules region, create two validation rules for the template you added:
---
Group #
Attribute
Validation
Operation
Value String
Rule # 1
105
Customer
XX-Big City Electronics
Rule # 2
106
Currency
USD
9. (I) Save.
10. Close the Defaulting Condition Validation Template window.
Setting Up a Defaulting Sourcing Rule for the Freight Terms Attribute
12. Select Attribute = Freight Terms.
13. (B) Defaulting Rules. The Attribute Defaulting Rules window appears.
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
16. (M) Tools > Generate Defaulting Handler Package. This program generates the defaulting rules for
the attribute.
17. (I) Save.
Viewing the Freight Terms Attribute in the Sales Order Window
18. Navigate to the Sales Orders window.
(N) Orders, Returns > Sales Orders
19. (T) Order Information, (T) Main:

20. Enter a sales order for the following customer:
Customer = XX-Big City*
Order Type = Mixed
Currency = USD*
Note: *These conditions are required for the Freight Terms rule to be applied.
21. (T) Order Information, (T) Others.
22. On the Freight Terms field, confirm that the defaulting freight term value is To Be Determined. If
so, then the default rule was applied successfully.
Disabling the Defaulting Condition SH-Freight Terms for SH-Big City Electronics for the
Freight Terms Attribute
24. Select Attribute = Freight Terms.
25. (B) Defaulting Rules. The Attribute Defaulting Rules window appears.
26. Select the Defaulting Condition = XX-Freight Terms for XX-Big City Electronics
Enabled = Deselected
Note: If the Enabled check box for the defaulting condition is not selected, the defaulting
condition is disabled and the rules and condition associated with this condition are not used in
default rule processing.
27. (M) Tools > Generate Defaulting Handler Package.

28. (I) Save.
Viewing the Freight Terms Attribute in the Sales Order Window

30. (T) Order Information, (T) Main.

31. 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.
32. (T) Order Information, (T) Others.
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.
Overview
In this practice, you will learn how to create a discount modifier to apply a 5% discount.
You will then create a sales order and see the discount applied automatically.
Creating a Discount Modifier
QP: Allow Buckets For Manual Modifiers
Default Value: No
This profile option enables you to define buckets for manual line or group of line level modifiers.
Yes: Enables you to define buckets for manual line or group of line level modifiers.
No: You cannot define buckets for manual line or group of line level modifiers.
1.
2.
Navigate to the Define Modifier window.

(T) Main:
Modifier Type = Discount List
Number = SH-Discount 1
Active = Deselected (to start)
Automatic = Selected
Name = SH-Discount 1
Version =1
Description = 4
3.
(B) List Qualifiers. Enter the following qualifiers:

Qualifier
Context
Qualifier
Attribute
Operat
or
Value From
Customer
Customer Name
Global Communications
Modifier List
Price List
SH-Price List 4
4.
5.
6.
(B) OK.
This action applies the qualifier to the modifier and modifier lines defined in the Modifiers
Summary tab.
(T) Modifiers Summary tab:
Modifi Modifier Modifier
Start/
Pricing Phase
Incompatibility
er
Level
Type
Finish
Level
Numb
Dates
er
1
Line
Discount
Optional
10 List Line
(blank)
Adjustment
(T) Discounts/Charges:
Application Method = Percent
Value = 5
7.
A discount of 5% will be applied for all products ordered, but only when:
Buck
et
1
8.
Customer is Global Communications, and

Price list for the order is SH-Price List 4
Return to the header of the modifier and select the Active check box.
9. (I) Save.
Creating a Sales Order Using a Discount Modifier
Responsibility = Order Management Super User, Vision Operations
11. (T) Order Information, (T) Main:

Customer = Global Communications. Required sales order header information defaults from
your customer setup.
Order Type = Mixed
12. (T) Line Items:

Ordered Item = DD-00010-0040-01
Qty = 10
13. (I) Save. Note the order number 66399.

14. (B) Actions > View Adjustments.
15. (T) Adjustments. Note that the 5% modifier discount has been applied.
Manual Apply
Overview
In this practice, you create a Freight and Special Charge List modifier using formulas,
modifiers, and qualifiers. In this exercise you will define:
Two Special Charge Formulas
A Modifier List with four line modifiers that determine how to use the formulas
List and line qualifiers to determine eligibility
Note: For freight charge modifiers, you can apply freight charges corresponding to ONLY ONE
Charge name (such as "Freight Costs") even if several charge names qualify.
Assumptions
Oracle Order Management Super User responsibility

You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.
Note: Oracle Advanced Pricing screenshots are shown in the Solution section of this practice. If
you are running Basic Pricing, the pricing system software components restrict exposure of
advanced features in the pricing windows. Therefore, the screenshots may differ from the pricing
windows in the Oracle Application Vision database or comparable training or test instance you use
at your site to complete this practice.
Defining the First Formula
Responsibility = Oracle Order Management Super User, Vision Operations (USA)
1. Navigate to the Pricing Formulas window.
2.
(N) Pricing > Pricing Formulas > Formulas Setup
Enter the following:

Name = SH-Freight
Description = Dollar Amount x Constant .01
Formula = 1*2
Formula Type
Pricing Attribute
Pricing
Context
Attribute
Pricing
Volume
Item Amount
Attribute
Numeric
N/A
N/A
Constant
Compone
nt
N/A
Step
.01
3.
(I) Save.
Defining the Second Formula

4. Enter the next formula
Name = SH-Handling
Description = Item Quantity x Constant .05
Formula = 1*2
5. Formula Lines region:
Formula Type
Pricing Attribute
Pricing
Context
Attribute
Pricing Attribute Volume
Item Quantity
Numeric
N/A
N/A
Constant
6. (I) Save.
7. Run Build Formula Package
8. Build Attribute Mapping Rules
Compon
ent
N/A
.05
Step
1
2
Defining a Freight and Special Charge List Modifier

Note: For freight charge modifiers, you can apply freight charges of one Charge Name (such as
"Freight Costs") only once even if more number of charges qualifies.
7. Navigate to the Define Modifier window.
8.
(N) Pricing > Modifiers > Modifier Setup
(T) Main. Enter the following:

Type = Freight and Special charge List
Number = SH-Freight and Handling
Active = Deselected (to start)
Automatic = Selected
Name = SH-Freight and Handling
Version = 1
Start Date = Default
Currency =Defaults
Description = Enter a meaningful description
9.
(B) List Qualifiers.

Grouping
Qualifier
Number
Context
1
Modifier List
Qualifier
Attribute
Price List
Preceden
ce
Defaults
Operator
Value From
Order Type
Defaults
SH-Price List
1
Mixed
Order
10. (B) OK.

11. (T) Main, (T) Modifiers Summary.
Modifier
Leve
Modifier Type
Number
l
Freight1
Line
Freight/Special
Charge
12. (T) Discounts/Charges.
Charge Name
Formula
Freight Costs
SH-Freight
Start/End
Dates
Optional
Automa
tic
Selected
Application Method
Lumpsum
Pricing
Phase
50 (Line
Charges)
Buck
et
1
Valu
e
(blan
k)
13. (B) Line Qualifiers:

Grouping
Number
Qualifier
Context
Volume
Qualifier
Attribute
Precede
nce
Operator
Order Amount
Defaults
BETWEEN
Value
From
Valu
e To
1000
0
14. (B) OK.

15. (T) Modifiers Summary to create a new modifier line:
Modifier
Number
Freight2
Leve
l
Modifier Type
Start/End
Dates
Automati
c
Pricing Phase
Bucke
t
Orde
r
Freight/Special
Charge
Optional
Selected
70 (Charges:
Header/All
Lines)
(Blank
)

Charge Name
Freight Costs
Application Method
Lumpsum
Value
100
17. (B) Line Qualifier.

Groupin
g
Number
Qualifie
r
Context
Volume
Qualifier
Attribute
Order
Amount
Preceden
ce
Operator
Valu
e
From
Defaults
BETWEEN
Valu
e To
1000
0
18. (B) OK.

19. (T) Modifiers Summary. Create a new modifier line
Modifier
Number
Handling1
Lev
el
Modifier Type
Line
Freight/Special
Charge
Start/End
Dates
Optional
Automat
ic
Pricing
Phase
Bucket
Selected
50 (Line
Charges)

Charge Name
Handling Costs
Formula
SH-Handling
Application
Method
Lumpsum
Value
Blank
21. (B) Line Qualifier and create a Line Level Qualifier.

Grouping
Number
1
Qualifier
Context
Volume
Qualifier
Attribute
Preceden
ce
Operator
Order Amount
Defaults
BETWEEN
Value
From
0
Value
To
10000.9
9
22. (B) OK.

23. (T) Modifiers Summary. Create a new modifier line:
Modifier
Number
Leve
l
Handling2
Orde
r
Modifier Type
Freight/Special
Charge
Start/End
Dates
Optional
Automat
ic
Selected
Pricing Phase
70 (Charges:
Header/All Lines)
Charge Name
Handling Costs
Application Method
Lumpsum
Value
50
25. (B) Line Qualifier. Create a Line Level Qualifier:

Groupin
g
Number
Qualifie
r
Contex
t
Volume
Qualifier
Attribute
Order
Amount
Operator
Valu
e
Fro
m
Value
To
BETWEEN
1000
1
999999
9
Precede
nce
Defaults
Bucke
t
(blank
)
26. (B) OK.

27. (T) Main tab.
28. Select the Active check box.
29. (I) Save your work.

Creating a Sales Order Using the Freight and Special Charge Modifier
Responsibility = Oracle Order Management Super User, Vision Operations (USA)
31. (T) Order Information, (T) Main

Customer = XX-Big City Electronics
Order Type = Mixed
Required Header information defaults from your customer setup
Price List = XX-Price List 1
32. (T) Line Items

Quantity =10
33. (I) Save your work and note the order number 66402.
34. (B) Actions > Charges and Freight Costs to view your charges.
35. Close the window.

36. (T) Order Information.
37. (B) Actions > Charges.
38. Close the Charges window.

39. Increase the quantity ordered (such as quantity 20) of the order line so that the ordered amount
exceeds $1,000.
40. (I) Save.
41. (B) Actions > Charges and Freight Costs. There should be no changes provided that the Order Total
is above $1,000.
42. Close the window.

43. (T) Order Information tab.
44. (B) Actions > Charges.
There should be a line for Freight Costs of $750 and a line for Handling Costs of $100 (provided
the Order Total is greater than $1,000).
45. Save your work.
Discount Per Item And Quantity

For any 10 compact discs purchased by Jan 2016, the customer receives two Currency
Discount
1. Create a modifier.
Modifier Type: Discount
Modifier Level: Line

End Date: 31 Jan 2016
Product Attribute: Item Number

Product Attribute Value: DD-00010-0040-01
Volume Type: Item Quantity
Break Type: Recurring
Value From: 10
Application Method: Lumpsum

Value: 2
Test Scenario
Explain New Selling Price

Quantit
y
100
List
Price
20
Extended
Amount
2000
Lump sum
(100/10)=10 ---(10*2)=20
NEW Selling
Price
(200020)/100=19.8
Line 2

Quantity
List Price
20
25
Extended
Amount
500
Lump sum
NEW Selling Price
(20/5)=4---
(500-8)/20=24.6
(4*2)=8
Discount for Third Unit

Customers who buy two bottles of shampoo receive one Currency unit off of the third bottle of
shampoo.
Modifier Type: Discount
Product Attribute Value: DD-00030-0110-01
Volume Type: Item Quantity
Break Type: Recurring
UOM: Each
Value From: 3
Application Method: Lumpsum

Value: 1
Test Scenario

Quantit
y
100
List
Price
30
Extended
Amount
3000
Lump sum
NEW Selling Price
(100/3)=33--(33*1)=33
(300033)/100=29.67
Price Break
Scenario 1
All employees in Company ABC's mobile phone plan receive per minute discounts based on
minutes used, as follows:
Minute Discount Per Minute
s
($USD)
0-120
120-240
240-420
> 420
0.05
0.10
0.12
0.15
A customer who uses 150 minutes receives the following discounts:

- $ 0.05 per minute discount on 120 minutes
- $ 0.10 per minute discount on 30 minutes
Modifier Type: Price Break Header
- Product Attribute: Item Number
- Product Attribute Value: Minutes
- Volume Type: Item Quantity
- Break Type: Range
- Adjustment Type: Discount
2. In the Line Qualifiers window, create a qualifier for the price break modifier.
- Grouping Number: 1
- Qualifier Context: Customer
Qualifier Attribute: Customer Name

Operator: =
- Value From: Global Communications
-
3. In the Price Break Lines region, enter the break lines.

Value From
Value To
Application Method
0
120
Amount
120
240
Amount
240
420
Amount
420
Amount
Value
.05
.10
.12
.15
Test Price Break Scenario 1
Sales Order Change Management

Processing Constraints
Overview
Processing Constraints enable you to control changes to sales documents in Oracle Order Management.
This chapter describes the Processing Constraints framework in detail.
Introduction
Processing constraints are rules that control who can change what and when they can change it.
Processing constraints can prevent certain changes, but can also be set up to perform actions based on those
changes.
They can define actions that can result from these changes, such as requiring a reason for the change,
triggering an action in Audit Trail or Versioning, or raising an Integration Event.
With processing constraints, you can control:
Who can make changes based on responsibility.
A constraint (rule) may apply to all responsibilities, to only a list of constrained responsibilities or to all except a
list of authorized responsibilities.
More than just what can be updated. The following operations can be controlled:
Create, update, delete, cancel, and split all at the entity level. For example, given a set of conditions you may
not want to allow a user to create a new order line.
You can also control the update operation down to the attribute level.
For example, given a set of conditions, you could choose to allow update to the warehouse field of an order line
but not to the price list field.
Changes to entities. An entity roughly corresponds to a table or window.
The entities you can control in Order Management are:
Order Header
Order Line
Order Sales Credit
Line Sales Credit
Order Price Adjustment
Line Price Adjustment
Order Payment
Line Payment
Sales Agreement Header
Sales Agreement Line
Changes based on a group of conditions.
The conditions must be collectively true for the constraint to fire or prevent the changes.
The conditions may be based on either the state of a workflow activity (where the entity is in the flow) or a value
in a table.
A condition may also be based on a custom API, which means that you can call your own PL/SQL code to
evaluate the condition.
Multiple conditions can be combined using either AND logic (all the conditions must be true) or OR logic (at least
one of the conditions must be true.)
A custom message can display when an attempt is made to violate a constraint.
This chapter details the differences between Processing Constraints and the functionality in Order Entry that it
replaced - Security Rules.
It describes in detail the implications of selected values in the following forms:
Processing Constraints, Validation Templates and Record Sets. Finally, set up for processing constraints is
demonstrated using the following business examples:
No one can change the customer purchase order at the line level;
your company requires that one sales order can relate to only one customer purchase order.
No one can add a line to an order after any of the lines on the order have been invoice interfaced.
A reason is required to cancel an order line after it has been booked.
Only the Customer Service Manager can change the discount percentage on an order line after the line has
been shipped.
Require all return orders, identified by order type = Return, to be shipped to a central returns processing
facility.
Constraints for drop ship functionality enable you to control changes within the drop ship flow between Oracle
Order Management and Oracle Purchasing. See Processing Constraints, page 10-1 for details on these
constraints.
Versioning in Order Management uses constraints to enable automatic versioning.
You can use validation templates for example to drive versioning by transaction type as a condition.
By using the processing constraints and workflow activity, you can increment the version and determine the
statuses available to version, which give you complete flexibility setting up versioning. See: Versioning, page 1021
Background
Security Rules provide functionality to control changes to orders.
However, they have certain limitations both in the philosophy and in implementation.
In Order Management there is a processing constraints framework usable by other products.
This framework provides to you the ability to:
Control changes based on who is trying to make them (by responsibility)
Define constraining conditions based on the state of related objects (for example, define a constraint on a line
based on the state of the order)
Control changes based on the value of a field - see Validation Templates section below
Call custom PL/SQL code to determine whether a condition is true
Constrain operations at any point in the process flow. In prior releases you could only control operations for
certain hardcoded cycle actions.
Terminology
Processing Constraints are very powerful and setting them up is not difficult; however, knowledge of the
following terms is helpful:
Entity
A group of related attributes that roughly correspond to a table or a window in Order Management.
The entities that can be managed using processing constraints are Order Header, Order Line, Order Price
Adjustment, Line Price Adjustment, Order Sales Credit, Line Sales Credit, Order Payment, Line Payment, Sales
Agreement Header, and Sales Agreement Line.
Entities correspond to 'objects' in the old security rules.
Attribute
A field or column that belongs to an entity.
For example, the ordered unit of measure is an attribute of the Order Line entity.
Attributes correspond to fields in the old security rules.
Operation
An action that you can take on an entity. The operations that can be controlled by processing constraints are
Create, Update, Delete, Cancel and Split.
Processing Constraints Framework
A generic facility that will enable you to define processing constraints for application entities and attributes.
It includes the set of APIs that will enable you to query the existence of any constraint against the operations
you wish to perform on that entity or its attributes.
Seeded constraints have the System box checked and cannot be modified.
Validation Template
Names a condition and defines the semantics of how to validate that condition.
These validation templates can be used in the processing constraints framework to specify the conditions for a
given constraint.
Record Set
A record set is a set of records that are bound by some common attribute values (for example all lines on an
order).
In the processing constraints framework, when you define constraining conditions, you may specify a record set
to be validated for a given
condition as defined by its validation template.
Scope
Given a record set and a condition, the scope (Any/All) defines how the validation should be performed on
records of the record set. "All" requires the validation to be TRUE for every record in the set. "Any" requires the
validation to be TRUE for at least one record in the set.
Conditions
The test(s) which must be passed for a constraint to be active. For example, a condition for a constraint might
be that the order is booked.
Defining Processing Constraints

Processing Constraints Window Conditions Tab
Navigate to the Processing Constraints window.

Order Management > Setup > Rules > Security > Processing Constraints.
Note that the window is divided into several regions.

The top region has fields for the Application and the Entity.
Any one of the OM entities are the valid values for the entity field.
This is used for queryingyou cannot create new entities.
When you query an entity you will see all the constraints defined against that entity.
Constraints
The Constraints region is where most of the details of a processing constraint are defined.
The region enables you to view the seeded constraints, view, or update the constraints that were created for
your company.
You can create new constraints, but you cannot change the seeded constraints with the system check box
marked.
Operation Field
The Operation field can have the values of Create, Update, and Delete for any of the entities, Cancel for Order
Header and Order Line entities only, and Split for the Order Line Entity only.
Attribute Field
The Attribute field can only be used if the operation selected is UPDATE.
You may enter a value here, and the constraint will only apply to that field.
For instance you may define a constraint that affects only the warehouse field on the order line.
If the Attribute field is left blank the constraint will be in effect for all the attributes of the entity.
For instance, you may define a constraint which prevents updates to any of the fields of an order line.
Please note that only when constrainable attributes are updated, processing constraints execute.
All attributes are not constrainable, therefore processing constraints will not execute for such attributes, even
though the operation selected is UPDATE.
Action Field
The Action field allows you to select the action to be taken if the constraining conditions are met.
Note: There is no unique Require Reason action; it must be used in conjunction with Versioning or Audit.
Processing Constraints Window with User Action Menu Displayed
The combination of Actions that can be selected are:

Generate Version, Require Reason and Raise Integration Event
Generate Version and Require Reason
Generate Version
Require Reason, History and Raise Integration Event
Require Reason and Require History
Require History
Raise Integration Event
Actions of Require Reason and Require Reasons and Require History for audit history are supported only for the
UPDATE operation.
Constraints are evaluated in the following order (Only one constraint may take effect for a change):
User Action
Not Allowed.
Generate Version, Require Reason and Raise Integration Event. This activates automatic versioning.
Generate Version and Require Reason. This activates automatic versioning.
Generate Version. This activates automatic versioning.
Require Reason, History, and Raise Integration Event. This activates Audit Trail to capture changes.
Require Reason and Require History. This activates Audit Trail to capture changes.
Require History. This activates Audit Trail to capture changes.
Raise Integration Event. This can be used with versioning.
During implementation any action which includes "Raise Integration Event" may be selected. This event is
presently used by XML processing and can be used by any other product.
Actions that Require Reason take precedence over actions that do not.
Example
Assume that both versioning and audit constraints apply to update of price list. Only version is captured as it
takes precedence and audit history is not available for this update.
However, if audit constraint is on a different attribute like update of payment term and you change the payment
term and price list, both version and audit history are captured.
Applies To Field
The Applies To field is used to define whether the constraint is applicable in the
Negotiation or Fulfillment transaction phase. If the field is blank, then it is applicable to
both phases.
Enabled Field
The Enabled field indicates whether the current Constraint is active.
This allows constraints to be temporarily disabled if necessary.
System Changes Field
Use the System Changes field to indicate if system changes are allowed even if the constraining conditions are
met.
The system changes here refer to an attribute initially getting a default value or being re-defaulted when a
source attribute changes.
This is applicable only for attribute or field level UPDATE operations.
The possible values are:
Never after Insert: System changes are allowed to this field only if the entity has not yet been saved to the
database.
This is the default value.
Always: System changes are always allowed on the attribute
User Changes Field
Use the User Changes field to indicate when the user performing the operation is
constrained. This is applicable only for attribute or field level UPDATE operations.
Never after Insert: You can change this field only if the entity has not yet been saved to the database. This is
the default value.
Always: You can never enter a value for this attribute, even if the entity (for
example an order) is being created for the first time.
System Field
The System Field indicates if a constraint included with the OM system is user updateable. System constraints
help prevent data integrity problems and cannot be updated. Any operation, field, action, or list of
responsibilities attached to these constraints cannot be modified. However, additional validation conditions can
be included as long as they do not have the same group number.
Enabled Field
The Enabled field indicates whether the current Condition is active.
This allows conditions to be temporarily disabled if necessary.
Note that if all conditions are disabled and the constraint itself is not disabled, the constraint always applies for
that change.
Care must be taken to ensure that the disabling of conditions does not introduce problems in the business flow.
The bottom section of the window has two tabbed regions - the Conditions region and the Applicable to region.
Conditions
The Conditions region allows you to define the condition(s) that must be true for the constraint to fire. Unless the
group of conditions are true, the constraint will not be active.
Group Number Field
The Group Number field determines whether AND or OR logic is used to combine conditions. For conditions that
should together evaluate to TRUE (AND conditions), enter the same group number. Define OR conditions by
using different numbers.
Scope Field
The Scope field is evaluated with the Record Set field to determine if the condition is true.
ANY: If the record set on this validation condition can select multiple records, then this condition should be
TRUE for AT LEAST ONE of the records. For example you can evaluate a condition against any line on an order: If
ANY line on the order is canceled.
ALL: If the record set on this validation condition can select multiple records, then this condition should be
TRUE for ALL the records. For example you can evaluate a condition against all lines on an order: If ALL lines on
the order are canceled.
Validation Entity
The Validation Entity is the one for which the condition is evaluated.
The validation entity can be the constrained entity (displayed in the Entity region) or any related entity.
For example, the constrained entity could be an order line and the constraint could be evaluated based on
characteristics of the validation entity order header.
Select the Record Set and based on the selected scope, the conditions will be evaluated for any or all of the
records in the set.
An example of a seeded Record Set is a ship set.
You may define additional record sets as needed.
Note: If the validation entity on the condition is different from the constrained entity, then only the record set
based on the primary key
for the validation entity will be available in the LOV Check the NOT Box to create a NOT condition.
For example if the condition is Booked, checking this flag will evaluate the condition NOT Booked.
System Field
The System field is checked for the conditions that were included with the OM system and are not user
updateable.
You cannot define new AND conditions with the same group number as a system condition.
User Message Field
The User Message field displays when an attempt is made to violate a constraint. The message is specific not
just to the constraint but also to the specific condition that was violated. For example, you can create a user
message that states: "line has been booked."
If the constraint is set up to prevent any update to the item field on the order line if the line had been booked,
the complete error message displayed at run time is: "You are not allowed to update the item; line has been
booked."
The following screen shows the Processing Constraints window again, this time with the Applicable To tab
selected. Use this tab to define the responsibilities the constraint applies to.
Processing Constraints Window, Applicable Tab
If the button for All Responsibilities is selected, then the constraint will apply to all users.
No one will be able to perform the constrained action. All seeded constraints are applicable to all responsibilities.
If you select the Authorized Responsibilities button, then only the responsibilities that you list will be allowed to
perform the action.
All other users will be stopped from performing the action by the constraint.
If you select the Constrained Responsibilities button, then all users except for the responsibilities defined will be
able to perform the action. The users that you list will be stopped from performing the action by the constraint.
There are two other forms that are used in setting up processing constraints.
These are the Validation Templates window and the Record Sets window.
The validation templates and record sets you create, as well as the seeded ones can be used in the Processing
Constraints window as described above.
Note: After updating constraints and/or conditions, close and reopen the sales document windows for the
updated constraints to apply correctly.
In this demonstration, you will learn how to set up a processing constraint that prevents a sales order
header from being updated when the order is booked or when there are order lines created.
Processing constraints control who can change what and when they can change it.
Processing constraints can prevent certain changes, but also can perform actions based on those
changes such as requiring a reason for the change, triggering an action in Audit Trail or Versioning, or
raising an Integration Event.
Responsibility: Oracle Management Super User, Vision Operations
1. (N) Order Management > Setup > Rules> Security > Processing Constraints
2. Query in the top of the window (To query, press CNTRL + F11):
Entity = Order Header
3.
Create a new line on the Constraints region:
4.
Operation = Update
Attribute = Order Type
User Action = Not Allowed. This means the constrained operation cannot be performed.
Leave System Changes and User Changes fields blank.
Enabled check box = Selected
Create a new line on the Conditions tab:
Group Number = 101
Scope = Any
5.
Validation Entity = Order Header

Record Set = Order. The record set corresponds to the entities to which the constraints
process should apply the condition.
For example, if you enter the order line record set Line, the condition is evaluated against
the order line in question. If you enter the order line record set Order, the condition is
evaluated against any or all (depending on the scope) lines of the order in question.
NOT check box = Deselected
Validation Template = Booked
Enabled check box = Selected
User Message = The order is booked.
Create a second line on the Conditions tab:
Group Number = 102
Scope = Any
Validation Entity = Order Header
Record Set = Order
NOT check box = Deselected
Validation Template = Lines Exist
User Message = The order has lines.
Applying the Processing Constraint to a Sales Order (Constraint Based on Booked Orders)
7. Enter the sales order header using the following information (all remaining information defaults
in):
8.

Order Type = Order Only
In the Line Items tab, enter the following line items:
Ordered Item
Quantity
XX- Phone
XX-Palm Pilot
9. Save the sales order.

10. Book the order.
11. On the Order Information tab, Main subtab, change the order type:
Order Type = Drop Shipment
12. Save your work.
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)
14. Enter the sales order header using the following information (all remaining information defaults
in):
Order Type = Order Only
15. In the Line Items tab, enter the following line items:
Ordered Item
XX- Phone
Quantity
2
16. Save your work.

17. On the Order Information tab, Main subtab, change the order type:
Order Type = Bill Only
18. Save your work.
Note: You should not be able to save your changes because the second processing constraint
condition does not allow you to update the Order Type for orders with existing order lines.
Roles and Users

Shipping Execution provides data access controls called roles that control users' access to the Actions list and
Tools menu in the Shipping Transactions form and the Quick Ship window. Roles also control ship confirm error
and warning messages for breaking ship sets, missing inventory controls, and breaking proportionality of ship
model complete. Roles are assigned to users using grants that control access to view or edit specific shipping
data or actions.
This is useful, for example, if you want to assign a grant to inexperienced users that provides view-only access
or assign grants that prevent unwanted actions such as unintentional pick releases across multiple
organizations.
Note: Roles provide data access controls for the Shipping Transactions form and the Quick Ship window. If you
want to restrict user access to other windows like the Pick Release or setup windows, you can edit the Shipping
menus in Shipping Administration.
For each role, select the following data access controls that control Edit and View access to shipping entities:
Data Access Edit enables you to edit and view the data
Data Access View enables you to browse the data
Data Access None prevents you from editing and browsing data and performing actions
A role can provide either view-only, edit-only, or a combination of view and edit access depending on how you
setup the role. You can create customized roles by defining the access controls you want.
During the setup for each role, you enable or disable actions by selecting or deselecting the check box next to
each action.
Note: If no data access control is selected, the user cannot edit or view the selected action.
Note: Ship confirm error and warning message configuration, on the Message tab, does not use data access.
After you have defined a role you can assign it to a user through a grant. A grant defines both the user's role and
related information about the grant including the date, and the organization(s) to which the grant applies.
The system administrator or super user is responsible for defining roles and assigning the grants to users.
Defining a New Role

Shipping Execution enables you to define new roles by selecting the data access controls that you want. You can
define a new role by:
Copying an existing role: An existing role can be copied to create a new role.
The copied role has the same data access privileges of the original, but if desired, these privileges can be edited
for the new role. Save the new role with a different name than the original.
Manually defining a new role: You can create a new role in the Shipping Execution Role Definition window by
selecting the data access controls to trips, stops, lines, and deliveries. Save the new role with a unique name.
After you have created the new role you can assign it by grant to a user.
Note: In an environment that does not have Oracle Transportation Execution installed, five privileges related to
Oracle Transportation Execution are grayed out in the Shipping Execution Role Definition window.
The following privileges are strictly related to Oracle Transportation Execution, and therefore, do not apply if this
application is not licensed: Send Outbound Message, Select Carrier, Get Freight Costs, Cancel Ship Method, and
View Message History.
To define a new role:
1. Navigate to the Shipping Execution Role Definition window.

Shipping Execution Role Definition Window
2. Enter the Name of the role.

3. Enter a Description for the role.
4. In the Trips tab, in the Data Access field, select:
Edit to provide edit access for the trip records

View to provide view-only access for the trip records
None to disable access and actions
5. Enable each action that you want the user to have permission to perform.
Note: As a shortcut, choose the Disable Actions button to disable all the actions or the Enable Actions button to
enable all the actions.
6. Select the Stops tab.

Shipping Execution Role Definition Window - Stops Tab
7. In the Data Access field, select:
Edit to provide edit access to the stop records

View to provide view-only access to the stop records
None to provide no access to the stop records
9. Select the Deliveries tab.

Shipping Execution Role Definition Window - Deliveries Tab
Edit to provide edit access to the delivery records

View to provide view-only access to the delivery records
None to provide no access to the delivery records
Note: Use the Actions View Message History, Send Outbound Message, Select Carrier, Get Freight Costs, and
Cancel Ship Method if you have Oracle Transportation Execution installed.

12. Select the Lines/LPNs tab.
Shipping Execution Role Definition Window - Lines/LPNs Tab
Edit to provide edit access to the lines/LPNs records

View to provide view-only access to the lines/LPNs records
None to provide no access to the lines/LPNs records
Note: The delivery records also include delivery legs and packing slips.

15. Select the General tab.
Shipping Execution Role Definition Window - General Tab

17. Select the Message tab.
The Message tab enables you to configure ship confirm messages for Breaking Proportionality of Ship Model
Complete, Breaking Ship Sets, and Missing Inventory
Controls. See: Message Configuration in the Shipping Execution chapter of the Oracle Order Management
Implementation Manual.
18. From the Activity list of values, select Ship Confirm.
19. For each Message, select either Error or Warning depending on your business needs.
Note: The System Defaults are Warning for each Message.

20. Save your work.
Copying an Existing Role

Copying a role is useful for creating a new role based on the privileges of an exiting role.
Because copying automatically duplicates the original role, it saves you time from manually entering all the
control privileges of the original.
You can edit the privileges of the copied role, save the role with a new name, and assign it to users.
To copy an existing role:
Navigate to the Shipping Execution Role Definition window.

Find the role that you want to copy.
Click New Record to create a new record.
From the Edit menu, select DuplicateRecord Above to create a new role based on the privileges of the
original.
1.
2.
3.
4.
5. Save the new role.
Granting a Role to a User

You can grant a user a role in one organization or all organizations for a period of time.
The role is assigned to a user by a grant. The grant is specific to a particular user and defines the role(s)
assigned to the user, the organization where the grant is effective, the start date and optionally, an end date.
More than one grant can be assigned if the user requires different access controls to more than one
organization.
The start and end dates for grants can overlap.
For example, if a user requires full-access privileges to three organizations and view-only access to a fourth, the
user must be assigned four grantsone for each respective organization (three full-access and one view-only
grant).
However, if only one grant is assigned, that grant becomes the default grant for the user.
In addition, the grant has the following requirements:
A grant may or may not have one inventory organization selected.
Many grants can be assigned for each role.
A user can have one or more grants. If the user does not have any grant (expired, effective, or future), the
default is view-only access to all organizations. If the user has grants, the user's access is controlled by the
effective grants. If there are overlapping grants in the same organization or an intersection of grant date ranges,
the union of grant privileges controls the user's access.
A grant cannot be designated as the default grant. A role can be assigned to a user that spans all
organizations instead of granting a unique grant per organization. If an organization is not specified, the grant is
applicable to all organizations.
Warehouse Organization
A grant can have one or all inventory organizations. If an organization is not specified, the grant is applicable to
all organizations.
For example, you can use grants to prevent a shipping clerk from assigning freight costs or planning a delivery in
one or all organizations.
Note: Use caution when creating grants for all organizations (when no specific organization is selected). For
example, if a user has a grant to view all organizations and a grant to perform actions on one organization, the
union of these grants will enable the user to perform actions in all organizations.
Changing Organizations in the Shipping Transactions Form
If a user's effective grants are single organization, the user can select an organization when opening the
Shipping Transactions form or from the Tools menuChoose Organization. If all effective grants are in the same
organization, the Shipping
Transactions form defaults to that organization.
Effective Dates for a Grant
Optionally, in the Start and End Date fields, you can enter a start and end date for the grant to assign it for a
specific period. For example, you can assign temporary employees a grant that is effective for the duration of
their assignment. The date status for a grant can be endless, future or expired:
Endless: If you enter a start date but no end date, the grant is effective for an indefinite period.
Future: You can specify start and end dates for a grant so that the grant is effective only between those dates.
For example, a temporary employee can be assigned a role that is effective for the duration of his/her contract.
The start date can be a current or future date. You cannot back-date the date: for example, you cannot enter a
start date of yesterday.
Expired: When the end date of the grant expires, the user cannot perform the job duties unless assigned a new
grant by the system administrator.
Note: If the user has expired and future grants but no effective grants, the user has no access to the Shipping
Transactions form. If required, you can leave a gap between an expired grant and a future grant: for example,
one grant can expire in June and another can begin in August.
To grant a role to a user:
1. Navigate to the Shipping Execution Grants window.
Shipping Execution Grants Window
2. In the User field, select the user's name.

3. In the Role field, select the role that you want assigned to the user.
Note: To view the available privileges for a selected role, click Edit Role to display the Shipping Execution Role
Definition window.
4. In the Org field, select the organization to which the grant is assigned (optional).
A user can be assigned only role per warehouse (organization). However, you can assign a different role to a
different warehouse.
5. In the Start Date field, enter the date that you want the role to start.
6. In the End Date field, enter the date that you want the role to end. If you do not want the role to end, leave
the field blank.

Once the grant is saved, only the end date can be updated. However, the date cannot be updated once it has
expired.
7. Save your work to activate the role.

Querying using Query Manager
1.
2.
(N) Shipping > Transactions

Search for region
3.
Lines (B) - Select

(T) Lines
4.
Line Status: Not Shipped

Saved Query region
5.
Name: SH-Notshipped
Description: Not Shipped Lines
Saved Query?: Select. This makes the query public to all users
(B) Find. All lines which are not shipped are displayed in the Shipping Transaction Form
Shipping Transaction Form

9. Click on the Vertical Splitter on the left of the Shipping Transaction Form to view the Query details.
10. Click on the Vertical Splitter on the right of the Shipping Transaction Form to view the Packing
Calculator.

WSH: Quick Ship Default View = Delivery Confirm
(N) Shipping > Quick Ship
Changing Quick Ship View

1.
2.
(N) Shipping > Quick Ship

(M) Tools > Change View to toggle between the two Quick Ship views. The two Quick Ship views
are as follows:
Delivery Confirm View
Trip Confirm View
Finding Deliveries
3.
4.
Ensure that you are in the Delivery Confirm View.

You can find the deliveries in the Quick Ship window using any one the following methods:
Enter the delivery in the Name field and click Tab
Click on Name LOV to find for a delivery.
Click on the Find icon to find the delivery using Find Deliveries window. In the Find Deliveries
window, you can find the delivery based on the search criteria you enter.
Using Folder Option

5.
To hide the Number of LPNs field. Click on the field. You can hide a field using any one of the
following option
(M) Folder > Hide Field.
6.
Right click on the field, select Folders option on the popmenu, and click Hide Field.
To show a field, you can use anyone of the following methods:
(M) Folder > Show Field. Select a field, which you want to display from the LOV.
Right click on any field, select Folders option on the popmenu and click Show field. Select a
field, which you want to display from the LOV.
7. To change the position of a field in the Quick Ship window, you can use anyone of the following
methods.
Click on the field to be moved. Click (M) Folder and click on Move Right, Move Left,
Move Up, and Move Down to move to respective position.
Right click on the field to be moved. Select the Folders option in the popment, and
click on Move Right, Move Left, Move Up, and Move Down to move to respective
position.
Creating New Folder

8.
9.
10.
11.
12.
(M) Folder > New

Enter XX-Folder in the Folder field.
Select the Show Additional Delivery to display the Additional tab.
Select the Show Trip Information to display the Trip tab
(M) File > Save.
Practice Overview
In this practice, you will learn how to create orders with a standard item. Please note that you
will be completing an order to cash cycle with a standard item using all the seeded data
available in the environment. Examples of seeded data are: Order Type, Customer, Price List,
Item, etc.
Tasks
Create an order to cash lifecycle

1. Create an order.
2. Save and book the order.
3. Pick release the order.
4. Ship confirm the order.
5. Use AutoInvoice to create an invoice for the order.
Create an order
1. Navigate to the Quick Sales Orders window:
2. (N) Orders, Returns > Quick Sales Orders
3. Create an order for Computer Service and Rental:
Customer: Advanced Network Devices ( )
Order Type: SH-Mixed
4. Verify the following on the Main tab and Others tab (if the field is not visible on the window, you
can folder-enable it):
Operating Unit = should be Vision Operations

Shipping Method: DHL
Warehouse: SH1
Price List: SH-Price List 1
Ship To and Bill To Address should default depending on the Customer
Name/Number field value
5. Enter Order Line Information:
6. Save
Ordered Item: DD-00100-0105-01 , DD-00020-0110-01

Qty: 10
Shipping Method: DHL
your work. The Status on the line should display as Entered.
7. Book the Order using (B) Book Order.
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.
Pick Release the order

9. (N) Shipping > Release Sales Orders
10.
Enter the order number in the Order Number field.
11.
The Customer and Order Type fields get populated based on the Order Number
field value.
12.
Click (T) Inventory. Set Auto Allocate to Yes. (From Release Rule)
13.
Click (T) Shipping. Set Auto Pick Confirm and Autocreate Delivery to Yes.
14.
Click (B) Execute Now to pick release and pick confirm the order.
Ship Confirmation
15.
Open the Shipping > Shipping Transactions window.
16.
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.
17.
Click Find to find your order.
18.
The Shipping Transactions window opens to display your order details with the
statuses.
The Order Line Status Backordered Because No On Hand In Inventory Shipping

Organization Mack Miscellaneous Receipt For Items You Want Shipped
Pick Release again
The Line Status Is Ready To Release You Must Go To Inventory To Transact Move Order
Find SO Number
Cause #1:
The rules are not yet visible though they are created. This could be because they are not
enabled, or because the "Generate All Rules" concurrent program (WMSGRULE) was not run.
SOLUTION
For Cause #1:
Sometimes the enabled flag on the rule or association is not checked. Other times the Rules
were not generated.
1.
2.
3.
4.
Review each Picking Rule defined in Inventory > Setup > Rules > Picking Rules.
Ensure each rule is enabled.
Press the associations and ensure that each association is enabled.
Run the "Generate All Rules" concurrent program (WMSGRULE).
Note: If your responsibility does not have this, you could add it to your responsibility using System
Administrator > Security > Responsibility > Define. Query your responsibility and see what your
request set is. Then choose System Administrator > Security > Responsibility > Request, query your
request group name, add a row for the program "Generate All Rules".
19.
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,
Auto-Create Trip.
20.
Navigate to the (T) Delivery tab. Click (B) Ship Confirm.
select trigger_name,status,owner from dba_triggers

where trigger_name like '%ADS_WSH_DELIVERY_DET_TRG1%';
alter trigger ADS_WSH_DELIVERY_DET_TRG1 disable;
21.
Accept all other defaults. Click (B) Ok.
22.
You will get a message that the delivery was successfully confirmed. Click Ok and
close the Shipping Transactions window.
Verifying Status
23.
Open the Quick Sales Orders window to check the status of your order. It should
display as Shipped.
24.
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
25.
Click (B) Actions > Additional Line Information to view the delivery and trip
information and status.
Order Header Main
Line Status
Additional Line
Tab
Information
Booked
Shipped
Delivery Status =
Closed
Picked Status =
Shipped
Trip Status = Closed
Interfacing to Receivables using the Workflow Background Process concurrent

program
26.
From the Quick Sales Orders window, navigate to (M) View > Requests. Click (B)
Submit a New Request (single request) and select the concurrent request Workflow
Background Process. Enter the following as parameters:
Parameters window:
Item Type: OM Order Line
Process Deferred: Yes
Process Timeout: No
27.
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.
28.
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.
Shipping Transition Form Line Status
Run AutoInvoice
29.
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.
30.
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
31.
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.
Viewing your Invoice details

32.
(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.
33.
Click (B) Invoice Details to view the invoice that has been autocreated from your
order.
Receivables, Vision Operations (USA)
Practice Overview
In this practice you will learn how to customize the Quick Sales Orders window.
Open the Quick Sales Orders window
Use the Folder Tool
Enable Diagnostics
Personalize the Quick Sales Orders window
Tasks
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. Personalize the Quick Sales Orders window.
1.
Customize the Quick Sales Orders window

2.
(N) > Orders, Returns > Quick Sales Orders
3.
Place your cursor on any of the header fields and then select (M) Folder > New or (I) Folder
Tools > (I) New.
4.
The following window opens:
5.
Enter
the following:
Folder - a name for the header level folder, replacing XX with your initials.
Autoquery Never
Open as default selected
Public selected
Others tab (Others box) selected
Configure Buttons block you need to display the Actions button in the window, so
select the Display box of the Actions entry in the Action Name column
Click OK to save and return to the Quick Sales Orders window
Verify the following: your new folder name, Others tab, Actions button should be
visible on the window
6. 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.
7. Enter the following:
Folder enter the folder name, replacing XX with your initials
Autoquery Never
Open as default selected
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)
8.
Save your work and return to the Quick Sales Orders window.
9.
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

10. With the Quick Sales Orders window open, navigate to the Personalizations window: (M) Help
> Diagnostics > Custom Code > Personalize
11. If there are seeded personalizations already in the window, do not modify them.
12. Enter a short description in the Description column, Workflow Status menu. Select the Level
as Function and select the Enabled box.
13. (T) Condition: Select the Trigger Event as WHEN-NEW-FORM-INSTANCE with a processing mode
of BOTH.
14. (T) Actions: Enter the following:

a. Seq: 1
b. Type: Menu
c. Description: wf menu
d. Language: All
e. Enabled box: selected
15. Menu Entry: SPECIAL2:
16. Menu Label: Workflow Status
17. (B) Validate.

18. (B) Apply Now.
19. Close the Personalizations form and return to the Quick Sales Orders window.
20. Close the Quick Sales Orders window and reopen it. Check if the Workflow Status menu option
is now available in the Tools menu.
Use the Specials Menus to add some menu option to your Quick Sales Order window. The list is
below:
Function
Special Menu #
Find Customer
SPECIAL1
Workflow Status
SPECIAL2
Price Debug
SPECIAL3
AutoSchedule
SPECIAL4
User Sets
SPECIAL5
Purge
SPECIAL6
Show Line Details
SPECIAL7
Item Search
SPECIAL8
Quick Customer Entry
SPECIAL9
Debug
SPECIAL10
Apply Holds
SPECIAL11
Mass Change
SPECIAL12
Schedule
SPECIAL14
Audit
SPECIAL15
Scheduling in the Sales Orders

Scheduling Activity
The Schedule function can be performed anywhere in a process flow according to your business needs. If you
want to setup scheduling to run automatically, you can set it as a synchronous function within the workflow
process so it will happen automatically. The profile option OM: Autoschedule should be set to Yes.
Or the user can schedule manually directly from the sales orders window. See Scheduling for details on
scheduling setup.
Overview
In this practice, you will learn how to schedule an order both manually and automatically. Your
customer XX-Big City Electronics wants to order 15 units of item XX-Phone, 45 days from todays date.
Assumptions
Oracle Management Super User, Vision Operations responsibility
Prior practices are completed. Practices build on earlier exercises.
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 profile option:
You have set the following system parameter. Setup-> System Parameters -> Values
OM: AutoSchedule = No
Reservation Time Fence = 30

* The Time Fence Reservations are performed automatically whenever a line is scheduled and
the schedule date is within the reservation time fence.
For example, suppose the today's date is November 25th. An order line is scheduled for
December 1st, which is 6 days away. If the reservation time fence is 10, the line will be
reserved because 6 < 10. If the reservation time fence is 2, the line will not be reserved
because 6 > 2. If the reservation time fence is NULL, then lines will not be automatically
reserved. The reservation time fence is set using the system parameter Reservation Time
Fence.
Reservations Time Fence is affected by the scheduling parameters, Allow Partials.
If you want the reservation time fence to reserve as much as possible, even though full supply
is not available, set the scheduling parameter to allow partials.
Creating a Sales Order

2.
(T) Order Information, (T) Main:

Order Type = Mixed
Price List = Corporate
3.
(T) Line Items, (T) Main:

Qty = 100
Request Date = Todays Date + 45 days
Line Type = Standard (Header Invoicing)
Checking Item Availability

4. Select the order line for item DD-00010-0040-01.
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.
Scheduling the Order Line

6. (M) Tools > Scheduling > Schedule.
7.
8.
(B) OK.
(T) Line Items, (T) Shipping.
Note: Notice that the schedule ship date has been set to the request date.
Reserving the Order Line

9. From the Tools menu, select Scheduling > Reserve.
Check The On-hand Item Status Before And After Reservation
Item Code = DD-00010-0040-01
10. Click OK.

11. On the Shipping tab note that the Qty Reserved field shows the reserved quantity.
12. (I) Save.

Using the Auto Scheduling Feature
13. (M) Tools > Auto Schedule (Ensure Auto Schedule is selected)
14. (I) New:
Item = XX-Phone Card
Qty = 2
15. (I) Save.

16. (T) Line Items, (T) Shipping.
Notice that the Qty Reserved field has been automatically entered for item XX-Phone Card.
Sales Quotes in Oracle Order Management.

Negotiation in Order Management
Overview
Order Management provides an end to end solution for processing a simple Quote through the negotiation
process and automating the transition of the document to fulfillment.
This process reduces administration expenses, and increases productivity in an environment geared for rapid
response to the customer base.
A quote can pass through various stages from its initial preparation to fulfillment (as a Sales or Sales
Agreement).
These stages include preparation of a draft; negotiation with the customer; internal and external business
approvals; versioning based on customer feedback and conversion to an order or archival as an unsuccessful or
unused quote. Negotiation in Order Management provides a seamless flow from a quote status through to firm
order. Negotiation:
Prepares and publishes quotes for assisted selling of products and services to customers and business
partners.
Creates and manage quotes as a negotiation tool and transition the quote to a firm order acting as a
single point of entry into Order Management.
Allows quick entry of order lines with a minimum of data entry. Quoting processes the quote and submits
to Oracle Order Management a firm order complete with approvals (Internal/External). Relevant
information captured by the quote flows through to the order.
You can use quoting to:
Create, modify and select quotes.
Configure Complex Products.
Manually adjust quote prices.
Perform real time global availability checks.
Calculate taxes
Assign sales Credits
Convert quotes to orders.
Support E-Business requirements.
Reduce administration expenses and increase productivity.
Oracle Order Management includes a workflow phase to support the activities that typically occur within a
negotiation process, such as internal approval and customer acceptance. This allows you to create and manage
quotes during the negotiation phase and transition the quote to a firm order. Features include:
A separate menu option for entering Quotes
Date Expiration
Pricing and Availability queries
Copy support
Defaulting of attributes that can affect a quote
Display of Related Items, such as up-sell, cross-sell or substitute items, and their price and availability
Integration with Pricing
Integration with TCA
Minimal data entry that can be processed through to Oracle Order Management as a firm order complete
with approvals (Internal/External). Relevant information captured by the quote flows through to the order.
Change Management using Processing Constraints and versioning
Automated Process definitionworkflows can be defined and extended.
Visibility through the Order Information Portal
Miscellaneous
Both Quotes and SAs use the same seeded Negotiation workflows.
After Customer Acceptance, Quotes transition to a sales order and Sales Agreements become Active.
SAs do not capture an Offer Expiration date and therefore do not leverage this functionality in the Negotiation
flow.
Unsupported Features
The functionality supported with Quotes is similar to the level of support for Sales Orders. There are a few Sales
Order features that are not available during the negotiation phase of a transaction including:
Holds
Scheduling
Copy a return from a quote.
Independent line flows
Cancellations progress to LOST Status
Ship and Arrival Sets
Commitments
Quotes for returns or Internal Sales Orders
Sales Agreements - Can specify sales agreement reference on a quote but released quantity and released
amount on a sales agreement are updated only when a quote is converted to an order
Setup
Transaction Type
To create a Transaction Type

1. Set up the transaction type. See Transaction Types for generic setup instructions.
Note : that when the transaction type contains both a fulfilment and negotiation phase there are some
additional implementation considerations associated with set up.
These impact when and how document numbers are generated by document sequencing.
On the transaction type set up form there is a check box for retain Document Number.
When an order type is created two categories are created.
Depending upon the value of Retain Document Number the following steps need to be taken.
SH Qut To So
2. If you want to keep the document number from the quote when the transaction moves to fulfilment, use
the category appended with TTXXX-Quote when creating and assigning document sequencing.
3. If you need to generate a new document number for the transaction in the fulfilment phase, two
document sequences need to be set up:
o
One for fulfilment, using the category with no appending text TTXXX
One for the category appended with -Quote.

If this is not set up correctly then the document will not transition to fulfilment because the
document cannot be assigned a Sales Order Number.
NOTE: Retain Document Number check box applies only to transaction types with Sales Document
Type of Sales Order. Sales Agreements have only one document number, Sales Agreement
Number, associated with the transaction irrespective of whether agreement is in negotiation or
fulfillment phase.
4. Then optionally assign a default transaction phase.
The transaction phase defaults to either Negotiation or Fulfillment based on Order Management
defaulting rules when the quick sales or standard sales order form is opened. The transaction phase
always defaults to Negotiation independent of the defaulting rules when the form is opened through the
Quotes menu option. If the transaction phase defaults to Negotiation, only the transaction types that also
have a negotiation workflow associated with it are displayed.
In the absence of a default, the fulfillment phase is automatically populated by the system.
Note: The transaction phase can be changed up to the point of saving the transaction or before lines are
entered. Once the transaction is saved or lines are entered, the transaction phase cannot be changed
and the transaction phase field is non-updatable.
You can set the transaction phase directly on the sales document; the transaction phase determines where in
the workflow the transaction starts. Using a single transaction type you can choose to begin the transaction
process in either phase if both fulfillment and negotiation workflow assignments exist on that transaction type.
Note: While Sales Orders lines are assigned a line type through which the transaction is processed, quotes and
SAs do not use line types and follow a header flow only.
Transaction type designed for use with Sales documents For example in addition to header and line block data:
SA uses the following settings on the transaction types:
Document numbering
Flow assignments
Layout and contract templates.
Transaction phase
Quotes use:
Retain document number
Header flow assignment
Transaction phase
Layout and contract templates.
Workflows
Quotes and Sales Agreements leverage the flexibility of Workflow to manage the quote life cycle. There are two
phases for workflow: Negotiation and Fulfillment. Workflow flexibility allows you to tailor your Negotiation and
Fulfillment phases to your specific processes. You can choose one of the following generic seeded header-level
negotiation flows, these flows can be associated to transaction types for both Sales Orders and Sales
Agreements. Both can be converted to an order. Quotes can be converted to sales orders in either the Entered or
Booked status (if the booking activity is synchronous). The seeded workflows are as follows:
Negotiation Flow - Simple :This workflow does not require any approvals nor customer acceptance.
However the quote can either expire or get lost if it does not progress to being converted to an order.
Negotiation FlowGeneric: Simple negotiation flow, without approval. Prepares quote document, get
customer final acceptance, convert quote to the Sales Order.
Negotiation FlowGeneric with Approval: Flow with Approval. Prepare quote document, get
management approval, get customer final acceptance, and convert the quote to an order.
In support of a quote the following Status types are predefined:
Draft
Pending Internal Approval
Lost
Pending Customer Acceptance
Draft Submitted
Internal Approved
Customer Accepted
Offer Expired - This status does not apply to Sales Agreements.
Draft - Customer Accepted
Draft - Customer Rejected
Seeded workflow that incorporates Internal Approval and customer acceptance
After a quote has been put together, it can be submitted for approval. The relevant documents can be
routed to various people in the organization, including people from Sales, Business Practice, Legal, or
Finance, for review.
The list of approvers is defined at the Transaction Type level.
The document must be approved by each participant in the list before the transaction is eligible to
move forward in the workflow. If the approver fails to respond within the time limit, the system will resend the notification. If the approver again fails to respond, the system will either send the notification
to the next approver (if the current approver is not the last approver), or reject the notification based
on the system parameter setup.
The Approver List can be accessed two ways:
1. From the Transaction Type setup window: (N) > Orders, Returns > Setup > Transaction Type >
Define. Select the Approvals button to bring up the Approver List.
2. Navigate directly to the window: (N) > Orders, Returns > Setup > Transaction Type > Approvals.
If an approver is deleted from the list the notifications still need to be processed.
If an approver is added to the list and any transaction is pending approval they will receive a
notification.
The user will receive a notification and must approve or reject.
Practice Quotes Functionality.

Topics that I will cover here are
1.
Setup
2.
Defaulting Rule & Generation of Defaulting Rule (When Required).
3.
Profile setup.
4.
Transaction Type.
Data Flow from Quotes to OM Order.
Oracle Quotes offers limited capability to create Quotes and Progress it through the Negotiation phase and
finally creates Sales Order .
In case your Organization has complex / advance quoting needs you should Implement Oracle Sales Quoting.
One of advantage of Sales Quoting is that it enhance user experience , since it is part of OM , it retrieve all
the relevant information from the Order management and once created and approved it creates Sales Order
without much input from user.
In Oracle OM Quotes, Oracle has provided Negotiation , Customer Acceptance and Sale Order creation
feature.
Following are features introduced in Oracle Quotes
1.Seeded Work flow ( Oracle has Introduced 2 worklfows ).
Workflow has introduced for the Order Header Type Only (OENH) , there is no Workflow for the Quote Lines.
Negotiation Flow - Generic - It Support Negotiation , Customer Acceptance and Conversion of negotiation
into Sales Order
Negotiation Flow - Generic with Approval - It Supports Negotiation , Internal Approval , Customer
Acceptance and finally conversion into Sales Order.
With these workflow customer has flexibility to customized their Quotes process by adding or removing
Functions.
2.Quote Expiration Date - Every Quote has expiration date , once expiration date reached , Quote will be
expired and Quote Headre workflow is eligible for Purge.
SETUP
1.Transaction Type Setup
Set Document Sequence
2.Defaulting Rule Setup - This Defaulting Setup is required to populate the Transaction phase = "
Negotiation " in Order Header Form. Note: Common Mistake in these area are (User forgot to generate the
defaulting Rule after enabling this Rule).
3.Profile Setup - this is Not a required setup , unless their is business requirement .We can leave this as
blank.
4.Transaction Types - Oracle has introduce following New transaction types for Quotes Draft,
Pending Internal Approval, Approved, Lost, Pending Customer Approval, Accepted
Data Flow for OM Quotes
Create Quote - User Interface Similar to OM. When you save Quote , Quote status will be "Draft" and it
indicate the Negotiation Phase.
Enter line details for quote , there will be no Line level workflow associated with Quote lines.
Quote Header Workflow is in Submit Draft Eligible Notified Status.

Once the Negotiation Process is complete , Progress the Quote header from the Negotiation Phase
Quote status will be now "Pending Customer Approval".
Once receive confirmation from customer regarding Approval /rejection , approve or reject the quote.
Once Quote is Approve , It automatically converted in Sales order .

System will Automatically Assign the Order Header level and line level workflow to Sales Order and Lines.
Order Header Workflow will be at "BOOK - ELIGIBLE" Notified and
Order Line Workflow will be at "Wait for Booking" Notified
Difference between back to back and drop shipment flow in Order

management
Conceptual Difference:
Back to back flow - A business scenario where the material is specially purchased for a particular sales
order and the material needs to be received Into one of The warehouses of the selling group of
companies, is referred as "Back to back" cycle.
Back to back Purchase order is hard linked to the sales order until it is received.
Please note highlighted words here. Since, the material is received into the warehouse, the sales
order needs to follow additional picking/packing/shipping process only after which the goods are sent
to the customer.
Drop Shipment flow - A business scenario where the material is specially purchased for a particular
sales order and the material is directly sent from the supplier to the customer, is referred as
"Drop Shipment" cycle.
Drop shipment purchase order is also hard linked to the sales order until is received. However, in this
case the material is never received in the internal warehouse. Also, no additional
picking/packing/shipping is involved by the selling company. Hence, when such purchase order is
received it is directly shipped without any physical shipping process.
Technical different in Oracle
Phase
Sales order line source
Back to back
Sales order line ORDER SOURCE should be internal
Import purchase
requisitions
Back to back requisition data is immediately

pumped into requisition interface table after
PROGRESS ORDER action in sales order
Reservations
Back to back purchase requisition is reserved to

the sales order in MTL_RESERVATIONS table. Same
process is following by oracle for all sales order
reservations.
It does not have Drop Ship tab in the PO
Shipments form
Deliver To location in purchase order shipment is
set to the internal warehouse address
Line status changes on Progress Order, Requisition
Creation, Purchase Order Approval & Purchase
order receipts
Purchase orders
Purchase order delivery
location
Sales order line status
Viewing PO reservations
PO receipt
Flow of purchased
material
After receipt
Sales order delivery
lines/delivery
e.g. Requisition Requested, Requisition Open, PO

Open
Available in sales order line-Actions>Reservation
details screen
Physical receipt of the material happens
Material is received inside the warehouse and then
shipped
Stock of the goods received increases, stock gets
reserved to the sales order automatically
Sales order status changes to Awaiting Shipping
Delivery lines are created in shipping when PO is
received
Drop shipment
Sales order line ORDER SOURCE should be
External
Drop Ship requisition data is NOT immediately
pumped into requisition interface table after
PROGRESS ORDER action in sales order. Workflow
background process needs to be run to insert
data into requisition interface tables
Drop ship requisition is reserved to the sales
order in special table called
OE_DROP_SHIP_SOURCES. This is a unique
process followed only for drop shipment
It has Drop Ship tab in the PO Shipments form
Deliver to location in purchase order shipment is
set to Customer Ship To address
Line status does NOT change on Progress Order
and Purchase Order Approval.
E.g. Awaiting Receipts only status until PO is
received
Available in Sales order line->Actions->Additional
Line information
Only logical receipt of the material
Material is never received in the warehouse, it is
shipped directly from supplier to the customer
Stock is received and immediately shipped out by
the system. Sales order status changes directly
to Shipped
No delivery lines are created, since shipping
process in the system is skipped
Drop Ship Setup Steps

1-Create Transactions Type (Sales Order Type)
2-Defaulting Rules (Source Type)
3-Profile Options
4-Create New Buyer
5-Create New Item
6-Reciving Options (Clearing Account)
7-Drop Ship Test Cycle
1-OM: Setup ->Transactions Types ->Define
Transaction Type = SH Drop Ship
Define Item Attribute
Drop Ship Line Status Flow
Entered
Booked
Purchase Release: Item requires inspection before Purchasing can create a receipt
Awaiting Receipt: Purchasing creates a receipt of the item
Interfaced to Receivables
Closed
OM: Order, Returns -> Requisitions Import

Parameter
Import Source : ORDER ENTERY
Group By : Buyer
Convert this PR(Drop ship) to Po
Practice Overview
In this practice you will learn how to setup and create a Drop Ship Order.
The line item will ship directly from your supplier in an operating unit to your customers ship to
address in another operating unit.
Perform the necessary setup steps for Drop Shipment across operating units
Enter and book an order with a drop ship order line
View the order processing in the workflow status window and progress the order
through purchase release
Run the requisition import concurrent program to generate a purchase requisition
Autocreate a purchase order from the sales order (purchase requisition)
Create a logical receipt for the quantity ordered
View the quantities received in the Drop Ship tab, thereby completing the Drop Ship
Order creation cycle
Tasks
1.
Login to the database and navigate to the Sales Orders window.
2.
Use the following header information for your drop shipment order:
Operating Unit: Vision Operations

Customer Name: Business World (1608)
Customer PO: XX-015
Order Type: Mixed
(T) Others > Warehouse: D1
3.
Use the following line information for your order:
Ordered Item: AS54888

Qty: 2
Price List: Corporate
Receiving Org: D1
Source Type: External
Profile Option for Inter-Company Invoicing

1.
Set the profile option INV:Advanced Pricing for Intercompany Invoice = No. This is set as a
personal level profile option.
2. Switch responsibility to Order Management Super User, Vision Operations (USA).

3. (N) Inventory > Setup > Organizations > Intercompany Transaction Flows
Start Operating Unit: Vision Operations
End Operating Unit: Singapore Distribution Center
Type: Procuring
Ship From/To Organization: D1
At the Nodes level, enter the following:
Seq: 1
From Operating Unit: Vision Operations
To Operating Unit: Singapore Distribution Center
4. Click (B) Intercompany Relations. Enter the following information in the window:
Customer: Vision
Number: 1021
Location: 5490
Transaction Type: Invoice
COGS Account: 01-580-7740-000-000
Supplier: Vision
Site: New York
Inventory Accrual Account: 01-000-1810-0000-000
Expense Accrual Account : 01-000-1110-0000-000
5. Save your work. The setup steps for drop ship are complete.
Drop Shipments Flow

6. Change Responsibility to Order Management Super User, Vision Operations USA.
7. Enter the sales order header information:
Customer PO: SH-015
(T) Others > Warehouse: D1
8. Enter line information:

Ordered Item: AS54888
Qty: 2
Receiving Org: D1
Source Type: External
9. (B) Book the Order.

10. Write your sales order number: 20140007 .
11. Check the workflow status in the (M) Tools > Workflow Status page. Verify that the
order line has been Purchase Released. If not, use the (B) Actions > Progress Order
option or the Workflow Background Process concurrent program to progress the order
to complete Purchase Release. The parameters that you will need for the Workflow
Background Process are:
Item Type: OM Order Line
Process Deferred: Yes
Process Timeout: Yes
12. The status of the order line will change to Awaiting Receipt.
13. The workflow status of the line is below. (M) Tools > Workflow Status
Run the Requisition Import concurrent program

Note: Please use the Purchasing option / responsibilitys Reports > Run functionality and not
Order Managements.
14. (N) Purchasing
15. (M) View > Requests
Name: Requisition Import
Operating Unit: Singapore Distribution Center (D1)
Parameters window: Import Source: Order Entry (optional)
16. (B) Submit.

17. View the purchase requisition in the sales orders window. (N) Orders, Returns > Quick
Sales Orders. Click the Lines region and click (B) Actions > Additional Line Information.
The Drop Ship tab will show the purchase requisition with an approved status.
18. Enter the purchase requisition number____________________.
Autocreate Purchase Order

19. Change to Purchasing. (N) Purchasing > Autocreate
20. Click (B) Clear and then enter the purchase requisition number from the above step
and click (B) Find to display the requisition.
21. The search results open in the AutoCreate Documents page:
22. Select the requisition or requisitions that you require by clicking the box on the left of
the Requisition column. Click (B) Automatic.
23. In the New Document window, select the supplier as Vision and supplier site as NEW
YORK.
24. Click (B) Approve to approve the purchase order when the Purchase Order window
appears.
Note: Please ensure that the Submit for Approval box is selected.
25. (N) Receiving > Receipts

26. Enter the Purchase Order number that you created in Step 24. Enter the following
information in the Receipts window:
27. Receipt Header window: Select the Create New Receipt radio button.
28. Receipts window:

Quantity: 5
Destination Type: Inventory
Subinventory: Drop Ship
29. Save your work and close the Receipts window.

Verifying that the order has been dropped shipped
30. (N) Orders, Returns > Quick Sales Orders
31. Query for your order number using the F11+Ctrl-F11 keys.
32. Select (T) Line Items. Choose (B) Actions > Additional Line Information.
33. In (T) Drop Ship, the quantity reserved will be 5.
This completes the drop shipment across operating units cycle.
Guided Demonstration Creating Back to Back Orders

Setups for Back-to-Back Orders Item Attributes
Note: Use Order Management Super User, Vision Operations (USA) or comparable Super User Order
Management responsibility.
1.
2.
3.
4.
Create an item using the Inventory > Items > Master Items.
Select the Vision Operations (V1) organization if prompted.
Setup Item Attributes for a standard item SH-FG2.
The item type for the item SH-FG2 should display a value Finished Goods and an Item Status of
Active.
Enter the following attributes in each of the tabs indicated below:
(T) Purchasing Select Purchasable box. Enter a list price in the List Price field.
(T) General Planning Select Buy in the Make or Buy LOV
(T) Work in Process Select Build in WIP box
(T) Order Management Select Customer Ordered box and Assemble to Order box
5. The profile option MRP:Default Sourcing Assignment Set should be set to Null or any %Supplier%
value.
6. Add the item SH-FG2 to the Corporate pricelist. (N) Pricing > Price List Setup.
Create an order
7. Navigate to the Quick Sales Orders window:
8. (N) Orders, Returns > Quick Sales Orders. Create a sales order for Business World:
Customer: Business World (1608)
Warehouse: SH1
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: SH1
10.Enter Order Line Information:

Ordered Item: SH-FG2
Qty: 100
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.
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.
13.When you progress the order ((B) Actions > Progress Order), the line status is PO Requisition
Requested.
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
After the concurrent request is processed successfully, the Sales Orders line shows External Req Open.
Find the PO Requisition

15.(N) Purchasing > Requisitions > Requisition Summary
16.Clear all fields and enter CTO in the Import Source field. The Requisition Headers Summary window
displays.
17.The Approval Status should be Approved. Verify that the line information corresponds to that in the
sales orders window.
AutoCreate the Purchase Order
18.(N) Purchasing > AutoCreate
19.In the Find Requisitions window, click (B) Clear and enter the PO Requsition number you created in
Step 20140022.
20.In the AutoCreate Documents window that displays, verify the requisition details and click (B)
Automatic to create the purchase order.
21.Enter the following in the window:

Supplier: Elshayeb Corporation
Source: NEW YORK
Approve PO
22.Note: The line status of the sales order is PO Open.
23.(N) Purchasing > Receiving > Receipts

24.(B) Clear. Enter the PO Number and click (B) Find.
25.The Receipts window opens with the PO details.
26.Select the (T) Lines and enter Stores as the Subinventory value. (I) Save.
27.Note: If the value of the Subinventory field is blank, you can populate it by updating the value of
the Subinventory field in the Receiving Transactions window. (N) Purchasing > Receiving >
Receiving Transactions.
28.Note: The line status on the Sales Order is Awaiting Shipping.
Creating Material Transactions

29.(N) Inventory > Transactions > Material Transactions
30.The following information is displayed:
Item: SH-FG2
Source Type: Purchase Order
Source: 20140021
Transaction Type: PO Received
Transaction Action: Receipt in Stores
The Quantity Reserved To SO Number 20140008
31.Check the on-hand quantity in the Quick Sales Orders window, it should be 100.
32.Pick Release the order.
33.Ship Confirm the order.
Sales Agreements
Overview
Sales Agreements are used when you have specific characteristics related to a purchasing agreement between a
customer and a supplier. These characteristics include the date range of the agreement, the items included, the
price of the items, the quantity of each item that the parties committed to, as well as other attributes, like
freight or payment terms.
Once a Sales Agreement is entered for a customer, multiple releases (sales orders) against the Sales Agreement
are processed over a period of time within Order Management.
The order is fulfilled and billed according to the terms of the Sales Agreement.
Tracking information will also be accumulated for Sales Agreements, such as, quantity fulfilled, and dollar value
fulfilled of released lines. This information is used to view status of orders executed against a Sales Agreement.
Sales Agreement functionality includes the following:
New windows: Find Sales Agreements, Sales Agreements Summary, and Sales Agreements windows
Captures agreement information
Enforce sales agreements terms such as: price list, shipping method, payment terms, ship to, bill to.
Ability to secure who can enter Sales Agreements
Specify defaulting rules for sales agreement attributes for releases
Ability to create non-customer specific Sales Agreements
Default information from the Sales Agreement to the release
Support Standard, ATO items, Kits, Services, and other items
Support Item Categories and all items
Ability to create releases by Order Import and Process Order API
View releases of Sales Agreements
Process the releases against the Sales Agreement
Aggregate information about the releases and access that consolidated information from the Sales
Agreement
Integrations with Advanced Pricing and Release Management
Effectivity dates of the agreement
Inline Pricing
Enhanced sales documents with Preview and Print
Ability to terminate a Sales Agreement
Workflows:
Negotiation and Fulfillment flows
Automatically attach Adobe Portable Document Format (PDF) of current SA for Approvers to reference easily
Quality Assurance (QA) validation for contractual terms and conditions included in Negotiation flow
Draft, Internal Approval, Customer Acceptance, Terminate, Expire, Lost, and Close
Internal Approvals
Create Internal Approver List
Processes:
Automatic and Manual Versioning
Customer Acceptance captured
Ability to create customer-specific Price List
Ability to add customer items to a Price List
Ability to author and negotiate Contract Terms with Oracle Sales Contracts enabled
Configuration support:
Ability to define options and option classes on the Sales Agreement to hold price for configurations on
releases
Attachments
Contract Documents
Copy
Security through Processing Constraints
Profiles
OM: Default Sales Agreement Type
This enables the system to use a common (default) transaction type across Sales Agreements to generate
unique sales agreement numbers. There is no default value for this profile option.
This profile is seeded as available to setup at the responsibility and site level.
In most business processes, the profile option can only be modified by the System Administrator.
The profile is visible to the user but not updateable.
OM: Default Agreement Transaction Phase
This profile enables the system to use a common transaction phase across Sales Agreements.
Defining transaction types for Sales Agreements

Navigate to the Transaction Types window to set up transaction types.
The three seeded workflows for Sales Agreements are:

Negotiation FlowGeneric: Simple negotiation flow, without approval.
Prepares negotiation, no management approval, get customer final acceptance, converts from negotiation phase
to fulfillment phase.
Negotiation FlowGeneric with Approval: Flow with approval.
Prepares draft, gets management approval, gets customer final acceptance, converts from negotiation phase to
fulfillment phase.
Sales Agreement FlowGeneric: Generic fulfillment flow for Sales Agreements.
Note the following when setting up a transaction type for Sales Agreement:
Fulfillment Flow: Assign the fulfillment flow.
Negotiation Flow: Assign the optional negotiation flow.
Default Transaction Phase: Transaction phase determines where in the workflow the transaction will start.
Select either Fulfillment or Negotiation.
The profile OM: Default Sales Agreement Transaction Phase is the preferred source for the transaction default on
Sales Agreements.
If the profile has not been set, the system looks at the transaction phase defined on the transaction type.
If neither default is available, the system uses Fulfillment phase as the default. (Optional)
Layout Template: Assign the layout template that you would like to use when generating a customer facing
document to be previewed or printed. See Preview and Print Sales Documents, page 5-29. (Optional)
Contract Template: When Oracle Sales Contracts is enabled, assign a Contract Template to the sales
agreement type for defaulting purposes. See Authoring and Negotiating Contract Terms, page 20-15. (Optional)
Transaction types can point to the same template or different templates depending on the business process.
There is direct access to the Approval List setup from the transaction type. It can also be accessed from the
menu.
For more information on setting up Approvals, see Defining Approvals, page 2-105 .
The Negotiation flow offers Internal Approval as well as Customer Acceptance prior to transitioning the Sales
Agreement transaction to Active where releases can be placed against the Sales Agreement.
Note: If you want to create an automatic attachment on the workflow notification (to allow approvers to easily
view the document), on the transaction itself as a reference in Contract Documents when Oracle Sales Contracts
is enabled, or for FND attachments, the workflow must
be extended to add the "Sales Agreement/Sales Order Generation" process in between Submit Draft and Internal
Approval, and XML
Publisher must be installed.
Practice Overview
In this practice, you will learn how to create a Sales Agreement and also how to create releases
against this Sales Agreement. In this practice, the SA creation begins in the Negotiation Phase and the
Negotiation Flow selected does not include an approval step.
Create a Sales Agreement
Create a release (sales order) against the Sales Agreement
Tasks
Create a Sales Agreement (SA)
1. Business World (1608) has contacted you to place a long-term order for item SH-FG2. 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.
SA Creation
1.
2.
Navigate to the Sales Agreements window:

(N) Blanket Agreements > Sales Agreements
Create a SA for Business World:
Customer: Business World (1608)
Sales Agreement Type: SA without Approvals
Sales Agreement Name: SH-Blanket Practice
Activation Date: enter todays date
Expiration Date: enter the date 8 months from today
3.
(T) Pricing in the upper block. Enter the following information:
4.
Price List: Corporate.

Check box Enforce Price List should be checked.
(B) Price List Setup. In (T) List Lines enter the following information:
Product Context: Item
Product Value: SH-FG2
Value: 50
5.
6.
7.
Note: The above image shows the SA window, Pricing tab and above that, the Price Lists window is
displayed.
Click (I) Save and close the Price Lists window to return to the SA window.
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
In (T) Fulfillment of the lower region, enter the following information:
Min Release Quantity: 15
Max Release Quantity: 30
Min Release Amount: 1000
Max Release Amount: 100000

8. In (T) Accounting for both the header and line regions, enter Payment Term of 30 NET 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
SH-FG2 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 201401. 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.
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.
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.
16. In (T) Line Items, enter SH-FG2 with a quantity of 15.
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.
Returns and Credits

Overview
Oracle Order Management provides Return Materials Authorization (RMA) functionality within the Sales Orders
window, where you can enter both standard and return order lines within the same order.
RMA is often used interchangeably with Return or Credit Orders and Returned Material.
An order can have a mix of outbound (standard) and inbound (return) lines, as restricted by the order type
definition.
Credit order types can have an order type category as Return or an order with both standard and return lines can
have an order type category as Mixed. Each order type and each line type is associated with a workflow process.
A return line is indicated by Line Type Category of return negative and highlighted item quantity and negative
line total.
Return Line types can include flows like Return with Approval, or Return for Credit Only, etc.
There are three ways to create RMA's within Order Management. First, identify a sales order to be returned and
query the order lines.
After you have selected the sales order or order lines, use the Copy function in the Actions list to generate the
return order or line by specifying an RMA line type. Second, reference a sales order, invoice, PO number or serial
number of an item directly in the Return Reference field within the Line Items tab of the Sales Orders window.
Lastly, for return without originating sales order line, manually enter return line information and choose the
appropriate return line type in the Sales Orders window.
Setup
Profile Options
OM: Return Item Mismatch Action
This profile allows a mismatch value between the item on the RMA line and the item on the referenced line.
For example, you may need to allow a mismatch when a wrong item is shipped and you want to put the
correct item on the RMA line.
The seeded value is Allow or no profile option entry will be treated as Allow.
OM: Return Unfulfilled Referenced Line Action
This profile allows non-fulfilled lines to be used as referenced lines.
The seeded value is Allow or no profile option entry will be treated as Allow.
OM: Over Return Tolerance
This profile option indicates the percentage by which a return line can be over-received.
Any value greater than or equal to zero (0) is a valid value. This profile option is set at the site level. The
default value is zero (0).
OM: Under Return Tolerance
This profile option indicates the percentage by which a return line can be under-received for it to be
considered fulfilled.
Any value between zero (0) and 100 (both inclusive) is a valid value. This profile option is set at the site
level.
The default value is zero (0).
OM: Charges for Back Orders
In previous releases, Calculate Price Flag on the split (back order) lines was set to Freeze Price always.
Now in the current release, for return lines that are split, this profile option enables you to control the setting
of the Calculate Price Flag to calculate, partially calculate or freeze the price.
If the Calculate Price Flag is set to Partial, no repricing is carried out and only charges can be applied for
return lines.
If the Calculate Price Flag is set to Freeze, the return lines are not priced. For a value of Calculate, the return
lines are priced.
Workflow
Order Management comes with seeded Oracle Workflow processes. Review the seeded flows, activities and
notifications to determine if the seeded data can meet your business needs.
To successfully enter an RMA in OM, you can use the
Generic - Order Flow Return with Approval
Line Flow - Return for Credit only.
Line Flow - Return with Receipt Only, No Credit
Note: For Mixed Order types, if the workflow attached is Order Flow Return with Approval, then notifications are
sent to the users only if
the order contains return lines.
The user can also modify existing seeded workflows or create new workflows to include or exclude inspections
and/or invoicing activity.
For instance, you can have the Invoicing Activity after the Receiving activity, or you can simply close the line
without interfacing data to Receivables. For inspections, a workflow can be setup to process Invoicing once the
materials have been received or to wait until inspection has been completed before invoicing is invoked.
The seeded workflow will process Invoicing only after the completion of Inspection (delivery) Activity. Also, if any
return lines are flagged as non-shippable or non-transactable, the Receiving workflow activity will complete with
a Not Eligible result.
However, fulfillment of ATO/PTO items is required before crediting the ATO/PTO lines.
This is achieved by inserting ATO/PTO lines into Fulfillment sets. This means the ATO/PTO line will wait at
fulfillment until all its children are received and reach fulfillment.
ATO model line workflow waits until the configured line is shipped and then it progresses further no matter
whether it is PTO and ATO or only ATO or PTO.
With services, OM will use only the seeded "Return for Credit Only" workflow for returning service items when
product items are returned. Now, Order Management will use the RMA line to govern full or partial credit to the
customer when a product is returned.
Install Base will use the information from the RMA product line to determine whether a credit is given.
Transaction Types
Both order and line transaction types need to be setup in order to process an RMA.
When setting up order types, you need to assign order header and line workflows to the order type.
Since each line can go through its own flow process, you need to setup workflow assignments to let each line
assign its own workflow process.
Credit order types have an order type category Return. An order with a Mixed order type category can contain
both standard and return lines. Line level workflow processes are assigned based on the order type, line type,
and item type combination.
When you setup a return order type or mixed order type, you have the option to set a default return line type, so
that the user doesn't have to manually choose the line type unless they want it to be different. Refer to the
topical essay Using Transaction Types in Oracle Order
Management at the end of this manual for details on setting up transaction types.
Master Items Attributes

You can create a return line only if an item is Returnable. Therefore, a standard, finished good item should be
defined in Oracle Inventory with appropriately set attributes.
The best way to create your items is to copy them from the Finished Good seeded template and set additional
attributes as needed in the Master Item window. The key attributes that control the processing of a returnable
item are:
Order Management Tab: Returnable, Shippable and Transactable = Yes, RMA Inspection Required = Yes or No
Receiving Tab: Receipt Routing = Inspection (if required)
Invoicing Tab: Invoicable Item = Yes or No, Invoice Enabled = Yes or No
Note: If the Item is not flagged as Returnable, Shippable and Transactable, you cannot receive in Oracle
Purchasing's receiving module and if the item is not flagged as Invoicable the return lines will not interface to
Receivables.
Also, an item can be returnable but not orderable. This is commonly used if a company stops selling an item, but
they still want to be able to do returns for it.
For lot and/or serial controlled items, Oracle Order Management has the capability to store one or more lot and
serial numbers associated with one RMA line.
Oracle Order Management does not validate the serial numbers against Inventory serial numbers in the system
or against serial numbers associated with the referenced sales order.
Receiving captures the serial numbers of the items at delivery.
The Credit Order Discrepancy Report can show the difference between actually delivered lot/serial numbers and
the numbers on the RMA. The sales orders window can capture lot and serial numbers suggested by the
customer for the RMA line.
For ATO/PTO configurations, only the Returnable configuration lines are displayed on the sales orders window.
You need to make sure that the item attributes are set correctly for ATO/PTO children items.
Price List Setup

In order to price any new items when entering an ordered item on the sales orders window, add the new item to
a price list.
The item is added to a price list in the Price List Setup window: Pricing > Lists > Price Lists Setup. Query an
existing price list or create a new price list. Add a new line, enter the item name, UOM and price and save.
The price and UOM will default when entering the item on the order line.
When an RMA line is created and the originating transaction is known, the pricing information is populated from
the originating order line. The user can change the pricing if needed.
The list of values on the Price List will show all the active price lists on the pricing date.
Also, ATO configured items and PTO included items should be included on a price list in order to be received and
credited.
Processing Constraints
Order Management has seeded constraints that prevent data integrity problems.
For instance, you can prevent change for a line if it has been:
Closed
Canceled
Canceled at order level
Shipped
Invoiced
A return line cannot be canceled after it has been interfaced to Receivables or after it has been received. If your
business needs more restrictive rules when processing orders, you can set up rules to control changes or
operations of the order process flow.
See Processing Constraints, page 10-1 for details on setting up processing constraints.
Return Reason Codes

You can set up your own reason codes in the Receivables QuickCodes window.
Navigate to the Order Management responsibility and select the menu: Setup > Quickcodes > Receivables.
The Oracle Receivables Lookup window will appear. Query the CREDIT_MEMO_REASON code from the query
manager (Flashlight icon). View the existing codes or add a new code. These codes appear in the Return Reason
list of values.
Reports
The Returns by Reason report can be used to view all return reasons setup in the system. You can run the report
by Return Reason, Credit Order Date, Credit Order or Line Type and/or Item Number.
Freight and Special Charges for Returns

When setting up freight or special charges, you can specify if the charge is returnable, meaning the charge may
be refunded. When you create a return line from an original order line, you should copy the refundable invoiced
charges.
You can also setup special charges to be applied specifically to returns, like restocking fees, return handling,
damage etc. You can set this through an attribute called Refundable Flag (Include on Returns field) within the
Pricing Modifier setup.
See Freight and Special Charges, page 3-101 for more information.
Process Flow
This section will guide you through a basic flow for a Return for Credit with Receipt, from entry to generating a
credit memo, including:
Create an RMA having a single line whose originating transaction is unknown
Book the RMA
Receive the RMA using the Receipts window of Oracle Purchasing
Check the on-hand quantity of the item in Inventory to verify that correct quantity was received
Fulfill RMA line
Generate a Credit Memo
View the Credit Memo in Order Management
Check the Shipped and Fulfilled quantity on the RMA line
1. Enter the RMA on the Sales Orders window. Entering a return on the Sales Orders window is exactly the same
as entering an order, except at the line level the user specifies the Line Type as a Return and a negative line
quantity.
Thus, in the Order Information tab of the Sales Orders window, the user will enter the same information (i.e.
Customer Name, Order Type, etc.) as a standard order.
The Standard order type is assigned to a Generic Order and Line workflow which allows either an order or return
to be entered.
Refer to the Workflow section for details on the Generic Order and Line workflow for returns.
This is the Sales Orders window for entering the Header information for the RMA:
Sales Orders (Header) window for Returns
2. Once the Order Header information is entered, you will enter the line information within the Line Items screen:
Line Items Window
3. In the Main Tab, enter the Ordered Item and the Quantity to be returned.
The user can enter a positive or negative number. You will also see that the negative quantity will be highlighted
in another color.
Next, in the Returns tab, the user will need to enter the Line Type as a return (i.e. Return for Credit with Receipt
of Goods) and
enter a Return Reason. A Return Reason is required to be entered (i.e. Product Discontinued).
Since we did not reference a sales order, we are entering a single line RMA where the originating transaction is
unknown.
If you receive the returns partially, and if the Calculate Price Flag is set to Y (Calculate Price) or P (Partial Price),
then freight charges get applied automatically on the partially received lines.
However if the Calculate Price Flag is set to N, then the freight charges do not get applied on the partially
received lines.
4. Book the RMA. Users are able to book an order or return at either the Order Information Tab or Line Items Tab
via the Book button.
5. Receive the RMA using the Receipts window in Oracle Purchasing.
Change responsibilities to Purchasing and navigate to the Receiving > Receipts window.
In the Find Expected Receipts window, an Organization window will be displayed if this is the first time you have
navigated to the Purchasing > Receipts window since your login.
The organization you choose should be the same warehouse where your RMA is created.
In the Receipt Header window, select the Customer Tab and find your RMA #.
Tab through the Header window to the Receipts Line window.

Once you are in the Receipts Line window, the RMA number and quantity will populate the window. Check the
box next to the line you wish to receive, enter a Destination Type as Inventory and subinventory.
Save this transaction and record the receipt number in the Header window.
By choosing the Destination Type as Inventory, the user is creating a transfer to inventory transaction in
Purchasing.
These items are now considered as supply.
Purchasing will communicate the quantity received to Order Management to update the RMA.
Receipt Header Window
Receipts (Line) Window
6. Check the on-hand quantity of the item in Inventory to verify that correct quantity was received.
Change responsibilities to Inventory and navigate to the Transactions > Material Transactions window.
In the Material Transactions window, an Organization window will be displayed if this is the first time you have
navigated to the Inventory > Material Transactions window since your login.
The organization you choose should be the same warehouse where your RMA is created.
Find the item being returned and navigate to the Transaction Type tab.
Verify that the source type is RMA and the source is your RMA # for the quantity being returned.
This window will show you your item #, the subinventory chosen and the quantity specified to be returned from
the Receipts window.
Material Transaction Window
7. Fulfill RMA line.
The fulfillment activity acts as a synchronization point for all lines on the order that are in a fulfillment set.
The lines in the fulfillment set will wait at the fulfillment activity until all the lines in the set have reached the
activity.
Lines that are not in a fulfillment set simply pass through the activity automatically.
The user will not have to perform anything during this step.
The eligible lines will automatically be put into a fulfillment set.
8. Generate a credit memo for the return. The Workflow process of the return line(s) will be on the Invoice
Interface activity, once the Fulfillment activity completes. The invoice interface activity places the information
from the return line into the Receivables Interface tables. Once the information is written to the tables, the
invoice interface activity is complete, and the line proceeds to the close line activity.
However, note that the credit memo is not actually generated until the Autoinvoice program in Receivables has
been run.
The credit memo will then be viewable in the Sales Orders window.
To run the Autoinvoice program, the user needs to change responsibilities to Receivables and navigate to the
Interfaces window.
Select the Autoinvoice Master program and run the program for your RMA # and specify the invoice source as
the one associated with the line type of the RMA line.
The Autoinvoice Master program will generate the Autoinvoice Import program which generates the credit
memo.
These programs can be setup to run automatically in the background. Just set the programs as 'Deferred.'
9. View the credit memo in Order Management. To view the credit memo in Order Management, the user need to
change responsibilities to Order Management > Orders, Returns > Order Organizer window.
Query your RMA # in the Order Organizer. Once the RMA is queried, open the RMA order, click Actions and
choose Additional Order Information. Once the Additional Order Information window has opened, click on the
Receivables tab to view the credit memo.
This window will show your the credit memo number and amount.
10. Check the Shipped and Fulfilled quantity on the RMA line. From the above step, navigate in the Sales Orders
window to the Line Items tab for the RMA. Scroll to view the Shipped Quantity field.
To access the Fulfilled Quantity field, the user needs to use the folder technology to add the field to the sales
orders window.
To add the field, click on the Warehouse field in the Shipping Tab of the Line Items window.
Next, select the Folder menu at the top of the window, select Show Field and choose the Quantity Fulfilled field
from the list.
The field will populate in the window.
The Shipped Quantity means the received quantity for return lines and the Fulfilled Quantity means the
delivered quantity for the return lines.
Workflow
In Oracle Order Management, you can have many types of credit order by specifying it's Order Type and Line
Type.
Each order type and each line type is associated with an Oracle Workflow process.
You can customize order types and RMA line types to meet your business needs. For instance, you can use
Approvals and Holds with returns in order to manage exceptions when your customer returns more or less than
you authorize.
Credit order types have order type category Return'.
An order with a Mixed order type category can contain both standard and return lines. But you cannot enter
return lines into an order with order type category Regular.
The following is an example of a seeded Order Return Flow process (enter -> book -> approval notification ->
close):
Order Flow - Return with Approval
The following is an example of a seeded Order Return Line Flow process (enter -> return-> invoice -> close):
Line Flow - Return for Credit with Receipt
The following are other workflow processes that Order Management seeds for Return
Line flows:
Line Flow - Return for Credit only
Line Flow - Return for Credit only with Approval
In Oracle Order Management, there are also flows that support both order and return lines (inbound and
outbound transactions), however, there are no seeded workflows for these flows. You can create flows that
support both Order and Return Lines. For instance, the flow listed below will not work correctly, since once a line
is booked, workflow randomly picks which transition to process first. It then processes it all the way till it can go
no further. So for an outbound Line using this flow, if the branch 'Returns receiving' is first processed, it will get
marked as Not Eligible and hit the Fulfill -Defer activity and stop.
Then the WF Engine starts executing the other branch; the line will schedule and hit the Ship - Line, Manual subprocess, where it will stop and wait to get picked and shipped. However the Background Engine could pick up
the deferred activity and execute the Fulfill activity.
This activity will error out since the fulfilling event for the order line Ship-Confirmation is not yet complete.
INCORRECT Line Flow - Supporting inbound and outbound shipments
For this flow to work correctly, the flow ensures that only one transition is executed (Order or Return).
The flow needs to be defined as follows:
CORRECT Line Flow - Supporting inbound and outbound shipments
After booking the line flow branches based on the Line Category ensuring that only one of the branches are
(Order or Return) executed runtime. The activity Utility to get Line Category is seeded OM: Order Line Work Item.
With regard to item inspections, the Order Management system does not process inspection results, and only
processes delivery transactions. Based on the users business rules, if an item is rejected, the user can either
deliver to inventory (scrap sub-inventory) or return to the customer. Delivering to inventory will give credit to the
customer.
Returning to the customer will reduce the shipped quantity and credit will be given for only accepted goods.
Therefore, receiving transactions drive the flow of the return and what gets credited.
Defining Credit Check Rules

Overview
Order Management credit check rules enable you to determine what credit checking criteria is used when
determining credit exposure during the credit checking process.
Order Management transaction types determine when credit checking actually occurs, and when used in
conjunction with credit checking rules, define your credit checking process.
For example, you can define credit checking rules that utilize pre-calculated exposure information to use when
comparing a customer's current order amount against their overall exposure; if the order transaction type
utilizes this rule, and the order fails during the credit check process, it is automatically placed on credit check
hold.
You can define as many credit checking rules as you need, and if you inactivate a credit checking rule, you also
must remove it from any order types that use it.
Additionally, you can include in or exclude from your credit check rule some or all of your open accounts
receivable balances, and some or all of your uninvoiced orders.
Order Management uses the currency of the order you are credit checking to determine which credit limits to
use in credit checking calculations.
Order Management only includes orders and invoices in the same currency as the order you are credit checking
when calculating a customer's outstanding credit balance, unless you have set up multiple currency credit
checking.
You can also include/exclude returns based on your credit check rule definition.
However this should be used only if you are using return lines with credit memos.
Besides defining your credit exposure composition, the credit check rule also determines:
Credit check level (order or line)
Credit Hold level (order or line)
Conversion type used when you enable multi-currency credit check
Use of item category credit check
Send hold notifications to the sales order creator
Use of pre-calculated exposure
Credit Limits for Credit Checking and Rules Summary

1. When the Credit Check flag is turned off at the site level that pertains to the Bill-To address, there will be no
credit checking for orders for this Bill-To site. It doesn't roll up to the next level to get the credit limits.
2. If the Credit Check flag is turned on at the site level, and both overall credit limits and order credit limits are
all NULL/BLANK, then the limits for a customer who owns that bill to site will be automatically considered .
3. If the Credit Check flag is turned on at the customer level, and both overall credit limits and order credit limits
are all NULL/BLANK, roll up to the next level in the party hierarchy (if any).
Otherwise, use the Operating Unit Credit profile.
Note that party profiles are used only if Credit Management is setup. If not, from the customer level we go
directly to the Operating Unit.
4. If the Credit Check flag is turned on at each level, and there is only one field left NULL/BLANK (for example,
order limit is null but overall exposure is some number), then this NULL/BLANK field is treated as unlimited and it
does not rollup to next level.
5. If the last level reached with the Credit Check flag enabled has both overall and order credit limits set as
NULL/BLANK, it means no credit checking should be performed. IF the Credit Check flag is enabled and order
credit limit is not NULL/BLANK, then a credit check will be performed at the item category level.
6. If the Credit Check flag is disabled for item category or if the Credit Check flag is enabled and both order
credit limit and overall credit limit are all NULL/BLANK for item category, then credit checking will not happen at
the item category level, but credit checking will still be performed for the site-customer-(party)-OU level based
on the rules discussed. IF the Credit Check flag is enabled and at least one of the order credit limit and overall
credit limit fields are not NULL/BLANK, then a credit check will be performed at the item category level.
Performance Note
In order to improve performance you can enable the use of pre-calculated exposure.
Utilizing this option, the credit check engine will use summary balance details stored in a periodically updated
summary table.
The update is done by running a concurrent program which accesses Order Management and Account
Receivable transactional tables.
This program should be scheduled to run periodically based on your specific business needs.
You should also run this concurrent program when you have done major changes in your set up or transactional
data (merge customers, incorporate transactions from external systems, change transaction status using
customized programs, etc.).
To define a credit check rule:

1. Navigate to the Credit Check Rules window.
Credit Check Rules Window
2. Enter a name for your credit check rule.

3. Optionally, enter the Effective Dates for your rule.
Options Tab
4. Select the entity to perform credit checking against for your rule. Select from:
Sales Order
Sales Order Line
Note: If you select Sales Order Line as your credit check level, the Use Pre-calculated Exposure check box will be
checked and protected against update If you choose to perform credit checking at the Sales Order level, you are
limited to the system generating header level credit holds only. The Credit Hold Level field will default to Sales
Order and is protected against update.
5. Select the Credit Hold Level for your credit rule. Select from:
Sales Order: Sales Order (order level) credit check is performed for the header Bill To site.
Sales Order level credit checking provides backward compatibility with previous credit check versions. When
credit checking rules are defining using Sales Order as the credit check level, the credit check engine will
examine order totals and evaluate credit exposure against the credit profile attached at header level.
Holds will be always applied at header level.
Use order level credit check when order lines always have the same Bill To Site as the Order Header.
Sales Order Line: Sales Order Line (line level) credit check is performed against order line Bill To Sites. The
credit check engine will group all order lines belonging to the same Bill To Site and check available credit for
each specific Bill To Site.
When an order line fails credit check, any remaining lines grouped with the same Bill To Site are placed on hold.
Holds can be placed at either the order or order line level when you use line level credit checking.
Use line level credit check when sales order lines are attached to different Bill To Sites and you want to use the
credit profile defined at that level.
Additionally, you can use line level credit check when you have defined customer relationships within your
system and actively use them within Order Management.
Using customer relationships, you can create sales orders with order lines attached to different Bill To Sites
owned by different customers.
Order Header level credit checking uses header level information ignoring different bill-to sites detailed at the
line.
Credit Check uses the credit profile attached to the customer Bill-to site defined at order (header) level.
Credit checking at the Order Header level will use order totals and will evaluate credit exposure against the
credit profile attached at header level, and holds are always applied at header level.
Special Considerations for Credit Hold Level

If you update the Credit Hold Level from Sales Order to Sales Order Line, a pop up dialog box will display a
message indicating that existing sales order credit holds will need to be released manually. Select Yes to
continue or No to not commit the update.
If you update the Credit Hold Level from Sales Order Line to Sales Order, a pop up dialog box will display a
message indicating that existing sales order line credit holds will not be released automatically. Select Yes to
continue or No to not commit the update.
6. Override Manual Release check box: This check box enables an order or line which had failed credit checking
and then was subsequently manually released to be eligible for additional credit check processing. Select from:
Yes: Manual Released Holds will be overridden. You must also enter a value within the Days to Honor Manual
Release field.
No: Manual Released Holds will be honored. The field Days to Honor Manual Release will be non-updatable.
7. Days to Honor Manual Release: The field is used in conjunction with the Override Manual Release check box. If
you enable the Override Manual Release check box, you must enter a numeric value greater than zero within
this field.
Manual Released Holds (Credit Checking Procedures)
Each time a credit check failure occurs for order or order line, the corresponding order or order line is placed on
credit check hold. However, prior to the credit check holds actually being applied, the credit check process
determines:
If a manually released credit check hold exists and
If your credit check rule enables override of manually released holds (in conjunction with the value for Days to
Honor Manual Release).
If Override Manual Release is not enabled for your credit check rule, then manually released holds are honored
and no additional credit checking will occur.
If Override Manual Release is enabled, the credit checking process will validate if the release date is within the
interval defined by the value of Days to Honor Manual Release.
If the value is within the range defined, then manually released holds will be honored and additional credit
checking is not performed.
If the value is not within the range defined, credit checking can occur again and credit check holds can be
applied if the order or lines fails the credit check process.
Note: The value of OE_HOLD_RELEASES.CREATION_ DATE is used by the credit check process to determine if the
duration defined for the credit check rule is within range for additional credit checking: when any hold is
released for an order or line, Order Management inserts a record within OE_HOLD_RELEASES.
8. Select the conversion type to use when performing credit checking using your credit rule.
The LOV for this field is limited to the values you define within the Oracle General Ledger Conversion Rate Types
window.
9. Select the Check Item Categories check box for your credit rule if you wish to perform credit checking for
sales orders by Item Categories defined for Order Management.
10. Select the Send Hold Notifications check box if you wish to send hold notifications whenever a credit hold is
placed for a sales order or order line. The notification is sent to the creator of the order.
Determine the type of credit exposure to use when defining your credit check rules by selecting the Exposure
Tab within the Define Credit Check Rules window.
Exposure tab in the Credit Check Rules Window
Exposure Tab
11. Select the Use Pre-calculated Exposure check box for your credit rule if you wish to perform credit checking
against pre-calculated exposure summary tables.
When the first credit check rule that has the Use Pre-Calculated Exposure check box checked is successfully
saved, the following message will display:
This credit check rule uses pre-calculated exposure. Please run the Initialize Credit Summaries program to
update the pre-calculated data.
If the Use Pre-calculated Exposure check box is checked and the Include Open Receivables balance check box
is checked, then Open Receivables Days is protected against update and is NULL.
If the Use Pre-calculated Exposure check box is checked and the Include Uninvoiced Orders check box is
checked, then Shipping Horizon Days is protected against update and is NULL.
12. Select the Include External Credit Exposure check box if you wish to include external exposure details
imported into Order Management during the credit checking process.
When an Oracle Order Management sales order is credit checked, the exposure data from the external system is
included in the overall exposure check.
The default value for this check box is un-checked (exclude external exposure details when performing credit
checking).
Receivables Balance Region
13. Select the Open Receivables Balance check box for your credit rule if you wish to include open receivables
balances.
You must enable either the Include Open Receivables Balance check box or the Include
Uninvoiced Orders check box in your credit check rule.
You can activate both, but you cannot toggle both off.
If you select both the Pre-calculated Exposure and Open Receivables Balance check boxes, you are unable to
specify Open Receivables Days.
14. If you enabled Include Open Receivables Balance in your credit check rule, you can indicate whether to
Include Payments at Risk when calculating a customer's outstanding balance.
Receipts at risk are remitted receipts that have not been cleared, or discounted (factored) receipts that have not
been risk eliminated.
If the performance of credit checking requires improvement you can toggle off this option.
15. If you enabled Include Open Receivables Balance, enter a value to indicate the range of dates for open
receivables you wish to include for your credit check rule.
Negative Number: Includes past due, current, and future open receivables up to X days beyond the current
date
Positive Number: Includes open receivables with invoice dates X days earlier than the current date
No Value: Includes all open receivables
Uninvoiced Orders Region
Note: If you do not select the Include Uninvoiced Orders check box, you cannot select any check boxes within
the region.
Important: If an order line has been interfaced to the Receivables interface table but hasn't been invoiced yet,
the Order Management
credit check engine will include this line amount as part of the uninvoiced order amount. If your system enables
credit checking and your Receivables Interface table can potentially contain large volume of data, it is
recommended that you create a custom index on RA_INTERFACE_LINES_ALL table
ORIG_SYSTEM_BILL_CUSTOMER_ID column.
16. Select the Include Uninvoiced Orders check box if you wish to include uninvoiced orders for your credit rule.
If you enabled Include Uninvoiced Orders:
Indicate whether to include Freight and Special Charges for uninvoiced orders when performing credit
checking.
Select the Freight and Special charges check box to include Freight and Special Charges.
Indicate whether to include Tax information for uninvoiced orders when performing credit checking Select the
Tax check box to include Tax information for uninvoiced orders.
Credit checking calculations on open receivables always include tax amounts and are not affected by the Include
Tax option. If the performance of credit checking requires improvement you can toggle off this option.
Indicate the number of scheduled shipping horizon days for your credit rule for uninvoiced orders to be
included in your total credit exposure when performing credit checking.
For example, if you enter 45, the total exposure includes only uninvoiced orders scheduled to ship within 45
days of the current date.
Orders scheduled to ship after 45 days are not included when calculating exposure.
Note: If the Use Pre-calculated Exposure check box is checked, Scheduled Shipping Horizon Days is protected
against update.
Indicate whether to Include Orders Currently On hold. Select the Include Orders Currently On hold check box to
include orders on hold within the exposure calculation for your credit rule.
17. Indicate the Maximum Days Past Due.
The Maximum Days Past Due field value specifies the number of day that you will allow an invoice to be past
due before holding the customers orders. During the credit checking process, Order Management will verify that
no invoices for the customer have been past due beyond the number of days you specified with this field. If
there are any such past due invoices, the order is placed on credit hold.
18. Save your work.
Deactivating Credit Checking

There are three ways to deactivate Credit Checking on an order:
Use an order type that does not have an assigned credit rule
Define the Customer Profile so that the Credit Check box is not selected
Use payment terms for which the Credit Check box is not selected Deactivating Credit Checking does not
automatically release orders previously on credit hold. However, the next time you attempt to Book, Pick Release
or Purchase Release (for drop shipments), Pack, or Ship Confirm an order which utilizes a Order Management
Transaction type that enables credit checking to occur at the specified order points, or you perform an order
change that trigger credit checking in the Sales Orders window, Order Management will releases the credit check
hold if the order or line meets the requirements for successful credit check.
Overview
In this practice you will learn how to create a credit check rule in Oracle Order Management
Tasks
4.
Create a credit check rule named Booking.
Credit Check Level: Sales Order
Credit Hold Level: Sales Order
Conversion Type: Corporate
5.
Enable Credit Check and Credit Hold for your customer.
6.
Suspend the customers credit.
Solution Defining Credit Check and Hold

Login
Login to the database using the User Name and Password supplied by your instructor.
Create Credit Check Rule
(N) Order Management > Setup > Credit > Define Credit Check Rule
1. Enter Booking in the Rule field.
2. Use the list of values to select Sales Order in the Credit Check Level field.
3. Use the list of values to select Sales Order in the Credit Hold Level field.
4. Use the list of values to select Corporate in the Conversion Type field.
5. On the Exposure tab, enable the following fields:
Use Pre-Calculated Exposure
Include Uninvoiced Orders
Include Freight and Special Charges
Include Tax
Include Orders Currently On Hold
Include Returns
6. Save.
Define Credit Check and Hold
(N) Order Management > Receivables > Customers > Customers
26.Enter your customer name in the Name field.
27.(B) Find.
28.Click your company name in the Name column. (SH-Big City)
29.Within the Accounts tab, click the View Details icon in the Details column.
30.Open the Account Profile tab.
31.Enable Credit Check.
32.Enable Credit Hold.
33. (B) Apply.

34.(B) Save.
OM Concurrent Programs
Initialize Credit Summaries Table7

OM: Prevent Booking for Line Generic Holds
Credit Check Processor
Credit Exposure Report
Practice Overview
In this practice, you will learn how to create orders and record customer acceptance. Please
note that you will be completing an order to cash cycle with customer acceptance using all
the seeded data available in the environment.
Tasks
Create an order to cash lifecycle
1.
Create an order.
2. Save and book the order.
3. Pick release the order .
4. Ship confirm the order.
5. Use AutoInvoice to create an invoice for the order.
Enable Customer Acceptance in Order Management

1. (N) Orders, Returns > Setup > System Parameters
Enable Fulfillment Acceptance = Yes
2. Enable function security for the Order Management Super User responsibility for the following
two functions:
Sales Orders: Fulfillment Acceptance This ensures that the action attribute
Fulfillment Acceptance is available in the Actions LOV. You can use the folder
functionality to include the Fulfillment Acceptance option in the Actions LOV.
Sales Orders: Update Acceptance Attributes This allows for updating the
acceptance attributes of Acceptance Name and Acceptance Expire days.
Note: These are attached to the sales order menu ADS_OM_SUPERMENU.

3. Change your responsibility to Revenue Management Super User Vision Operations USA.
4. (N) Revenue Contingencies > Contingency Definition
5. Create a Contingency Rule for pre-billing implicit acceptance. Contingency rules are terms and
conditions that prevent immediate revenue recognition like delivery, acceptance, government
regulations, customer creditworthiness etc.
6. A contingency rule consists of the following that you need to enter:
Deferral Reason: XX-CA-PREBILL-IMPLICIT
Start Date: enter a date of your choice
Related General Policy region: Select the None button
Define Deferral Reason Removal Event region:
Removal Event: Invoicing
Event Attribute: Ship Confirm Date
Days Added to Event Attribute: any number that you want the removal event to occur
7. Click (B) Apply and return to the main page.

8. Click (B) Define Assignment Rules.
9. Enter the following information:
Rule Name: XX-CA-PREBILL-IMPLICIT-RULE
Revenue Contingency Name: XX-CA-PREBILL-IMPLICIT
Parameter: Bill-To Customer
Condition: IN
Case Sensitive: No
Value: Business World
10.You can add one or more parameters for the assignment rule. Click (B) Apply.
Using Pre-Billing Implicit Customer Acceptance
11.Change responsibility to Order Management Super User, Vision Operations USA
12.Enable the Acceptance-related fields using folder functionality on the sales orders line in the
Others tab:
Acceptance Name (this is known as Deferral Reason in Revenue Management

responsibility)
Acceptance Date
Acceptance Expire Event
Acceptance Expire Days
Acceptance Type
Accepted By
Accepted Qty
Acceptance Description
13.Open a default folder, include the above fields in the Others tab using the Show Field option.
Checke the Make as Default box and Use Folder > Save As giving the folder name as XX-LineCust-Accept.
14.The concurrent request set Implicit Acceptance Request set will run for recording implicit
acceptance and updating the above fields.
15.Enter the following in the Quick Sales Orders window:
Order Type: Mixed
Item: AS54888
Qty: 2
16.The default acceptance details will be displayed in (T) Others.
17.Book the order, using (B) Book.

18.Pick Release the order using (N) Shipping > Release Sales Orders > Release Sales Orders.
19.Ship Confirm the order.
20.Use AutoInvoice to invoice the order. (N) Receivables > Interface > AutoInvoice.
Note: If you require to perform an explicit acceptance, use Actions > Fulfillment Acceptance to
open the Order Information Portal page and record your acceptance details.
Overview of Internal Requisitions
Internal requisitions provide the mechanism for requesting and transferring material from inventory to other
inventory or expense locations. When Purchasing, Order Management, Shipping Execution, and Inventory are
installed, they combine to give you a flexible solution for your inter-organization and intra-organization
requests. You should be able to:
Set up your supply chain and automatically source your requirements from inventory or suppliers
Define your inter-organization shipping network, and optionally require that you use internal orders for your
inter-organization transfers
Use intransit inventory when you want to track items as they move between organizations
Reduce warehousing, shipping, and handling costs by requesting items in fixed lot sizes
Use the same windows for data entry and inquiry that you use for purchase requisitions and sales orders
Take advantage of standard requisition and sales order functionality to suit your individual business
requirements
Automatically generate inventory replenishment requisitions and fulfill them via internal or external
suppliers
Automatically source MRP generated requisitions to internal or external suppliers
View the status of requests online
Use internal requisitions to move inventory items from one inventory organization to another, even if that
organization belongs to a different operating unit, legal entity, or ledger
Major Features
Complete Item Sourcing Definition
Purchasing and Inventory combine to provide the flexibility you need to define your item sourcing information.
You can use the default sourcing options to automatically determine the correct source type and source for
your requests.
You can specify either Inventory or Supplier as the default source type, as well as the source organization and
subinventory for internal requests.
Inter-Organization Shipping Network

Inventory provides the features you need to define your inter-organization shipping network.
For transfers between two organizations, you can specify whether to use intransit or direct shipments.
You can also require internal orders for transfers between specific organizations.
Flexible Processing
You can tailor internal requisition processing to fit your requirements. You can limit online interaction by setting
up background processes to automatically perform specific actions such as creating inventory replenishment
requests and creating internal sales orders in Order Management. Or, you can take advantage of other
features such as online requisition approvals, internal sales order cycles, and online receipt and delivery of
internally requested items.
Creating Online Requisitions

You can create online internal requisitions for both expense and inventory destinations using the same
windows you use to create purchase requisitions.
You can combine inventory and supplier sourced requisition lines on the same requisition.
Also, Purchasing uses your item sourcing information to default the correct source type and supplier for the
item and destination. You can define requisition templates for commonly requested internally sourced items.
Full Unit of Issue Enforcement

Purchasing offers the option of full unit of issue enforcement in which quantities entered on internal
requisitions are automatically rounded to a full unit of issue defined for the item.
You can also set this option to recommend a rounded quantity on requisitions, but leave the opportunity to
change the recommended quantity.
The quantity rounding is based on the specified unit of issue, if available, otherwise on the primary unit of
measure.
Inventory Replenishment Requisitions

Inventory generates replenishment requisitions through min-max planning, reorder point planning,
subinventory replenishment for replenishment counts, and Kanban replenishment. Purchasing uses your item
sourcing information to create inter-organization or subinventory transfer requests.
See: Overview of Inventory Planning and Replenishment, Oracle Inventory User's Guide.
See: Demand for Internal Requisitions, page 3-16.
MRP Generated Requisitions

MRP generated requisitions are sourced using the same item sourcing information that you define for inventory
replenishment and online requisitions. For "buy" items, the Requisition Import process uses the item sourcing
information to create either a purchase requisition or an inter-organization internal requisition for planned
orders.
Approvals and Controls

You can control internal requisition approvals and document security just as you control purchase requisitions.
Purchasing gives you the flexibility you need to set up approvals and limits for internal requests.
You can use the same authorization rules, or you can relax or tighten controls for internal requisitions.
Creation of Internal Sales Orders

When you approve an internal requisition for a stocked item, Purchasing translates the requisition into an
internal sales order, providing a link between the end user's requirement and the physical demand against
Inventory.
Order Management
Once you create an internal sales order from a requisition, you can manage internal requisitions just as you
manage regular sales orders. You can use Order Management to define order cycles, approvals and holds to
effectively process requisition orders.
You can selectively pick release and otherwise process internal sales orders as easily as you do regular sales
orders.
Complete Requisitions Status Visibility

You get complete visibility on the status of requests through inquiries and reports.
You get online visibility to the internal sales order number, as well as the shipment and delivery status for
requisitions.
You can report on backordered items, internal requisition status, and delivery discrepancies.
Exception Processing
Internal requisitions help you manage exceptions to your normal business flow. Order Management
automatically backorders your request when you have insufficient supply to fill the internal order by creating
another shipment line for the unavailable quantity.
You can reschedule orders when the shipment date changes, and the expected arrival date on the intransit
shipment is updated automatically.
Cancellation of Requisitions
You can easily cancel a request if you have a change in requirements or if you cannot fulfill the entire order.
Using Order Management, you can partially or fully cancel the line quantities on the internal sales order.
You complete the cancellation process by cancelling the original requisition line in Purchasing.
Using Internal Requisitions

Internal requisitions provide a flexible solution to your inventory requisitioning needs.
You can eliminate user intervention when you do not need it, such as when you are loading internal
requisitions into Order Management or placing demand. The following sections describe the entire business
and information flow for internal requisitions, and identifies opportunities for you to simplify processing.
Demand for Internal Requisitions

Demand for inventory requests can come from several sources. The primary sources are:
Online user's request for stock items out of inventory
Inventory Replenishment Requests
Oracle Master Scheduling/MRP and Supply Chain Planning generated requisitions
External system's requests
Online Requests
Online requisitions give you the choice of supplier or inventory sourced requisitions.
Default sourcing information is determined by the requisition type, the item, and the destination of the
request. When you enter a requisition, Purchasing automatically selects the correct source type and source
information for the item and destination.
To restrict certain users to internal requisitions only, set their profile PO: Legal Requisition Type to Internal.
Purchasing then requires that they source all internally orderable items from inventory. See: Entering
Requisition Headers, page 3-48.
For frequently requested items, you can define requisition templates to create internal requisitions quickly.
Requestors can pull up the template they need, fill in the need-by date and destination of the request, and
specify the quantity for each desired item.
Internal requisitions also use the Account Generator, which automatically builds account distributions. You
can specify only one accounting distribution per inventory sourced line. See: Using the Account Generator in
Oracle Purchasing, page E-6.
Inventory Replenishment Requests
Inventory automatically generates requisitions to maintain an item's stock level.

The requisitions may request stock from an internal predefined source organization or from an outside
supplier.
See: Overview of Inventory Planning and Replenishment, Oracle Inventory User's Guide.
Inventory generates replenishment requests automatically using the following methods:
Min-Max Planning
Reorder Point Planning
Subinventory Replenishments for Replenishment Counts
Kanban Replenishments
All inventory replenishment methods create requisitions via the Requisitions Open Interface.
Important: If the destination subinventory uses locator control, you must specify a primary locator for direct
inter-organization and subinventory transfers.
Tip: You can interface with third-party systems to enter count information and load it into Inventory using the
Replenishment Interface. Inventory automatically creates replenishment requisitions using the source and
planning method you define.
Kanban Replenishments
In a pull-based system, inventory items for a particular part or assembly area are replenished as soon as
they are needed. When the items are needed, kanban cards in Oracle Inventory change their Supply Status
to Empty, and Inventory generates the kanban replenishment request automatically. Then Requisition
Import in Purchasing validates and imports replenishment requests as requisitions. If the Source Type of the
request is Supplier, Purchasing creates a blanket release (if a blanket agreement exists) or a standard
purchase order (if a valid quotation exists) for the item. If the Source Type is Inter-Org, Requisition Import
generates an internal requisition for the item. See: Overview of Kanban Replenishment, Oracle Inventory
User's Guide. See: Requisition Import Process,
Once Purchasing approves the standard purchase order, blanket release, or internal requisition, Inventory
automatically receives a status for the kanban card of In Process.
In Purchasing, Kanban replenishment requests look like any other purchasing document, and you receive
them like you do any other shipment. As soon as you receive the item for delivery through the Receipts or
Receiving Transactions windows in Purchasing, Inventory automatically receives a status for the kanban
request of Full, indicating that the inventory supply has been replenished.
MRP Generated Requisitions
Master Scheduling/MRP creates requisitions for "buy" items when you release them using the Planner
Workbench. MRP generated requisitions are sourced using the same rules as online and inventory
replenishment requisitions. However, since MRP is planning for the entire organization, inventory sourced
requisitions for MRP planned orders must be inter-organization transfer requests. You cannot request
subinventory transfers using internal requisitions for MRP planned orders, unless you specify a non-nettable
source subinventory on the internal requisition. See: Viewing On-hand Quantities, Oracle Master Scheduling
/ MRP User's Guide.
External Systems
You can automatically import internal requisitions from other Oracle Applications or existing non-Oracle
systems using the Requisitions Open Interface. This interface lets you integrate the Purchasing application
quickly with new or existing applications.
Purchasing automatically validates your data and imports your requisitions.
You can import requisitions as often as you want. Then, you can review these requisitions, approve or
reserve funds for them if necessary, and place them on internal sales orders.
See: Requisition Import Process, page 13-29.
Internal Requisition Approvals

After you create an internal requisition, you can optionally require approval.
For online requests, you can set up approval rules that are specific for internal requisitions, or you can share
the same rules you use for purchase requisitions. If you do not require additional approval steps, you can set
up rules so that you can always complete and approve the document in the Requisitions window. See:
Entering Requisition Headers, page 3-48.
Min-max planning, Reorder Point planning, and MRP generated requisitions are loaded as approved
requisitions through the Requisitions Open Interface.
If you set the Inventory Profile INV: RC Requisition Approval to Unapproved, you can optionally load
Subinventory Replenishment requisitions as unapproved and use the document approval functionality in
Purchasing.
This profile option affects only Subinventory Replenishment requisitions. See: Submitting a Document for
Approval, page 2-32.
See: Oracle Inventory Profile Options, Oracle Inventory User's Guide.
An internal requisition corresponding to a kanban card in Oracle Inventory enters Purchasing through
Requisition Import with a status of Approved. (If encumbrance/budgetary control is on, Purchasing sets the
status to Pre-Approved.) As soon as the internal requisition is approved, Inventory automatically receives a
status for the kanban card of In Process.
See: Demand for Internal Requisitions, page 3-16. See: Requisition Import Process, page13-29.
Requisition supply is created for the destination organization as soon as the requisition is approved. If you
create approved requisitions through Requisition Import, supply is created at the time the requisition is
created. Master Scheduling/MRP and Inventory planning get complete visibility to the incoming internal
requisition supply so the planning processes do not create additional reorders for items that you have already
requested.
Creation of Internal Sales Orders

Once you approve inventory sourced requisition lines, Purchasing translates the requisition into an internal
sales order, providing the link between the requestor's requirement and the physical demand against
inventory. You run two separate batch
processes to create the internal sales order from the approved requisition:
Create Internal Sales Orders. See: Create Internal Sales Orders Process, page 13-4.
Order Import. See: Order Import, Oracle Order Management Implementation Manual.
Purchasing uses location associations to create internal sales orders from internal requisitions for a given
deliver-to location. When you associate a customer and customer site with a location and then enter an
internal requisition with that location as the deliver-to point, Purchasing uses the associated customer and
customer site on the internal sales order that it creates. The associated customer site becomes the ship-to
site
for Order Management's ship confirmation. See: Defining Locations, page 1-18.
See: Creating and Updating Customers, Oracle Receivables User's Guide.
Internal orders are automatically scheduled by setting the Schedule Ship Date on the sales order to the Needby Date from the requisition. If you specify a subinventory on the internal requisition line, Order Management
reserves the goods and uses only the specified subinventory for allocation. If the goods do not exist at the
specified subinventory, Order Management backorders them, even if they do exist in another subinventory.
The Create Internal Sales Orders process loads the Order Management open interface,
OrderImport, using the order type you define in the Purchasing Options window. See: Defining Internal
Requisition Options, page 1-38. OrderImport creates internal sales orders from the records in the interface
table, and determines the order cycle and defaults values based on the order type.
Note: You should not drop-ship internal sales orders. See: Drop Shipments, page 4-114.
Multi-Org: Creation of Internal Sales Orders Across Operating Units
A Multi-Org implementation of Purchasing enables separate operating units within an organization to operate
independently of each other. However, you may still need to obtain goods from another operating unit, and
Purchasing supports this.
You can create an internal sales order for an item in another operating unit. When creating this internal sales
order, you must create it in the destination organization's operating unit, and all Order Management activity
must take place within that destination operating unit.
For example, the following table lists the generalized steps involved and indicate the organization in which
they take place.
Step Action Operating Unit 1
Inventory Org A
Operating Unit 2
Inventory Org B
1- Create and approve internal requisition. X
2- Run Create Internal Sales Orders. X
3- Run Order Import in Order. Management X
4- Perform pick release and ship confirm in Order Management. X
5- Receive goods. X
When you use internal sales orders to transfer goods from another operating unit, the items' transfer cost is
posted to the intercompany payables and receivables accounts as defined in the shipping network and an
intercompany invoice can be generated.
See: Inter-Organization Shipping Network, Oracle Inventory User's Guide.
Management of Internal Sales Orders

You manage internal sales orders using some of the same windows as customer sales orders.
Once you import an internal requisition using Order Import, you can use the Sales Orders window to change
the reserved quantity, schedule date, ship-to contact, and shipment priority.
The destination organization has complete visibility to any changes in incoming supply based on schedule
date changes or partial shipments.
The price on the internal sales order line comes directly from the price on the requisition line, and is always
the item cost.
Order Import does not use the price list to recalculate the line price and Oracle Receivables ignores internal
sales orders. So the price on the internal sales order is not used.
The profile option INV: Advanced Pricing for Intercompany Invoice actually controls the price on the
intercompany payables invoice.
When this profile option is set to No (or null), the price on the intercompany invoice is derived from the
Transfer Price List associated to the customer or item. If set to Yes, the price is derived from the Advanced
Pricing engine. See: Intercompany Invoice Pricing and Using Advanced Pricing Engine with Intercompany
Invoicing, Oracle Inventory User's Guide.
Once an internal sales order is scheduled, it is visible as demand. You can reserve inventory for internal
requisitions either to the organization, or the organization and subinventory levels.
Order Management does not process internal sales order lines for the Receivables Interface, even if the
Receivables Interface is an action in the order cycle for the internal sales order.
Note: You should not drop-ship internal sales orders. See: Drop Shipments, page 4-114.
Pick Release for Internal Sales Orders

You can directly pick release from the Shipping Transactions window. Or you can selectively release one
internal sales order at a time by entering the internal sales order number as a pick release criterion. Or, you
can release a group of internal sales orders by specifying the internal sales order, order type, and a range of
dates, or by using the shipment planning delivery, trip, and trip stop information. You can also release internal
sales orders with customer orders by entering a range of dates.
When you enter an internal requisition, you must specify the source organization, and you can optionally
specify the subinventory source. If you do not enter source subinventory information on an internal
requisition, picking proceeds using the standard inventory picking rules.
Oracle Shipping Execution releases only order lines which meet the prerequisites of the order cycle specific to
the internal sales order type. See: Oracle Shipping Execution User's Guide.
Ship Confirmation for Internal Sales Orders

Use the Shipping Transactions window to ship confirm entire or partial shipments. You can also backorder the
internal sales order when you do not have enough on-hand quantity to fulfill the request.
Partial shipments are handled by splitting internal order lines into multiple shipment schedules with different
delivery dates. You cannot change the warehouse or the subinventories on the delivery details.
When you ship confirm, Shipping Execution updates the Inventory Interface and generates a delivery ship
notice outbound (DSNO) transaction. Inventory automatically updates on-hand quantities to reflect the
internally ordered items that you shipped.
If you are shipping using intransit inventory, the destination organization gets complete visibility of the
incoming intransit supply. Internal requisition supply is reduced by the quantity of the shipment.
You can also enter the expected arrival date at ship confirmation to provide a more accurate supply picture to
MRP and inventory planning. See: Oracle Shipping Execution User's Guide.
Management of Internal Requisitions

Update Intransit Information
For inter-organization transfers that use intransit, you can use the Manage Shipments window to update the
expected arrival date. Master Scheduling/MRP and inventory planning get complete visibility to the change in
expected arrival date.
See: Managing Shipments, page 9-81.
Receive, Inspect, and Deliver Items

Use the Receipts and Receiving Transactions windows to process receipts of
inter-organization requests that use intransit. Receiving personnel can simply enter the
requisition number on the shipping documentation and process the entire shipment
using express receiving transactions. For receipt of partial shipments, you can record
the quantities for the individual items included in the shipment. You can receive items
into receiving, or you can receive the goods directly to the final destination, either an
inventory or expense location.
If you receive items into receiving/inspection, you process inspections, transfers, and
deliveries for internal requisitions just as you would process supplier receipts or
inventory transfers. See: Overview of Receiving, page 9-1.
View Internal Requisition Status

In Purchasing, you can view the internal sales order and any changes to it, by selecting
View Sales Orders on the Tools menu in the Requisition Lines Summary window. Or,
you can access the Sales Orders window directly in Order Management and query on
the specific internal sales order number, or any other relevant criteria. The Sales Orders
window provides information about the status of the internal sales order, quantities
shipped, quantities cancelled, and dates of transactions.
You can also report on requisition status. See: Backordered Internal Requisitions Report,
page 11-6, Internal Requisitions Status Report, page 11-19, Internal
Requisitions/Deliveries Discrepancy Report, page 11-20, and Requisitions on Cancelled
Sales Order Report, page 11-77.
Cancelling Internal Requisitions

If you cancel an internal sales order that was generated by an internal requisition, you get a warning message
that the order line is related to a requisition line that is now awaiting cancellation. You can then use the
Control Document window to cancel the requisition line.
See: Controlling Documents, page 2-57.
Purchasing lets you cancel or final close an inventory sourced requisition line only after you cancel the
internal sales order in Order Management. See: Cancelling Orders, Oracle Order Management User's Guide.
Internal Requisitions Processing Summary

Below is a summary of key transactions and processes you use for Internal requisitions.
If you are using inventory replenishment or MRP generated internal requisitions, Pick Release and Ship
Confirmation are the only required online transactions.
If you are creating online requests, you also use the Requisitions window.
See: Online Processing Automation for Internal Requisitions, page 3-30 for suggestions on how to implement
automated processing and reduce online interaction.
Step Action Required Window/Process

1- Create Internal Requisition On-line or Automatic Requisitions window and Requisition Import process: Inventory
replenishment, MRP Planned Orders, External Sources
2- Approve Requisition Optional Approve Documents window
3- Create Internal Sales Orders Automatic Create Internal Sales Orders process, Order Import process
4- Modify Order Schedule Optional Sales Orders window
5- Pick Release Orders On-line Release Sales Orders for Picking window or Shipping Transactions window
6- Confirm Pick-Wave Move Order Optional Transact Move Order window (if not auto-pick confirming from Pick Release
window)
7- Ship Confirmation On-line Shipping Transactions window, Order Management Interface, Inventory Interface
8- Receive Items Optional Receipts window, Receiving Transaction Processor
9- Inspect Receipts Optional Receiving Transactions window, Receiving Transaction Processor
10- Deliver Receipts Optional Receiving Transactions window, Receiving Transaction Processor, Inventory Transaction
Processor
11- View Requisition Status Optional Requisition Headers Summary window, Requisition Lines Summary window
12- Cancelling Internal Orders Optional Sales Orders window, Control Document window, Define Mass Cancel window, Run
Mass Cancel window
Internal Requisitions Setup Overview

Internal requisitions provide a solution to a variety of inventory requisitioning needs.
When you implement this feature, you need to carefully review the options and configure the applications to
support your business processes.
For example, if you are using internal requisitions to generate inventory replenishment requisitions and fulfill
them via subinventory transfers within a plant, you may want to limit your online interaction to pick release
and ship confirmation.
You do not have to record separate ship, receive, and deliver transactions when the same employee actually
picks the items out of the source subinventory and places them at the destination in one step.
Product Internal Requisition Setup Function

Order Management Update profile options,
Define transaction types,
Define order number sources,
Update/define default value rules,
Define price lists,
Define Concurrent Program Resubmission interval for the Order Import process
Shipping Execution Define release sequence rules,
Define pick slip grouping rules,
Define shipping parameters Inventory Define internally requested items,
Define inter-organization shipping network,
Define item sourcing,
Define Concurrent Program Resubmission intervals in Inventory planning and replenishment windows
Purchasing Define Internal Requisition Deliver-To Sites,
Set Legal Requisition Type profile,
Define Purchasing Options,
Define Concurrent Program Resubmission intervals for the Requisition Import and Create Internal Sales Orders
processes
Minimum Order Management Setup for Internal Requisitions

You use standard sales order functionality to define transaction types for internal sales orders.
You also need to use the Purchasing Options window to specify the order type you use for internal requisitions.
See: Defining Internal Requisition Options ,You must perform the following setups in Order Management to use
the internal requisition features.
You may choose to take advantage of other Order Management features which require additional setups.
See: Oracle Order Management Recommended Setup, Oracle Order Management Implementation Manual.
Define Order Management Profile Options

Set the profile option OM: Item Flexfield.
This profile option defines which structure of the item flexfield to use.
Note. that Order Management uses the same ledger as defined in the System Options window in Oracle
Receivables.
Use the Parameters window in Order Management to define the Item Master organization for this installation.
Tip: Set the Item Validation Organization to the same Item Master organization as your purchasing reference
organization (set in the Financials Options window).
Define Transaction Types
Use the Transaction Types window to define order and line types.
Order Management provides default order cycle workflows that you must associate with each order and line
type.
Define an Order Management Number Source For Internal Requisitions
Define order number sources to automatically number internal sales orders as you import them.
You can use a single order number source to assign unique numbers to all your orders, or you can use a
different order number source within each order type.
Define a Price List For Internal Requisition

Although internal requisitions use the item's cost as the price, Order Management requires price lists to
process all sales orders.
Define a price list for use with the internal requisition order type.
You do not need to add any lines to the price list.
Decide which Default Value Rules to Use

Default value rules define the defaulting that occurs as orders are entered or imported.
Order Management provides default value rules that you can use for internal sales orders.
Confirm that the default value rules that Order Management provides suit your business needs.
If not, use the Defaulting Rules window to modify them.
Define Inventory Accounting (Account Generator)

Order Management can dynamically create the Cost of Goods Sold (COGS) Account for each shipped or
returned item based on rules you define. Order Management provides a default Account Generator process to
be used in determining the COGS Account
during the Inventory Interface process.
You can either accept the default COGS Account Generator process or customize it to suit your business
needs. For more information on how to accept or customize this feature, see the Oracle Order Management
documentation.
Internal Sales Orders Processing Constraints (Optional)
Order Management processing constraints apply to all your sales orders, including internal sales orders
imported from Purchasing. Processing constraints prevent users from adding, updating, deleting and
cancelling order information beyond certain points in the order cycles.
You can use the System rules Order Management provides, which prevent data integrity violations, or define
your own, stricter, rules. See: Defining Processing Constraints, Oracle Order Management Implementation
Manual.
Minimum Shipping Execution Setup for Internal Requisitions

Perform the following steps:
Define release sequence rules
Define pick slip grouping rules
Define shipping parameters
Minimum Purchasing Setup for Internal Requisitions

Define Internal Requisition Deliver-To Sites
Purchasing uses locations to identify the final delivery location for both inventory and supplier sourced
requisitions.
As a requestor, you want to specify the same destination for both purchase and internal requisitions. As a
shipping clerk, you are concerned with the final delivery location of the item, regardless whether it is for an
internal or external customer.
Purchasing and Order Management use location associations to minimize the decisions you need to make
when you create internal requests.
Use the Location window to define a location for each site that receives either inventory or supplier sourced
material.
For internal requisition deliver-to locations, you also need to associate the locations with a customer.
Use the Customers window to define a Customer and Ship-To site for each deliver-to location.
Use the Business Purposes region in the Customers window to associate your internal locations to your
customers.
Tip: Create an internal customer for each destination organization, and customer ship-to site for each deliverto location within the destination organization.
Tip: Define the same address for the customer ship-to site as the deliver-to location. Order Management
prints the ship-to address on
the shipping documentation.
Tip: Order Management requires both a ship-to and an invoice-to for each order, even though internal order
lines are not invoiced.
When you define a customer, either make the ship-to address both a ship-to and bill-to business purpose and
set the Primary flag to Yes on the business purpose, or assign the ship-to to a bill-to location.
Set Up Internal Requisition Approvals and Security
You set up approval and security rules for internal requisitions just as you do for purchase requisitions.
Use the Document Types, Positions, Position Hierarchies, Approval Groups, and Assign Approval Groups
windows to set up approval and security options for internal requisitions. See: Setting Up Document Approval
and Security
Define Purchasing Options for Internal Requisitions
You need to set up these additional purchasing options to use internal requisitions:
Order Type
Pick the Order Type you defined in Order Management for internal sales orders.
Purchasing uses this type to create sales orders from internal requisitions. See: Defining Internal Requisition
Options,
Enforce Quantity Rounding In the Purchasing Options window, specify whether you enforce lot quantity
rounding or display advisory messages when you create online requisitions using the Requisitions window.
See: Defining Control Options
Minimum Inventory Setup for Internal Requisitions

Define Internally Orderable Items
When you define internally orderable items, there are a few attributes that require extra consideration.
Inventory and Order Management regions Items you use on internal requisitions must be Inventory enabled,
internally orderable and stockable, shippable, and Order Management transactable for the source
organizations.
Under Inventory, you need to select the Inventory Item,
Transactable, and Stockable options. Under Order Management, you need to select the Internal Ordered,
Internal Orders Enabled, OE Transactable, and Shippable options.
Source Type - General Planning region Specify a default source type of Inventory or Supplier.
You cannot create intra-organization internal requisitions for MRP planned items.
When you specify sourcing information for MRP planned items, you need to ensure that you do not define an
intra-organization sourcing rule for these items.
List Price - Purchasing region Inventory sourced requisitions use item costs for pricing. You may still want to
specify a list price for items that are sourced both from suppliers or inventory.
Unit of Issue - Purchasing region You use units of issue to round order quantities, minimizing shipping,
warehousing, and handling costs.
Enter the unit of measure you typically use to issue the item from inventory.
Purchasing uses this unit of measure as the default for internal requisition lines sourced from inventory when
you create them in the Requisitions window.
Rounding Factor - Purchasing region Enter a number between 0 and 1.
This factor determines how to round the quantity on an internal requisition that results from conversions
between the requisition line
unit of measure and the item's Unit of Issue.
This factor ensures that the unit of issue resolves to an integer, rather than a fractional amount.
Purchasing either performs rounding automatically or advises you of the suggested quantity, depending how
you set up your purchasing options.
Set Up Item Sourcing

Internal requisitions use the sourcing information you specify in Inventory.
All items, subinventories, and organizations may have item sourcing information specified for them.
At each level (item, subinventory, or organization), you can choose whether items are replenished from
inventory or purchased from a supplier.
Source Type Specify Inventory as the default source type if you want to source requests from an internal
stock location.
Source Organization and Subinventory If you specify an item to be replenished from inventory, you must
specify a source organization; a source subinventory is optional.
When you place an order for this item, Inventory creates an internal requisition for the item from the source
location.
In case of a conflict between the item, subinventory, and organization levels, internal requisitions use the
following order of precedence to determine the default source type and source for the item and destination:
Sourcing information specified in the item-subinventory relationship
Sourcing information specified in the subinventory definition
Sourcing information specified in the item definition
Sourcing information specified in the organization setup options
Define the Inter-Organization Shipping Network

Use the Shipping Networks window to define your inter-organization network.
You must enable the network between each source (shipping) and destination (receiving) organization.
Internal Order Required
Select Internal Order Required if you want all transfers between these two organizations to use internal
orders.
Transfer Type
Specify whether you ship material directly, or use intransit inventory for shipments between these two
organizations.
Important: If you use Lot, Serial, or Item Revision Control in both the source and destination organization, you
must use intransit if
you ship from an organization with less control (i.e. Lot Control), to an organization with more control (i.e. Lot
and Serial Control).
Receipt Routing
For intransit transfers, you can choose from the following primary receipt routings:
Standard receipt, Inspection required, or Direct delivery.
FOB Point
Specify whether the destination organization takes ownership of transferred items when they are issued to
intransit (Shipment), or when they are received out of intransit (Receipt).
Transfer Charge Type
Specify how you want to apply transfer costs to the destination organization.
Choose either a predefined or requested percentage of the transaction value or a fixed amount that
represents an added value.
Set Up a Customer Association

To define your organization as the destination for an internal requisition, Order Management has to recognize
you as a customer.
See: Defining Locations, See: Creating and Updating Customers, Oracle Receivables User's Guide
Online Processing Automation for Internal Requisitions

Internal requisitions provide a number of options to automate processing.
You can set up the following processes to run automatically as often as you like to limit online interaction and
streamline processing.
Reorder Point Planning Report
Min-Max Planning Report
Requisition Import
Create Internal Sales Orders
OrderImport
Tip: Create a report group to run all requests back-to-back over specific time intervals when you are using
internal requisitions for automatic subinventory transfers.
Internal Requisitions Example

Purchasing provides flexible internal requisitions that you can tailor to meet your needs.
Review the example in this section to better understand how you can use internal requisitions.
You are not required to manage internal requisition activities exactly as described in the
following example.
Rather, the objective of these examples is to highlight the flexibility of internal requisitions
across a variety of situations.
Oracle Manufacturing recommends that you experiment and review the results of different
approaches to determine the best implementation of the internal requisition functionality for
your unique needs.
You should use this example as a starting point to better understand how you might use internal
requisitions.
Example Overview
Global Computers, Incorporated is a computer manufacturer with organizations in Austin, TX and Sacramento,
CA.
The Austin organization repetitively manufactures plastic components and uses the components, along with
purchased items, to assemble base and cover assemblies in the Sacramento organization. Ownership of interorganization transfers between Austin and Sacramento changes hands at the time of receipt (FOB Point:
Receiving).
The Sacramento organization uses the Austin base and cover assemblies to assemble configurations of
Sentinel computers. Sacramento also has a local sales offices for customer visits and demonstrations. Your
salespeople distribute sales brochures during customer visits.
Employees can request Sentinel Computers for their own use, as well as mouse pads and wrist pads for their
offices.
Define the following items at Global Computers:
Item Description
A54888 Sentinel Base Assembly Assembled in Austin, Sub Assembly of Sentinel Computer, Internally Orderable in
Austin, Default Source Type of Inventory, Default Source Organization of Austin, Default Source Subinventory of
Repetitive Assembly
S86662 Sentinel Cover Assembly Sub Assembly of Sentinel Computer, Assembled in Austin, Internally Orderable from
Austin,
Default Source Type of Inventory, Default Source Organization of Austin, Default Source Subinventory of Repetitive
Assembly
S56302 Sentinel Computer Assembled in Sacramento, Internally Orderable by Employees
C13139 Hard Drive Used in Sentinel Base Assembly
S85773 Sales Brochure Purchased from external suppliers, Stocked at Sacramento for internal use, Limited quantities on
hand at the sales office
M1002 Mouse Pad Purchased from external suppliers, Stocked at Sacramento for internal use
M1002 Wrist Pad Purchased from external suppliers, Stocked at Sacramento for internal use
Define the following subinventories at Global Computers:
Organization Subinventory
Austin AUS-Finished Goods: Contains completed Sentinel Base Assemblies,
Contains completed Sentinel Cover Assemblies, Tracked - asset subinventory
Austin Repetitive Assembly: Contains Hard Drives for final assembly in WIP,
Uses Min/Max replenishment to signal replenishment, Request from AUS-Stores subinventory
Austin AUS-Stores: Contains additional supply of Hard Drives, Tracked - asset subinventory
Organization Subinventory
Sacramento SAC-Finished Goods: Contains completed Sentinel Computers,
Tracked - asset subinventory
Sacramento SAC-Stores: Contains completed Sentinel Base Assemblies shipped
from Austin, Contains completed Sentinel Cover Assemblies shipped
from Austin, Tracked - asset subinventory
Sacramento Office Supplies: Contains supply of Wrist Pads and Mouse Pads for
internal use, Not tracked - expense subinventory
Sacramento Storage: Central storage for excess Sales Brochures, Tracked - asset
subinventory
Sacramento Visit Center: Contains local supply of Sales Brochures for customer
visits, Space for only 100 Sales Brochures, Not tracked - expense
subinventory
Inventory Replenishment Request (Manufacturing)

You use one Hard Drive during the assembly of each Sentinel Base Assembly, and
keep a limited supply of the Hard Drives in your Repetitive Assembly subinventory. As
you consume Hard Drives from the Repetitive Assembly, you want to automatically
send inventory replenishment requests to transfer additional Hard Drives from your
Stores subinventory. The material handler needs to receive the inventory request and
transfer the material before you run into a shortage situation. You create a report group
that submits the Min-Max Planning, Requisition Import, Create Internal Sales Orders,
and OrderImport processes every two hours.

As soon as the Hard Drive supply in the Repetitive Assembly subinventory drops
below the minimum quantity, the next run of the Min-Max Planning process
automatically creates a replenishment order for the reorder quantity. The reorder uses
the item sourcing information to automatically create an intraorganization request in
the Austin plant to move Hard Drives from Stores to the Repetitive Assembly
subinventory. The request is automatically loaded as an internal requisition and an
internal sales order, providing visibility of the request to the material handlers in the
Austin plant.
The material handler also runs Pick Release every two hours to identify the pull
requests from the shop floor subinventory. The next run of Pick Release creates a move
order line for the subinventory transfer of Hard Drives. The material handler picks the
Hard Drives out of the Stores subinventory, completes a ship confirmation and
replenishes the Repetitive Assembly subinventory before a shortage occurs. At ship
confirmation, the on-hand balances of the two subinventories are automatically updated.
MRP Generated Inter-Organization Request (Manufacturing)

You use Oracle Master Scheduling/MRP and Supply Chain Planning in Sacramento to
schedule production of the final assembly of the Sentinel Computer. The Sentinel Base
Assembly and Sentinel Cover Assembly are provided by the Austin organization, so
you define these items as "buy" items in Sacramento. You also specify the following
sourcing information for the item:
Source Type - Inventory
Source Organization - Austin
Source Subinventory - AUS-Finished Goods
Master Scheduling/MRP recommends that you produce 400 Sentinel Computers to
fulfill demand over the next four weeks (100 each week), and you only have 100
Sentinel Cover Assemblies and 100 Sentinel Base Assemblies on hand in Sacramento.
You need five days to ship material from Austin to Sacramento, so the planner
implements planned orders for 100 Sentinel Cover Assemblies and 100 Sentinel Base
Assemblies for the next three weeks using the Planner Workbench.
When the planner releases the planned orders for Sacramento, Master Scheduling/MRP
automatically loads the Requisitions Open Interface and submits Requisition Import.
Requisition Import uses the sourcing information that you set up to create a requisition
line for each week sourced from the Austin AUS-Finished Goods subinventory. In the
background, the Create Internal Sales Orders and OrderImport processes automatically
load the internal sales order against the Austin organization.
What if you have a three day production delay in Austin and you need to delay the
third shipment of Sentinel Base Assemblies for a few days? Sacramento needs
visibility to the delay to adjust the production schedules of the final assembly of the
Sentinel Computers. In Austin, you can use the Sales Orders window to update the
scheduled shipment date by three days, or choose a different freight carrier for faster
delivery if you need to expedite the shipment to prevent a shortage in Sacramento.
When you ship the third shipment from Austin, you can update the expected arrival
date, giving the planner and MRP in Sacramento full visibility of supply changes.
Each ship confirmation of the Sentinel Base Assemblies creates an intransit shipment
from Austin to Sacramento. You do not require inspection of your own
inter-organization transfers, so the receiving clerk in Sacramento receives directly into
the Final Assembly subinventory when the shipment arrives. The intransit inventory
balance is automatically updated and the inter-organization accounting entries are
created along with the receipt transaction.
Inventory Replenishment Request (Office Stock Locations)

In the Sacramento sales office, you use internal requisitions to replenish your stock of
Requisitions 3-35
sales brochures in the Visit Center.

Sales representatives use your brochures well, and most customers take brochures with
them after the visit. You want easy access to brochures in the Visit Center, but only
have room for 100 Sales Brochures. You typically use about 75 a week, but the number
fluctuates with sales activity. Sales representatives take what they need; you do a stock
count on Monday and Wednesday of each week and replenish whenever the stock
count falls below 25.
You need to define min-max information for the Sales Brochures that you stock in the
Visit Center subinventory. Use the Item Subinventories window to specify a planning
method of Min-max planning, a minimum quantity of 25, and a maximum quantity of
100.
Requisition Import creates an approved internal requisition for subinventory transfers,
and the sales order is automatically loaded.

The material handler reviews the picking slip, pulls the 80 Sales Brochures from Storage
Subinventory and delivers them to the Visit Center. After delivering the material the
handler records the shipment using the Confirm Shipments window. The shipment,
receipt, and delivery information is recorded at once, and the on-hand balance of the
Storage subinventory is updated automatically. Inventory automatically creates the
necessary accounting entries to reduce the overall value of Sales Brochures in the
Storage subinventory and charges the accounts associated with the Visit Center
subinventory.
Online Request for Goods out of Inventory

In Sacramento, you stock low-cost office supplies on site to provide quick delivery to
your employees. Employees can request items that are sourced from suppliers or
inventory, but they do not know the source type at the time of the request. You also
require internal requisitions to process requests for goods out of the stock locations. You
have a company policy to always request items from Office Supplies whenever
possible. You do not require any additional approvals, and a material handler picks the
items out of inventory and delivers them directly to your office. A one day turnaround
time is required for all internal requests.
As a requestor, you want to order the following items to improve your comfort and
productivity:
Sentinel Computer
Mouse Pad
Wrist Pad
Glare Screen (not stocked on site)
Use the Requisitions window to create your request. Since company policy dictates that
you request items from inventory whenever possible, the default requisition type is
3-36 Oracle Purchasing User's Guide
Internal Requisition and the default source type is Inventory. When you create the
four requisition lines for your items, Purchasing automatically uses the item sourcing
information to source the Sentinel Computer from the SAC-Finished Goods
subinventory. Since the Glare Screen can only be purchased from suppliers, Purchasing
sets the source type to Supplier and uses your sourcing rules and Approved Supplier
List entries to determine the suggested supplier and document information. See:
Automatic Sourcing, page 5-24. See: Approved Supplier List, page 5-35.
Material handlers need immediate visibility of your requests to be able to deliver in 24
hours. The system administrator sets the Create Internal Sales Orders and OrderImport
processes to run every hour for internal sales orders.
The material handler in charge of the Office Supplies subinventory runs Pick Release
twice a day to generate pick slips. The material handler reviews the picking slip, pulls
the Mouse Pad and Wrist Pad from Storage and delivers them to your office. After
getting your signature, the handler records the shipment using the Confirm Shipments
window. The shipment, receipt, and delivery information is recorded at once, and the
quantity delivered on the internal request is updated.
Office Supplies is an expense subinventory, and the correct accounts are charged when
you receive the supplies into this subinventory. Since you are sourcing from an expense
subinventory, ship confirmation does not generate any accounting entries for the issue
of the items from the Office Supplies subinventory to your office location.
A separate material handler receives the Sentinel Computer request, and picks and
ships it from the SAC-Finished Goods subinventory. When you complete the ship
confirmation, Inventory automatically issues the Sentinel Computer out of the
SAC-Finished Goods asset subinventory to the expense location listed on the
requisition. Inventory and Purchasing also record the accounting transactions to credit
the SAC-Finished Goods asset account and debits the appropriate charge account
listed on the requisition.
Finding Requisitions
Use the Find Requisitions window to:
Access the Requisitions window.
Perform requisition inquiries at header, line, and distribution levels
Depending on the function security assigned to your responsibility, you have varying
levels of access to information. A responsibility defines an application user's current
privileges while working with Oracle Applications. See: Function Security for
Purchasing, page D-1.
To enter search criteria:

1. Navigate to the Find Requisitions window. Then enter as many as desired of the search criteria described in
the following steps.
2. Select the Operating Unit for this search.

3. Enter the requisition number. If you enter a requisition number, you can also enter a Line number.
4. Select the requisition Type (Purchase or Internal).
5. Enter the Preparer.
6. Enter the Requestor.
7. Enter the Buyer.
8. Select Yes or No to restrict the search to Modified requisitions.
9. Enter the Reference Number.
10. Enter the Import Source.
11. Enter the Line Type.
12. Use the tabbed regions to further restrict the search:
In the Item region, you can enter the following search criteria: Item number,
Revision number, Category, item Description, and Supplier Item number.
In the Status region, you can limit the search by Approval status (Approved, Incomplete, In Process, PreApproved, Rejected, or Returned), Control status
(Open, Cancelled, or Finally Closed), or Reserved status (Yes or No).
In the Date Ranges region, you can enter date ranges for the following dates: Creation, Need By, and
Closed.
In the Sourcing region, you can limit the search by Source (Supplier or Inventory).
For Supplier sourced requisitions, you can further limit the search by Supplier, Site, and Currency. For
Inventory sourced requisitions, you can further limit the search by Organization and Subinventory. If you have
enabled vendored managed inventory, you can limit your search results to those items by checking the VMI
box.
In the Deliver To region, you can limit the search by Destination Type (Expense,
Inventory, or Shop Floor), Organization, Location, and (for Inventory
destinations only) Subinventory.
In the Related Documents region, you can limit the search by Document Type,
Document number and Line Number, Purchase Order number, and drop
shipment Sales Order number.
In the Accounting region, you can limit the search by Period, GL Date, Charge
Account, Budget Account, and whether there are Active Encumbrances (Yes or
No).
In the Projects region, you can limit the search by Project or Task number.
13. Select the Results group (Headers, Lines, or Distributions) to determine which
summary window to open. Depending on the search criteria you have specified, all
summary windows may not be available. For example, if you specify criteria in the
Accounting region, only the Distributions summary window is available.
14. Select the Find button to initiate the search and open the appropriate Summary window.
To clear existing search criteria:
Select the Clear button to clear any existing search criteria.

To enter a new requisition:
Select the New button to open the Requisitions window. See: Entering Requisition Headers,
Overview
In order to use internal requisitions, you must have Oracle Inventory, Oracle Order Management, and
Oracle Purchasing installed. Order Management is used to track internal sales orders. To enter an
internal sales order, you must start with a requisition in Purchasing. Steps for this practice:
Create an internal requisition in Oracle Purchasing
Instructor will run processes in Oracle Order Management
Verify the shipment of your internal order in Oracle Purchasing
R12: What Are The Steps Required To Setup An Internal Requisition In Purchasing? (Doc ID
1384716.1)
Goal
Solution
Step 1 - Creating the Item
Step 2 - Creating the Shipping Network
Step 3 - Create the Internal Location
Step 4 - Conduct a Miscellanies Transaction (Receipt)
Step 5 - Create the Internal Customer - Assign the Location
Step 6 - Item Price Information
Step 7 - Creating the Requisition (PO Requisition Approval, Main Requisition Approval, PO
Create Documents, Overall Document Creation/Launch Approval)
Step 8 - Submitting the Create Internal Orders Concurrent Request
Step 9 - Import the Internal Sales Order
Step 10 - Execute Pick Release/Ship Confirm
Step 11 - Conduct the Receipt in the Destination Organization
Step 12 - Confirm the Quantity is Delivered
SOLUTION
Test case Scenario : The following setups will demonstrate the flow of an Internal Requisition between two
inventory organizations.
M1 - Seattle Manufacturing will represent the destination organization
M2 - Boston Manufacturing will represent the source organization
In this example, the item will be procured internally from the M2 - Boston Manufacturing inventory organization
The following responsibilities are utilized in this example:
Purchasing Super User (or equivalent)
Order Management Super User, Vision Operations (USA)
Inventory
Step 1 - Creating the Item

Purchasing Super User - Navigation: Items/Master Items
Enter the Item Name
Ensure it is Purchased and Purchasable
Enter the Item Name

Ensure it is Purchased and Purchasable
Select these attributes:

Customer Ordered and Customer Orders Enabled
Shippable
Internal Ordered
Internal Orders Enabled
OE Transactable
Assign the item to the inventory organizations which are involved in the Internal Requisitioning process.
M1 will be the destination inventory organization and M2 will be the Source Inventory Organization.
Step 2 - Creating the Shipping Network

Inventory: Navigation: Setup/Organizations/Shipping Networks
Enter the Inventory Organization that will be the Source and the scope should be From or To Organizations
Choose the Transfer Type:
Direct - means that when the Internal Sales Order is shipped the receipt process in the destination
organization 1. is done automatically
2. Intransit - means that when the Internal Sales Order is shipped - the destination inventory organization has
to manually do the receiving process in Purchasing
Choose Internal Order Required checkbox - Save
In this example, the setups are being done to allow the user to Enter a Receipt in SH1 after the item has been
shipped from SH2 (Intransit).
Please Note - If the Source and Destination Inventory Organizations are the same, then this step is
conditionally not required. (Essentially the Item is being transferred between subinventories in the same
Inventory Organization).
Step 3 - Create the Internal Location
Purchasing Super User: Setup/Organizations/Locations
Enter a Location Name - for the Internal Location

This is the location that is used as the Destination Location The Location will eventually be tied to a customer
Choose the Other Details tab, enter the Inventory Organization for the Destination Organization.
The location created will be used to tie the Destination Location in the requisition form to the Internal Customer
to be used on the Sales Order form.
Purchasing does not allow the entry of a Customer - therefore it passes the location to Order Management.
During Order Import in Order Management - the system locates the Customer Record to which the Location is
assigned. Associating the location to the customer record will be done in the later steps.
Step 5 - Create the Internal Customer - Assign the Location
Order Management Super User: Navigation: Customers/Standard
A web based form will open, choose the Create button in the lower left.
Enter the Customer Name - in the Organization Name field.
Choose the Profile Class that applies to the customer. Ex. Excellent.
Scroll further down and enter the Address details for the Internal Customer.
Move to the bottom of the form and under Business Purposes - Choose Add Another Row.
Set the purpose for the new row as 'Ship To'
Choose the Save and Add Details
Move to the bottom of the page, and the address should be visible.
Choose the Details icon
The Account Site Information will appear, select the Business Purposes tab
The Ship To and Bill To should now be visible.

Select the Details icon to the right of the Ship To
Under the Order Management section, there is a field 'Internal Location'

Enter the Location that was created in Step 3 (Ex. M1-Internal Location)
Apply and save the record
PLEASE NOTE: The Customer must be created in the Operating Unit of the Source Inventory Organization that
is used on the Internal Requisition. You can check the Operating Unit for the Source Inventory Organization by
using the following sql:
Select 'The Inventory Organization '
||oo.organization_code||'has the inventory organization ID of '
||oo.organization_id||' and is under the Operating Unit'
||hro.name||' which has the Operating Unit ID of '||oo.operating_Unit
from org_organization_definitions oo, hr_all_organization_units hro
where upper(oo.organization_code) like upper('%&INV_ORG_CODE%')
and hro.organization_id = oo.operating_unit;
Pass in the Source Inventory Organization Code - and then ensure the Customer is created in the Operating Unit
for the Source Inventory Organization.
Step 6 - Item Price Information
Purchasing Super User: Items/Master Items The price used on the requisition comes from the item costs section.
Query back the item Choose from the top text menu - Tools/Item Costs
The screen to follow shows the item price that is used when creating the Internal Requisition. This is how
purchasing derives the price when creating the Internal Requisition. It uses the price for the Cost - in the Source
Inventory Organization. Whatever the price is in the Source Inventory Organization used on the requisition - the
price is derived. The reason is that the Sales Order is being created in the Source Organization, so the price in
the Source Organization must be used.
Step 7 - Creating the Requisition
Purchasing Super User: Navigation - Requisitions/Requisitions
In the Order Type Field - change the Order Type to Internal Click into the Lines Region on the Item field
At this point - look to the Destination fields - this information is fetched from the Employee Record
If the Destination Inventory Organization is not proper - move to that field and change it
If the Location is not the internal location - move to that field and change it to the new Internal Location Approve
the requisition.
Question: Why is the Following Error message encountered : 'Destination location requires
customer association.'
The reason for this error is that the code is trying to match the Location that is currently entered on the form
to a
customer, and the customer association is not found. This was done earlier in step 5. The solution to this
error is to
setup the employee record to default a location that was associated with a customer (as in step 5 above) or
prior to
entering the item, move to the destination section of the form and enter an inventory organization and
location that is
properly assigned to a customer, followed with entry of the item.
Question: Why is the Source Inventory Organization Not showing the inventory organization which
was setup in the shipping networks?
If the internal requisition is going to be for a cross operating unit scenario - then it should be noted that the
HR: Security Profile is used.
Both operating units for which the inventory organizations belong too must exist in the HR: Security Profile.
To confirm the operating units for the inventory organizations - this sql can be used:
SELECT oo.operating_Unit OU_id, hro.name Oper_Unit, oo.organization_code inv_org
FROM org_organization_definitions oo, hr_all_organization_units hro
WHERE oo.organization_id in (207, 204)

and hro.organization_id = oo.operating_unit;
Confirm that the operating units in the given output exist in the security profile that is set for the HR:
Security Profile - profile.
Step 8 - Submitting the Create Internal Orders Concurrent Request
Purchasing Super User: Navigation - Reports/Run
This process is responsible for inserting data into the Order Management interface Tables.
One of the fields that is inserted is the location_id - and because Order Management uses Customers rather than
locations - this is why it is mandatory to assign the Internal Location to the Customer. The location that is passed
from purchasing is correlated to a customer so as to allow the Order Import to run successfully.
Please note that the calculate_price_flag is inserted as N into the Order Management interface tables.
This means that Purchasing is going to pass the price and it will not be impacted or recalculated when imported
into Order Management.
This is proper functionality. We are currently tracking on Enhancement Request Bug 3095239 that would allow
the use of an Internal Price List.
The following sql can be used to review the data in the oe_iface tables.
SELECT *
FROM OE_HEADERS_IFACE_ALL
WHERE order_source_id = 10
AND orig_sys_document_ref IN
(SELECT REQUISITION_HEADER_ID
FROM PO_REQUISITION_HEADERS_ALL
WHERE segment1 = '&requisition_number');
SELECT *
FROM OE_LINES_IFACE_ALL
Pass in the requisition number when prompted.
Question: How can the interface data for Internal Requisitions be viewed in the Order Management
Module?
This is possible using the Order Management Responsibility - and navigating to Orders>Import
Orders>Corrections
Choose an order type of Internal In Order Reference use the List of Values to locate the Requisition Number
If the Requisition is not located - it has either been created into a Sales Order or not inserted into the tables by
the Create Internal Orders program The records are viewable at this stage and can be deleted.
PLEASE NOTE - if records are going to be deleted, it is necessary to Delete the Lines first and then the
header
Be sure to choose Lines first - and then choose the delete icon from the toolbar - then delete the
header
Deletion of the header record will NOT delete the line - it is not a cascade delete option. If the header is deleted
prior to the line - it is not possible to ever again locate the line in this form - sqlplus will have to be used to
remove the line.
Enhancement Bug 4966920 has been created to improve this form and add the cascade delete functionality and
now is implemented with the following
Patch 13702362 - AFTER HEADER IS DELETED, ORPHAN DATA IS LEAVED IN SALES ORDER INTERFACE TABLES>>
Question: How can the Internal Requisition be resubmitted to the Order Management interface
tables?
In the po_requisition_headers_all and po_requisition_lines_all table there is a column 'transferred_to_oe_flag'.
Setting this column to a value of 'N' followed with a run of the
Create Internal Orders process will again post the requisition data into the Order Management interface tables.
There are currently no options available through the Oracle Purchasing forms that allow the updating of this flag,
so sqlplus would have to be used.
Question (Problem):
When Running the Create Internal Sales Order Process - it completes with Success
But no records are inserted into the Order Management Interface Tables?
When the internal requisition is created the code needs to validate that the customer was created in the
Operating Unit that the Source Inventory Organization belongs too.
When the Create Internal Sales Order process runs, if the Deliver to Location is not tied to a Customer Ship To
Site in the Operating Unit of the Source Inventory Organization used on the requisition - then it will not insert
data into the oe_headers_iface and oe_lines_iface table.
Please review the previous step 5 and use the sql given to ensure that the Customer was created in the
Operating Unit that belongs to the Source Inventory Organization. For
this example, it would be required to check the Purchasing Options for the Operating Unit which M2 is belonging
too.
VERY IMPORTANT ALSO REGARDING Create Internal Orders
In Release 12 you must make sure that you are choosing an Order Type in the Purchasing Options - that was
created in the SAME operating unit for the Purchasing Options you are setting up.
Ex. If you are in the Germany Purchasing Options - then ensure you choose a Order Management Order Type that
was created in Germany Order Management. BEWARE - The list of values for Order Type is showing Transaction
Types from other Operating Units. So, if you are in Germany Purchasing Options and then choose a France
Created
Transaction Type - no Records will be inserted during the Create Internal Orders Process. This is fixed in Release
12.1.1 and beyond.
Also, remember that whatever the Source Inventory Organization that is used on the Internal Requisition - the
purchasing options must be setup for that Source Organizations
Operating Unit. So if the internal requisition has two inventory organizations from different Operating Units ensure the Purchasing Options have been setup for both of the Inventory Organizations Operating Units - as the
code is going to check the Purchasing Options from the operating unit of the Source Organization to obtain the
Order Type to
use - as the Sales Order is going to be created in the Source Organizations Operating Unit.
Question: Does the Purchasing Create Internal Orders process pass flexfield values from the
Purchase Requisition?
Currently, the Create Internal Orders process does not pass any values from flexfields. If there are
mandatory/required flexfields setup on the Order Lines table in Order Management, a value will have to be
defaulted as a default value from some other method in order for the import process to complete successfully.
Step 9 - Import the Internal Sales Order
Order Management Super User: Navigation: Orders ,Returns/Import Orders/Order Import Request
Enter these values:
Operating Unit - Operating Unit of the Source Inventory Organization (Ex. M2)
Order Source - Internal (or the order type being used
Order Reference - Requisition Number
Submit the request. Confirm that it completes.
Navigating to Orders, Returns/Order Organizer
Enter the requisition number in the Find form

Confirm that the Internal Sales Order was created from the import
Question: Can the price be updated adjusted during the Order Import?
The calculate price flag is frozen and the price cannot be changed. This is based on the values inserted by the
Create Internal Orders process from Purchasing.
Question: Where is the schedule Ship Date coming from?
The scheduled ship date is passed from the requisition Need By Date, it cannot be defaulted any differently.
Question: How is the Order Type being chosen?
This is coming from the Purchasing Options - Responsibility Purchasing Super User Setup/Organizations/Purchasing Options.
The following queries can be used to confirm that the Internal Sales Order was created.
SELECT *
FROM OE_ORDER_HEADERS_ALL
SELECT *
FROM OE_ORDER_LINES_ALL
Pass the requisition number into the script when prompted.
Step 10 - Execute Pick Release/Ship Confirm
Set Shipping Role For User
Order Management Super User: Shipping/Transactions

Enter the field - From Order Number - give the Internal Sales Order
Choose Find
From the Actions - choose Launch Pick Release

Once the Pick Release has been completed, requery the Internal Sales Order in the shipping transactions form.
The field 'Next Step' should now be showing Ship Confirm.

Choose the Delivery tab
While in the Delivery form, choose actions 'Ship Confirm'
The Ship Confirm submission form appears.

Ship Entered Quantities
Create Delivery for Staged quantities
Close Trip
The selections above were all defaulted into the ship confirm submission form. Choose OK.
Requiring the record shows that the Next Step is to Run Interfaces.
This represents running the Interface Trip Stop process.
In this example, the Interface Trip Stop ran automatically.
Navigation: Shipping/Interfaces/Run - Interface Trip Stop If required, run the Interface Trip Stop process for the
Trip that was created.
Confirm that it completes with success.
The shipping process in M2 will also automatically create the receipt in M1 - if the Shipping Network
was setup to have a transfer type of Direct. For this example, Intransit was used to as to be able to
demonstrate the receiving process.
Step 11 - Conduct the Receipt in the Destination Organization
Purchasing Super User: Receiving/Receipts
Upon entering the Receiving form, search based on the requisition number.
Select the line for Receipt - and save the record. The Receiving Transaction Processor will be engaged and the
item will be transacted into the M1 - Destination Inventory
Organization.
Navigating to Receiving/Receiving Transactions Summary - it is possible to search on the requisition and view the
completed Receiving Transactions.
Step 12 - Confirm the Quantity is Delivered
Purchasing Super User: Requisitions/Requisition Summary
Querying the requisition lines, it is possible to view the quantity delivered - giving confirmation that the Sales
Order was shipped from the source inventory organization (M2) and receipted into the destination inventory
organization (M1).
Additional Scenario
Line Flow - Generic, Bill Only
The Line Flow - Generic, Bill Only process is a workflow process is used for order lines that do not require
shipping.
The Line Flow - Generic, Bill Only process is used in a situation when only a bill for the order must be generated.
The process contains several subprocesses to ensure that the order line is properly entered, invoiced, fulfilled,
and closed.
When you save an order line in Oracle Order Management, the Line Flow - Generic, Bill Only process verifies that
the order is booked before proceeding. Once booking is verified, the process continues with invoicing, fulfillment,
and closing.
Several of these actions are performed in the following workflow subprocesses contained in Line Flow - Generic,
Bill Only:
Enter - Line
Invoice Interface
Close - Line
Line Flow - Generic, Bill Only ends once the line is successfully closed. The only process is contained in the
Seeded Data File oexwford.wft, page 1-6 and is associated with the OM Order Line, page 6-6 item type.
Summary of the Line Flow - Generic, Bill Only Process

To view the properties of the Line Flow - Generic, Bill Only process, select the process in the navigator tree and
then select Properties from the Edit menu. This process is runnable, which indicates that it can be assigned to a
transaction type.
The Details property page of the process activity indicates that the Line Flow - Generic, Bill Only process has an
error item type of WFERROR. This item type is associated with the RETRY_ONLY error process. The purpose of
this error handling process is to alert an administrator when an error occurs in a process and prompt the
administrator to retry the process in error.
This error process is initiated only when an unexpected error with Oracle Workflow is encountered in the process.
When you display the Process window for the Line Flow - Generic, Bill Only, you see that the process consists of
2 unique
activities and 3 subprocesses, which comprise the 5 nodes that appear in the workflow diagram.
The following diagram depicts the Line Flow - Generic, Bill Only process.
Each node of this process is numbered for referencing.
Line Flow - Generic, Bill Only Workflow
The Line Flow - Generic, Bill Only workflow begins at node 1 with the Enter - Line,
page 5-39 subprocess.
This subprocess verifies that the order is booked before proceeding with the remainder of the workflow.
The process attempts to fulfill the order at node 2. At node 3, the Invoice Interface - Line, Deferred, subprocess
is initiated.
This subprocess moves the invoice interface to the background engine. The process initiates the Close - Line,
subprocess at node 4. After the line is successfully closed, the process ends at node 5.
Line Flow - Generic, Bill Only Activities
The following table provides descriptions of each activity in the Line Flow - Generic, Bill Only process.
For more information about individual activities, refer to Seeded Function Activity Definitions, page 6-1.
Line Flow - Generic, Bill Only Activities
Activity Function Result Type Required
Fulfill OE_FULFILL_WF.ST
ART_FULFILLMENT
None Yes
Seeded Workflow Definitions 4-35
Activity Function Result Type Required
End WF_STANDARD.NO
OP
None Yes
Line Flow - Standard Service

Line Flow - Generic, Bill Only with Payment Assurance

Elshayeboracler12ordermanagement 141215031454 Conversion Gate01

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Elshayeboracler12ordermanagement 141215031454 Conversion Gate01

Transféré par

Droits d'auteur :

Formats disponibles

Order Management

Profile Option For New Responsibility

Run Request == Replicate Seed Data

Vision Operations (USA)

Order Management Setup Stapes

User Name: operations

2. Select the System Administrator responsibility.

(M) File > Save.

11. Save your work and close the Responsibilities window.

Guided Demonstration Setting Up

Responsibility: HRMS Management

the following details for some new locations:

2. Address flexfield enter the following:

When You Define OU Additional Information

When You Define Inventory Organization

16.Save your work

Save Your Work

20.Save your work and exit the window.

27.Save your work.

29.Responsibility: System Administrator

Define Inventory Parameter For Inventory Organization

Item Master Organization

Other Account Parameters

Revision, Lot, Serial, LPN Parameters

ATP, Pick, ItemSourcing Parameters

Defining InterOrganization Information

Defining Warehouse Parameters

Auto delete allocation at Move Order cancellation

Indicate whether this organization is enabled for Quality inspection.

Enter a total volume and unit of measure for this organization.

Enter The Following Valuation Account

Revision, Lot, Serial, LPN Parameters

ATP, Pick, ItemSourcing Parameters

Enter a default subinventory picking order.

Enter The Following Other Account Information:

Repeat This Steps Fro To Organization SH 1 And SH 2

Setting OM System Parameters

Country: Your choice

Region: Your choice

Start: Todays date

End: Leave blank

Setting OM System Parameters

To define Order Management system parameters:

Setup > System Parameters > Define

Setting Parameter Values

To set up Order Management system parameter values:

Setup > System Parameters > Values

2. Select the operating unit from the available list of values.

Receivables (AR) Required Steps For Order Management

Common Accounts configuration pertains to the Accounting Flexfield setup.

Manage Receivables System Options

Realized Gains Account

Realized Losses Account

Header Rounding Account

Also highlighted is the Grouping rule we defined earlier.

Line Transaction Flexfield

Link-to Transaction Flexfield

Reference Transaction Flexfield

Invoice Transaction Flexfield

3. Manage Receivables Profile Options

Several Profile options impact the behavior of AutoInvoice.

Navigation: Setup > Transactions > Transaction Types

Unbilled Receivable Account