Search Results invoice_base_amount

Overview

The APPS.PAFV_COST_DISTRIBUTIONS view is a business-facing reporting object within the Oracle Projects (PA) module. Its documented purpose is to present information about cost distribution lines, which represent the accounting-level breakdown of expenditure items as they are processed, burdened, accounted, and ultimately transferred to Oracle General Ledger. The view consolidates data from the cost distribution lines table with related project expenditure, AP invoice distribution, vendor, and organization data, producing a denormalized result set suitable for inquiry screens, concurrent program extracts, and custom reports.

Within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, this view is registered in the APPS schema with a status of VALID and is secured through an organization-based predicate referencing PCDL.ORG_ID, consistent with Multi-Org Access Control (MOAC). Users who searched for invoice_base_amount will find that this figure is not exposed as a direct column; rather, it is the base-currency amount of a supplier invoice distribution, represented in the view by APID.BASE_AMOUNT (aliased from AP_INVOICE_DISTRIBUTIONS_ALL), alongside APID.AMOUNT. This makes the view valuable for reconciling Projects cost against the originating payables invoice amounts.

Underlying Base Objects

The view is defined over the following documented referenced objects:

• PA_COST_DISTRIBUTION_LINES_ALL (synonym) — the primary driver table, supplying amount, quantity, burdened cost, transfer status, and currency-related columns.
• PA_EXPENDITURE_ITEMS_ALL (synonym) — joined on EXPENDITURE_ITEM_ID, providing expenditure item context such as vendor, document header, and distribution references.
• AP_INVOICE_DISTRIBUTIONS_ALL (synonym) — the source of the invoice distribution amount and base amount, joined through the expenditure item's document distribution identifier.
• PO_VENDORS (view) — supplies VENDOR_NAME.
• HR_ALL_ORGANIZATION_UNITS and HR_ALL_ORGANIZATION_UNITS_TL (synonyms) — outer-joined on ORG_ID to derive the operating unit name, with the _TL joined at USERENV('LANG').
• PA_CONVERSION_TYPES_V (view) — referenced twice (aliases PCT and PCT1) to resolve the account and project rate type user names.

Joins to the organization and translation tables are outer joins, whereas the linkage between cost distribution lines and expenditure items is an inner equi-join on EXPENDITURE_ITEM_ID, ensuring only lines with a valid parent expenditure item are returned.

Key Columns

• EXPENDITURE_ITEM_ID, LINE_NUM, LINE_NUM_REVERSED — identity and sequencing of the cost distribution line, including reversal reference.
• AMOUNT, QUANTITY, BURDENED_COST — raw cost, distributed quantity, and burdened (total) cost.
• APID.BASE_AMOUNT and APID.AMOUNT — the AP invoice distribution base and entered amounts; the invoice_base_amount sought by users corresponds to BASE_AMOUNT.
• BILLABLE_FLAG, REVERSED_FLAG, LINE_TYPE, TRANSFER_STATUS_CODE — descriptive flags resolved to lookup meanings.
• PA_DATE, GL_DATE, TRANSFERRED_DATE, TRANSFER_REJECTION_REASON — accounting and transfer lifecycle dates and rejection detail.
• VENDOR_NAME, VENDOR_ID, AP_INVOICE_ID, AP_INVOICE_DISTRIBUTION_ID, AP_INVOICE_LINE_NUMBER, DOCUMENT_TYPE — payables linkage for invoice-originated costs.
• DENOM_RAW_COST, DENOM_BURDENED_COST, ACCT_RAW_COST, ACCT_BURDENED_COST, PROJECT_CURRENCY_CODE and associated rate types, dates, and exchange rates — multi-currency cost amounts.
• DR_CODE_COMBINATION_ID, CR_CODE_COMBINATION_ID — debit and credit accounting flexfield combinations.
• ORG_ID, NAME, CREATION_DATE, CREATED_BY, BATCH_NAME — operating unit, audit, and batch information.

Common Use Cases and Queries

Typical scenarios include reconciling project costs to AP invoices, reviewing transfer status to General Ledger, analyzing burdened versus raw cost by vendor, and extracting cost distributions for subledger accounting or audit. A representative query retrieving invoice base amounts is:

• SELECT expenditure_item_id, line_num, amount, base_amount, vendor_name, ap_invoice_id FROM apps.pafv_cost_distributions WHERE org_id = :p_org_id ORDER BY line_num;
• SELECT vendor_name, SUM(base_amount) invoice_base_total FROM apps.pafv_cost_distributions WHERE transfer_status_code = 'P' GROUP BY vendor_name;

Because ORG_ID is enforced by the view predicate, queries are filtered to the organizations the user is authorized to access under MOAC, ensuring data segregation across operating units.