Oracle R12 O2C Steps

6/10/22, 11:58 AM order to cash process in oracle apps
erpSchools
Order to Cash Process
order to cash process steps can be listed as below
Enter the Sales Order

Book the Sales Order
Launch Pick Release
Ship Confirm
Create Invoice
Create the Receipts either manually or using Auto Lockbox ( In this article we
will concentrate on Manual creation)
Transfer to General Ledger
Journal Import
Posting
Watch o2c Video: Order to Cash cycle Video
Query: Order to Cash query
Let’s get into the details of each step mentioned above.
Enter the Sales Order:
https://erpschools.com/erps/articles/order-to-cash-cycle 1/22
Navigation: Order Management Super User Operations (USA)>Orders

Returns >Sales Orders
Enter the Customer details (Ship to and Bill to address), Order type.
Click on Lines Tab. Enter the Item to be ordered and the quantity
required.
Line is scheduled automatically when the Line Item is saved.
Scheduling/unscheduling can be done manually by selecting

Schedule/Un schedule from the Actions Menu.
You can check if the item to be ordered is available in the Inventory by

clicking on Availability Button.
Save the work.
Underlying Tables affected:
In Oracle, Order information is maintained at the header and line level.
The header information is stored in OE_ORDER_HEADERS_ALL and the

line information in OE_ORDER_LINES_ALL when the order is entered. The
column called FLOW_STATUS_CODE is available in both the headers and
lines tables which tell us the status of the order at each stage.
At this stage, the FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL is

‘Entered’
Book the Sales Order:
Book the Order by clicking on the Book Order button.
Now that the Order is BOOKED, the status on the header is change
accordingly.
Underlying tables affected:
At this stage:
The FLOW_STATUS_CODE in the table OE_ORDER_HEADERS_ALL would

be
‘BOOKED’
The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will be
‘AWAITING_SHIPPING’.
Record(s) will be created in the table WSH_DELIVERY_DETAILS with
RELEASED_STATUS=’R’ (Ready to Release)
Also Record(s) will be inserted into WSH_DELIVERY_ASSIGNMENTS.
At the same time DEMAND INTERFACE PROGRAM runs in the

background and inserts
into MTL_DEMAND
Launch Pick Release:
Navigation: Shipping > Release Sales Order > Release Sales Orders.
Key in Based on Rule and Order Number
In the Shipping Tab key in the below:
Auto Create Delivery: Yes
Auto Pick Confirm: Yes
Auto Pack Delivery: Yes
In the Inventory Tab:
Auto Allocate: Yes
Enter the Warehouse
Click on Execute Now Button.
On successful completion, the below message would pop up as shown

below.
Pick Release process in turn will kick off several other requests like Pick
Slip Report,
Shipping Exception Report and Auto Pack Report
Underlying Tables affected:
If Autocreate Delivery is set to ‘Yes’ then a new record is created in the

table WSH_NEW_DELIVERIES.
DELIVERY_ID is populated in the table WSH_DELIVERY_ASSIGNMENTS.
The RELEASED_STATUS in WSH_DELIVERY_DETAILS would be now set to

‘Y’ (Pick Confirmed) if Auto Pick Confirm is set to Yes otherwise
RELEASED_STATUS is ‘S’ (Release to Warehouse).
Pick Confirm the Order:
IF Auto Pick Confirm in the above step is set to NO, then the following
should be done.
Navigation: Inventory Super User > Move Order> Transact Move Order
In the HEADER tab, enter the BATCH NUMBER (from the above step) of
the order. Click FIND. Click on VIEW/UPDATE Allocation, then Click
TRANSACT button. Then Transact button will be deactivated then just
close it and go to next step.
Ship Confirm the Order:
Navigation: Order Management Super User>Shipping >Transactions.
Query with the Order Number.
Click On Delivery Tab
Click on Ship Confirm.
The Status in Shipping Transaction screen will now be closed.
This will kick off concurrent programs like.INTERFACE TRIP Stop,

Commercial Invoice, Packing Slip Report, Bill of Lading
Underlying tables affected:
RELEASED_STATUS in WSH_DELIVERY_DETAILS would be ‘C’ (Ship

Confirmed)
FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL would be “BOOKED”
FLOW_STATUS_CODE in OE_ORDER_LINES_ALL would be “SHIPPED”
Create Invoice:
Run workflow background Process.
Navigation: Order Management >view >Requests
Workflow Background Process inserts the records

RA_INTERFACE_LINES_ALL with
INTERFACE_LINE_CONTEXT = ‘ORDER ENTRY’
INTERFACE_LINE_ATTRIBUTE1= Order_number
INTERFACE_LINE_ATTRIBUTE3= Delivery_id
and spawns Auto invoice Master Program and Auto invoice import
program which creates Invoice for that particular Order.
The Invoice created can be seen using the Receivables responsibility
Navigation: Receivables Super User> Transactions> Transactions
Query with the Order Number as Reference.
Underlying tables:
RA_CUSTOMER_TRX_ALL will have the Invoice header information. The

column INTERFACE_HEADER_ATTRIBUTE1 will have the Order Number.
RA_CUSTOMER_TRX_LINES_ALL will have the Invoice lines information.

The column INTERFACE_LINE_ATTRIBUTE1 will have the Order Number.
Create receipt:
Navigation: Receivables> Receipts> Receipts
Enter the information.
Click on Apply Button to apply it to the Invoice.
Underlying tables:
AR_CASH_RECEIPTS_ALL
Transfer to General Ledger:
To transfer the Receivables accounting information to general ledger, run

General Ledger Transfer Program.
Navigation: Receivables> View Requests
Parameters:
Give in the Start date and Post through date to specify the date range of the
transactions to be transferred.
Specify the GL Posted Date, defaults to SYSDATE.
Post in summary: This controls how Receivables creates journal entries for your
transactions in the interface table. If you select ‘No’, then the General Ledger
Interface program creates at least one journal entry in the interface table for
each transaction in your posting submission. If you select ‘Yes’, then the
program creates one journal entry for each general ledger account.
If the Parameter Run Journal Import is set to ‘Yes’, the journal import program
is kicked off automatically which transfers journal entries from the interface
table to General Ledger, otherwise follow the topic Journal Import to import
the journals to General Ledger manually.
Underlying tables:
This transfers data about your adjustments, chargeback, credit memos,

commitments, debit memos, invoices, and receipts to the GL_INTERFACE
table.
Journal Import:
To transfer the data from General Ledger Interface table to General

Ledger, run the Journal Import program from Oracle General Ledger.
Navigation: General Ledger > Journal> Import> Run
Parameters:
Select the appropriate Source.

Enter one of the following Selection Criteria:
No Group ID: To import all data for that source that has no group ID.
Use this option if you specified a NULL group ID for this source.
All Group IDs: To import all data for that source that has a group ID.
Use this option to import multiple journal batches for the same source
with varying group IDs.
Specific Group ID: To import data for a specific source/group ID

combination. Choose a specific group ID from the List of Values for the
Specific Value field.
If you do not specify a Group ID, General Ledger imports all data from
the specified journal entry source, where the Group_ID is null.
Define the Journal Import Run Options (optional)
Choose Post Errors to Suspense if you have suspense posting enabled

for your set of books to post the difference resulting from any
unbalanced journals to your suspense account.
Choose Create Summary Journals to have journal import create the

following:
• one journal line for all transactions that share the same account,
period, and currency and that has a debit balance
• one journal line for all transactions that share the same account,
period, and currency and that has a credit balance.
Enter a Date Range to have General Ledger import only journals with
accounting dates in that range. If you do not specify a date range, General
Ledger imports all journals data.
Choose whether to Import Descriptive Flexfields, and whether to import them
with validation.
Click on Import button.

Underlying tables:
GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES
Posting:
We have to Post journal batches that we have imported previously to

update the account balances in General Ledger.
Navigation: General Ledger> Journals > Enter
Query for the unposted journals for a specific period as shown below.
From the list of unposted journals displayed, select one journal at a time
and click on Post button to post the journal.
If you know the batch name to be posted you can directly post using the
Post window
Navigation: General Ledger> Journals> Post
Underlying tables:
GL_BALANCES.
April 14, 2011 Prudhvi Articles, Process Flows
erpSchools Contact us at info@erpschools.com or +1 669.696.5296

Oracle R12 O2C Steps

Uploaded by

Copyright:

Available Formats

Oracle R12 O2C Steps

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle R12 O2C Steps

Uploaded by

Copyright:

Available Formats

6/10/22, 11:58 AM order to cash process in oracle apps

Order to Cash Process

order to cash process steps can be listed as below

Enter the Sales Order

Watch o2c Video: Order to Cash cycle Video

Query: Order to Cash query

Let’s get into the details of each step mentioned above.

Enter the Sales Order:

Navigation: Order Management Super User Operations (USA)>Orders

Line is scheduled automatically when the Line Item is saved.

Scheduling/unscheduling can be done manually by selecting

You can check if the item to be ordered is available in the Inventory by

Save the work.

Underlying Tables affected:

In Oracle, Order information is maintained at the header and line level.

The header information is stored in OE_ORDER_HEADERS_ALL and the

At this stage, the FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL is

Book the Sales Order:

Book the Order by clicking on the Book Order button.

Underlying tables affected:

The FLOW_STATUS_CODE in the table OE_ORDER_HEADERS_ALL would

The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will be

Record(s) will be created in the table WSH_DELIVERY_DETAILS with

RELEASED_STATUS=’R’ (Ready to Release)

Also Record(s) will be inserted into WSH_DELIVERY_ASSIGNMENTS.

At the same time DEMAND INTERFACE PROGRAM runs in the

Launch Pick Release:

Key in Based on Rule and Order Number

In the Shipping Tab key in the below:

Auto Create Delivery: Yes

Auto Pick Confirm: Yes

Auto Pack Delivery: Yes

In the Inventory Tab:

Auto Allocate: Yes

Enter the Warehouse

Click on Execute Now Button.

On successful completion, the below message would pop up as shown

Shipping Exception Report and Auto Pack Report

Underlying Tables affected:

If Autocreate Delivery is set to ‘Yes’ then a new record is created in the

DELIVERY_ID is populated in the table WSH_DELIVERY_ASSIGNMENTS.

The RELEASED_STATUS in WSH_DELIVERY_DETAILS would be now set to

Pick Confirm the Order:

Ship Confirm the Order:

Navigation: Order Management Super User>Shipping >Transactions.

Query with the Order Number.

Click On Delivery Tab

Click on Ship Confirm.

The Status in Shipping Transaction screen will now be closed.

This will kick off concurrent programs like.INTERFACE TRIP Stop,

Underlying tables affected:

RELEASED_STATUS in WSH_DELIVERY_DETAILS would be ‘C’ (Ship

FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL would be “BOOKED”

FLOW_STATUS_CODE in OE_ORDER_LINES_ALL would be “SHIPPED”

Run workflow background Process.

Navigation: Order Management >view >Requests

Workflow Background Process inserts the records

INTERFACE_LINE_CONTEXT = ‘ORDER ENTRY’

The Invoice created can be seen using the Receivables responsibility

Navigation: Receivables Super User> Transactions> Transactions