Friday, November 8, 2019

Payables Open Interface Import program in Oracle apps r12



ACCOUNTS PAYABLE:
In order to create invoice automatically in oracle Accounts Payables, import data in following interface tables:

Interface Tables:
1. AP_INVOICES_INTERFACE
2. AP_INVOICE_LINES_INTERFACE

AP_INVOICES_INTERFACE:
Data in the AP_INVOICES_INTERFACE table used in conjunction with AP_INVOICE_LINES_INTERFACE table to create Payables Invoice, Invoice lines, Distributions and Schedule payments. Data in this table can be viewed and edited using ‘Open Interface Invoices’ window. The Payables Open Interface program validates each record in this interface table selected for import, and if the record contains valid data then the program creates a Payables Invoice.

AP_INVOICE_LINES_INTERFACE:
AP_INVOICE_LINES_INTERFACE stores information used to create one or more invoice distributions. Note that one row in this table may create, during the import process, more than one invoice distribution.

Interface Error table:
1. AP_INTERFACE_REJECTIONS
2. AP_INTERFACE_CONTROLS

AP_INTERFACE_REJECTIONS stores information about invoice data from the AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE tables which could not be processed by Payables Open Interface Import.

SELECT * FROM AP_INTERFACE_REJECTIONS
----------------------------------------------
After successfully importing data in above interface tables, call the following concurrent program in order to create invoices in AP:

Request:
Payables Open Interface Import
This request after successfully run creates invoices in oracle payables.
Payables Open Interface Import commits in cycles of 100. For example, if there is an error that stops the import program when it is validating the 350th invoice record, the system will have already committed the first 300 invoices.

Base Tables:
AP_INVOICES_ALL
AP_INVOICE_DISTRIBUTIONS_ALL
AP_PAYMENT_SCHEDULES_ALL

Invoice Validation:

Once the Invoices have been created invoice validation needs to be done so that invoices can be processed further to make payments and transfer to GL. For this we need to either manually validate individual invoices from the Invoice Screen or run the Invoice Validation Program. This activity will validate the invoices and allow further processing, In case invoices fail in validation then the invoices will be put on hold. The user can see the hold details by pressing the "HOLDS" button on the invoice screen. At the backend hold details will be stored in the table: AP_INVOICE_HOLDS
----------------------------------------------
**Payables Open Interface Outbound Advice -> standalone report to be manually submitted by the user.
This program creates notification data about e-Commerce invoices processed during Payables Open Interface Import.

**Payables Open Interface Purge -> standalone report to be manually submitted by the user.
This report is used to purge records from the Payables Open Interface tables (AP_INVOICES_INTERFACE and AP_INVOICE_LINES_INTERFACE).
We strongly recommend to purge only invoices successfully imported setting the 'Purge All' parameter to No. Setting this parameter to Yes purges all records in the Payables Open Interface tables.





Previous Post
Next Post

Overall 5+ Years Hands-on Experience in RICE COMPONENTS i.e. Reports, Interfaces, Conversions and Enhancements of screens/reports (using Oracle FORMS/Oracle REPORT/ XML Publisher) for standard and customize Oracle Applications. Write, debug, database packages, procedures/Function/Triggers in RDBMS using Oracle Technologies i.e. (SQL, PL/SQL) as per business requirement with SQL/PLSQL Tuning, Code Review, Testing, Training and providing Technical support to Clients.

0 comments: