Loading

Monday, May 17, 2010

PAYABLES OPEN INTERFACE IMPORT BASICS (R12)

Different Sources that can load data into Open invoice import interface tables
  1. Quick Invoices window
  2. Oracle e-Commerce Gateway
  3. Credit Card transaction data
  4. Property Manager
  5. The Oracle Assets Export Lease Payments to Payables process
  6. Oracle XML Gateway
  7. SQL*Loader OR BPEL Interfaces can load invoice information from Legacy Systems
  8.  Invoices that your suppliers entered and submitted online via Oracle iSupplier Portal
Interface Tables:
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE
Base Tables:
                AP_INVOICES_ALL
                AP_INVOICE_LINES_ALL
                AP_INVOICE_DISTRIBUTIONS_ALL
                                     (&)
                Payment Tables
Basic Process:
                The Payables Open Interface program validates each record you select for import, and if the record contains valid data, then the program creates a Payables invoice with distributions and scheduled payments based on the invoice header and line information in the record.
Records in the AP_INVOICE_LINES_INTERFACE table create one or more invoice distributions. Note that one row may create more than one distribution. For example, if you enter a Tax line in this table and prorate it across three Item lines, during Open Interface Import the system will create three Tax invoice distributions based on the single Tax line in this table.


My Other related Posts :-






1 Responses to “PAYABLES OPEN INTERFACE IMPORT BASICS (R12)”

Anonymous said...
July 14, 2010 at 2:45 PM

We need to import supplier invoices that are project related. It looks like the project number and task number fields are not available on the interface tables, but the project_id and task_id are available. However, the suppliers would not know the project_id or task_id.
What is the best way of populating the open invoice interface table with project-related invoices?


Post a Comment

Disclaimer

The ideas, thoughts and concepts expressed here are my own. They, in no way reflect those of my employer or any other organization/client that I am associated. The articles presented doesn't imply to any particular organization or client and are meant only for knowledge Sharing purpose. The articles can't be reproduced or copied without the Owner's knowledge or permission.