Oracle Order Management is an order-to-cash solution that provides the capabilities for customers, partners and employees to select the right products and services, negotiate the best prices and ensure timely order fulfillment. Oracle Order Management drives the order fulfillment process of any business. The open, workflow based architecture supports non-customized, tailored and automated fulfillment processes. It captures multi-channel demand from sources including EDI, XML, Telesales and web storefronts. As part of a complete order to cash solution, it enables global order promising and is integrated with Transportation Management.
This chapter describes the following test flows in Oracle Order Management:
Create Order from Quote for a Standard Line
Generate Invoice for PTO Model, ATO Model and Standard Line
Verify Scheduling Dates for Sales Order by Assigning to Ship Sets
Verify Split Configuration Concurrent Program for PTO Model Line, ATO Model Line and Kit
Verify Authorization of a Sales Order with Credit Card and Cash
Create and Verify Tax on Sales Order
Verify Intercompany Invoicing for Sales Order
Fulfillment of a Bill Only Line With Standard Item
Multiple Processing Constraints Validations for a Sales Order Header and Line
Verify Audit History for a Sales Order Header and Line
Create Processing Constraints for Customer PO
User is logged in with Order Management Super User responsibility.
Oracle Quoting offers limited capability to create quotes and progress it through the negotiation phase and finally creates sales order, thus acting as a single point of entry into Oracle Order Management.
The Create Order from Quote for a Standard Item flow creates an order from quote for a standard line, with approvals and converts the same to a sales order.
Transaction type Mixed of workflow type Negotiation Flow-Generic.
Transaction type Mixed of workflow type Negotiation Flow-Generic, with Use Approvals Management Engine check box deselected.
A customer or party, with address and account number.
Not applicable.
Not applicable.
Table 36-1 Setup Data for Create Order from Quote for a Standard Item Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Quote |
Customer Number |
1005 (Pick a Party of type Organization) |
|
Ordered Item |
AS54888 (Pick a standard item of finished goods template) |
|
|
Order Type |
Mixed (Pick an Order Type) |
|
|
Price List |
Corporate (Pick a Price List) |
Invoice processing in Oracle Order Management is the process by which data from orders and returns is interfaced to Oracle Receivables for the creation of invoices and credit memos, to recognize revenue and manage sales credits. This flow verifies the generation of invoice for the PTO Model, ATO Model and Standard Line.
A standard item of type 'Finished Good' template.
An item of PTO model type with optional classes and optional items.
An item of ATO model type with optional classes and optional items.
A customer or party, with address and account number.
A non-WMS warehouse.
Not applicable.
Not applicable.
Table 36-2 Setup Data for Generate Invoice for PTO Model, ATO Model and Standard Line Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Sales Order |
Customer Number |
1005 (Pick a customer number) |
|
Order Type |
Mixed (Pick an order type) |
|
|
Warehouse |
M1(Pick a non-WMS organization) |
|
|
Ordered Item |
Vision-SMC-PTO-Model -Vision-PTO-Non-ATP-Op-Item -Vision-PTO-ATP-Op-Item (Pick a PTO model with optional classes and items) |
|
|
Ordered Item |
Vision-ATO-Model -Vision-ATO-Op-Item (Pick an ATO model with optional classes and items) |
|
|
Ordered Item |
AS54888(Pick a finished good) |
Creates a sales order and verifies the scheduling dates. This flow assigns the new ship set, adds to the existing hip set and verifies whether lines are getting scheduled or not.
A customer or party, with address and account number.
A non-WMS warehouse.
Two standard items with finished good template.
A Hold Source for an item.
PTO Model with PTO-Model template.
ATO Model with ATO-Model template.
Kit Model with Kit-Model template.
Not applicable.
Not applicable.
Table 36-3 Setup Data for Verify Scheduling Dates for Sales Order by Assigning to Ship Sets Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
System Parameters |
Schedule Lines on Hold |
Yes or No |
|
OM: Auto Schedule Sets |
Yes or No |
|
|
OM: Auto Schedule |
Yes or No |
|
|
Schedule Lines on Hold |
Yes or No |
|
|
Sales Order |
Customer Number |
1005 (Pick A customer Number) |
|
Warehouse |
V1 (Select a non WMS warehouse ) |
|
|
Ordered Item |
AS54888 (Select a product) |
|
|
Ordered Item |
AS54999 (Select a product) |
|
|
Ordered Item |
(Select a PTO Model product) |
|
|
Ordered Item |
(Select an ATO Model product) |
|
|
Ordered Item |
(Select a KIT Model product) |
|
|
Ship Set |
Ship Set |
Any value for a ship set |
Users can split lines in the background using the concurrent request Split Configuration in the Sales Orders window. This applies to ATO Models, PTO configurations and Kits. The Defer Split check box in the Split Line window enables splitting configuration lines in the background and continuing with other actions on the sales order. When a user selects the Defer Split box and clicks Split, the Split Configuration concurrent program splits the lines as a background process.
This test flow verifies the split line functionality using the Split Configuration concurrent program for PTO Model line, ATO Model Line and Kit.
An item of PTO model type with optional classes and optional items.
An item of ATO model type with optional classes and optional items.
An item of type Kit.
A customer or party, with address and account number.
A non WMS warehouse.
Not applicable.
Not applicable.
Table 36-4 Setup Data for Verify Split Configuration Concurrent Program for PTO Model Line, ATO Model Line and Kit Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Sales Order |
Customer Number |
1006 (Pick A customer number) |
|
Order Type |
Mixed (Pick an Order Type) |
|
|
Warehouse |
M1(Pick a non-WMS organization) |
|
|
Ordered Item |
Vision-PTO-Model (Pick a valid PTO model with optional classes) |
|
|
Ordered Item |
Vision-ATO-Model (Pick a valid ATO model with optional classes) |
|
|
Ordered Item |
Vision-SMC-Kit (Pick an item of type Kit template) |
This flow tests the authorization of a sales order with credit card and cash. It also verifies multiple payments for a standard item.
Credit check rule.
Credit option for the payment terms in the sales order is selected.
A customer or party, with address and account number.
A transaction type with the Credit Check rule set at ordering level.
A non WMS warehouse.
Not applicable.
Not applicable.
Table 36-5 Setup Data for Verify Authorization of a Sales Order With Credit Card and Cash Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Sales Order |
Transaction Type |
Mixed (Pick a Transaction Type) |
|
Rule |
CC-Rule1 |
|
|
Customer Number |
1005(Pick a Party of type Organization) |
|
|
Warehouse |
V1 (Select a valid non WMS warehouse ) |
|
|
Ordered Item |
AS54888 (Select a product) |
|
|
Ordered Item |
AS54999 (Select a product ) |
|
|
Name |
N30 (Pick a Payment Term) |
This test flow verifies the tax applicability for a customer who comes under the United States jurisdiction. A tax rate is set up using Tax Manager responsibility with tax rate as 10% with United Status jurisdiction, and tax calculation is verified when a sales order is created for the customer falling under that tax jurisdiction.
A new tax rate for a transaction:
New tax.
New tax status.
New tax rate with 10%.
New tax jurisdiction with geography as NY, United States.
A customer or party, with address and account number, with bill to site under New York location.
A tax code.
Not applicable.
Table 36-6 Predefined Data for Create and Verify Tax on Sales Order Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Sales Order |
Payment Type |
Cash |
Table 36-7 Setup Data for Create and Verify Tax on Sales Order Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Sales Order |
Customer Number |
1001 (Pick a Party of Type Organization) |
|
Warehouse |
M1 (Pick a non-WMS organization) |
|
|
Order Type |
Mixed (Pick an Order Type) |
|
|
Price List |
Corporate (Pick a Price List) |
|
|
Ordered Item |
AS54888 (Pick a finished good) |
|
|
Tax Code |
VISIONUSSALESTAX (Select a Tax Code) |
When a customer processes and invoices an order, the selling organization records entries to Accounts Receivable for revenue, tax and freight. The shipping warehouse records entries to the inventory asset account and cost of goods sold (COGS) account. When the above scenario involves a selling organization in one operating unit and a shipping organization in another operating unit, additional accounting takes place.
The shipping organization must bill the selling organization at the transfer price and the selling organization must make the corresponding payment. The intercompany accounts receivable invoice is the transaction the system uses, to record the intercompany receivable accounting for the shipping organization. It debits the intercompany accounts receivable at transfer price, charges tax and freight cost, and credits the intercompany revenue.
The intercompany Accounts Payable invoice is the transaction the system uses to record the payable accounting for the selling organization. The system debits the intercompany COGS and freight, and credits the intercompany payable account.
This flow verifies the inter-company invoicing as follows:
Places an order with the selling operating unit.
The system ships the order to the customer from a shipping warehouse associated with an operating unit that differs from the selling operating unit.
The shipping operating unit issues an intercompany receivable invoice to the selling operating unit at the transfer price.
The selling operating unit issues an intercompany invoice payable to the shipping operating unit.
If the customer is external, then the selling operating unit sends a separate invoice to the customer.
Shipping networks between the selling and shipping organizations.
Intercompany transaction flows between the selling and shipping operating units.
An internal location for the selling organization.
An internal customer with an internal location to the customer's ship-to site attached.
Price lists for selling and shipping OU, and the internally used price lists attached to the internal customer's bill-to site.
Tax structures in Oracle Payables and Oracle Receivables.
Oracle Receivables system options are defined.
Account Generator for the COGS accounts is set up.
Table 36-8 Profile Options for Verify Intercompany Invoicing for Sales Order Flow
| Profile Name | Profile Value |
|---|---|
|
AR: Use Parallel Hints |
No |
Not applicable.
Table 36-9 Setup Data for Verify Intercompany Invoicing for Sales Order Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Requisitions |
Item |
AS54888 (Pick a finished good) |
|
Organization |
M1 Seattle Manufacturing (Pick a non-WMS organization) |
|
|
Organization (Source) |
D1 Singapore Distribution Center (Pick a non-WMS organization) |
This process refers to the fulfillment of a line, the line type being Bill Only, with standard item and Generic - Bill only with Inventory Interface workflow.
A standard item with finished good template.
A transaction type with line type as Bill Only and process name as Line Flow - Generic, Bill only with Inventory Interface.
A customer or party.
Not applicable.
Not applicable.
Table 36-10 Setup Data for Fulfillment of a Bill Only Line with Standard Item Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
Sales Order |
Order Type |
Mixed (Pick an Order Type) |
|
Customer Number |
1006 (Pick a Party of Type Organization) |
|
|
Warehouse |
V1 (A non WMS Warehouse can be selected) |
|
|
Ordered Item |
AS54888 (A product can be selected) |
|
|
Payment Terms |
N30 (A Payment Term value can be selected) |
This test flow verifies multiple processing constraints validations for a sales order header and line for change in payment terms, customer purchase order and warehouse.
Processing constraints for the warehouse, customer PO and payment terms attributes are created for both header and line.
A non WMS warehouse.
A valid customer or party, with address and account number.
Not applicable.
Not applicable.
Table 36-11 Setup Data for Multiple Processing Constraints Validations for a Sales Order Header and Line Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
System Parameters |
Audit Trail |
Enable when Order is Entered |
|
Sales Order |
Order Type |
Mixed (Pick an Order Type) |
|
Payment Terms |
N30 (Pick a Payment Term) |
|
|
Customer Number |
1006 (Pick a Party of type Organization) |
|
|
Warehouse |
M1 (Pick a Non-WMS Warehouse) |
|
|
Ordered Item |
AS54888 (Pick a product) |
|
|
Processing Constraints (Application :Order Management) (Entity: Order Header and Order Line) |
Operation Group Scope Validation Entity Record Set Validation Template User Message |
Update 101 Any Order Header Order Booked Booked |
|
User Action |
Require Reason and Require History Generate Version and Require Reason Not Allowed |
|
|
Attribute |
Payment Term Warehouse Customer PO |
This flow verifies the audit history recorded for a sales order header and line, for change in payment terms.
Processing constraints for the attribute payment terms for both header and line.
A non WMS warehouse.
A customer or party, with address and account number.
Not applicable.
Not applicable.
Table 36-12 Setup Data for Verify Audit History for a Sales Order Header and Line Flow
| Window Name | Field Name | Field Value |
|---|---|---|
|
System Parameters |
Audit Trail |
Enable when order is entered |
|
Sales Order |
Customer Number |
1006 (Pick a party of type Organization) |
|
Warehouse |
V1 (Pick a non WMS warehouse ) |
|
|
Ordered Item |
AS54888 (Pick a product) |
|
|
Payment Terms |
N 30 (Pick a payment term) |
|
|
Processing Constraints (Application :Order Management) (Entity: Order Header) |
Operation Attribute User Action Group Scope Validation Entity Record Set Validation Template User Message |
Update Payment Term Require Reason and Require History 101 Any Order Header Order Booked Booked |
|
Processing Constraints (Application :Order Management) (Entity: Order Line) |
Operation Attribute User Action Group Scope Validation Entity Record Set Validation Template User Message |
Update Payment Term Require Reason and Require History 101 Any Order Line Line Booked Booked |
The processing constraints for a customer PO attribute are checked for the processing constraints with user action as Versioning and Not Allowed. User can create the processing constraints for Not Allowed user action for customer PO and verify the same in the sales order. Also, the versions of a sales order are generated whenever the customer PO is updated.
A customer or party.
A non WMS warehouse.
Not applicable.