Pricing for Order Management

To manage pricing for Order Management, we need pricing responsibility.

Define Pricing Responsibility:
Application: Advanced Pricing
Menu: QP_PRICING_MANGER

Request Group:
Name: QP Concurrent Programs

Pricing Responsibility Security Profile Options:

N: System Administrator>Profile>System

Responsibility: Pricing
Profile:	Responsibility:
HR: Business Group	XX Business Group
HR: Security Profile	XX Security Profile
HR: User Type	HR User
QP: Item Validation Organization	XX Item Master Org

Operating Unit is setup only to default currency.

As Pricing is controlled at legal entity level Operating unit security profile is optional

Define Document Assignments

Document Assignments: Document Sequence Assignments is used to assign sequences to order types.

N: Setup>Documents>Assign

Document:
Application: Order Management
Category: XX Sales Order Header Type
Ledger: XX Ledger
Method: Automatic/Manual/Null

Assignment:
Start Date:
Sequence: XX Standard Sales Order Doc Seq

Defining Document Sequence

Document sequence is used for maintaining document numbering.

N: Setup>Documents>Define

Name: XX Standard Sales Order Doc Seq
Application: Order Management
From:
Type: Automatic/Manual/Gapless
Initial Value: 100

Defining Order Type

Order Type:
An order type is used to identify the type of transaction. It is the transaction type that we define based on how we transact, like standard order, return order, mixed order etc.

There are two levels for order types. One is at header level and the second is at line level. This is because, sometimes we may have a scenario where we need to do a transaction with both standard and return lines in the same SO.

Define Transaction Type:
When we want to define a new transaction type, we need to define line type first and then tie it to Order header.

Line:
N: Setup>Transaction Types>Define

PIC

Transaction Type: XX Sales Order Line Type
Sales Document Type: Sales Order/Sales Agreement
Order Category: Order/Return/Mixed
Transaction Type Code: LINE
Effective Dates

Order Header:
N: Setup>Transaction Types>Define

PIC

Transaction Type: XX Sales Order Header Type
Sales Document Type: Sales Order/Sales Agreement
Order Category: Order/Return/Mixed
Transaction Type Code: ORDER
Fulfillment Flow: Order Flow - Generic (It decided the user actions based on the workflow)
Effective Dates
Default Order Line Type: XX Sales Order Line Type (Tie Line to Order)

Assign Line Flows:
Line Type: XX Sales Order Line Type
Process Name: Line Flow - Generic
Start Date:

Order types can defined for return and mixed similarly using the respective workflows.

Defining a customer

To fill a sales order we need the details of the customer for whom we are creating a SO.
Customer details are used for billing, shipping etc.
We may need bill to location to send the bill details and ship to details to ship the item to that location.

N: OM>Customers>Standard

PIC

Click on Create
Fill below mandatory details

Customer Information:
Organization Name

Account Information:
Account Type: External/Internal
External:
Internal: Internal is used for ISO IRS cycles

Account Site Address:
Country
Address Line 1

Account Site Details:
Operating Unit
Category
Territory

Business Purpose:
Bill To
Ship To

Click on Save and Add details to save the customer details.
Click on Apply for saving the details.

OM Security Profile Options

N: System Administrator>Profile>System

Responsibility: Order Management
Profile:	Responsibility:
HR: Business Group	XX Business Group
HR: Security Profile	XX Security Profile
HR: User Type	HR User
MO: Operating Unit	XX Operating Unit
MO: Default Operating Unit	XX Operating Unit

Accounting entries created in Oracle Apps during O2C cycle