AutoInovoice Process setups & Steps

[adilskhan]

Dear Members,

Can anyone help me on Autoinvoice Process Steps from External file to AR interface Tables. I want to load data from external file (Ex Excel, CSV) to AR interface tables (RA Interface Lines All, RA interface distributions All, RA Interface Salescrdit all) and from interface to AR base tables using Autoinvoice program. My client is using foxpro base program system and after implementing AR they will provide the file data that has to be load into AR Interface Tables.

I dont know how to extract Interface table in Excel and loading data into Interface table (using sql*loader or else).

Please help me if with steps or with any simple and step by step document from the skertch

Best Regards,
Adil

[smishra0oracle]

You can use to import and validate transaction data from other financial systems and create invoices, debit memos, credit memos, and on-account credits in Oracle Receivables. You use a custom feeder program to transfer transaction data from an external system into the AutoInvoice interface tables. AutoInvoice then selects data from the interface tables and creates transactions in Receivables. Receivable rejects transactions with invalid information to ensure the integrity of your data. AutoInvoice can also initiate receipt handling when importing credits against paid invoices. You can run AutoInvoice together with Customer Interface or separately. Your feeder program must convert data from your original system into a standard data format that AutoInvoice can read. AutoInvoice can then convert your imported data into Receivables invoices, credit memos, on-account credits, and debit memos.
Receivables uses the following tables to temporarily store the data you transfer from other systems:
? AR_INTERFACE_CONTS_ALL
? RA_INTERFACE_LINES_ALL
? RA_INTERFACE_SALESCREDITS_ALL
? RA_INTERFACE_DISTRIBUTIONS_ALL
AutoInvoice uses a fifth table, RA_INTERFACE_ERRORS_ALL, to store information about interface data that failed validation. For a detailed description of these tables, AutoInvoice can be divided into three major phases: pre-grouping, grouping, and transfer.
In the pre-grouping phase, AutoInvoice validates all of the line-level data as well as any other data that is not dependent upon successful grouping. Some examples include validating that a transaction type is valid and validating that only one freight account exists for each freight line passed.
In the grouping phase, AutoInvoice groups lines based on the grouping rules and validates header-level data that is dependent on how your lines are grouped. Some examples include validating the overapplication rules specified for your batch source and validating that the general ledger date of an invoice against a commitment is not before the general ledger date of the commitment. If AutoInvoice incorrectly groups transactions, check the grouping rule that you are using, paying particular attention to the mandatory and optional attributes that are included in this rule.
In the transfer phase, AutoInvoice validates information that exists in Receivables tables, such as tax defaulting and AutoAccounting data.
Receivables Tables
AutoInvoice transfers transaction data from the interface tables AR_INTERFACE_ CONTS_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL, RA_INTERFACE_LINES_ALL, and RA_INTERFACE_SALESCREDITS_ALL into the following Receivables tables:
? RA_BATCHES_ALL
? RA_CUSTOMER_TRX _ALL
? RA_CUSTOMER_TRX_LINES _ALL
? RA_CUST_TRX_LINE_GL_DIST_ALL
? RA_CUST_TRX_LINE_SALESREPS_ALL
? AR_PAYMENT_SCHEDULES_ALL
? AR_RECEIVABLE_APPLICATIONS_ALL
? AR_ADJUSTMENTS_ALL