Sie sind auf Seite 1von 12

Transaction Types in

Oracle Order Management


An Oracle White Paper
October 2000
Using Transaction Types in Oracle Order Management

EXECUTIVE OVERVIEW
Release 11I of Oracle Order Management is fully integrated with the Oracle
Workflow product. Workflow is a magical product which provides graphical tools
that allow non-programmers to define flexible business flows to precisely model
their business processes.
In order to capture the power of workflow in the workhorse module of Oracle
Order Management the implementers must define Transaction Types.

INTRODUCTION
This white paper discusses the differences between the implementation of
Transaction Types in Order Management and Order Types in previous releases of
Order Entry. It describes the setup steps required to create a new transaction type,
including creating the order transaction type, the line transaction type, associating
the appropriate workflows and assigning the document sequence. Then it goes
through a detailed example.

BACKGROUND
In Order Entry release 11 and prior Order Cycles controlled the processing steps
for an order. Order Cycles have been replaced by Workflow in Order
Management release 11i.
In Order Entry release 11 and prior Order Types were used to determine the
Order Cycle that an order would have. They were also used as a source for
defaulting information on orders and to establish certain processing controls,
including invoicing controls. Order Types have been replaced by Transaction
Types in Order Management Release 11i. Both orders and lines have transaction
types. The transaction types determine what workflow the order and line will have
and are still used as a source for defaulting and to establish processing controls.

FUNCTIONAL DIFFERENCES
As previously mentioned one of the primary differences between order types and
transaction types is that transaction types work with workflow as opposed to order
cycles. There are transaction types associated with both orders and order lines.
Order numbers are now controlled by assigning an AOL document sequence to
your order type. Creating document sequences and assigning them to order types

Using Transaction Types in Oracle Order Management Page 1


are two separate steps in Order Management, and neither can be done directly
from the transaction types form.

Key Enhancements
Some of the great new enhancements of Transaction Types/Workflow are:
• Since each line has its own workflow, each line on an order follow a different
flow. This allows you to have both order and return lines on the same order.
• You can create newworkflow 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. Order Cycles
could have no more than 30 actions.
• There is no limit on 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.

Terminology
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.

Defining Line Transaction Types

Using Transaction Types in Oracle Order Management Page 2


The Define Transaction Types form is used to define both order and line types.
Here is how you define Line Transaction
Types.
Define your line types first. You should define line types for both order lines and
return lines. To access the form from the order management navigation menu
choose Setup -> Transaction Types -> Define. 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. Enter LINE for the
Transaction Type Code. Enter either Order or Return for the Order Category
depending on whether your new line type is for sales lines or return lines. Many of
the other fields on this form 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. The inaccessible fields include Order Workflow, Default
Return Line Type, Default Order Line Type, Agreement Required, Purchase Order
Required, Credit Check Rule for Ordering and Credit Check Rule for Shipping.
The Agreement Type field is used for validation on the order line. If you enter an
agreement type here, you can only use agreements of this type on sales order lines.
If the field is blank you may enter agreements of any type. If you want to use the
line type for a defaulting source 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 line at the time of order entry.
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. The Scheduling level controls the way
scheduling works at the time of order entry for lines of this type. The rest of the
fields can be used for defaulting.
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.

Here is how you define Order Transaction Defining Order Transaction Types
Types
Next, define your order type. To access the form from the order management
navigation menu choose Setup -> Transaction Types -> Define. Enter a name for
the order type in the Transaction Type field. Again, this name must be unique; you
cannot create an order type and a line type with the same name. Enter ORDER
for the Transaction Type Code. Enter the value Mixed, Order or Return for the
Order Category. If you enter Order the order type can only have lines with

Using Transaction Types in Oracle Order Management Page 3


transaction type of ORDER. If you enter Return the order type can only have
lines with transaction type of RETURN. If you enter MIXED the order can have
lines with either transaction type. We will skip the Order Workflow field, the
Assign Workflows button, the Default Return Line Type field and the Default
Order Line Type field until the next section.
The Agreement Type field is used for validation on the order. If you enter an
agreement type here, you can only use agreements of this agreement type on sales
orders of this order type. If the field is blank you may enter agreements of any
type. The Agreement Required and Purchase Order Required are used for
validation. If the box is checked then these fields will be required on all orders of
this type when the order is booked. 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.

Assigning Workflows to Transaction Types

This is the step that attaches the magic of workflow to the practical reality of order
management.
The first thing you need to do is select appropriate workflows for your order type
and line types. Several header and line workflows are seeded. You can perform all
standard OM processing including orders, returns, drop ship orders, orders for
configured items and orders for assemble to order items using only seeded
workflows. You may also define your own workflows if you need additional steps
(such as notifications) or additional processes. You cannot just select any order

Using Transaction Types in Oracle Order Management Page 4


workflow to be used with any line workflow. Some workflow steps between an
order and line are dependent on each other. For example, the order flow with
header level invoicing has a step which waits for a continue activity in the line flow
with header level invoicing 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 when you are not ready for them to complete or which will
never complete.

The order type alone determines the order workflow. In the define transaction
types form for the order type, enter the order workflow that you have selected.
This is the name of the process in the workflow builder. Save the order type. (If
you don’t save, you won’t be able to select the order type in the next step.)

The combination of the order type, the line type and the item type determine the
workflow that a line will have. For this reason, you define the line workflows from
the order type workflow definition form. Press the Assign Line Flows button.
Enter the order type. For each combination of line type and item type that you
want to use with this order enter a line in the Assign Workflow processes form.
The line types are the ones that you defined. The item types are based on the
definition of the items in the inventory module and include values such as standard
item, kit, and PTO model. If you leave the item type blank the workflow process
that you define will be used for all item types. (Exception: If you use the
configure to order process, you must specifically assign a workflow to the
configured item type; the configured item will not use a workflow where the item
type field is blank.) The process name is the name of the workflow process as
defined in the workflow builder. You must enter a start date for each line flow
definition. Note: Once documents have been created using an order type you
cannot change the associated workflow assignments. Therefore if you need to
change the workflows assigned to a transaction or disable a transaction you must
enter an end date for the existing assignment, and if appropriate enter a new
assignment for the for the new workflow.

Finally you may enter a Default Order Line Type and a Default Return Line Type
on the order transaction form. These values can be used as sources for defaulting
the line type to orders of this order type.

Creating a Document Sequence

OM uses the AOL document sequence functionality for numbering orders. You
must define at least one document sequence to be used for your order types
(unless you are upgrading from a previous release of Order Entry in which case
your document sequences will be upgraded), and you may use it for all your order
types if you want, or you may define multiple document sequences and use
different ones with different order types. For instance, you could define an

Using Transaction Types in Oracle Order Management Page 5


automatic sequence beginning with 1 and assign it to all your order types. Then
each new order that you enter will receive the next number in the sequence.
Alternatively you could define one sequence to use with your domestic orders
which begins with 1 and another sequence to use with your international orders
which begins with 100000 and then the number ranges would be separate.

To create a document sequence from OM navigate to Setup -> Documents ->


Define. Give the document sequence a name. Enter Oracle Order Management
for the application. Enter an effective from date, select the numbering type
(automatic, manual or gapless) and assign an initial value.

Assigning a Document Sequence to the Order Transaction Type

To assign your order type to a document sequence navigate to Setup ->


Documents -> Assign. On the Document tab enter Oracle Order Management in
the Application field and the order type in the Category field. Select the set of
books. Enter Manual in the method field if the number sequence is manual,
otherwise enter Null. On the assignment tab enter the start date and the sequence
that you defined for your order type in the previous step. Note that you cannot
change the assignment for an order type and set of books. To change the
assignment you must assign an end date to the existing assignment and create a
new one for the new assignment. You cannot have more than one assignment for
the same date range, document type and set of books.

Reports
There is a report available which will print the setup information for your
transaction types. It is called the Transaction Type Listing Report and you can
print for one transaction type by name, a range of transaction types by name, only
order transaction types, only line transaction types or any combination of these
parameters.

MIGRATION/UPGRADE FROM ORDER TYPES


If you are a customer who is upgrading from a previous release of Order Entry to
Order Management your existing order types will be upgraded to new order and
line transaction types. Your existing order cycles will be upgraded to new order
and line workflow processes. However, you should not use these upgraded
workflows for your new orders. They include many activities which check for
status and are necessary for upgraded orders but are very inefficient for new
orders. As part of the upgrade you should set up the flows associated with your
upgraded transaction types as either seeded or custom flows which were created
for new OM orders.
Also note that your existing order number sources are upgraded to document
sequences. Document sequence categories are created for your upgraded order

Using Transaction Types in Oracle Order Management Page 6


types, and these are assigned to the correct sequences. So you shouldn’t need to
do anything to these.

EXAMPLE
Now let’s create a new order type with associated line types, assign the workflow
processes, and create and assign a document sequence. Then we’ll be ready to
enter an order.
Here’s how you’d do this:
First, create a line type for your order lines. Navigate to Setup -> Transaction
Types -> Define. Create a new transaction type with the following information.
(Any fields not in this table should be left blank.)
Tab Field Value
Main
Transaction Type Standard
Description Standard Order Line
Effective Dates - From [Today’s Date]
Transaction Type Code LINE
Order Category Order
Shipping Scheduling Allow all scheduling actions
Finance Credit Method for Invoices with Prorate
Split Rules
Credit Method for Split Term Prorate
Invoices

Next, create a line type for your return lines. On the same form create a new
transaction type with the following information. (Any fields not in this table
should be left blank.)
Tab Field Value
Main
Transaction Type Return with Receipt and
Credit
Description Standard Return Line
Effective Dates - From [Today’s Date]
Transaction Type Code LINE

Using Transaction Types in Oracle Order Management Page 7


Order Category Return
Shipping Scheduling Allow all scheduling actions
Finance Credit Method for Invoices with Prorate
Split Rules
Credit Method for Split Term Prorate
Invoices

The last transaction type that you need to create is the order transaction
type. On the same form create a new transaction type with the following
information. (Any fields not in this table should be left blank.)
Tab Field Value
Main
Transaction Type Mixed
Description Standard Order with both
Order and Return Lines
Effective Dates - From [Today’s Date]
Transaction Type Code ORDER
Order Category Mixed
Shipping Scheduling Allow all scheduling actions
Finance Invoicing Rule ADVANCE INVOICE
Accounting Rule IMMEDIATE
Credit Method for Invoices with Prorate
Split Rules
Credit Method for Split Term Prorate
Invoices
Receivables Transaction Type Invoice

Now assign your workflows to your transaction types. You should still be on
the define transaction type form for the Mixed order type. Add the following
information to this form:
Tab Field Value
Main
Order Workflow Order Flow - Generic

Using Transaction Types in Oracle Order Management Page 8


Default Return Line Type Return with Receipt and
Credit
Default Order Line type Standard

Save your order transaction type so that you will be able to use it in the next step.
Press the Assign Line Flows button and enter the following information on the
Line Workflow Assignments Form:
Field Value
Order Type Mixed
Line 1
Line Type Standard
Item Type [Blank]
Process Name Line Flow - Generic
Start Date [Today’s Date]
Line 2
Line Type Return with Receipt and
Credit
Item Type [Blank]
Process Name Line Flow - Return for Credit
with Receipt
Start Date [Today’s Date]

Create a document sequence for Orders. Navigate to Setup -> Documents ->
Define. Enter the following information:
Field Value
Name Mixed Orders Sequence
Application Oracle Order Management
Effective From Date [Today’s Date]
Type Automatic
Initial Value 1
Start Date [Today’s Date]

Using Transaction Types in Oracle Order Management Page 9


Finally, assign the order type to the document sequence. Navigate to Setup -
> Documents -> Assign. Enter the following information:
Tab Field Value
Document
Application Oracle Order Management
Category Mixed [This is the name of
the order type]
Set of Books [The set of books for the
order type]
Assignment
Start Date [Today’s Date]
Sequence Mixed Orders Sequence

Voila! You should now be able to enter an order of type Mixed and process both
order and return lines through invoicing.

CONCLUSION
This white paper should give you the information that you need to begin setting up
transaction types. For additional information on transaction types, using workflow
in Order Management, defaulting, etc. see the Oracle Order Management User’s
Guide. For additional detailed information on Workflow see the Oracle
Workflow Guide.

Using Transaction Types in Oracle Order Management Page 10


Using Transaction Types in Oracle Order Management
October 2000
Author: Ginger Alexander

Oracle Corporation
World Headquarters
500 Oracle Parkway
Redwood Shores, CA 94065
U.S.A.

Worldwide Inquiries:
Phone: +1.650.506.7000
Fax: +1.650.506.7200
Web: www.oracle.com

This document is provided for informational purposes


only and the information herein is subject to change
without notice. Please report any errors herein to
Oracle Corporation. Oracle Corporation does not
provide any warranties covering and specifically
disclaims any liability in connection with this document.

Oracle is a registered trademark, and Oracle Order Management is a


trademark(s) or registered trademark(s) of Oracle corporation.
All other names may be trademarks of their respective owners.

Copyright © Oracle Corporation 2000


All Rights Reserved