Results for “cst_source_type”

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

Overview

APPS.CST_ITEM_COST_DETAILS_V is a reporting and inquiry view in the Oracle E-Business Suite Cost Management (CST) module. It presents the granular cost rollup detail records stored in the CST_ITEM_COST_DETAILS base table, augmented with descriptive information decoded from reference and lookup tables. The view exposes the elemental composition of a manufactured item's cost by cost element, activity, resource, department, and operation sequence, making it a primary source for cost decomposition reporting, cost element analysis, and integration extracts.

The object is particularly relevant to users investigating the cst_source_type lookup, since the view resolves the ROLLUP_SOURCE_TYPE column against the CST_SOURCE_TYPE lookup type to return its meaning. This allows report authors to display whether a rollup cost component originated from a resource, an outside processing operation, or another defined source.

Underlying Base Objects

The view is defined over five documented base objects, joined primarily on CST_ITEM_COST_DETAILS, aliased CICD:

• CST_ITEM_COST_DETAILS — the driving table holding item cost detail rows keyed by inventory item, organization, and cost type.
• CST_ACTIVITIES — outer-joined on ACTIVITY_ID and organization, supplying the activity name.
• BOM_RESOURCES — outer-joined on RESOURCE_ID, supplying resource code and unit of measure.
• CST_COST_ELEMENTS — joined on COST_ELEMENT_ID to supply the cost element name.
• MFG_LOOKUPS — referenced three times to decode BASIS_TYPE (CST_BASIS), ROLLUP_SOURCE_TYPE (CST_SOURCE_TYPE), and LEVEL_TYPE (CST_LEVEL).

The dependency on MFG_LOOKUPS means the view returns rows only where valid lookup codes exist for CST_BASIS, CST_SOURCE_TYPE, and CST_LEVEL, and the join to CST_COST_ELEMENTS is enforced (non-outer).

Key Columns

• INVENTORY_ITEM_ID, ORGANIZATION_ID, COST_TYPE_ID — identify the item, inventory organization, and cost type context of the detail row.
• COST_ELEMENT_ID / COST_ELEMENT — the cost element (material, material overhead, resource, overhead, outside processing) and its decoded name.
• LEVEL_TYPE — the level of the cost structure (for example, this level or level 1), decoded via CST_LEVEL.
• ACTIVITY_ID / ACTIVITY — the activity associated with the cost component.
• RESOURCE_ID / RESOURCE_CODE / UNIT_OF_MEASURE — the resource consumed and its UOM.
• RESOURCE_RATE, USAGE_RATE_OR_AMOUNT, ITEM_UNITS, ACTIVITY_UNITS — the rate and usage quantities used to derive the cost.
• BASIS_TYPE — the basis of the resource usage, decoded from CST_BASIS.
• ROLLUP_SOURCE_TYPE — the source of the rolled-up cost, decoded from CST_SOURCE_TYPE.
• ITEM_COST — the computed cost contribution of the detail line.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — the concurrent program that generated the row.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY — descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include cost element breakdown reports, resource usage audits, and extracts that feed external costing or analytics platforms. The view is also used to validate the meaning behind rollup source codes without re-implementing lookup joins.

Listing all distinct rollup source meanings for an organization and cost type:

• SELECT DISTINCT rollup_source_type, meaning FROM apps.cst_item_cost_details_v WHERE organization_id = :org AND cost_type_id = :ct

Summarizing cost by element for a single item:

• SELECT cost_element, SUM(item_cost) FROM apps.cst_item_cost_details_v WHERE inventory_item_id = :item AND organization_id = :org AND cost_type_id = :ct GROUP BY cost_element

Filtering resource-based rollups using the decoded source meaning, for example restricting to rollup rows whose CST_SOURCE_TYPE meaning identifies a resource contribution, supports targeted variance analysis between frozen and pending cost types.