Search Results cst_dept_overheads_interface




Overview
Explore in AI Chat

Overview

CST_DEPT_OVERHEADS_INTERFACE is an open interface table owned by the BOM schema in Oracle E-Business Suite. It functions as the staging area through which external systems, legacy data conversions, or custom programs load departmental overhead rate information into Oracle's costing engine. Rather than writing directly into the base overhead definition tables, source systems populate this interface, and a concurrent program subsequently validates the rows and transfers them into the destination cost tables. In Oracle EBS 12.1.1 and 12.2.2 the physical structure is documented with 44 columns, consistent with a wide, denormalized staging table that carries both code-based and ID-based references for each key entity.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign-key structure is standalone. This is a sensible suggestion for a staging table: it is not itself a hub, link, or satellite, but rather a transient landing zone whose rows carry the natural and surrogate keys that would feed such structures downstream. Its relationship to BOM_DEPARTMENTS and CST_COST_TYPES indicates it acts as an inbound feeder for cost-related reference data rather than a persistent business entity.

Key Information Stored

The table stores overhead rate records pending validation and import. The most significant columns fall into three groups.

No dedicated surrogate primary key is documented for this interface table; the column list identifies DEPARTMENT_ID and COST_TYPE_ID as the prominent foreign-key candidates, while business-key uniqueness is typically enforced through the combination of department, cost type, organization, and overhead during import processing rather than by a declared single-column key.

Common Use Cases and Queries

Typical usage centers on data conversion and bulk rate maintenance. A common scenario is loading overhead rates from a legacy system, then querying the interface to confirm what was staged before the import program runs:

SELECT department_code, cost_type, organization_code,
       overhead, basis_type, rate_or_amount, process_flag, error_flag
FROM   bom.cst_dept_overheads_interface
WHERE  group_id = :p_group_id
ORDER  BY department_code, cost_type;

Error reconciliation is another frequent pattern, surfacing failed rows for correction:

SELECT transaction_id, department_code, overhead,
       error_code, error_explanation
FROM   bom.cst_dept_overheads_interface
WHERE  error_flag = 'Y';

Reporting use cases include auditing pending loads by request, tracking which organizations have staged rates, and validating that required basis types are populated before submission. The PROCESS_FLAG, REQUEST_ID, and GROUP_ID columns are the primary filters for these queries.

Related Objects

The following objects are most significant in relation to this interface table:

  • BOM_DEPARTMENTS — joined on DEPARTMENT_ID; supplies valid department reference data.
  • CST_COST_TYPES — joined on COST_TYPE_ID; supplies the costing method definitions.
  • CST_DEPT_OVERHEADS — the base destination table into which validated interface rows are transferred.
  • CST_ACTIVITIES — referenced by ACTIVITY_ID for activity-based overheads.
  • MTL_PARAMETERS / ORG_ORGANIZATION_DEFINITIONS — resolve ORGANIZATION_ID to an inventory organization.
  • Overhead import concurrent programs and their request records, driven by REQUEST_ID and PROCESS_FLAG.

Together these objects complete the flow from staged interface data through validation into live departmental overhead definitions.