Oracle Apps Order Management - Defining Order Management Transaction Types

Overview

In prior releases of Oracle Order Entry, Order Types were used for defaulting information on orders, establishing processing controls such as invoicing, and most importantly, determining the Order Cycle that an order would have. Order Cycles, in turn, controlled the processing flow of an order.

With the release of Oracle Order Management 11i, Order Cycles have been replaced by Oracle Order Management Workflow definitions, and Order Types have been replaced by Order Management Transaction Types. Order Management provides seeded Workflow process definitions for both orders and lines, and Order Management also enables you to define both order header and Order Line transaction types.

Note: Order Management provides NO seeded transaction types. For existing Oracle Order Entry customers, Order Management will update existing Order Types to order and line transaction types during the upgrade process

Order Management Transaction types:

• Determine the workflow processes executed for both the order and line.
• Can act as sources for order and line level attribute defaulting.
• Can establish order or line level processing constraints.
• Can default from the Customer, Ship To, Bill To, or Deliver-To site at the order header, and line transaction types can default from the order transaction type.
• Enable you to group orders and lines.
• Can specific processing controls for an order or line based upon the transaction type entered.

For example, the Scheduling level controls the way scheduling works at the time of order entry for lines.

Prerequisites

• Review seeded order and line flows.
• Define all lookups. See: Defining Order Management QuickCodes.Oracle Order Management Suite Implementation Manual, Release 11i, Defining Order Management QuickCodes.
• Define freight carriers. See: Oracle Shipping Execution User's Guide.
• Define organizations. See: Creating an Organization, Oracle Human Resources Management Systems User's Guide.
• Define document sequences. See: Defining Document Sequences for Order Numbering.Oracle Order Management Suite Implementation Manual, Release 11i, Defining Document Sequences for Order Numbering.
• Define defaulting rules. See Overview of Defining Defaulting Rules
• Define price lists. See: Creating a Price List.

Define credit check rules. See: Defining Credit Check Rules

See: Defining Credit Check Rules

• Define currencies and currency types. See: Defining Currencies, Oracle Applications System Administrator's Guide.
• Set up your cost of goods sold account flexfield segments. See: Defining Key Flexfield Segments, Oracle Applications Flexfields Guide.

Note: You must first define your OM Line Transaction Types so that they can be assigned when defining your OM Order transaction types.

Order and Line Level Controls

You can define order controls that apply to the order as a whole and are not overridable at the line level. For example, order numbering is controlled at the order level. An order can be numbered differently based on the order type, such as an order or return.

You can also define line controls that affect the line type level. You can set up certain controls that default from the order level and can be overridden at the line level. For example, you can have both return and order lines on a single order, however, the return and order lines process differently. The individual line processing is controlled at a higher line type level. You need to specify the workflow couplings for the permitted transaction type combinations. If a combination has notifications or workflow activities at the header flow which need to be completed before the line can proceed, then the header flow needs to have a Continue-flow activity. The line flow needs to have the appropriate Wait-for-flow activity.

The following table displays the various column controls that are available for Order Management Order transaction types.

Column Name	Purpose	Define for Order Transaction Types	Required on Order Transaction Types	Defaulting Source for Header
NAME	Unique within the table for a given language.	Yes	Yes	No
TRANSACTION_TYPE_CODE	Distinguishes between order and line types. Line types are Order and Line.	Yes	Yes	No
ORDER_CATEGORY_CODE	Defaulting on the order or line. Restricts the types of lines on an Order. Mixed, Order, or Return. Line types are Order or Return.	Yes	Yes	Yes
CURRENCY_CODE	Defaulting source.	Yes	No	Yes
CONVERSION_TYPE_CODE	Defaulting source.	Yes	No	Yes
CUST_TRX_TYPE_ID	Invoicing Interface./Tax	Yes	No	No
COST_OF_GOODS_SOLD_ACCOUNT	Invoicing Interface	Yes	No	No
ENTRY_CREDIT_CHECK_RULE_ID	Credit checking.	Yes	No	No
SHIPPING_CREDIT_CHECK_RULE_ID	Credit checking.	Yes	No	No
PRICE_LIST_ID	Defaulting source	Yes	No	Yes
ENFORCE_LINE_PRICES_FLAG	Used for validating discount application on order and lines	Yes	Yes	No
WAREHOUSE_ID	Defaulting source.	Yes	No	Yes
DEMAND_CLASS_CODE	Defaulting source.	Yes	No	Yes
SHIPMENT_PRIORITY_CODE	Defaulting source.	Yes	No	Yes
SHIPPING_METHOD_CODE	Defaulting source.	Yes	No	Yes
FREIGHT_TERMS_CODE	Defaulting source.	Yes	No	Yes
FOB_POINT_CODE	Defaulting source.	Yes	No	Yes
SHIP_SOURCE_TYPE_CODE	Defaulting source. The values are Internal, External.	No	No	No
AUTO_SCHEDULE_FLAG	Used by Scheduling. The values are Yes, No.	Yes	No	No
SCHEDULING_LEVEL_CODE	Used by Scheduling. The values are 0, 1, 2.	Yes	No	No
AGREEMENT_TYPE_CODE	Validation at header level.	Yes	No	No
AGREEMENT_REQUIRED_FLAG	Validation on Header.	Yes	Yes	No
PO_REQUIRED_FLAG	Validation at header level.	Yes	Yes	No
INVOICING_RULE_ID	Defaulting source.	Yes	No	Yes
INVOICING_CREDIT_METHOD_CODE	Defaulting source.	Yes	No	Yes
ACCOUNTING_RULE_ID	Defaulting source.	Yes	No	Yes
ACCOUNTING_CREDIT_METHOD_CODE	Defaulting source.	Yes	No	Yes
INVOICE_SOURCE_ID	Invoicing Interface.	Yes	No	No
NON_DELIVERY_INVOICE_SOURCE_ID	Invoicing Interface.	Yes	No	No
DEFAULT_INBOUND_LINE_TYPE_ID	Defaulting source for inbound lines. Use this value as Source for defaulting Line type on Line.	Yes	No	No
DEFAULT_OUTBOUND_LINE_TYPE_ID	Defaulting source for outbound lines. Use this value as Source for defaulting Line type on Line.	Yes	No	No

Note: The transaction type name for the base language cannot be changed once there are orders or lines referenced.

Order Category

You can specify an order category on the order transaction type. The category code controls the types of lines which are permitted on the order.

The order category can be defined as Order, Return, or Mixed. If the category code is Order, then the order can only have outbound lines. If the category code is Return, then the order can only have inbound lines. If the category code is Mixed, then the order can have inbound and/or outbound lines.

Order Numbering

Define your order numbering options using the Oracle Application Object Library (AOL) Document Sequence functionary. You can set up various OM order transaction types and different document sequences. Both OM transaction types and document sequences can control which types of orders are numbered automatically or manually.

For example, you can have all your outbound orders numbered in a certain sequence and all your returns in a different sequence.When an OM order transaction type is created, a document category with the same name is automatically created. You can define sequences and assign them to the respective document category. See: Defining Document Sequences for Order Numbering.

Order Management Line Transaction Types

Order Management line transaction types can be defined to control order line information. There are specific controls that need to be definable at the line type level. Some controls can be such that, they default from the order level, but can be overridden at the line level. For example, you can have both order and return lines on a single order. However, order and return lines go through different types of processing. The kind of processing that an individual line undergoes is controllable at a line type level.

The following table displays the various column controls that are available for Order Management Line transaction types.

Column	Purpose	Usable on Line Type	Required for Line Type	Defaulting source for Line
NAME	Unique within the table for a given language.	Yes	Yes
TRANSACTION_TYPE_CODE	Distinguish between order and line types. Valid values for Line types: Order/Line.	Yes	Yes	No
ORDER_CATEGORY_CODE	Defaulting for order or line; If used on Order Type, restricts line types.Valid values for Line Types: Order/Return	Yes	Yes	Yes
CURRENCY_CODE	Defaulting Source	No	No	No
CONVERSION_TYPE_CODE	Defaulting Source	No	No	No
CUST_TRX_TYPE_ID	Used by Invoicing	Yes	No	No
COST_OF_GOODS_SOLD_ACCOUNT	Used by Inventory Interface	No	No	No
ENTRY_CREDIT_CHECK_RULE_ID	Used by Credit Checking	No	No	No
SHIPPING_CREDIT_CHECK_RULE_ID	Used by Credit Checking	No	No	No
PRICE_LIST_ID	Defaulting Source	Yes	No	Yes
ENFORCE_LINE_PRICES_FLAG	Used for validating discount application on Order/Lines	No	No	No
WAREHOUSE_ID	Defaulting source	Yes	No	Yes
DEMAND_CLASS_CODE	Defaulting source	Yes	No	Yes
SHIPMENT_PRIORITY_CODE	Defaulting source	Yes	No	Yes
SHIPPING_METHOD_CODE	Defaulting source	Yes	No	Yes
FREIGHT_TERMS_CODE	Defaulting source	Yes	No	Yes
FOB_POINT_CODE	Defaulting source	Yes	No	Yes
SHIP_SOURCE_TYPE_CODE	Defaulting source. Valid values: Internal/External	Yes	No	Yes
AUTO_SCHEDULE_FLAG	Used by Scheduling. Valid values: Yes/No	No	No	No
SCHEDULING_LEVEL_CODE	Used by Scheduling. Valid values: ONE, TWO, THREE	Yes	No	No
AGREEMENT_TYPE_CODE	Validation on Header	No	No	No
AGREEMENT_REQUIRED_FLAG	Validation on Header	No	No	No
PO_REQUIRED_FLAG	Validation on Header	No	No	No
INVOICING_RULE_ID	Defaulting source	Yes	No	Yes
INVOICING_CREDIT_METHOD_CODE	Defaulting Source	Yes	No	Yes
ACCOUNTING_RULE_ID	Defaulting source	Yes	No	Yes
ACCOUNTING_CREDIT_METHOD_CODE	Defaulting Source	Yes	No	Yes
INVOICE_SOURCE_ID	Used by Invoicing	Yes	No	No
NON_DELIVERY_INVOICE_SOURCE_ID	Used by Invoicing	Yes	No	No
DEFAULT_INBOUND_LINE_TYPE_ID	Defaulting source for Inbound Lines. Use this value as Source for defaulting Line type on Line	No	No	Yes
DEFAULT_OUTBOUND_LINE_TYPE_ID	Defaulting Source for Outbound Lines. Use this value as Source for defaulting Line type on Line	No	No	Yes

When you define OM line transaction types, you can define the line flow that lines of this type will follow. A line transaction type can be coupled with different OM order transaction types. For example, a return transaction type can be used with a standard order type or an international order type. However, you need to specify the flow couplings for the permitted transaction type combinations.

Workflow Assignments

The order type determines the order workflow. The combination of the order type, the line type, and the item type determines the line workflow.

Select appropriate workflows for order types, line types and item types:

You can perform all standard processing including orders, returns, drop ship orders, orders for configured items, and orders for assemble-to-order items using seeded workflows. You can also create your own workflows if you need additional steps, for example, additional notifications or processes.

You cannot select any order workflow to be used with a line workflow. Some workflow steps between an order and line are interdependent based on how Continue-flow and Wait-for-flow activities are paired.Therefore, the same line transaction type needs to follow a different line flow when used with a different order transaction type.

For example, the order flow with header level invoicing waits for an activity in the line flow to complete. If you do not use order and line flows which are designed to work together you can have orders or lines which either complete activities too early or which never complete.

The inventory item that a line is processing may have specific flow requirements. For example, a configuration needs to have a BOM and work order created before it can be picked and shipped. The standard item can be picked from stock and shipped. Therefore, the workflow for a configuration item is different than a standard item. However, both types of order lines can be use the same line type. The Workflow Assignments window displays the following item types for which a workflow can be assigned for a given order or order line type assignment:

• ATO Models, Classes, Options, Items
• Configured Item
• Kits
• Included Items
• PTO Models, Classes, Options
• Standard Items
• Service Items

If the item type code is left blank, the specified workflow assignment applies to all item types for which there is no specific assignment.However, you should specify an assignment for the configured item type, if you plan to use the line type for ATO models.

Note: A workflow assignment is required for a given line type to support creation of lines using that line type.

The following table displays sample Order types and associated Order Header workflow assignments.

Order Type	Header Flow Assignment
Domestic	Header - Standard
International	Header - International (This has a post-booking approval.)

Line Flow Assignments

The Line Flow Assignments window is available only for OM order transaction types only. Use this window to assign line flows to the various line types that can be used with an order type.

A line flow can be assigned to an order type, line type and item type combination. Order Management enables you to define only one effective assignment for a given combination. If the item type is left blank, then that assignment will apply to all item types that do not have a specific assignment. If you plan to use a line type for ATO models then Order Management requires that you specify an assignment for the item type of configured item. Refer to Overview of Workflows and Setting up Workflow.

The following table displays sample Order Line types and associated Order line workflow assignments.

Line Type	Order Types used with	For Item Type	Line Flow Assignments	Comments
Standard	Domestic		Outbound Domestic	For all item types (except configured items)
Standard	Domestic	Configured Item	Outbound Domestic Configuration	Workflow specific to configured items.
Standard	International		Outbound International	This has the appropriate Wait-for Flow defined for the notification activity on the International Header flow. The workflow is for all item types (except configured items).
Standard	International	Configured Item	Outbound Domestic - Configuration	This workflow is specifically for configured items.
Return	Domestic		Inbound Domestic	For all item types.
Return	International		Inbound International	This has the appropriate Wait-for- Flow defined for the notification activity on the International Header flow. This workflow is for all item types.

Defining Order Management Transaction Types

Prerequisites

• Review seeded Order and Line flows. Define new to meet your business requirements.
• Define all lookups.
• Define freight carriers. See: Oracle Shipping Execution User's Guide.
• Define organizations. See: Creating an Organization, Oracle Human Resources Management Systems User's Guide.
• Create Document Sequences for order numbering.
• Define defaulting rules.
• Define price lists.
• Define credit check rules.
• Define currencies and currency types. See: Defining Currencies, Oracle Applications System Administrator's Guide.
• Set up your cost of goods sold account flexfield segments. See: Defining Key Flexfield Segments, Oracle Applications Flexfields User's Guide.

   To define Order Management document, Pricing, or Credit Check order or line transaction types information:

1. Navigate to the Transaction Types window.

The Transaction Types window displays.

2. Select the Main tabbed region and specify a name that is unique across Operating Units.

3. Enter a Description.

4. Specify whether this is an order or line transaction type.

5. Specify the category.

For Order Types, you can specify a value of Order, Return, or Mixed. For Line Types you can specify Order or Return. When an order type is assigned to an order, the category determines whether both order and return lines can go on the order. A category of Mixed enables an order to have both kinds of lines.

6. For Order Transaction Type only - Optionally, enter an agreement type.

If you enter an agreement type here, you can choose only agreements with this agreement type when using this order type. Define agreement types using Order Management QuickCodes.

7. For Order Transaction Type only, specify a line type that will serve a default for all lines on the order with this order type.

If you are defining a Mixed order type, specify an inbound and outbound default line type. When you create a return line with negative quantities, the Sales Order window automatically sets the category on the to Return.

For Order Lines, the Sales Orders window automatically sets the category to Order. Order Management seeds defaulting rules to get the appropriate default outbound or inbound line transaction type from an order type to a line based on its category code.

8. Indicate whether an agreement is required for order transaction type only.

9. For Order Transaction Type only, check Purchase Order Required to require purchase order numbers during order entry for orders and returns with this Order type.

10. Select a price list to serve as a defaulting source.

11. For Order Transaction Type only- Optionally check Enforce List Price, if you do you cannot apply discounts to the order line list price when you use this order type and you cannot override the selling price, unless the profile option OM: Discounting Privilege is set at the appropriate level.

12. Optionally, select credit check rules to use when performing checking credit at either Booking, Pick Release and Purchase Release (for drop shipments), Packing, or Shipping within the corresponding Credit Check Rule fields.

You can select a credit check rule for each field within the Credit Check Rule region, or choose to select combinations that suit your business purposes. For example, you can choose to select a credit check rule for booking only, or booking and shipping.

If you leave any of the Credit Check Rule fields blank, no credit checking will occur when an order or order line reaches the corresponding workflow activity within the order or line flow, using the order or order line type specified.

Note: When an order type is created, Order Management automatically creates a Document Sequence Category of the same name for you. You can then go an assign a document sequence that you have defined for order numbering to this document sequence category. Document sequence categories are not MLS Compliant. Order Management recommends that you create your order types in the base language of your installation to minimize potential confusion.

Note: Workflow assignments are required for order types to support the creation of orders.

13. Save your work.

   To define Shipping Related Attributes for Order Management order and line transaction types:

1. Navigate to the Shipping tabbed region in the Transaction Types window.

2. Optionally, select a warehouse. Warehouses are synonymous with inventory organizations in Oracle Manufacturing.

3. Optionally, enter a Shipping Method.

4. Optionally, enter a Shipment priority.

Define shipment priorities using Order Management QuickCodes.

5. Optionally, enter the Freight terms.

Define freight terms using Order Management QuickCodes.

6. Optionally, enter the Free On Board (FOB) point.

Define FOB points using Receivables QuickCodes.

7. For Line Transaction Type only - Optionally specify a value for ship source type. It can be either internal or external. This determines whether the order line is sourced internally or externally (via Drop Shipment).

8. Optionally, enter the Demand Class.

Define demand classes using Manufacturing QuickCodes.

9. Optionally, specify the scheduling level. It can have the following values:
• One: Perform only ATP check.
• TWO: Perform ATP check and Scheduling - No reservations
• THREE: perform complete scheduling (ATP Check, Demanding, Reserving).

Note: If you do not specify a value for an Order Transaction type, the application interpreted the null value as Complete Scheduling. If you do not specify a value for a Line Transaction Type the application uses the value from the Order Type on the Order.

10. For order transaction type only - Optionally, check auto-schedule.

This setting determines whether auto-scheduling is performed for orders using this order type.

11. For return line transaction type only - Optionally, set whether inspection is required.

   To define Financial attributes for Order Management order or line transaction types:

1. Navigate to the Finance tabbed region in the Transaction Types window.

2. If you use Oracle Receivables, enter the Default Invoicing Rule to apply to this order or line type.

An invoicing rule controls the amount and timing of your invoices.

3. If you use Oracle Receivables, enter the default accounting rule to apply to this order type or line type. An accounting rule controls the amount and timing of when you recognize revenue for this order.

See: Defining Invoicing and Accounting Rules, Oracle Receivables User's Guide.

4. Optionally, select a Invoice Source.

5. Optionally, select a Non-Delivery Invoice Source.

6. Optionally, select the Accounting credit method Oracle Receivables uses when adjusting the revenue account assignments of invoices using multi-period invoicing and accounting rules. See: Crediting Transactions, Oracle Receivables User's Guide.
• LIFO (Last In First Out)--Backs out revenue starting with the last general ledger period, and reverses all prior periods until it has used up the credit memo.
• Prorate--Credits an equal percentage to all account assignments for that invoice.
• Unit--Reverses the revenue for the number of units you specify from an original line of the invoice.
7. Optionally, select the Invoicing credit method Oracle Receivables uses when crediting the installments of invoices that have multiple installments (split term invoices). Crediting Transactions, Oracle Receivables User's Guide.
• LIFO (Last In First Out)--Credits the last installment to be credited first and then credits all prior installments until all of the credit is used.
• FIFO (First In First Out)--Credits the first installment first and then credits all subsequent installments until all of the credit is used.
• Prorate--Prorates the credit received by the installments of invoices by the amount remaining on their installments.
8. If you use Oracle Receivables, enter the receivables transaction invoice type.

Invoice types designate invoice status, invoice printing options, credit memo type, and whether the invoice posts to General Ledger or creates an open receivable. Ensure the Tax Calculation Flag for the Receivables transaction type you choose is set accordingly as this will determine whether Tax is calculated for the order line.

9. If you are defining a return type, select the invoice type associated with the appropriate credit memo type.
10. Optionally, enter a Cost of Goods Sold Account. - Definable only for the Order Transaction Type.
11. Optionally, enter a currency and a currency conversion type. - Definable only for the order transaction type.

If you choose User as the currency conversion type, the Sales Orders window requires you to enter the conversion rate and date.

12. Save your work.

   To assign workflows to transaction types:

Use this procedure to assign workflows to line transaction types. The combination of the order type, the line type, and the item type determines the line workflow.

Once you have created a document using an order type you cannot change the existing line workflow assignments. Instead, enter an end date for the existing assignment and enter a new assignment for the for the new workflow.

1. Navigate to the Transaction Types window and query the desired transaction type.

2. Click Assign Line Flows.

The Line Workflow Assignments window displays.

3. In Order Type, select the order type/line type/item type combination to which you want to assign a 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).

If you use line type ATO Models, use item type Configured Item and return line types use item type Standard even if they are for configurations.

4. In Process Name, select the workflow that Oracle Order Management should use for the order type/line type/item type.

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

5. In Start Date and End Date, select the time period during which the assignment is effective.

6. Save your work.