Search Results apfv_ap_invoice_distributions

Overview

APFV_AP_INVOICE_DISTRIBUTIONS is a business (reporting) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is registered under the Oracle Payables (AP) product family and carries a VALID status in the ETRM object registry. The view exposes invoice distribution data from Oracle Payables in a denormalized, business-friendly form intended for reporting, inquiry, and integration consumption rather than for transactional processing. In EBS, views prefixed with "APFV" follow the Oracle Application Object Library convention for "AP Financial Views," which are typically flexfield-enabled, read-only presentations of base transaction tables. The presence of the WITH READ ONLY clause in the view definition confirms that it is non-updatable and cannot be used as a DML target.

The view is defined primarily to provide a streamlined reporting layer over the AP_INVOICE_DISTRIBUTIONS table while resolving the distribution accounting flexfield through a join to GL_CODE_COMBINATIONS. This allows report developers and integrators to retrieve distribution amounts together with the corresponding general ledger code combination without writing the join themselves.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over two referenced base objects, both presented as synonyms in the APPS schema:

• AP_INVOICE_DISTRIBUTIONS (SYNONYM) — The core Payables distribution table. In the view text it appears with the alias DIST and supplies the overwhelming majority of the projected columns.
• GL_CODE_COMBINATIONS (SYNONYM) — The General Ledger chart of accounts combinations table, aliased GCC3, joined on DIST.DIST_CODE_COMBINATION_ID = GCC3.CODE_COMBINATION_ID. Its columns are surfaced through the key flexfield descriptor _KF:SQLGL:GL#:GCC3 and the accounting flexfield segment mapping.

Because the view returns a key flexfield-derived column, it relies on Oracle's flexfield view mechanism to translate the concatenated code combination identifier into segment values at runtime. The definition is read-only and does not support inserts, updates, or deletes.

Key Columns

The view projects a broad set of distribution attributes. Notable columns, as documented in the view text and ETRM column list, include:

• INVOICE_ID, INVOICE_LINE_NUMBER, DISTRIBUTION_LINE_NUMBER — Keys linking the distribution to its parent invoice and line.
• AMOUNT and BASE_AMOUNT — The entered and functional-currency distribution amounts.
• POSTED_AMOUNT, POSTED_BASE_AMOUNT, POSTED_FLAG — Indicators of accounting posting status.
• ACCOUNTING_DATE — The GL accounting date carried on the distribution.
• DIST_CODE_COMBINATION_ID — The accounting flexfield combination identifier, resolved through GL_CODE_COMBINATIONS.
• LINE_TYPE_LOOKUP_CODE — Distribution line type, with a lookup descriptor against AP_LOOKUP_CODES:INVOICE DISTRIBUTION TYPE.
• MATCH_STATUS_FLAG, DIST_MATCH_TYPE, FINAL_MATCH_FLAG — PO matching and final-match indicators enriched by AP_LOOKUP_CODES.
• PRICE_VARIANCE_AMT, QUANTITY_VARIANCE, BASE_QUANTITY_VARIANCE, CRNCY_EXCHANGE_RATE_VARIANCE — Variance amounts for price, quantity, and exchange rate.
• PO_DISTRIBUTION_ID, PO_MATCHED_DIST_QTY_BILLED, PO_MATCHED_DIST_UNIT_ — Purchase order matching attributes.
• AWT_FLAG, AWT_GROSS_AMOUNT — Withholding tax indicators.
• TYPE_1099, INCOME_TAX_REGION — Tax reporting attributes.
• PA_ADDITION_FLAG, ASSETS_ADDITION_FLAG, ASSETS_TRACKING_FLAG — Flags for Projects and Assets integration.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard audit columns.

Several columns are defined as TO_NUMBER(NULL) placeholders, and one is explicitly annotated as "OBSOLETE", reflecting Oracle's practice of retaining column positions for compatibility while retiring the underlying attribute.

Common Use Cases and Queries

Because the view presents distribution data with the accounting flexfield already resolved, it is frequently used in Payables reporting, reconciliation extracts, and downstream integrations that need posted distribution amounts by account. Typical scenarios include matching distribution amounts to GL postings, extracting PO-matched distributions, and building withholding tax or 1099 reporting extracts.

A representative query retrieving posted distributions for a given invoice is:

• SELECT invoice_id, distribution_line_number, line_type_lookup_code, amount, base_amount, posted_flag, accounting_date, dist_code_combination_id FROM apps.apfv_ap_invoice_distributions WHERE invoice_id = :p_invoice_id ORDER BY distribution_line_number;

For reconciliation against the general ledger, consumers typically join the resolved code combination identifier to GL_CODE_COMBINATIONS or to GL balances, and filter on POSTED_FLAG = 'Y' and a specific ACCOUNTING_DATE range. Because the view is read-only and flexfield-backed, it is well suited to ad hoc reporting and BI Publisher data templates, but it should not be used for transactional updates, which must be performed against the base AP_INVOICE_DISTRIBUTIONS table through the standard Payables APIs.