Search Results ap_invoices_all




Overview
Explore in AI Chat

Overview

CSTBV_RCV_ACQ_COST_DETAILS is an APPS-owned read-only view in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, residing within the Bills of Material (BOM) product family, specifically the Costing component. It presents the detail-level acquisition costs captured during receiving, enriched with descriptive attributes drawn from purchasing, receiving, and Payables. This view is the primary analytical access point for users who need to reconcile receipt-based acquisition costs with the accounts payable invoice distributions that ultimately clear those costs.

Because the view is defined WITH READ ONLY, it is intended exclusively for query and reporting purposes, not for DML. Its principal role is to expose the linkage between the CST_RCV_ACQ_COST_DETAILS transactional base and AP_INVOICE_DISTRIBUTIONS_ALL, allowing cost accountants and Payables analysts to trace a receipt's cost element to the specific invoice distribution line that matched it. This is particularly valuable during period-end accrual reconciliation, purchase price variance (PPV) analysis, and the investigation of unmatched or partially matched receipts.

Underlying Base Objects

The view is built over eight documented base objects, joined through both inner and outer joins. The driving table is CST_RCV_ACQ_COST_DETAILS (CRACD), which supplies the header and detail primary keys and the transactional amounts. Its parent, CST_RCV_ACQ_COSTS (CRAC), is joined on HEADER_ID to retrieve the cost group, cost type, period, and receiving transaction identifiers. Three reference tables — CST_PAC_PERIODS, CST_COST_GROUPS, and CST_COST_TYPES — are joined on their respective identifier columns to resolve recognizable names for the period, cost group, and cost type. RCV_TRANSACTIONS supplies the transaction type and transaction date.

The remaining objects are all in the Payables domain. AP_INVOICE_DISTRIBUTIONS_ALL is referenced three separate times as aliases AIDA, AIDA1, and AIDA2, each carrying an outer join (+) to the corresponding CRACD foreign keys PARENT_DISTRIBUTION_ID, INVOICE_DISTRIBUTION_ID, and PARENT_INVOICE_DIST_ID. Each of these is in turn outer-joined to AP_INVOICES_ALL (aliases AIA, AIA1, AIA2) to resolve invoice numbers. The use of the (+) operator ensures that receipt cost detail rows are retained even when no matching invoice distribution exists, which is essential for identifying unreconciled receipts. All base objects are referenced through APPS synonyms.

Key Columns

Common Use Cases and Queries

A frequent requirement is reconciling receipt acquisition costs to their matching invoice distributions. The following query returns unsettled receipt costs where no invoice distribution has been matched:

SELECT header_id, detail_id, amount, quantity, price,
       receiving_txn_type, invoice_num
FROM   apps.cstbv_rcv_acq_cost_details
WHERE  invoice_distribution_id IS NULL
ORDER BY receiving_txn_date;

Analysts also use the view to compare the immediate parent invoice against the current invoice for a receipt, supporting variance and accrual analysis:

SELECT pac_period_name, cost_group_name, cost_type_name,
       immedi_parent_invo, invoice_num, amount
FROM   apps.cstbv_rcv_acq_cost_details
WHERE  receiving_txn_date BETWEEN :start_date AND :end_date;

Because the view exposes both the Payables distribution identifiers and the receiving transaction detail, it is well suited to integration extracts and custom reconciliation dashboards. One caution applies: the view joins AP_INVOICE_DISTRIBUTIONS_ALL three times, so queries should filter on the appropriate alias-derived column to avoid row multiplication. The READ ONLY constraint also means any corrective action must be performed against the underlying base tables, not this view.