Search Results amount_variance

Overview

PA_TRANSFER_AP_INVOICES_VIEW is a Projects (PA) module database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to present project-related invoice distributions originating in Oracle Payables (AP). The view consolidates invoice distribution attributes, purchase order accrual context, and prepayment exchange-rate derivation into a single queryable structure. It is primarily used by the Payables-to-Projects transfer and integration processes, which identify AP invoice distributions that are chargeable to projects and convey them into Project Costing for expenditure processing and subsequently into Project Billing.

Because the view is defined over AP invoice distribution data rather than directly over a table, it serves as a stable reporting and integration interface. The AMOUNT_VARIANCE column, which the user searched for, is inherited directly from AP_INVOICE_DISTRIBUTIONS and represents the variance between an invoice distribution amount and its matched purchase order or receipt reference amount, making it relevant to match variance analysis and reconciliation reporting.

Underlying Base Objects

The documented base objects referenced by the view are AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS, AP_SELF_ASSESSED_TAX_DIST, AP_SYSTEM_PARAMETERS, AP_UTILITIES_PKG, MTL_SYSTEM_ITEMS, PA_NL_INSTALLED, PO_DISTRIBUTIONS, and PO_LINES_ALL. All the AP, MTL, and PO objects are accessed through synonyms, while AP_UTILITIES_PKG is a PL/SQL package.

• AP_INVOICE_DISTRIBUTIONS is the driving table; every column of interest, including AMOUNT_VARIANCE, BASE_AMOUNT_VARIANCE, INVOICE_ID, INVOICE_DISTRIBUTION_ID, and the various ATTRIBUTE and referencing columns, is sourced from it.
• AP_INVOICES_ALL supplies invoice-level context, particularly the EXCHANGE_RATE and EXCHANGE_RATE_TYPE used in the prepayment DECODE logic.
• AP_SYSTEM_PARAMETERS provides BASE_CURRENCY_CODE, and AP_UTILITIES_PKG provides the AP_ROUND_CURRENCY rounding function used to compute base amounts for prepayment lines.
• PO_DISTRIBUTIONS and PO_LINES_ALL supply PO accrual details; the ACCRUE_ON_RECEIPT_FLAG drives a DECODE that determines whether the PO distribution's CODE_COMBINATION_ID or the invoice distribution's DIST_CODE_COMBINATION_ID is exposed.
• MTL_SYSTEM_ITEMS, AP_SELF_ASSESSED_TAX_DIST, and PA_NL_INSTALLED appear in the documented object list as supporting references.

Key Columns

• INVOICE_ID and INVOICE_DISTRIBUTION_ID — unique identifiers linking back to the AP invoice and its distribution line.
• AMOUNT_VARIANCE and BASE_AMOUNT_VARIANCE — the entered and base-currency variance amounts between matched amounts on the invoice distribution.
• CORRECTED_INVOICE_DIST_ID, CHARGE_APPLICABLE_TO_DIST_ID, RELATED_ID, PARENT_REVERSAL_ID, and CANCELLATION_FLAG — correction, reversal, and cancellation lineage for the distribution.
• AMOUNT, BASE_AMOUNT, EXCHANGE_RATE, and EXCHANGE_RATE_TYPE — distribution amounts and currency conversion, with prepayment lines derived through subqueries against AP_INVOICES_ALL.
• ACCOUNTING_DATE, PERIOD_NAME, SET_OF_BOOKS_ID, and POSTED_FLAG — accounting period and posting status used to determine transfer eligibility.
• PO_DISTRIBUTION_ID and the DECODE on ACCRUE_ON_RECEIPT_FLAG — purchase order matching and accrual accounting determination.
• QUANTITY_INVOICED, UNIT_PRICE, MATCH_STATUS_FLAG, and LINE_TYPE_LOOKUP_CODE — quantity, price, matching status, and line classification such as PREPAY.

Common Use Cases and Queries

The view is typically queried to identify project-related AP invoice distributions eligible for transfer to Projects, or to analyze match variances. A representative query filters on a specific invoice and examines the variance columns:

• SELECT invoice_id, invoice_distribution_id, amount, amount_variance, base_amount_variance FROM apps.pa_transfer_ap_invoices_view WHERE invoice_id = :invoice_id;
• SELECT invoice_distribution_id, period_name, posted_flag, amount FROM apps.pa_transfer_ap_invoices_view WHERE set_of_books_id = :sob AND period_name = :period;

Because AMOUNT_VARIANCE is exposed directly, users can aggregate variance by period, supplier, or PO distribution to reconcile invoice-to-PO matching discrepancies prior to project cost transfer.