Search Results rollup_id




Overview
Explore in AI Chat

Overview

The CST_SC_ROLLUP_HISTORY table is a core data repository within the Oracle E-Business Suite (EBS) Bills of Material (BOM) module. It serves as the historical audit and tracking mechanism for Supply Chain Rollup processes. A rollup is a critical costing operation that aggregates and calculates the total cost of an item by summing its component costs through all levels of its bill of material. This table records a permanent entry for each execution of such a rollup, providing a traceable history essential for cost analysis, troubleshooting, and audit compliance. Its role is to anchor the lineage of cost calculations, enabling users to understand when a rollup was performed and to correlate it with the resulting cost data.

Key Information Stored

The primary data element stored in this table is the ROLLUP_ID, which acts as the unique identifier for a specific rollup transaction. As defined by the provided metadata, the ROLLUP_ID column constitutes the sole primary key for the table, enforced by the constraints CST_SC_ROLLUP_HISTORY_PK and CST_SC_ROLLUP_HISTORY_U1. While the explicit column list is not detailed in the excerpt, typical columns in such a history table would include timestamps for the rollup execution, the initiating user or concurrent request ID, parameters used for the rollup (such as cost type, effective date, and item range), and a status indicator. The ROLLUP_ID from this table is the key used to join to detailed rollup transaction data in related child tables.

Common Use Cases and Queries

The primary use case is auditing and reporting on cost rollup activity. Analysts query this table to determine the sequence and timing of rollups, identify the most recent rollup for a given cost type, or investigate periods of cost variance. A fundamental query retrieves the history for analysis:

  • SELECT rollup_id, creation_date, created_by, request_id FROM bom.cst_sc_rollup_history WHERE TRUNC(creation_date) = :p_date ORDER BY creation_date DESC;

Another critical pattern involves joining to detailed rollup output tables to analyze the cost impact of a specific rollup event. The ROLLUP_ID is the essential join key in all such analyses. Support personnel also use this table to diagnose failed or incomplete rollup processes by examining entries with anomalous statuses or missing related detail records.

Related Objects

The central relationship for this table is defined by its primary key, ROLLUP_ID. This identifier is a foreign key in numerous child tables that store the granular results of the rollup calculation. While the specific related tables are not listed in the provided metadata, based on the Oracle EBS costing schema, the ROLLUP_ID from CST_SC_ROLLUP_HISTORY would be referenced by tables such as CST_ITEM_COSTS, CST_ITEM_COST_DETAILS, or dedicated rollup summary tables. These dependent tables use the ROLLUP_ID to associate each calculated cost with the specific historical rollup transaction that generated or updated it, ensuring full data lineage from the rollup execution to the final cost figures.