Use Groups to Manage and Control Sales Orders
Set up the Order Type attribute on the order header to arrange sales orders into groups that you specify, then use these groups to help manage sales orders and control order processing.
-
You can search for sales orders on the Manage Orders page according to order type. This capability focuses the search and helps improve search productivity.
-
The Manage Orders page doesn't come predefined to display the Order Type attribute in the search area. The Order Entry Specialist must click Add Fields, then add it to the search area.
-
If you import a source order from a source system, then Order Management will examine the value of Order Type in the source order to make sure it matches one of the values that you set up for the lookup. If it doesn't match, then Order Management rejects the import and logs an error.
Use Order Type to Control Processing
Use Order Type in Business Rules
Use the order type in a business rule.
Type of Rule |
Description |
---|---|
Product transformation |
Use the order type as part of a pretransformation, transformation, or posttransformation rule. For example:
Order Management runs each pretransformation rule when you create or revise a sales order in the Order Management work area. For example, when you update the Business Unit, Customer, or Order Type, or adds an order line. To avoid overwriting these selections, you can write a pretransformation rule so it sets a value only if the attribute is empty. |
Process assignment |
Write a rule that uses the order type to assign an orchestration process. For example, if Order Type is Government Department of the Interior, then set up an orchestration process that fulfills order lines according to Department of the Interior procurement requirements. |
Routing |
Write a rule that uses the order type to determine which fulfillment system will fulfill the sales order. For example, if Order Type is Emergency, then route the sales order to a fulfillment system that prioritizes shipment speed over other factors. |
Use Order Types in Processing Constraints
Use the order type in the condition or result of a processing constraint. For example, prevent Order Management from updating an attribute according to the value of some other attribute. You can also use the order type to prevent Order Management from submitting a sales order. For example:
-
If Order Type is x, then don't allow change to attribute y after submit.
-
If Business Unit is x, then don't allow change to Order Type after submit.
-
If a submit validation happens, and if Order Type is empty, then display an error.
-
If a submit validation happens, and if Order Type is x, and if Purchase Order is empty, then display an error.
Set Up Order Types
In this example, you set up four order types so you can differentiate between sales orders in a deployment that uses drop ship.
This topic uses example values. You might need different values, depending on your business requirements.
-
In the Setup and Maintenance work area, go to the task.
-
Offering: Order Management
-
Functional Area: Orders
-
Task: Manage Order Lookups
-
-
On the Manage Order Lookups page, in the Search area, enter the value, then click Search.
Attribute
Value
Lookup Code
ORA_DOO_ORDER_TYPES
Order Management uses the ORA_DOO_ORDER_TYPES lookup for attribute Order Type, but doesn't come predefined with values for this lookup. If you don't add any values, then Order Management still displays the Order Type attribute but it won't contain any values.
-
In the Lookup Codes area, click Actions > New to add each lookup code.
Lookup Code
Meaning
STD
Standard Sales Order
STD_DS
Drop-Ship Sales Order
MIX
Standard and Drop Ship Order Lines
RETN
Return Sales Order
You can modify other attributes, as necessary.
-
Click Save and Close.