Source : http://kishorecboracleapps.blogspot.

com

Prerequisite setups required for Order to Cash(O2C) process

Before we start with the Order to Cash flow Process, do the following setups:

1. Define a standard item in the Master Item and then assign it to the shipping organization
2. Add it the price list that we intended to use in order booking.
3. Also we are required to make the item available in the shipping organization.

1. Define a Standard Item - XX Standard Item

 While booking an order we need to first check whether the item is assigned to the
warehouse (ship_from_org_id)

Go to Inventory responsibility

Navigate to Master Item window

Define the item – XX Standard item and assign it to M1 Inventory organization

 Now navigate to Inventory Tab, and ensure the following are enabled:
o Inventory Item
o Stockable
o Transactable
o Reservable

 Now navigate to Order Management Tab, and ensure the following are enabled:
o Customer Ordered
o Customer Orders Enabled
o Shippable
o OE Transactable
o Returnable (Optional)
o Set Default SO Source Type = Internal
  Now navigate to Invoicing Tab, and ensure the following are enabled:
o o Invoicable Item
o o Invoice Enabled

 Save your work and then using Tools Menu select Organization Assignment. Assign the
Item to M1 Organization

2. Add the Item to the price list – Corporate

As the item fetches the list price, it has to be assigned to the price list as well.
3. Perform Miscellaneous receipt transaction in M1 inventory organization:

In order to cash process if sufficient item quantity does not exist in the shipping warehouse
then we need to perform misc. receipt transaction to replenish the inventory with sufficient
quantity.

Navigate to the Miscellaneous Transactions window (Transactions >Miscellaneous

Transaction), in the select organization window select the M1 organization. In the
Miscellaneous Transaction window select the Type = Miscellaneous receipt and then click on
the Transaction Lines button.
Complete Order to Cash(O2C) Techno-Functional flow in R12

Order to Cash Cycle in Brief:

The Order to Cash Process flow starts with entering the order with a standard item into system.
When you enter an order, the item are validated in oracle inventory, the price is calculated for
the items using the pricing engine; the availability of the items are checked and may be
reserved. Once all the required fields are entered on both the header and the lines, you can book
the order. When you click on the Book Order button, the API OEXUBOKB.pls, checks if the
order is eligible for booking. If eligible the order is booked and the order header status would
change to booked. The next step is the pick release with which you move the items from the
warehouse to the staging area. The next step is to ship confirm, to indicate that the items are
loaded on to the carrier from the staging area. When you run Ship Confirm, the system
decrements inventory and updates sales order line status. This information is then transferred
through the Auto Invoice to Account Receivables for invoicing. Then you sent the invoice to
your customer for the items shipped and then perform the cash management and bank
reconciliations.

Order Management receives detailed item information from the Inventory application
and price list information from the Pricing application. Orders and returns can be entered
manually or imported through an EDI, CRM, or external source. Once in the system the order
is ready to be pick released and shipped, if needed by the Shipping application. It can then
proceed through the Auto Invoice program into the Oracle Receivables application to be
invoiced. All of the accounting information is transferred to the General Ledger by the
Inventory and Receivables applications.

The required fields to enter on the sales order header are the customer name or number and
order type. Other values such as Ship-To Address, Bill-To Address, Shipping Method,
and Price List default. The order number is generated based on the order type. The required
fields to enter on the sales order lines are Ordered Item and Quantity. Again, based on
defaulting rules and setups in Pricing, Inventory and Shipping, the other values would default
on the sales order line.
Setup steps for executing the Order to Cash flow with a standard item:

 Prior to order entry, the items should be created / defined in inventory module using the
master items screen and assigned to the shipping organization. Check the blog post for the
related setups
 Add the item to the price list or create a new price list.
 Transaction Type must be defined
 Document Sequence must be assigned to the document category.
 Customers must be defined
 Salespersons must be defined
 Shipping Roles should be granted to the user.
 Ensure that the items are available in your shipping sub inventory or perform miscellaneous
transactions to augment the same.

Following are some useful related links:

Check the blog post for tables involved in various stages of O2C

Check the blog post on queries involved in Order management

Order to Cash flow with tables involved in various stages:

 Order to Cash flow with statuses at various stages:

All possible flow statuses of the order/line:

• OE_ORDER_HEADERS_ALL.flow_status_code: Order Header (Entered) Booked Order

(Booked) Closed Order (Closed)

• OE_ORDER_LINES_ALL.flow_status_code: Order Line (Entered) Booked Order

(Awaiting Shipping) Pick Released(Picked/Staged) Ship Confirmed
(Shipped) INV/OM interfaced (Fulfilled) Close Order (Closed)

1. Enter the order header, line details and Book it:

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

Navigate to Orders, Returns Sales Orders

Open the Sales Orders Window

Order Number: 66413

2. Schedule order:

 Check if the order lines are scheduled or not. If any of the order line is in BOOKED status,
it means that the order line is not yet scheduled.
 Run the Schedule Order concurrent program to schedule the order. After the concurrent
program is scheduled the order line will move to Awaiting Shipping status.
 Still if the order lines do not go to Awaiting Shipping, check for any holds on the order
line/ header. Release the holds (if any) and re-run the Schedule Order program.
 You can even schedule the order line in the following way: Right click on the order line
and progress the line to schedule it. Check the OM scheduling related setups
 Order tables:

OE_ORDER_LINES_ALL.visible_demand_flag: visible_demand_flag= Yes lines will be

made available as Demanded to Planning

Shipping tables: The shipping tables get populated after order scheduling.

WSH_DELIVERY_DETAILS.released_status: monitors the shipping process of the order line

WSH_DELIVERY_ASSIGNMENTS: Assigns delivery details to a delivery and/or a parent

delivery detail.

Once the order is booked from the application, following changes occur in the backend

OE_ORDER_HEADERS_ALL (flow_status_code as BOOKED, booked_flag updated to

Y)

OE_ORDER_LINES_ALL (flow_status_code as AWAITING_SHIPPING, booked_flag

updated Y)

Since the order is now booked, delivery details of the order are created in
WSH_DELIVERY_DETAILS table. WSH_DELIVERY_DETAILS has delivery lines and
LPNs.

OOL.line_id = WDD.source_line_id

These delivery details information can been viewed form ‘Shipping Transactions Form’ and
the delivery status in the application will be as ‘Ready to Release’

WSH_DELIVERY_DETAILS.released_status =’R’

WSH_DELIVERY_DETAILS.Release_Status can have any of the below valid values

WSH_DELIVERY_ASSIGNMENTS (WDA) assigns delivery details to a delivery and/or

a parent delivery detail (LPN).

WDA.delivery_detail_id = WDD.delivery_detail_id

WSH_DELIVERY_ASSIGNMENTS.delivery_id will be NULL as still pick release

operation is not performed as final delivery is not yet created.

At the same time when order is booked ‘Demand interface program’ is triggered in the
background and demand of the item with specified quantity is created and these demand
information is stored in MTL_DEMAND.

MTL_DEMAND.demand_source_line = OOL.line_id
3. Pick Release the Sales Order

Navigate to the Shipping Transaction Form (Shipping Transactions)

Enter the following in the Query Manager window and click Find

From Order Number = 66413 To Order Number = 66413

You can find the data in Shipping transaction screen (WSH shipping tables) only when
order is scheduled.

On the Shipping Transaction Form select Launch Pick Release from the Action menu
and click on GO button.

If Auto Pick confirm is not selected while pick release, then we have to manually do
the transact move order process. In fact pick confirm also triggers the transact move
order process in which the inventory is moved from item sub inventory to staging area.

Order line status becomes ‘Picked’ on Order and ‘Staged/Pick Confirmed’ on Shipping Form.

MTL_MATERIAL_TRANSACTIONS_TEMP (Record gets deleted from here and gets

posted to MTL_MATERIAL_TRANSACTIONS)

OE_ORDER_LINES_ALL.flow_status_code =’PICKED’

MTL_MATERIAL_TRANSACTIONS is updated with Sales Order Pick Transaction

MMT.trx_source_line_id = OOL.line_id

MTL_TRANSACTION_ACCOUNTS is updated with accounting information

WSH_DELIVERY_DETAILS. released_status=‘Y’ (‘Released’)

WSH_DELIVERY_ASSIGNMENTS, MTL_ONHAND_QUANTITIES are updated

accordingly

Note: Pick Confirm step can be eliminated if ‘Auto Pick Confirm’ is selected as ‘YES’ while
performed manual pick release. If Pick release is done through shipping transactions form and
if you want to perform auto pick confirm then picking rules setup has to be done.

4. Ship Confirm the Sales Order

Navigate to the Shipping Transaction Form (Shipping Transactions)

Enter the following in the Query Manager window and click Find

From Order Number = 66413 To Order Number = 66413

On the Shipping Transaction Form navigate to the Delivery Tab and select Ship
Confirm from the Action menu and click on GO button. Ship confirm process triggers the
Interface Trip Stops concurrent program.
o OE_ORDER_LINES_ALL.flow_status_code =‘SHIPPED’

o WSH_DELIVERY_DETAILS. released_status=‘C’ (‘Shipped’)

o Data from MTL_TRANSACTIONS_INTERFACE is moved to

MTL_MATERIAL_TRANACTIONS and MTL_MATERIAL_TRANSACTIONS is updated
withSales Order Issue transaction.

o Data is deleted from MTL_DEMAND, MTL_RESERVATIONS and

WSH_NEW_DELIVERIES

o Item reduced from MTL_ONHAND_QUANTITIES

MTL_TRANSACTION_ACCOUNTS is updated with accounting information.

Following are the pick release status:

Table: WSH_DELIVERY_DETAILS

Column: RELEASED_STATUS

Possible Values:

B: Backordered- Line failed to be allocated in Inventory

C: Shipped -Line has been shipped
D: Cancelled -Line is Cancelled
N: Not Ready for Release -Line is not ready to be released
R: Ready to Release: Line is ready to be released
S: Released to Warehouse: Line has been released to Inventory for processing
X: Not Applicable- Line is not applicable for Pick Release
Y: Staged- Line has been picked and staged by Inventory

Check the blog post for the detailed pick release status
 Verify the details on the Confirm Delivery window and click OK and close the
window.

5. Run the Interface Trip Stop – SRS Program

The Interface Trip Stop (ITS) will be trigger at the time of Shipping if check box “Defer
Interface” is not check. ITS can also be executed from concurrent request.

Interface Trip Stop has two main components:

1. Update the Order Management Data (oe_order_lines_all)

2. Trigger the Inventory Interface (to Update the Inventory tables)

ITS updates the following fields on oe_order_lines_all table:

Shipped_quantity

Shipping_quantity

Actual_shipment_date
 Inventory Interface will be trigger only if the first part, that means related to OM has
successfully completed and flag OE_INTERFACED_FLAG = ‘Y’ on
WSH_DELIVERY_DETAILS. If value of this flag is N/P then Inventory Interface will never
be triggered. And even if you try to submit the Inventory Interface from SRS, delivery detail
with oe_interfaced_flag =’N’ will never be picked up.

o oe_interfaced_flag = Y -- signifies ITS has interfaced shipping data to OM

o inv_interfaced_flag = Y -- signifies ITS has interfaced shipping data to INV

Navigate to Shipping Interfaces window (Shipping Interfaces Run)

Select the Interface Trip Stop - SRS Program from the LOVs

On the parameters window enter

Mode = All

Click on the OK button and then on the Submit button:

6. Run the Master AutoInvoice Program

Navigate to the Run AutoInvoice window, (Interfaces AutoInvoice)

Select the AutoInvoice Master Program from the LOV

On the parameters window enter

Invoice Source = ORDER ENTRY

Default Date = Enter Today’s Date

(Low) Sales Order Number = 66413

(High) Sales Order Number = 66413

Then click OK and Submit button.

7. View the Transaction created by the AutoInvoice Program

Navigate to the Additional Line Information window, (Orders, Returns Order

Organizer)

On the Find Order window, query your order number = 66413

On the Order Organizer window, navigate to Lines Tab and click on Actions button
and select the Additional Line information and click OK.
8. On the Additional Line Information window, navigate to Invoices / Credit Memos Tab and
click on the Invoice Details button. This would open Transactions window, where you can see
the invoice details.

Following is an important Query which gives the joining between OM, WSH, AR Tables
SELECT ooh.order_number

,ool.line_id

,ool.ordered_quantity

,ool.shipped_quantity

,ool.invoiced_quantity

,wdd.delivery_detail_id

,wnd.delivery_id

,rctl.interface_line_attribute1

,rctl.interface_line_attribute3

,rctl.interface_line_attribute6

,rct.org_id

,rct.creation_date

,trx_number

,rctl.quantity_ordered

,rct.interface_header_context

FROM oe_order_headers_all ooh

 ,oe_order_lines_all ool

,wsh_delivery_details wdd

,wsh_new_deliveries wnd

,wsh_delivery_assignments wda

,ra_customer_trx_all rct

,ra_customer_trx_lines_all rctl

WHERE ooh.header_Id=ool.header_id

AND wdd.source_header_id=ooh.header_id

AND wdd.delivery_detail_Id=wda.delivery_detail_id

AND wda.delivery_id=wnd.delivery_id

AND rctl.interface_line_attribute1=to_char(ooh.order_number)

AND rctl.interface_line_attribute6=to_char(ool.line_id)

AND rctl.interface_line_attribute3=to_char(wnd.delivery_id)

AND rctl.customer_trx_id=rct.customer_trx_id

AND rct.interface_header_context='ORDER ENTRY'

O2C: Accounting Entries:

Transaction Event Debit Credit Module

Enter Sales Order

Order
No Accounting Entry
Mgmt
Book Order
Pick Release Order

Cost of Goods
Ship goods to customer Inventory a/c Inventory
Sold a/c

Receivables
Issue Invoice Revenue a/c Receivables
a/c
 Receivables
Collecting Payment Cash/Bank a/c Receivables
a/c
 Scheduling in Order Management

Scheduling is a concept, which helps to place the demand in the inventory based on
the availability.

Scheduling helps with the following:

• Find the availability of the item

• Populate the Schedule Ship Date, Arrival Date and the Last Acceptable Date based on the
calculate ATP date

• Performs the reservation based on Scheduled Ship Date

• Calculates the delivery lead time based on ship method

• Prevents over demand by setting the items attribute Check ATP.

Scheduling is a communications tool that helps balance customer demands with your ability to
fulfill that demand.

Key Features:

Scheduling in Order Management includes the ability to:

• Schedule at multiple points - either manually or automatically as the line is entered, when
the order is booked, or later using a back ground process.

• Determine the best warehouse for an order line using sourcing rules. This includes using
ATO models.

• Define by customer whether the request date is the requested ship date or requested arrival
date.

• Automatically set the scheduled ship and arrival dates based on the calculated ATP date.

• Define a shipping network and determine the number of days required for delivery based on
the transit time.

• Automatically reserve on-hand inventory to order lines.

• Control, based on order transaction type, the level of scheduling which should occur.

• View availability for multiple warehouses at one time.

• Group lines into arrival sets which may be shipped from different warehouses on different
days but should arrive at the customer site on the same day, or group lines into ship sets which
ship on the same day from the same location.

• Reserve scheduled lines from multiple orders using the Reserve Orders concurrent program.
Optionally, you can use reservations strategies such as Fair Share, Percentage, and Partial. You
can choose whether to simulate or commit the reservations. An API Hook is provided for those
who want to write an API to tailor reservation logic for business-specific processes. Reserve
Orders can be run either from the concurrent request menu or from Scheduling across Orders.

• Override Available to Promise (ATP). This feature allows authorized users to override ATP
schedule date from the sales order window as needed for exceptions.

• Perform scheduling actions on multiple lines across orders.

• Scheduling can be updated based on the latest planning output for planned items.

• Configured items can be matched at scheduling for planned items.

• Flexible scheduling parameters allow users to control the use of Promise Date, the impact of
Request Date and Shipping Method on Schedule Date, the behavior of the LAD with manual
scheduling, and whether to allow partial reservations for manual reservations and the
reservation time fence.

• ATP/Scheduling uses Transportation calendars like Shipping Calendar, In-transit

(Carrier) Calendar, and Receiving Calendar to calculate the ship/arrival dates

• The ATP window displays the scheduling results for all recent (related to the current order)
scheduling actions- successes as well as failures.Check the blog post on Available to Promise
(ATP)

Scheduling happens during any one of the following events:

• Automatic scheduling upon entry

• Manual scheduling upon entry

• Scheduling during booking

• Scheduling after booking

 Different ways of Auto Scheduling

1. Auto Schedule through “OM: Auto Schedule” Profile Option

2. Auto Schedule Check box on Transaction Type window on the Shipping Tab

Select the Auto Schedule check box if you want automatic scheduling for this order type. This
is applicable only to order transaction types.

3. Auto Schedule using the Tools Menu when entering the Order
 The Scheduling level on the order transaction type determines what type of scheduling is
allowed. The possible values are:

• ATP Only

• No Reservations

• Allow All Scheduling Actions

• Inactive Demand With Reservations

• Inactive Demand Without Reservations

 Defaulting rules in Order Management

It is not necessary for the user to remember all the information while entering the order. It is
just enough to remember the customer number (say) and all the other customer related data will
be defaulted. Oracle has provided this feature with the defaulting rules setup.

• Defaulting refers to the supply of a value for a field that has no value.

• You can create and modify defaulting rules to improve the efficiency and accuracy with
which you enter orders.

• You can define the rules to determine the source and prioritization for defaulting order
information to reduce the amount of information you must enter manually in the Sales
Order window.

• Seeded defaulting rules can be disabled, but not modified.

Query entities and attributes:

1. Navigate to the Defaulting Setup - Entity Attributes window.

2. Application: The Application field displays the application context for the entity displayed.

3. Entity: The Entity field displays the name of the object for which defaulting rules and
conditions are being defined such as the order line. For Order Management you have the
following options:

• Order Header

• Order Line

• Sales Agreement Header

• Sales Agreement Line

• Order Payment

• Line Payment

4. The Defaulting Sequence field enables a user to assign the sequence (priority) number in which
this attribute should be defaulted.
5. The Attribute field stores the name of available attributes. Values are currently displayed based
upon the entity selected.

6. The “Include in Building Defaulting Conditions” check box indicates whether an attribute can
be used in defining conditions for the entity selected. This check box is for display purposes
only, and is non-updateable.

7. Save your work.

Define defaulting rules:

1. Navigate to the Attribute Defaulting Rules window.

2. Enter a value in the Precedence field to determine the precedence when resolving multiple
TRUE defaulting conditions.

3. Select a Defaulting Condition from the List of Values and then enter the defaulting rules to be
used if this defaulting condition is TRUE.

4. Select the Enable check box if you wish to enable the defaulting condition. If this check box
is not selected, the defaulting condition is disabled and the rules and condition associated with
this condition are not used in default possessing.

5. The check box for the field Seeded cannot be updated. This value is seeded by Order
Management. For seeded Order Management defaulting conditions, you are unable to update
or delete any fields except:

• The Precedence field on the defaulting rule condition

• The Enable check box. You can disable seeded Order Management defaulting rules.

6. Within the Default Sourcing Rules region, select the priority sequence in which you want to
retrieve the default for this attribute. The defaulting process searches for a default for your
attribute by evaluating defaulting rules in ascending order.

7. Select the defaulting source type. The defaulting source type determines data entry in the
Default Source/Value field.

8. Based on the default source type selected, either select the default sources or enter default
values in the Default Source/Value field.

The table below describes Order Management Source Types and the appropriate action
required by a user.
 Defaulting Rules Listing Report: This report displays the defaulting rules you have defined
for various objects and attributes in Order Management. This listing includes objects,
conditions, attributes and seeded data.

If defaulting rules or conditions are updated, the Defaulting Generator concurrent program
must be run to generate new defaulting packages.

• If you update an existing defaulting rule or condition from within the Defaulting Rules
window and the update is saved, a pop up window will display a note reminding you to submit
the Defaulting Generator concurrent program.
• Choose to submit the program by selecting Defaulting Generator from the Tools menu while
within the Defaulting Rules window, or from the Order Management SRS window.

• To generate the Defaulting Generator concurrent program for an entity, you must go to the
Requests form and select your entity.

Order Management Source Types and Actions

Source Type Action required

Constant Value Enter the default constant value.

Application Profile Select the profile option from where you want to retrieve the
default value.

Same Record Select the attribute on the same record from where you want to
retrieve the default value.

Related Record Object->Select the related object. Attribute->Select the attribute on

the related object from where you want to retrieve the default value.

System Variable Expression--Enter the system expression to be evaluated to obtain

the default value. (E.g. System Date.)

PL/SQL API You can write a custom API to obtain a default value if the value
cannot be obtained using other source types such as, the default order number from a sequence.

WAD Attribute

WAD Object Attribute

Order Management Setups - Profile Options

n R12, profiles have been categorized so that they can be easily classified or grouped. The
following list displays the profile categories and the profile options that belong to each one.
Some profile options belong to more than one category and are indicated in the below list.

Configurations

OM: Allow model fulfillment without configuration;

OM: Configuration Quick Save;

OM: Copy Model DFF to child lines;

OM: Included Item Freeze Method;

OM: Party Totals Currency;

OM: Use Configurator;

Customer Usage

OM: Add Customer;

OM: Add Customer (Order Import);

OM: Create Account Information;

OM: E-Mail Required on New Customers;

OM: Party Totals Currency;

OM: Sales Order Form: Restrict Customers

Debug

OM: Debug Log Directory;

OM: Debug Level;

OM: Generate Diagnostics for Error Activities;

Deployment

OM: DBI Installation;

OM: Orders Purge Per Commit;

OM: New EDI Acknowledgment Framework;

OM: Printed Document Extension Class Name;

OM: Use Configurator;

Electronic Messaging

OM: Change SO Response Required;

OM: Electronic Message Integration Event Sources

OM: New EDI Acknowledgment Framework;

OM: Order Accept State for XML;

OM: Run Order Import for XML;

OM: Send Acknowledgment for Change PO Response;

Forms UI

OM: Add Customer;

OM: Administer Public Queries;

OM: Automatically Open Related Items Window;

OM: Contact Center Actions Menu Name;

OM: Cust Item Shows Matches;

OM: Display Actions Button vs. Poplist;

OM: Display Current Selections in Pricing/Availability;

OM: Enable Related Items and Manual Substitutions;

OM: Item View Method;

OM: Quick Sales Order Form: Auto Refresh;

OM: Quick Sales Order Form: Defer Pricing;

OM: Sales Order Form: Cascade Header Changes to Line;

OM: Sales Order Form: Refresh Method (Query Coordination);

OM: Sales Order Form: Restrict Customers;

OM: Sales Order navigation from Pricing/Availability form;

OM: Sales Orders Form preference;

OM: Scheduling Role;

OM: Show Line Details;

OM: Show Process Messages Flag;

OM: Use Configurator;

OM: View Cancel Lines;

OM: View Closed Lines;

OM: View Pricing & Availability Information in Related Items;

Fulfillment

OM: Allow model fulfillment without configuration;

OM: Included Item Freeze Method;

OM: Over Return Tolerance;

OM: Over Shipment Tolerance;

OM: Population Of Buyer Code For Dropship Lines;

OM: Source Code;

OM: Under Return Tolerance;

OM: Under Shipment Tolerance;

Holds

OM: Modify Seeded Holds;

OM: Prevent Booking for Line Generic Holds;

Invoicing

OM: Interface freight tax code from line;

OM: Invoice Numbering Method;

OM: Set Receivables Transaction Date as Current Date for Non-Shippable Lines;

Item Usage

OM: Customer Item Shows Matches;

OM: Enable Related Items and Manual Substitutions;

OM: Item Flexfield;

OM: Restrict Customer Items for Line Level Ship To Address;

Logistics

OM: Sequence for TP Ship/Deliver Deadline;

OM: Source for TP Early Ship/Deliver Date;

Order Import

OM: Add Customer (Order Import);

OM: Import Multiple Shipments;

OM: Unique Order Source, Orig Sys Document Ref Combination For Each Customer;
Payments

OM: Commitment Sequencing;

OM: Credit Card Privileges;

OM: Preserve External Credit Balances

Portal UI

OM: Customer Service Feedback;

OM: Customer Service Report Defect;

OM: Records On Summary Page For External Users;

Pricing

OM: Charges For Backorders;

OM: Charges for included item;

OM: Charging Privilege;

OM: Discounting Privileges;

OM: Enable Group pricing for DSP lines;

OM: Item Change Honors Frozen Price;

OM: List Price Override Privilege;

OM: Negative Pricing;

OM: Promotion Limit Violation Action;

OM: Send Changed Lines to Pricing;

OM: Unit Price Precision Type;

OM: UOM Class for Charge Periodicity;

Returns
OM: Customer Service Feedback;

OM: Customer Service Report Defect;

OM: Over Return Tolerance;

OM: Notification Approver;

OM: Return Item Mismatch Action;

OM: Return Unfulfilled Referenced Line Action;

OM: Under Return Tolerance;

Scheduling

OM: Assign New Set For Each Line;

OM: Authorized To Override ATP;

OM: Auto Push Group Date;

OM: AutoSchedule;

OM: Enforce Shipping Method for Ship Sets;

OM: Schedule ATO Item Without BOM;

OM: Scheduling Role;

Security

OM: Add Customer;

OM: Add Customer (Order Import);

OM: Administer Public Queries;

OM: Authorized To Override ATP;

OM: Cascade Service;

OM: Charging Privilege;

OM: Create Account Information;

OM: Credit Card Privileges;

OM: Discounting Privileges;

OM: List Price Override Privilege;

OM: Modify Seeded Holds;

OM: Scheduling Role;

OM: Authorized To Override ATP;

Service OM: Cascade Service;

Transaction Entry

OM: Apply Automatic Attachments;

OM: Cascade Service;

OM: Configuration Quick Save;

OM: Copy Model dff to child lines;

OM: Default Blanket Agreement Type;

OM: Default Blanket Transaction Phase;

OM: Default Sales Transaction Phase;

OM: Default Salesrep;

OM: Enforce check for duplicate Purchase Orders;

OM: Generic Update Constraints Apply to DFF?;

OM: Prevent Booking for Line Generic Holds;

OM: Return Item Mismatch Action;

OM: Return Unfulfilled Referenced Line Action;

Upgrade
OM: Context Responsibility for Upgraded Orders;

OM: Notification Approver;

Profile options are set at the following levels:

Provide the responsibility name & the Profile name for which you are defining the profile
value:
 Oracle Workflows in Order Management

Oracle Order Management uses Oracle Workflow to control the sequence of events that occur in
the processing of orders, quotes, sales agreements, returns, order lines, and return lines.

Oracle Workflow manages activities, executes functions, sends notifications, maintains

completed activity history, detect errors, and initiates error processes.

Oracle Order Management seeded workflows and their associated activities are contained
in oexwford.wft file.

The most commonly used Order header flows for outbound lines are:

Order Flow – Generic

Order Flow – Generic with Header Level Invoice Interface

The Order header flows for inbound lines are:

Order Flow – return with Approval

Order Flow – Return with Submission and Approval

Order Flow – Return with Approval and Header Invoicing

The most commonly used Order Line flows are:

Line Flow – Generic

Line Flow – Generic with Header Level Invoice Interface

The Order Line flows for inbound lines are:

Line Flow – Return for Credit Only

Line Flow – Return for Credit Only with Approval

Line Flow – Return for Credit with Receipt

Line Flow – Return for Credit with Receipt and Approval

 The Transaction Type determines the header level process used at the header level on an
order.

The Transaction Type window is used to assign the order flow to the order header
Transaction type.

Use the Assign Line Flows button to assign line flows to the order header

The combination of order type/line type/item type determines the line workflow.

If you leave Item Type blank, the workflow applies to all item types for the line type (unless
they have a specific assignment in this form).

In Process Name, select the workflow that Oracle Order Managementshould use for the
order type/line type/item type combination.

If you do not assign a workflow to a configured item type, the configured item does not use
a workflow.

You can perform all standard processing including orders, returns, drop-ship orders, Orders
for configured items, and orders for assemble-to-order items using seeded workflows.
Check Order line Workflow Activity Status

SELECT COUNT (1)

INTO ln_completed_lines

FROM wf_item_activity_statuses a,

wf_process_activities b,

oe_order_lines_all c

WHERE a.process_activity = b.instance_id

AND b.process_item_type = 'OEOL'

AND b.activity_name = <‘Activity_Name’>

AND activity_status = 'COMPLETE'

AND item_key = TO_CHAR (c.line_id)

AND c.header_id = pin_order_header_id