Results for “department_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The APPS.CSTBV_MFG_DEPARTMENT_OVERHEADS view is a reporting and integration object within the Oracle E-Business Suite Bills of Material (BOM) product family. Its documentation carries the description "Retrofitted," indicating that it was introduced or re-pointed in later releases (12.1.1 and 12.2.2) as a backward-compatibility layer that preserves a stable presentation of department-level overhead definitions even as the underlying cost and routing schemas evolved. The view consolidates cost type, department, overhead resource, and rate information into a single denormalized structure, joining identification columns to their human-readable names. It is declared WITH READ ONLY, confirming that it is intended exclusively for query, reporting, and integration consumption rather than as a maintenance interface. In practice it serves consultants and reporting tools that need to resolve numeric foreign keys such as DEPARTMENT_ID, COST_TYPE_ID, and OVERHEAD_ID into meaningful business labels like DEPARTMENT_NAME, COST_TYPE_NAME, and OVERHEAD_NAME, especially in environments where a user search term such as "department_name" is used to locate the column that carries the department label.

Underlying Base Objects

The view is defined over four base objects, each referenced through APPS synonyms:

• BOM_DEPARTMENTS — the source of department identification and the DEPARTMENT_CODE column aliased as DEPARTMENT_NAME; joined on DEPARTMENT_ID.
• BOM_RESOURCES — the source of overhead resource identification and RESOURCE_CODE aliased as OVERHEAD_NAME; joined on RESOURCE_ID = OVERHEAD_ID.
• CST_COST_TYPES — the source of the cost type label; joined on COST_TYPE_ID.
• CST_DEPARTMENT_OVERHEADS — the driving table that stores the department-overhead assignment and rate; supplies COST_TYPE_ID, DEPARTMENT_ID, OVERHEAD_ID, RATE_OR_AMOUNT, ORGANIZATION_ID, ACTIVITY_ID, and WHO audit columns.

Because the joins are inner joins, only department-overhead combinations that resolve to valid cost types, departments, and resources are returned. The WHERE clause references a reserved token ('_SEC:CDO.ORGANIZATION_ID') that enforces multi-org security filtering on the operating unit/organization context, restricting returned rows to the organization accessible to the session.

Key Columns

• COST_TYPE_ID / COST_TYPE_NAME — identifier and name of the cost type under which the overhead is defined (for example Frozen or Average cost types).
• DEPARTMENT_ID / DEPARTMENT_NAME — the department key and its code label; this is the column pair most frequently sought when searching for "department_name."
• OVERHEAD_ID / OVERHEAD_NAME — the overhead resource key and its resource code label.
• RATE_OR_AMOUNT — the overhead cost rate or fixed amount applied, depending on basis.
• UNIT_BASIS — the descriptor token that maps to a manufacturing lookup value (CST_BASIS), defining the basis on which the overhead is applied.
• ORGANIZATION_ID / ACTIVITY_ID — the organization context and optional activity identifier.
• CREATED_DATE, CREATED_BY, UPDATED_DATE, UPDATED_BY — standard WHO audit columns.

Common Use Cases and Queries

Typical scenarios include overhead rate audits by department and cost type, reconciliation of departmental overhead assignments, and reporting extracts for manufacturing cost analysis.

Sample: overheads by department for an organization

SELECT department_name, cost_type_name, overhead_name, rate_or_amount
FROM apps.cstbv_mfg_department_overheads
WHERE organization_id = :org_id
ORDER BY department_name, overhead_name;

Sample: locate department overheads by name pattern

SELECT department_name, cost_type_name, overhead_name, rate_or_amount
FROM apps.cstbv_mfg_department_overheads
WHERE department_name LIKE 'ASSEMBLY%';

Because the view is read only, it should be used for SELECT-based reporting only; inserts, updates, and deletes must target the base table CST_DEPARTMENT_OVERHEADS through the standard BOM and Costing maintenance forms and APIs.