Transaction Types are used to associate workflows for various phases of sales document (sales orders or sales agreements) processing. You can also associate various values like transaction phases, layout templates, approvers to a transaction type and these will be defaulted on the sales order or sales agreement

Transaction(Order/Line) Types

Transaction Types provide default information on orders and establish process controls.
Transaction type is the generic term that refers to both Order Transaction Types and Line Transaction Types in Order Management. This is not to be confused with the Receivables Transaction Type, which is a completely different object.

The transaction type code may have values of Order or Line and determines whether the transaction type is an order transaction type or a line transaction type. In this document order type is used synonymously with order transaction type and line type is used synonymously with line transaction type. A document sequence is a range of numbers that can be used for an order type and is defined by a numbering method (automatic, manual or gapless) and the beginning order number.

A document category is a specific type of document such as a sales order or a purchase order. These are used in many Oracle applications for key entities. In Order Management when you create an order transaction type the system automatically creates a document category with the same name. This is used to assign the numbering sequence to the order type.

Some of the features of Transaction Types/Workflow are:
■ Each line in an order has its own workflow so each line may follow a different flow. This allows you to have both order and return lines on the same order.
■ You can create new workflow activities from custom PL/SQL code. This makes it very easy to extend OM.
■ A workflow process can have subprocesses.
■ A workflow process can have an unlimited number of activities.
■ There is no limit to the number of custom workflow activities that can be defined in Order Management.
■ You can view the status of the workflow on an order or order line in either tabular or graphical format. In graphical format you can see not only the activities that the workflow has completed but also the activities that still require completion.

Line Transaction Types

The Define Transaction Types window is used to define both order and line types.
Define your line types first. You should define line types for both order lines and return lines. To access the window from the order management navigation menu choose
Setup -> Transaction Types -> Define.
Except the operating unit and transaction type name the other mandatory fields in the header are Order category, Transaction type and effective dates. And we should also specify the sales document type(agreement type: SO/Blanket Agreement)

1. Enter a name for the line type in the Transaction Type field. Note that this name must be unique; you cannot create an order type and a line type with the same name.

2. Sales Documnet Type : Sales Order / Sales Agreement

3. Order Category : Order / Return /Mixed
Enter either Order or Return for the Order Category depending on whetheryour new line type is for sales lines or return lines. For Line transaction type choose wither order/return.
The value Mixed is selected for order type which can contains both sales order and return lines.

4. Transaction Type Code : Order/Line
Enter LINE for the Transaction Type Code.

Many of the other fields on this window as well as the assign line flows button are not applicable to line types so
when you enter the transaction type code they will become inaccessible
On the Shipping tab the autoschedule flag is inaccessible because it only applies to order types. The inspection required flag determines whether inspection is required when return lines are received. There are five Scheduling level choices to control the way scheduling works at the time of order entry for lines of this type: ATP Only, Allow all scheduling actions, No reservations, Inactive Demand with Reservations and Inactive Demand without Reservations. The remainder of the fields can be used for defaulting.

Two values on the Schedule Level LOV on the Shipping tab support different requirements for reservations: Inactive Demand with Reservations and Inactive Demand without Reservations. These levels can be set on the transaction types,
which would mean that the line will not be scheduled and will not be seen as demand in APS. When this level is set, Schedule Ship Date entered by the user will be accepted and no scheduling is done. If scheduling is done as an action or through WF, Request Date will be copied to the Schedule Ship Date if it is already not there.

Shipping Source Type: External/Internal. Its used to default the values but can be changed in sales order. The shipping source type External is used for drop ship orders.

The Finance tab fields contain information which affects the interfaces with the financial applications. The Invoicing Rule and Accounting Rule fields are used as defaulting sources for the sales order, and this information on the sales order is
passed to Autoinvoicing. For the fields Invoice Source, Non-Delivery Invoice Source, and Receivables Transaction Type these values are required for interfacing to Receivables but they are not on the sales order header or line. When the invoice
interface activity in the workflow is executed the system will look for a value in the following order: line transaction type, order transaction type, profile option. If no value is found the invoice interface activity will fail. The Cost of Goods Sold
Account can be used by the Account Generator function of the inventory interface when a line is ship confirmed.

Order Transaction Types

Here the transaction type could would be order.
If you want to use the order type as a defaulting source for Price List on the order you may enter a Price List on the Main tab. The Enforce List Price flag will determine whether a user can apply a manual discount to the order at the time of order entry. The Credit Check rules for ordering and shipping determine whether credit check will occur for this order type. If the fields are blank, no credit checking will occur for orders of this type.

On the Shipping tab the autoschedule flag determines whether scheduling will try to autoschedule the lines on orders of this type. The inspection required flag is not accessible (it only applies to lines). The rest of the fields can be used for defaulting.

The Finance tab fields are used for information which affects the interfaces with the financial applications. The Currency and Currency Conversion Type can be used as defaulting sources for the order header. The Invoicing Rule and Accounting Rule
fields are used as defaulting sources for the sales order line, and this information on the sales order is passed to Autoinvoicing.For the fields Invoice Source, Non-Delivery Invoice Source, and Receivables Transaction Type these values are required for interfacing to Receivables but they are not on the sales order header or line. When the invoice interface activity in the workflow is executed the system will look for a value in the following order: line transaction type, order transaction type, profile option. If no value is found the invoice interface activity will fail. The Cost of Goods Sold Account is used by the inventory interface when a line is ship confirmed.