Your on-site personnel or Oracle consultant must first write a custom feeder program that transfers transaction data from your original system into Receivables AutoInvoice Interface tables. 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.

Writing a Feeder Program

The type of environment from which you want to transfer your data determines the type of feeder program you need to write. For example, you can use SQL*Loader, SQL*Report, PL/SQL, or Pro*C to write a feeder program to transfer transaction data from a non-Oracle system. Or, you can write a conversion program to transfer historical data from your previous accounting system.

Selecting an Import Utility

SQL*Loader and SQL*Report are powerful and easy-to-use tools that should be able to accommodate all of your import needs. However, depending on the complexity of your import program, you may also want to use Oracle's Pro* language products such as Pro*C, Pro*Cobol, and Pro*Fortran to write the program.

Understanding the Interface Tables

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, see: AutoInvoice Table and Column Descriptions.