Results for “cst_item_overhead_defaults_v”

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

Overview

CST_ITEM_OVERHEAD_DEFAULTS_V is a seeded APPS-schema view in Oracle E-Business Suite, classified under the BOM (Bills of Material) product family. Its documented purpose is to resolve all foreign key references for the base table CST_ITEM_OVERHEAD_DEFAULTS, exposing decoded and human-readable values in place of raw identifier columns. The view carries a VALID status in both Release 12.1.1 and 12.2.2 and is defined with the Oracle ETRM designation "Oracle Proprietary, Confidential."

Item overhead defaults define how overhead costs are applied to items during cost rollup and manufacturing cost calculation. Because the base table stores numeric foreign keys and lookup codes, operational reporting directly against it produces cryptic output. This view bridges that gap by joining the base table to resources, activities, and lookup tables so that report writers, cost accountants, and integration developers can retrieve meaningful descriptions without writing the join logic themselves. Its presence in the BOM module reflects the shared cost-rollup infrastructure between Bills of Material and Cost Management.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through SYNONYM or VIEW pointers in the APPS schema:

• CST_ITEM_OVERHEAD_DEFAULTS — the driving table, aliased CIOD in the view text. It supplies organization, category, activity, basis type, units, usage rate or amount, and the DFF attribute columns.
• BOM_RESOURCES — joined with an outer join on RESOURCE_ID = MATERIAL_OVERHEAD_ID, providing RESOURCE_ID and RESOURCE_CODE. The outer join allows overhead rows without a linked material overhead resource to remain visible.
• CST_ACTIVITIES — outer-joined on ACTIVITY_ID, supplying the ACTIVITY (name) column.
• MFG_LOOKUPS — accessed twice as LU1 and LU2 to decode ITEM_TYPE against lookup type CST_MTL_ITEM_TYPE and BASIS_TYPE against lookup type CST_BASIS. Both joins are outer joins, so unmapped codes do not eliminate rows.

Key Columns

The view exposes the ROWID of the base row plus the full column set of the driving table with decoded replacements. Key columns include:

• ORGANIZATION_ID — the inventory organization to which the overhead default applies.
• CATEGORY_SET_ID / CATEGORY_ID — the item category set and category used to scope the default.
• RESOURCE_ID / MATERIAL_OVERHEAD_CODE — the resolved material overhead resource; MATERIAL_OVERHEAD_CODE corresponds to BOM_RESOURCES.RESOURCE_CODE.
• ITEM_TYPE / ITEM_TYPE_NAME — the item type code and its decoded meaning from CST_MTL_ITEM_TYPE.
• ACTIVITY_ID / ACTIVITY — the cost activity and its name from CST_ACTIVITIES.
• BASIS_TYPE / BASIS_TYPE_NAME — the overhead basis code and its decoded meaning from CST_BASIS.
• ITEM_UNITS, ACTIVITY_UNITS, USAGE_RATE_OR_AMOUNT — the quantity and rate basis used in the overhead calculation.
• ATTRIBUTE_CATEGORY, ACTIVITY_CONTEXT, ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.
• Audit and concurrent columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include auditing overhead default setup by organization, validating category-level overhead assignments before a cost rollup, and feeding external cost engines with decoded resource and activity names. Because the view already decodes item type and basis type, it is the preferred source over the base table for ad hoc queries and custom reports.

List all overhead defaults for a given organization with decoded values:

• SELECT organization_id, category_set_id, category_id, material_overhead_code, item_type_name, activity, basis_type_name, usage_rate_or_amount FROM apps.cst_item_overhead_defaults_v WHERE organization_id = :org_id ORDER BY category_id, material_overhead_code;

Locate defaults referencing a specific overhead resource:

• SELECT category_id, item_type_name, basis_type_name, usage_rate_or_amount FROM apps.cst_item_overhead_defaults_v WHERE material_overhead_code = :resource_code;

Audit recently maintained rows for concurrent program tracking:

• SELECT row_id, organization_id, last_update_date, last_updated_by, request_id, program_id FROM apps.cst_item_overhead_defaults_v WHERE last_update_date > SYSDATE - 30;

Coupling these queries with CST_ITEM_COSTS or the cost rollup concurrent programs supports reconciliation of applied overhead against configured defaults.