Search Results dist_line_type_code

Overview

The APPS.APFV_AP_INVOICE_DISTRIBUTIONS view is an Oracle E-Business Suite Business Intelligence System (BIS) view owned by the APPS schema. It is registered in FND Design Data under the product identifier SQLAP (Payables), and its status is VALID in both EBS 12.1.1 and 12.2.2. The view exposes detailed information about individual charges on Payables invoice distribution lines, presenting the accounting, matching, variance, withholding tax, and posting attributes associated with each distribution.

Rather than requiring report developers and integrators to resolve a large number of lookup codes and denormalized attributes manually, the view provides a flattened, presentation-oriented projection of invoice distribution data. It is typically consumed by Oracle Business Intelligence (OBIEE) and other reporting layers, by custom concurrent programs, and by integration interfaces that must extract invoice distribution content for reconciliation, audit, or downstream system feeds. Because it is a BIS view rather than a base table, it is not the target of transactional DML; it is read-only.

Underlying Base Objects

The ETRM metadata documents two referenced base objects for this view:

• AP_INVOICE_DISTRIBUTIONS (accessed through a SYNONYM) — the primary transactional table holding invoice distribution lines, including distribution amounts, quantities, account references, matching attributes, variance amounts, and withholding tax information.
• GL_CODE_COMBINATIONS (accessed through a SYNONYM) — the General Ledger accounting flexfield combinations used to resolve the distribution's charge, variance, and rate variance accounts.

The view is therefore defined predominantly over AP_INVOICE_DISTRIBUTIONS, with joins to GL_CODE_COMBINATIONS to supply accounting flexfield context for account identifiers such as EXPENSE_ACCOUNT_ID, PRICE_VARIANCE_ACCOUNT_ID, and RATE_VARIANCE_ACCOUNT_ID. Additional descriptive columns are generated through Oracle's _LA (lookup attribute) and _KF (key flexfield) mechanisms, which translate stored codes into human-readable descriptions and concatenated account strings.

Key Columns

The view exposes a broad set of distribution-level attributes. Among the most significant are:

• INVOICE_ID, INVOICE_LINE_NUMBER, DISTRIBUTION_LINE_NUMBER — the keys that identify the parent invoice, the invoice line, and the specific distribution line.
• POSTED_TO_GL_AMOUNT and POSTED_TO_GL_FUNCTIONAL_AMOUNT — the entered and functional amounts posted to General Ledger for the distribution. These are central to reconciliation between Payables and GL.
• ACCOUNTING_DATE — the accounting date associated with the distribution; critical for period-based reporting.
• INVOICE_DIST_AMT and INVOICE_DIST_FUNC_AMT — the entered and functional distribution amounts.
• POSTED_FLAG — indicates whether the distribution has been transferred to GL.
• EXPENSE_ACCOUNT_ID and the derived _KF:ACCOUNT_NUM:EXPENSE:_CO — the charge account identifier and its concatenated flexfield representation.
• PRICE_VARIANCE_AMT, PRICE_VARIANCE_FUNCTIONAL_AMT, PRICE_VARIANCE_ACCOUNT_ID, QUANTITY_VARIANCE, FUNCTIONAL_QTY_VARIANCE_AMT, CRNCY_EXCHANGE_RATE_VARIANCE, and RATE_VARIANCE_ACCOUNT_ID — matching and exchange-rate variance attributes used in purchase order matching analysis.
• DIST_MATCH_TYPE_CODE, DIST_LINE_TYPE_CODE, FINAL_MATCHING_STATUS_CODE and their _LA descriptive counterparts — coded and decoded matching/line-type information.
• STATISTICAL_QUANTITY, PO_MATCHED_DIST_QTY_BILLED, PO_MATCHED_DIST_UNIT_PRICE, PO_DISTRIBUTION_ID — quantities and PO matching references.
• AWT_FLAG and AWT_GROSS_AMOUNT — withholding tax indicators and gross basis amounts.
• PREPAY_AMOUNT_REMAINING, ASSET_RELATED_FLAG, TRANSFERRED_TO_ASSETS_FLAG, PA_TRANSFER_STATUS_FLAG, DIST_LINE_ENCUMBRANCE_STATUS, AMOUNT_INCLUDES_TAX_FLAG, TYPE_1099, INCOME_TAX_REGION, JUSTIFICATION, and INVOICE_DIST_DESCRIPTION — supporting attributes for prepayment tracking, asset and project transfer status, encumbrance status, tax, and descriptive context.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

Common Use Cases and Queries

Because the user searched for the column posted_to_gl_amount, the most frequent usage of this view involves Payables-to-GL reconciliation. Analysts extract distributions that have been posted and compare the posted amounts against GL balances for the same accounting period, or they identify distributions not yet posted. A representative query follows:

• Reconcile posted distributions by accounting period:
  SELECT invoice_id, invoice_line_number, distribution_line_number, accounting_date, posted_to_gl_amount, posted_to_gl_functional_amount, posted_flag, distribution_approval_status FROM apps.apfv_ap_invoice_distributions WHERE accounting_date BETWEEN :start_date AND :end_date AND posted_flag = 'Y';
• Analyze matching variances:
  SELECT invoice_id, distribution_line_number, price_variance_amt, quantity_variance, crncy_exchange_rate_variance, dist_match_type_descr, final_match_status_descr FROM apps.apfv_ap_invoice_distributions WHERE dist_match_type_code IS NOT NULL;
• Audit charge accounts:
  SELECT invoice_id, distribution_line_number, expense_account_id, DIST_LINE_TYPE_DESCR FROM apps.apfv_ap_invoice_distributions WHERE expense_account_id = :account_id;

Because the view decodes lookup codes into _LA description columns and concatenates key flexfield segments, it is well suited for ad hoc reporting and BI extracts. Performance depends on indexes defined on the underlying AP_INVOICE_DISTRIBUTIONS table, and users should always qualify queries by accounting date, invoice, or status filters to avoid full scans of distribution data.