Search Results jai_fa_mass_additions

Overview

The AP_INVOICE_DISTRIBUTIONS_ALL table is a core transactional entity within Oracle E-Business Suite Payables (AP) module, versions 12.1.1 and 12.2.2. It stores detailed accounting and financial information for each distribution line of an invoice. Every invoice entered into the system must have at least one distribution line to define the expense or liability account, amount, and associated project or tax details. This table is central to the procure-to-pay cycle, enabling multi-organization accounting, tax calculation, matching to purchase orders or receipts, and the eventual transfer of accounting entries to the General Ledger. Its multi-org design, indicated by the "_ALL" suffix, allows it to hold data for multiple operating units, with access controlled by the MOAC (Multi-Org Access Control) security profile.

Key Information Stored

The table's primary key is a composite of INVOICE_ID and DISTRIBUTION_LINE_NUMBER, uniquely identifying each distribution. Critical columns include accounting attributes like CODE_COMBINATION_ID (the charged account), AMOUNT, and BASE_AMOUNT. For matched invoices, it links to procurement data via PO_DISTRIBUTION_ID and RCV_TRANSACTION_ID. Tax-related data is held in TAX_CODE_ID and INCOME_TAX_REGION. For project accounting, it integrates with Oracle Projects via PROJECT_ID, TASK_ID, and EXPENDITURE_TYPE. The table also tracks accounting event status through ACCOUNTING_EVENT_ID and holds variance accounts for rate (RATE_VAR_CODE_COMBINATION_ID) and price (PRICE_VAR_CODE_COMBINATION_ID) differences. Columns for Withholding Tax (AWT), such as AWT_GROUP_ID and AWT_INVOICE_ID, are also present.

Common Use Cases and Queries

This table is fundamental for invoice inquiry, audit reporting, account reconciliation, and custom accounting integrations. Common analytical queries include summarizing invoice amounts by general ledger account, identifying distributions linked to specific purchase orders or receipts, and analyzing tax or project-related expenditures. A typical pattern for joining to invoice headers and accounting flexfields is:

• SELECT aid.invoice_id, aid.distribution_line_number, aid.amount, aid.code_combination_id, gcc.segment1, ai.invoice_num FROM ap_invoice_distributions_all aid JOIN ap_invoices_all ai ON aid.invoice_id = ai.invoice_id JOIN gl_code_combinations gcc ON aid.code_combination_id = gcc.code_combination_id WHERE ai.invoice_date > SYSDATE - 30;

For audit purposes, queries often join to PO_DISTRIBUTIONS_ALL and RCV_TRANSACTIONS to verify three-way matching. Reporting on unaccounted or unposted distributions is another critical use case, achieved by filtering on the ACCOUNTING_EVENT_ID and related posting control columns.

Related Objects

As indicated by its foreign keys, AP_INVOICE_DISTRIBUTIONS_ALL has extensive relationships with other EBS entities. Its primary parent is AP_INVOICES_ALL, linked via INVOICE_ID, PARENT_INVOICE_ID, and AWT_INVOICE_ID. It references GL_CODE_COMBINATIONS for the main and variance accounting flexfields. Integration with purchasing and receiving is through PO_DISTRIBUTIONS_ALL (implied) and RCV_TRANSACTIONS. For tax, it links to AP_TAX_CODES_ALL and AP_INCOME_TAX_REGIONS. Project accounting links to PA_PROJECTS_ALL, PA_TASKS, and PA_EXPENDITURE_TYPES. The AP_ACCOUNTING_EVENTS_ALL table tracks the accounting lifecycle for each distribution. Key APIs, such as AP_INVOICES_PKG and AP_ACCOUNTING_EVENTS_PKG, often manipulate or validate data in this table.