Skip to main content

Oracle Apps AR R12 Interface Tables and Information

RECEIVABLE INTERFACE TABLES


Transactions

 RA_INTERFACE_LINES_ALL

This table acts as an intermediate storage of data between your external sytem, oracle subledgers and oracle receivables. You must enter all mandatory columns and columns required as per the transaction in this table (using a custom feeder program) alongwith the required oracle setups, so that Autoinvoice Master Program (AMP) can validate the information without any errors. Once data is validated, Autoinvoice Import Program (AIP) triggered by AMP imports data for various receivable batch sources (One AIP for each batch is trigerred) and creates oracle receivable transactions. Depending on the transaction you would create, populate the below transaction flexfields in the columns of this table: 
  • Line Transaction Flexfield - Use when creating invoice lines. 
  1. interface_line_context
  2. interface_line_attribute1 to interface_line_attribute15 ( Use any as per requirement ).
  • Reference Transaction Flexfield - Use to link credit memo to lines.
  1. reference_line_context
  2. reference_line_attribute1 to reference_line_attribute15 ( Use any as per requirement ).
  • Link-To Transaction Flexfield - Use to create link between lines and tax , freights , charges.
  1. link_to_line_context
  2. link_to_line_attribute1 to link_to_line_attribute15 ( Use any as per requirement ).
  • Invoice Transaction Flexfield - Use to link invoice lines to invoice header information.
  1. header_attribute_category
  2. header_attribute1 to header_attribute15 ( Use any as per requirement ).
RA_INTERFACE_ERRORS_ALL

If Autoinvoice Master Program finds validation issue with the data in ra_interface_lines_all then it would insert the data in ra_interface_errors_all alongwith error message and invalid value. Data in this table is used in Autoinvoice Validation Report. Column link_to_line_id identifies the line in ra_interface_lines all which has the validation issue. If the validation issue is fixed, the Autoinvoice Master Program validates again the data in ra_interface_lines_all and imports data into Receivables base tables for transactions. If purge interface table system option is disabled then you have to manually submit Autoinvoice Purge Program to delete data from ra_interface_lines_all which are imported to receivables. If purge interface table system option is enabled  then Autoinvoice Purge Program runs automatically after AMP.

RA_INTERFACE_DISTRIBUTIONS_ALL

 Use this as an intermediate table to record distributions for transactions. If you use autoaccounting to create distributions, then autoinvoice dos not require you to populate data in this table. If you use accounting and invoicing rules for transactions then populate the percent column in this table. If you do not use accounting and invoicing rules for transactions you may either populate amount or percent column in this table. According to batch source setup as amount or percent enter values in the columns of this table. If amount is populated , percent is auto-populated by autoinvoice. Distribution data in this table can be linked to ra_interface_lines using descriptive flexfields ( interface_line_context and interface_line_attribute1 to interface_line_attribute15). Though distribution for account_class 'REC' is at header level , it can be associated to any transaction line in ra_interface_lines_all. Use segment1 to segment30 or CCID column to denote the Accounting flexfield structure values you would be using for the transaction.

 RA_INTERFACE_SALESCREDITS_ALL


This table is used to assign salescredits to salespersons for transactions. Whether fields in this table needs to be populated is determined by setups Require Sales Person in System Options and Allow Salescredits Parameters in Transaction Sources. If Require Sales Person in System Options is set to Yes then irrespective of Allow Salescredits Parameters in Transaction Sources , columns in this table must be populated. If Allow Salescredits Parameters in Transaction Sources is set to Yes and  Require Sales Person in System Options to No, then you should enter values in columns of this table. If for a Credit memo, either Allow Salescredit Parameter in Transaction Sources is set to Yes or Require Sales Person in System Options or both  is set to yes in the system and information is not passed in this table, then Autoinvoice uses the Salescredits information of the transacction it is crediting . If the transaction does not have salescredit infomation then Autoinvoice creates 100% no sales credit line for this transaction and uses this line to create salescredit lines for the credit memos. Use interface_line_context and interface_line_attribute1 to interface_line_attribute15 to link salescredits to the transactions. Use columns salesrep_number to identify salesperson and sales_credit_amount_split or sales_credit_percent_split to assign a value of salescredit to the salesperson.






Location: India

Comments

Post a Comment

Popular posts from this blog

Prepayments in Oracle Receivables R12

When you determine that a prepayment is required, you record the payment information in your feeder system (eg: OM) , and the information is passed to Oracle Receivables. . When the order is later sent to Receivables for invoicing, AutoInvoice creates an invoice that is marked as prepaid. Setups :   1. In OM:System parameters set 'Allow Multiple Payments' to 'Yes'. 2. Create a Customer Bank Account. 3. Assign the Customer bank Account to Customer Site. 4. Create a Payment Method and assign an internal bank account (Receipt Method in Receipt Class         window). 5. Create a document sequence for the Payment method.  6. Create or Update a Payment term by checking Prepayment checkbox. 7. Create a Prepayment Receivable Activity. Process :  1. Book a Sales Order in OM responsibility.  2. Go to Action in Sales Order header and select Payments.  3. Select Payment Type as Cash , 100% (Percent amount of sales order t...
Post a Comment
Read more

AutoAccounting in Oracle Apps Receivables AR R12

AutoAccounting AutoAccounting is a powerful feature in Oracle Apps Receivables which is used to default the Accounting Flexfield Structure (Chart Of Account Structure) / General Ledger  (GL) accounts for the transactions entered either manually or imported using Autoinvoice. AutoAccounting defaults Accounting Flexfield segments only for transactions (eg:- Invoices, Debit Memo, Credit Memo, Chargeback, Deposit, Guarantee ) and not for receipts. Account for receipts is simply taken from the Bank Accounts defined in receipt class. The below table shows the sources from which a segment in the below accounts can take a value . Now, let us know the use of various accounts and when it is used : Autoinvoice Clearing Account : This account hits when there is a difference between the revenue recognized and Selling Price times the Quantity invoiced. For this account to hit, enabling this feature in transaction batch sources is required. Freight Account : This is...
Post a Comment
Read more