1.

Order entry
2. Order Booking
3. Reserving for items in an
Order
4. Pick Release
5. Pick Confirm
6. Ship Confirm
7. Enter Invoice
8. Close Order Line
9. Close Order Header
Definition

Oracle Trading Community

Architecture (TCA) is a data model that allows
you to manage complex information about the parties, or
customers, who belong to your commercial community,
including organizations, locations, and the network of
hierarchical relationships among them
Customer Model Overview

What is Trading Community Architecture (TCA)?

• TCA is designed to encapsulate all members of a ‘trading

community.’

• A trading community may include customers, prospects,

suppliers, distributors, resellers, consortiums, etc.

• TCA not only allows for the tracking of relationships

between the implementing organization and its trading
partners, but also tracks relationships between the trading
partners themselves.
TCA Concepts Agenda

 Party
 Party Site
 Customer Account
 Customer Sites
 Customer Site Usage
 Customer Profile Class
Trading Community Architecture
‘The Party Concept’
• The concept of ‘Party’ enables the Customer Model to treat all
business entities equally, regardless of type. It easily handles B2B,
B2C.
• Parties of type ‘Group’ allow for the grouping of any number of other
parties into a single entity which enable modeling of households and
buying consortiums.

• Parties of type ‘Relationship’ allow for the relationship between two

parties to be viewed as a party in its own right.
 The Customer Entity Data Model
- Party Entity
Party - A Party is an entity that can enter into a business
relationship and can be of four types.

• Person - A unique individual (dead or alive) of interest to the owner of the

software.

• Organization - A legal entity recognized by some government authority.

• Group - a combination of two or more people, organizations or groups of

created for the use of the owner of the software.

• Relationship - The association between an individual person and an

organization. Usually a contact at an organization or group.
 The Customer Entity Data Model
- Customer Account Entity
Account - Is a financial roll-up point to track the monitory
portion of a customer’s purchases and payments. Stores
details about a customer relationship between a Party and
your business.
A Party may have one or more Customer Accounts.

Account Role - The relationship that a Party has in regard to controlling or

using an account.

Customer Account Site is a Party Site that is used within the context of a
Customer Account (e.g., for billing or shipping purposes).

A Customer Account Contact is a Party Contact that is used in the context

of a Customer Account.
How do the RA tables equate/translate to the HZ tables?
--------------------------------------------------------------------

Release 11 Schema Release 11i Schema (Important Tables)

----------------------- ---------------------------
RA_CUSTOMERS_ALL HZ_PARTIES
HZ_PERSON_PROFILES
HZ_ORGANIZATIONS_PROFILES
HZ_CUSTOMER_ACCOUNTS

RA_ADDRESSES_ALL HZ_PARTY_SITES
HZ_LOCATIONS
HZ_CUST_ACCT_SITES_ALL

RA_PHONES HZ_CONTACT_POINTS

RA_CONTACTS HZ_CUST_ACCCOUNT_ROLES
HZ_ORG_CONTACTS
HZ_PARTIES
HZ_PARTY_RELATIONSHIPS

RA_CONTACT_ROLES HZ_ROLE_RESPONSIBILITY

RA_CUSTOMER_RELATIONSHIPS_ALL HZ_CUST_ACCT_RELATE_ALL

RA_SITE_USES_ALL HZ_CUST_SITE_USES_ALL

AR_CUSTOMER_PROFILE_CLASSES HZ_CUSTOMER_PROFILE_CLASSES

AR_CUST_PROF_CLASS_AMOUNTS HZ_CUST_PROF_CLASS_AMOUNTS

AR_CUSTOMER_PROFILES HZ_CUSTOMER_PROFILES

AR_CUSTOMER_PROFILE_AMOUNTS HZ_CUSTOMER_PROFILE_AMOUNTS
1. Create a Customer Manually.
2. Create a party using TCA API.
1. Setup – Order Type / Price Lists
2. Customer Creation
3. Creating Order
4. Booking the Order
5. Pick Release
6. Pick Confirm
7. Ship Confirm
8. Interface Trip Stop
9. Workflow Background process
10. Invoicing
 Order to Cash Life-Cycle
Order Management Shipping Execution

Enter Book Pick Release Ship

Confirm
Interface Trip
Workflow Background
Stop
Cash
Management

Bank
Receivables Invoice Receipt Reconciliation
Customer
 As a party to a contract, the customer is responsible for oversight of the contract,
payments and any agreed-to obligations with the contractor. The organization which is
in the process of placing an order with the company.
Creating Order
 The following information is to be provided while entering an order:
Order details
Customer information
Item information at line level
Booking an Order
 In Order Management, booking is workflow enabled. The application comes seeded
with two types of Booking processes:
Manual Booking Process
Deferred Booking Process
Pick Release
 An order cycle action to notify warehouse personnel that orders are ready for picking.
Pick Confirm
 Executes the sub-inventory transfer that moves the material from its source location in
the warehouse to the staging location.
Ship Confirm

To enter shipped quantity and inventory controls for specific shippable lines.
You can ship confirm the same delivery/departure repeatedly until you close the
delivery/departure. Once it is closed, no more changes can be made into a
delivery/departure.

Interface Trip Stop

Updates the quantity in inventory .

It runs two interface programs
Inventory interface
Order management interface program

Invoicing

The Invoicing workflow activity transfers shipped item information including quantities,
selling prices, payment terms, and transaction dates to Oracle Receivables, which
processes invoices and accounts for revenue.
Processing Constraints

 Processing constraints define whether change is allowed to an order after certain

activities have been completed as well as level of responsibility required to make
change.
 Processing constraints evaluate for an entity you try to cancel ,delete, insert, split or
update.
 Navigation:
Set up : Rules : Security : Processing Constraints

Defaulting Rules

Defaulting rules enable field values on forms to populate automatically.

You can setup your defaulting rules which allow you to default columns in the same way as
for orders entered on-line. You can pass the column value Null to Order Import if
you want the defaulting rules to populate the column. However, if the column is defined
as Not Null or Mandatory column and the defaulting rules fail to default the column,
Navigation:- Setup: Rules: Security :Defaulting
1. Create an order manually.
2. Create an order using Order Import.
Prerequisites 1. Transaction Types have been defined.
2. Customers exist in the Customer Master,
including Contacts, Addresses, and Location
Business Purposes.
3. Price Lists have been defined.
4. Items have been defined in the Item Master and
assigned to Price Lists.
5. Tax Codes and Tax Categories have been
defined.
6. Invoicing and Accounting Rules have been
defined.
7. Freight Carriers have been defined.
8. Shipping Warehouses have been set-up.
9. Payment types have been set-Up
Order Information Tab

The Order Information Tab consists of the following tabs:

 Main
 Other

Main Tab:
Customer: Enter Customer Name
Customer Number: Alternatively, enter Customer Number and
the Customer Name will default in
Order Type: Select the appropriate Order Type.
Order Type determines the order workflow, accounting
rules, and other characteristics of the order.
Order Date: The Current Date will default in as the Order Date.
Order Number: Oracle will assign the Sales Order Number as soon as
the Sales Orders Order Information is saved. <System Generated>
Ship-To ship-to address information will default or you can
choose from the list
Select Currency
Select a currency for the order
Bill-To Select the Bill-To customer information or it will default
from the customer
Entry Status: The initial entry status for a sales order is entered.
After booking the order, the status will change to Booked.
Others Tab:

Payment Terms: Payment Terms will default or you may override the default
value in this field
Warehouse: Select a Warehouse (inventory organization) from which
order line (s) will be shipped.4444
 Line Items Tab

The Sales Orders Line Items Tab consists of the following tabs:
 Main

 Pricing

 Shipping

 Addresses

 Returns

 Services – Related to CRM applications

 Other – Related to Project information

Main Tab:
Ordered Item: Enter the Ordered Item for this order line Quantity:
UOM: The Unit of Measure will default in form the Item definition
Unit Selling Price: The Selling price of the item.
Request date The request date will default the system date
Schedule Ship Date: Select the Schedule Ship Date from the calendar
Line Type: Select the Line Type from the list

Pricing Tab:
Price List: Select a Price List for the order. The value for Price List
will default from Sales Orders header Information tab previously selected
Unit Selling Price:
The Extended Price will automatically default when the Unit Selling
Price is entered.

Shipping Tab:
Warehouse: This is the default Shipping Warehouse for all sales orders line item
information
Receiving Org: Enter the Receiving Inventory Organization. Only applicable for
Return Material Authorizations (RMAs).
Request Date: The Current Date defaults in as the Request Date. Change it to the
date the Customer would like the Product Shipped.
Promise Date: The Current Date defaults in as the Promise Date. Change it to the
date the Customer has been promised for shipment date.
Order Booking:
When we book the order, we are just confirming and freezing our order.

Booking the Order:

The final step in the Sales Order Entry process is to Book the order.
This signifies that the Order Entry process is complete and that the order is eligible
for the next stage in the line flow for this order, as defined by its Transaction Type.
Select the Book Order button
The Entry Status of the Order will change to Booked < Note the Sales Order
Number>

Check Points:

Check the status of the order

Note the order Number

Status of the order is booked at the header level and awaiting for shipping in
the Line level.

Check for Tax category and Taxes on the localized screen

Order Entry Can be done by 3 ways

1. Manual Entry
2. Order Import
3. Copy an Order

Status:

Order Header: Entered

Order Line: Entered
Shipping Transaction form: NA

Table Level :

OE_ORDER_HEADERS_ALL
Flow_Status_code – Entered
OE_ORDER_LINES_ALL
Flow_Status_code – Entered
After Order Booking:
Order Header: Booked
Order Line : Awating Shipping
Shipping Transaction form: Ready to release

Table Level :
OE_ORDER_HEADERS_ALL
Flow_Status_code – Booked
OE_ORDER_LINES_ALL
Flow_Status_code – Awaiting Shipping
WSH_DELIVERY_DETAILS
Released_Status – R ( means – Ready to release)

Delivery Detail id will be created

Delivery id will not be created
 Order Management enables you to define transaction types that
help you categorize your orders and returns.
For your different order types you can assign a

 Default price list

 Defaulting rules
 Order lines
 Return lines
 Line types
 Workflow assignments
 Payment terms
 Freight terms.

Prerequisites
• Define organizations.
• Define document sequences.
• Define defaulting rules.
• Define price lists.
• Define credit check rules
• Define currencies and currency types.
• Set up your cost of goods sold account flex field segments
Price Lists:
Pricelists are essential to ordering products because each item
entered on an order must have a price. Each price list contains basic list
information like price list name, effective dates, currency, pricing controls,
rounding factor, shipping defaults such as freight terms and freight carrier,
and one or more pricing lines, pricing attributes.

STEPS FOR PRICING AN ORDER

Create a price list (one time)

This includes creation of price list headers and lines (which associates
items to a particular price)
Create pricing formulas (optional)
Create price list modifiers/qualifiers (optional)
Create an order.
Attach the price list to that order.
You can define the following types of prices on price lists:

■ Unit price: A fixed price.

■ Percent Price: A price (only for a service item) which is a percent of
the price of another item.
■ Formula: Multiple pricing entities and constant values related by
arithmetic operators. For example, you define the price
of an item to be a percentage price of another price list line.
Defining Pricelist

Navigation
[R] OM Super User  [M] Pricing  [F] Price List Setup
Main Tab
Name (Pricelist Name)
Currency (Pricelist Currency)
Round To (Precision of List Price of Items)
- The value returned depends on the value that
was set for the profile option QP: Unit Price
Precision Type
Standard: The rounding factor defaults to the currency's precision value.
Extended: The rounding factor defaults to the currency's extended precision value.
The pricing engine rounds the base price and all discount amounts before
using them in calculations.
Active checkbox (Activates the Pricelist)
Global checkbox
- Global box is selected when the Pricing Security
Control profile option is set to ON.
- This means that the price list can be used by
all operating units for pricing transactions.
- If cleared, the price list's use is restricted to
the operating unit of the user creating the
price list.
Mobile Download checkbox
- If you are using an Oracle Mobile application
and want to download specific price lists onto a
mobile device such as a laptop computer.
- The default value is No.
List Lines Tab
 Product Context (Default value: Item)
 Product Attribute (Select product attribute for the Item as Item Number or Item
Category or All Items)
 Product Value (Value for the Product Attribute selected)
 UOM (Unit Of Measure)
- Defaults from the item master of the validation
organization and it can changed to any valid unit
of measure for that item.
- The primary pricing unit of measure for the item
can be selected by enabling the Primary UOM
checkbox.
 Line Types
- Price Header: To set up price breaks for the item
- Price List Line: To enter a base list price for the
item.
 If Price Break Header is been selected as Line Type, select the Price Type has the
options:
- Point: The pricing engine charges each unit of
volume at the price of the within which the total
falls.
- Range: The pricing engine charges each unit of
volume at the price of the within which it falls.
List Lines Tab
 Application Method:
- Unit Price: Defines the price for inventory items
and item categories
- Block Price: This method is enabled only if Price
Header is selected as the Line Type. This will
define the price for the entire set of a block.
 Value: Base list price of the item
- If Price Break Header is selected as the Line
Type, you cannot enter the Value (price) at the
list line level. Instead, click Price Breaks to enter
price ranges.

Secondary Price List tab

 Secondary Pricelist
- If the item you are ordering is not in the primary
price list, the pricing engine looks for the price
on any attached secondary price list.
- There can be more than one Secondary pricelist
specified for a Pricelist.
 Precedence
- If the item is found, the pricing engine uses the
highest precedence secondary price list (the
secondary price list with the lowest value in the
Precedence field).
Price Breaks
Defining Price Breaks
Price breaks or "bracket pricing" can be used to define prices that vary with the quantity
ordered.

Price Breaks Type

 Point Break
Defines prices based on the price bracket in which the total quantity falls.

 Range Break
Defines prices based on the ranges of the defined price breaks. For each range, the
engine calculates a price and sums across all ranges to obtain the list price.

Price Breaks window setup

Price Pricing Pricing Attribute Value Price Application Recurring

Break Context From - To (Rs.) Method Value
1 Volume Item Quantity 1 – 11 50 Unit Price -
2 Volume Item Quantity 12 – 99999 45 Unit Price -

In Price Lists window, Line Type: Price Break Header

Application Method: Unit Price or Block Price
Price Breaks with Unit Pricing
Point Break
If you ordered 16 units then the total quantity falls into the Price 2 bracket
where the unit price is Rs.45. The total price is calculated as follows:
Total price = 16 * Rs.45 each = Rs.72

Range Break
If you ordered 16 units of Item A11111, the unit price from each price
(Price Breaks 1 and 2) is applied as follows:
Price 1: For first 11 units * Rs.50 each (unit price from Price 1) = Rs.550
Price 2: Remaining 5 units * Rs.45 each (unit price from Price 2) = Rs.225
Total price = Rs.550 + Rs.225 = Rs.775
Price Breaks with Block Pricing

Block pricing enables you to apply a lumpsum price rather than a per unit price to a pricing
line. It provides setup flexibility where the UOM of the header is different from the pricing
attributes of each child line. Block pricing also allows pricing setups that price by recurring
values within blocks.

Price Pricing Pricing Value Price Application Recurring

Break Context Attribute From - To (Rs.) Method Value
1 Volume Item Quantity 1 – 1200 100 Block Price 100
2 Volume Item Quantity 1201 – 2000 50 Block Price 20

If you order 1500 units then

• Block Pricing without Recurring Value

Block Price 1: For first 1200 units = Rs.100
Block Price 2: For remaining 500 units = Rs.50
Total price = Rs.100 + Rs.50 = Rs.150

• Block Pricing with Recurring Value

Block Price 1: For first 1200 units = 1200/100 * Rs.100 = Rs.1200
Block Price 2: For remaining 500 units = 500/20 * Rs.50 = Rs.1250
Total price = Rs.1200 + Rs.1250 = Rs.2450
Pricing Attributes
Defining Pricing Attributes
 Pricing Context and Pricing Attribute are selected based on
the Product selected in the List Lines tab.

 Operator: This can have values = or NOT = or BETWEEN

 Value From – To: Value To can have values only when

Operator is selected as BETWEEN

 There can be more than one Pricing Attribute defined for

a List Line and are joined as AND conditions since they
apply to one Price List Line.

Base Tables
• QP_LIST_HEADERS_B
• QP_LIST_LINES
• QP_PRICING_ATTRIBUTES
• QP_RLTD_MODIFIERS
• QP_QUALIFIERS
1. Collect all the tables related to Pricelists
Price List Qualifiers/Modifiers

Price List Qualifiers/Modifiers Modifiers enable you to setup price adjustments (for
example, discounts and surcharges) and freight and special charges (modifier lists)
that the pricing engine applies immediately to pricing requests.

Using modifiers you can:

Setup a modifier list with multiple modifier lines
Create eligibility rules for modifiers by assigning list and line level qualifiers
Qualifiers help the pricing engine to determine who is eligible for the modifier.
Modifiers enable you to setup price adjustments (for example, discounts and
surcharges) and freight and special charges that the pricing engine applies
immediately to pricing requests or accrues for later disbursement. Using modifiers,
you can:
■ Setup a modifier list with multiple modifier lines
■ Create eligibility rules for modifiers by assigning list and line level qualifiers

Modifier List Types

Using modifier lists, you can create groupings of price adjustments, and freight
and special charges that you offer and report together to meet various business
needs. At the list level, you define criteria that is common to all of the line level
modifiers.
You can use the following list types:
Deal
Discount List
Freight and Special charge List
Promotion
Surcharge List
Modifier Type:
Select the modifier type as Deal, Discount List,Freight and Special charge List
Promotion or Surcharge List
List Number :
Give the list number
Active:
The pricing engine evaluates the modifier only if the Active box is selected.
Global:

Modifier list can be used by all operating units for pricing transactions

Automatic
Pricing engine automatically applies the modifier. If cleared, then the modifier is
considered a "manual" modifier and the adjustment must be applied manually rather than
automatically.

Currency:
The pricing engine applies modifiers to sales orders of the same
currency.
Qualifiers
You can create qualifiers to determine the eligibility of who can receive
modifiers at the list level. If an order is not eligible for a modifier list, it is not
eligible for that list's line level modifiers even if the lines have qualifiers for
which the order is eligible.

Modifier list level qualifiers help the pricing engine to determine who is
eligible for the modifier lines. If an order is not eligible for a modifier list, it is
not eligible for that list’s line level modifiers even if the lines have qualifiers
for which the order is
eligible.

There are 2 types of Qualifiers

• Header Level Qualifiers
• Line Level Qualifiers

Line Level Qualifiers are having more precedence,

Define Pricelist and assign Items belongs to the Pricelist ,set the Unit price
for the Item so that selling price is calculated while creating order.
Set Qualifiers for the pricelist in the pricelist window the Context can be
customer or order type. these Context will be used to default the pricelist
when the customer or order type is selected.
Shipping Concepts

• Pick Release
• Pick Confirm / Transaction Move Order
• Ship Confirm
PICK RELEASE

Ideally pick release is the process which is defined in which the items on the sales
order are taken out from inventory.

Normally pick release SRS program runs in background . Once the program get
completed these are the table get affected:

oe_order_lines_all (flow_status_code ‘PICKED’ )

wsh_delivery_details (released_status ‘S’ ‘submitted for release’ )
mtl_txn_request_headers
mtl_txn_request_lines
(move order tables.Here request is generated to move item from saleble to staging
sub inventory)
Mtl_material_transactions_temp (link to above tables through
move_order_header_id/line_id

Navigation:

Shipping  Release sales Orders  Release sales order

Release Sales Orders Concurrently
Objective To Pick Release Sales Orders that are Pick Release eligible Prerequisites
Sales Order should be Booked (order lines must be shippable and the line must
have a Shipping Workflow activity).
Shipping Setups completed

Order Tab:
Based On rule: Select the Grouping rule the reaming details will default in Order,
Shipping and Inventory tab
Order Number: Select the Order Number. Values for the Order Type and Customer
fields of this form default to those for the order number you enter here
Ship Set: Select the Ship Set to be released. The Order Number must be
selected first.
Shipping Tab:
Auto creates Deliveries : Select Yes in this box to automatically create deliveries for
delivery lines once they are released
Release Sequence Rule Select Rule to specify the order in which the picking lines are
released.

Inventory tab:
Warehouse
Sub inventory
Pick Slip Grouping Rule
Default Stage Sub inventory
Select the Concurrent button.
Select the Warehouse
Select the Sub inventory
Select Rule. To determine how released picking lines
are grouped onto pick slips.
Select the Default Stage Sub inventory
PICK CONFIRM

Items are transferred from saleble to staging Subinventory.

mtl_material_transactions
mtl_transaction_accounts
wsh_delivery_details (released_status ‘Y’ ‘Released’ )
wsh_delivery_assignments
Shipping Confirmation

Prerequisites Sales Order should be Booked (order lines must be shippable and the line must
have a Shipping Workflow activity).
Shipping Setups completed

Prerequisites 1. Sales Order should be Booked (order lines must be shippable and
the line must have a Shipping Workflow activity).
2. Shipping Setups completed

Shipping Transaction window

The Shipping Transaction window provides a centralized workbench that
consolidates three major shipping functions: planning, pick releasing, and ship
confirming.

Navigation: Shipping  Shipping  Transactions

Ship Confirm

Here ship confirm interface program runs in background .

Data removed from wsh_new_deliveries

oe_order_lines_all (flow_status_code ‘shipped’)

wsh_delivery_details (released_status ‘C’ ‘Shipped’)
mtl_transaction_interface
mtl_material_transactions(linked through Transaction source header id)
mtl_transaction_accounts
Data deleted from mtl_demand,mtl_reservations
Item deducted from mtl_onhand_quantities
ENTER INVOICE

This is also called Receivables interface, that mean information moved to accounting area
for invoicing details

• Invoicing workflow activity transfers shipped item information to Oracle Receivables.

• ra_interface_lines_all (interface table into which the data is transferred from order
management)
• Then Autoinvoice program imports data from this

• Table which get affected into this stage are recievables base table.

 ra_customer_trx_all (cust_trx_id is primary key to link it to

trx_lines table and trx_number is the invoice number)

 ra_customer_trx_lines_all (line_attribute_1 and

line_attribute_6 are linked to header_id (or order number) and
line_id of the orders)
COMPLETE LINE

In this stage order line leval table get updated with Flow status and open flag .
oe_order_lines_all (flow_status_code ‘shipped’, open_flag “N”)

CLOSE ORDER

This is last step of Order Processing . In this stage only oe_order_lines_all table get updated .

These are the table get affected in this step .

oe_order_lines_all (flow_status_code ‘closed’,open_flag “N”)
These are the typically data flow of a order to cash model for a standard order .
O2C42 - EFSS to WMS Sales Orders with Modifiers and Tax

O2C42 interface - Data exchanges between the EFSS Oracle system and the different
Warehouse Management Systems (WMS) within the local markets.

• Extracting the data from specific tables and fields within the EFSS system
• Creation of standard Extract tables for processing by the local markets
• Transfer and processing of data through e-Gate
• Error handling of rejected data from Oracle

New Tables :

XXEFSS_SALES_ORDERS_OUT - Custom table for holding the Sales Order Information

XXEFSS_MODIFIERS_TAX_OUT - Custom table for holding Modifiers and Tax information
for XXEFSS_SALES_ORDERS_OUT table
XXEFSS_O2C42_ATTACHMENTS_OUT - Custom table for holding the Sales orders header
& the line level short text attachments.
O2C22 Shipment Confirmation From WMS To EFSS

The interface will be required to send details of all inventory movements recorded in the
local WSM system to the EFSS system so as to maintain a synchronized view of inventory
balances across the systems.

The interface will address the following:

• Import of the data into Oracle

• Error handling of rejected data from Oracle

Program Logic :

This program takes all the lines with status “NEW” of the staging table. With each line, it
will be made some lookups to retrieve some information that will be used by the APIs.
After, it compares the delivered quantity with the quantity or the deliver order. If it’s
different, the line is split. After the movement order is created and confirmed.

• If the WMS reference is given, the name of the delivery must be changed.

• If there is any change in the delivery detail, it will be changed, and at the end, the
shipment is confirmed.