Search Results cst_rcv_acq_cost_details




Overview
Explore in AI Chat

Overview

The table CST_RCV_ACQ_COST_DETAILS is a core transactional data store within the Oracle E-Business Suite (EBS) Bills of Material (BOM) module. Its primary function is to record detailed, period-specific acquisition cost information, segmented by organization and cost group, for received inventory. This table is critical for maintaining granular cost accounting and inventory valuation, enabling the system to track the precise cost composition of received items over time. It operates as a child table, holding the detailed line-level cost breakdowns that roll up to a summary cost header.

Key Information Stored

The table's structure is designed to capture the essential dimensions of acquisition cost. The primary key, DETAIL_ID, uniquely identifies each cost detail record. The HEADER_ID column is a foreign key linking the detail to its parent summary record in the CST_RCV_ACQ_COSTS table. A critical operational foreign key, PO_LINE_LOCATION_ID, links directly to the PO_LINES_ALL table, tying the cost detail to the specific purchase order shipment line that generated the receipt. While the provided metadata does not list all columns, typical data stored includes the accounting period, cost group identifier, organization identifier, the actual cost amount (often broken into base and burden components), and the associated item and transaction identifiers.

Common Use Cases and Queries

This table is central to cost analysis and reconciliation processes. A primary use case is investigating the detailed cost history of received inventory for a specific purchase order line or within a given period. Financial analysts query this table to validate period-end inventory valuations and to understand cost variances. For troubleshooting, one might join to the receiving transaction tables to reconcile physical receipts with their accounted costs. A typical reporting query would join CST_RCV_ACQ_COST_DETAILS to its parent header and the purchase order lines to analyze cost per unit by item and supplier over time.

SELECT crd.po_line_location_id,
       crd.period_id,
       crd.cost_group_id,
       crd.organization_id,
       crd.acquisition_cost
  FROM bom.cst_rcv_acq_cost_details crd,
       bom.cst_rcv_acq_costs        crc
 WHERE crd.header_id = crc.header_id
   AND crc.rcv_transaction_id = :p_transaction_id;

Related Objects

The table maintains defined foreign key relationships with other key EBS entities, as documented in the metadata. These relationships are fundamental for data integrity and application logic.

  • CST_RCV_ACQ_COSTS: This is the direct parent table. The relationship is defined by the foreign key column CST_RCV_ACQ_COST_DETAILS.HEADER_ID referencing the primary key of CST_RCV_ACQ_COSTS. Multiple detail records roll up to a single header.
  • PO_LINES_ALL: This relationship connects the acquisition cost detail to the procurement module. The foreign key column CST_RCV_ACQ_COST_DETAILS.PO_LINE_LOCATION_ID references the purchase order line location, ensuring the cost is tied to the specific procurement agreement.

In practice, this table is also closely related to core inventory tables such as MTL_MATERIAL_TRANSACTIONS and RCV_TRANSACTIONS, though these are not listed as formal foreign keys in the provided excerpt.