Oracle EBS Payables Data Flow and Data Model
In Oracle Payables, before an AP transaction can be generated, a supplier must exist in the system. When suppliers are created, records are created in AP_SUPPLIERS and AP_SUPPLIER_SITES. Invoices are saved in AP_INVOICES (invoice header records) and AP_INVOICE_LINES (invoice lines records).
Payments generate records in AP_INVOICE_PAYMENTS and AP_PAYMENTS_SCHEDULE. These tables will have 1 record for an invoice if the invoice is paid using a single payment, but will have multiple records for an invoice if the invoice is paid in installments or with more than one payment.
When an invoice is approved and when it is paid, accounting transactions are generated. These transactions make their way to the GL_INTERFACE table via Payables Transfer to GL process. In addition to interfacing with GL, Payables also interfaces with many other Oracle modules, such as, Purchasing, Assets, Projects, Inventory, and others (but will not be covered in this post).
Invoices can be entered into Oracle Payables from external systems via the AP_INVOICE_INTERFACE and AP_INVOICES_LINES_INTERFACE tables. When the Payables Open Interface Import program is run, the records are brought into the regular header and lines tables (AP_INVOICE and AP_INVOICE_LINES).
When payments are made, the information about the payment is recorded in AP_CHECKS.
These are some of the sources for the star-schemas (dimension and fact tables) used in Oracle Business Intelligence Applications (OBIA) Financials module, and in particular, the Payables dashboard and analyses.
No comments:
Post a Comment