Search Results cst_resource_overheads_u1

Overview

CST_RESOURCE_OVERHEADS is a transactional configuration table owned by the BOM schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the resource overhead definitions that govern how overhead costs are applied to resources during cost processing. When the Cost Manager invokes the appropriate cost worker — selected according to whether the organization uses average or standard costing — the rows in this table determine the resource overhead that should be applied to a transaction.

The functional rule embedded in this design is that overhead is earned on resources only when two conditions are met: an overhead must be associated with the resource being transacted, and a rate must be defined for that resource in the department where the transaction occurs. The table therefore acts as the association mechanism linking an overhead subelement to a resource, scoped by cost type. It resides in the APPS_TS_TX_DATA tablespace and is registered in FND Design Data as BOM.CST_RESOURCE_OVERHEADS. Its Data Vault classification, mined heuristically from the foreign key structure, suggests a link (association) table rather than a hub or satellite — it exists to resolve many-to-many relationships between resources, overheads, and cost types, carrying only auditing and descriptive flexfield attributes of its own.

Key Information Stored

The documented table contains 29 columns. The most significant are the three key columns plus the standard auditing and flexfield groups.

• RESOURCE_ID — Resource identifier and subelement. Part of the primary key and the unique index. Foreign key to BOM_RESOURCES.
• COST_TYPE_ID — Cost type identifier. Part of the primary key; foreign key to CST_COST_TYPES. Scopes overhead associations to a specific costing method or cost type.
• OVERHEAD_ID — Overhead subelement identifier. Part of the primary key; also a foreign key referencing BOM_RESOURCES, distinguishing overhead subelements from operational resources.
• ORGANIZATION_ID — Organization identifier, providing the organizational context for the overhead association.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Who columns recording audit history.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent Who columns identifying the concurrent program that last touched the row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield structure and segment columns (VARCHAR2 150 for the segments) enabling client-specific extensions.

The surrogate primary key is CST_RESOURCE_OVERHEADS_PK on (RESOURCE_ID, COST_TYPE_ID, OVERHEAD_ID). A unique index, CST_RESOURCE_OVERHEADS_U1 — the object the user searched for — enforces the same three-column business key in the APPS_TS_TX_IDX tablespace. A non-unique index, CST_RESOURCE_OVERHEADS_N1, covers (OVERHEAD_ID, COST_TYPE_ID) to support reverse lookups.

Common Use Cases and Queries

Typical scenarios include auditing which overheads are attached to a resource, validating that every overhead-bearing resource has a defined rate, and diagnosing missing overhead absorption during cost rollups. A representative query joining to the resource and cost type definitions:

• SELECT cro.RESOURCE_ID, cro.OVERHEAD_ID, cro.COST_TYPE_ID, cro.ORGANIZATION_ID FROM BOM.CST_RESOURCE_OVERHEADS cro WHERE cro.COST_TYPE_ID = :cost_type_id;
• Verify uniqueness and completeness: SELECT RESOURCE_ID, COST_TYPE_ID, OVERHEAD_ID FROM BOM.CST_RESOURCE_OVERHEADS GROUP BY RESOURCE_ID, COST_TYPE_ID, OVERHEAD_ID HAVING COUNT(*) > 1;
• Reverse lookup by overhead using the CST_RESOURCE_OVERHEADS_N1 pattern on OVERHEAD_ID and COST_TYPE_ID.

Reporting use cases focus on overhead-to-resource coverage matrices and cost type comparisons, particularly when standard and average costing coexist in the same organization set.

Related Objects

• BOM.BOM_RESOURCES — Referenced twice, via RESOURCE_ID and OVERHEAD_ID, resolving the operational resource and the overhead subelement.
• BOM.CST_COST_TYPES — Referenced via COST_TYPE_ID, defining the costing method context.
• BOM.CST_RESOURCE_OVERHEADS_U1 / _N1 / _PK — The unique, non-unique, and primary key index objects governing access paths.
• Cost Manager and cost worker programs — The concurrent processes (identified by REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID) that read this table to apply resource overhead during cost processing.