Search 800 + Posts

Nov 18, 2010

Data flow Between Oracle Order Management and Oracle Receivables

This and Post are about data flow between Oracle order Management and Oracle Receivable.

This post is very focus on the Invoices in AR from the Order Management and not about the invoices in AR from any other source.
Oracle Order Management is Workflow driven and almost all the workflow in Order management has Invoicing Activity, and while executing the code in the Invoicing activity, OM dump the data in RA_INTERFACE_LINES_ALL and other related Interface tables, and eventually when we run the Auto Invoice it created Invoices in AR.

As I have stated almost all workflow in the Order Management has Invoicing activity , though some exceptions like Ship Only workflow ,these workflow don’t have Invoicing activity.

Invoice Interface activity in Oracle Order Management workflow collects order, return, freight charges, discounts and sales credits information from Oracle Order Management tables, and transfer the information to Oracle Receivables and creates
  1.  Invoices
  2.  Credit Memo
  3.  Debit Memo

 Interface tables that Oracle Order management Populated in Receivables

  1.  RA_INTERFACE_LINES_ALL
  2.  RA_INTERFACE_SALESCREDITS_ALL
  3.  RA_INTERFACE_ERRORS_ALL 
Column Mapping from Oracle Order Management and Oracle Receivables

Interface_Line_Context              values from profile option OM: Source Code

Interface_Line_Attribute1          Order Number

Interface_Line_Attribute2          Transaction Type

Interface_Line_Attribute3          Delivery Name (if Required) , for Non Shippable Line it is 0

Interface_Line_Attribute4          waybill

Interface_Line_Attribute5

Interface_Line_Attribute6          Order Line ID

Interface_Line_Attribute7

Interface_Line_Attribute8           Bill of Lading

Interface_Line_Attribute9          Customer Item Num (If Required)


 Cases When Invoice/Credit Memo/Debit Memo Not Created

  1.  Invoice Enabled item property is set to NO or Invoicable item property is set to NO.
  2.  Line is part of an internal order.
  3.  Line is a service line and the servicable_product_flag for parent is set to NO.
  4.  Line is entered using Included Item
  5.  Referenced returns with CONFIG/INCLUDED item type code.
Types of Dataflow from Oracle Order management transfer to Oracle Receivables

 Header Level Interface – In this case data from Oracle Order management transfer to Oracle Receivables only when all the lines of Order are Closed. In such scenario there will not be any Invoicing data transfer from OM to AR at order Line level. Basic purpose of this Interface is to create only 1 Invoice for all the sales Order lines.

Line Level Interface – in this case data from Oracle Order management transfer to Oracle Receivables as soon as the Invoicing activity at the Order line level is executed. Basic purpose of this Interface is to created only 1 Invoice for all I order lines, unless some Grouping rules has defined.


 Delivery Based Invoice Interface – in this case All lines in a Delivery are shipped together, so customers would like one Invoice per Delivery. So data from Oracle Order management transfer to Oracle Receivableswill transfer only when all the lines associated with the delivery shipped.

Grouping Rules

Grouping Rules - Grouping Rules decide which lines from the interface table in appear in one invoice

Need help with EBS Forms/Reports/Workflow/Interface? Contact Bizinsight Cosulting Inc at 
Eamil us : inquiry@bizinsightinc.com
https://www.bizinsightinc.com/