ORDER MANAGEMENT

Query:
I have fetched the data from a run time view

so need to execute a standard package of oracle

exec mo_global.init('ONT');

exec mo_global.set_policy_context('S',:org_id);

-- This Query is to Fetch the Order Transaction type setup details ---
-- Without this transaction type this sales order can not be booked ---

-- Navigation --> OM super user --> setup --> Transaction type --> Define...-
--

select a.ORGANIZATION_NAME ,
a.NAME "Transaction type",
a.DESCRIPTION,
a.SALES_DOCUMENT_TYPE,
a.ORDER_CATEGORY_CODE "ORDER CATEGORY",
a.TRANSACTION_TYPE_CODE,
d.LINE_TYPE"Assign Line Flows",
(select LINE_TYPE from OE_WF_LINE_ASSIGN_V
where order_type_id =a.TRANSACTION_TYPE_ID
and line_type_id =DEFAULT_INBOUND_LINE_TYPE_ID) "Default Return Line Type",
(select LINE_TYPE from OE_WF_LINE_ASSIGN_V
where order_type_id =a.TRANSACTION_TYPE_ID
and line_type_id =a.DEFAULT_OUTBOUND_LINE_TYPE_ID) "Default order line type",
b.name "Invoice Source",
c.name "Receivable Transaction Type"
from oe_transaction_types_v a,
RA_BATCH_SOURCES b,
RA_CUST_TRX_TYPES c,
OE_WF_LINE_ASSIGN_V d
where --transaction_type_id =2621
--and
b.BATCH_SOURCE_ID(+)=a.INVOICE_SOURCE_ID
and a.cust_trx_type_id=c.cust_trx_type_id(+)
and a.TRANSACTION_TYPE_ID=d.order_type_id(+)

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 whether your 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 Auto invoicing. 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 auto schedule flag determines whether scheduling will try to auto schedule
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 Auto invoicing. 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.
You can define holds that are effective only at certain steps of the order or

line workflow, as well as, holds that apply regardless of the stage in the

order’s flow. Holds can be defined to be specific for pick, pack, or ship
activities.
Holds may be designed to be applied automatically, or may be applied
manually based on set criteria you define.

How to Apply and Remove a Hold

Source
How to Apply and Remove a Hold
Source
Suppose you want to hold all current and future sales order for a Customer. to do so you have to create a
hold source based on Customer and select conditions to hold all existing and future sales order for this
customer.

Lets create a Order Source. Open Sales order Form and Navigate to Tools> Create Hold Source
Enter the criteria as shown in above screenshot. Previous to this step we have defined the hold named
"Mandeep" which we Work Flow item is: OM Order Header and workflow activity: Book Order.

Now click on Hold Name

Click on Apply Hold. You will receive a message the Hold applier successfully

Now try to create a sales order for this customer using Order Management Super User responsibility
navigate to Orders, Returns > Sales Orders

Enter sales order header for this customer. Click on Lines Item, you will get an error ‘Hold Applied against
order based on Customer'
Enter the line, save it and click on BOOK and receive the error in the Process Message form: 'A hold
prevents booking of this order.'

You can see order will remain in entered state

Now after few days you want to remove this hold

source
Navigate to Order organizer form and click on Hold information > Hold Source
Query for your Hold based on Hold Name

To Release this hold you need to put a reason and then click on Release button

you will get a message that hold release successfully. Click OK

Now if you try to book our previous order you will face no issue

OE_HOLD_DEFINITIONS -- HOLD ID, NAME, DESCRIPTION, and ITEM TYPE – OEOL, OEOH, Activity
Code – Book Order, Pick Order etc.
OE_HOLD_AUTHORIZATIONS – HOLD ID, RESPONSIBILITY ID
OE_ORDER_HOLDS_ALL – All holds related to Orders and lines
ORDER_HOLD_ID (PK), HOLD_SOURCE_ID, HOLD_RELEASE_ID, HEADER_ID, LINE_ID, ORG_ID
OE_HOLD_SOURCE_ALL – Holds information about order source criteria
HOLD_SOURCE_ID (PK), HOLD_RELEASE_ID, HOLD_ID, HOLD_ENTITY_CODE, HOLD_ENTITY_ID,
RLEASED_FLAG etc.
OE_HOLD_RELEASES – This table holds the release information
HOLD_RELEASE_ID (PK), HOLD_SOURCE_ID, RELEASE_REASON_CODE (LOOKUP -
RELEASE_REASON)

QUERY:

SELECT OOHA.ORDER_NUMBER,
OHD.NAME "HOL_NAME",
OHSA.HOLD_COMMENT,
FLV.MEANING "RELEASE_REASON"
FROM APPS.OE_ORDER_HEADERS_ALL OOHA,
APPS.OE_ORDER_HOLDS_ALL OHA,
APPS.OE_HOLD_SOURCES_ALL OHSA,
APPS.OE_HOLD_DEFINITIONS OHD,
APPS.OE_HOLD_RELEASES OHR,
APPS.FND_LOOKUP_VALUES FLV
WHERE OOHA.HEADER_ID = OHA.HEADER_ID
AND OHA.HOLD_SOURCE_ID = OHSA.HOLD_SOURCE_ID
AND OHSA.HOLD_RELEASE_ID = OHR.HOLD_RELEASE_ID(+)
AND OHSA.HOLD_ID = OHD.HOLD_ID
AND FLV.LOOKUP_TYPE(+) = 'RELEASE_REASON'
AND FLV.LOOKUP_CODE(+) = OHR.RELEASE_REASON_CODE
AND OOHA.HEADER_ID = 12048;

SALES PERSONS:
TABLE: RA_SALESREP_ALL (or) JTF_RS_SALESREPS, jtf_rs_defresources_v

SALESREP_ID(PK),RESOURCE_ID,NAME,ORG_ID.

QUERY:

SELECT
HCS.SITE_USE_ID LOCATION_ID,
HCS.LAST_UPDATE_DATE,
HCS.LAST_UPDATED_BY,
FU.USER_NAME,
HCS.CREATION_DATE,
JRS.SALESREP_NUMBER,
JRS.ATTRIBUTE2 EMAIL,
JRR.RESOURCE_NAME ASE_NAME
FROM
AR.HZ_CUST_SITE_USES_ALL HCS,
FND_USER FU,
JTF_RS_SALESREPS JRS,
JTF.JTF_RS_RESOURCE_EXTNS_TL JRR
WHERE
HCS.LAST_UPDATED_BY = FU.USER_ID
AND HCS.PRIMARY_SALESREP_ID = JRS.SALESREP_ID
AND JRS.RESOURCE_ID = JRR.RESOURCE_ID
AND HCS.PRIMARY_SALESREP_ID = 122333444
ORDER BY LAST_UPDATE_DATE DESC;
SELECT * FROM APPS.HZ_CUST_SITE_USES_ALL
WHERE SITE_USE_ID = 17829;
SELECT * FROM APPS.RA_SALESREPS_ALL
WHERE SALESREP_ID = 100002512;
PRICE LISTS: Price lists are used to derive selling prices automatically during on-line order entry.

http://vipulsharmaoracleapps.blogspot.com/2013/11/price-lists.html

http://5lyoracleapps.blogspot.com/2008/04/enter-sales-order.html

Price List Tables:

qp_list_headers_TL

qp_list_headers_B

QP_LIST_LINES

qp_pricing_attributes