Results for “cstbv_item_unit_cost_details”

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

Overview

CSTBV_ITEM_UNIT_COST_DETAILS is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes item-level unit cost detail records from the Cost Management module, within the Bills of Material (BOM) product family. The object is documented in ETRM as "Retrofitted," reflecting that its definition was carried forward between release levels with only mechanical changes. The view presents the rows of CST_ITEM_COST_DETAILS, a foundational costing table that stores cost element, activity, resource, and basis information used by the Bills of Material and Cost Management costing engines. Because unit cost calculations for manufactured items depend on components such as item units, activity units, usage rates, and yield/shrinkage factors, this view provides a denormalized, key-flexfield-enabled presentation of that detail for reporting and integration. It is a read-only view (the underlying definition includes WITH READ ONLY), which reinforces its intended role as a query and extraction surface rather than a maintenance interface.

The name is commonly surfaced when users search for item_units, reflecting the column of the same name that appears in reports examining how unit costs are derived. In practical terms, the view serves as a reporting bridge between the raw cost detail table and descriptive master data such as organization codes, organization names, cost type names, item numbers, and lookup meanings for basis type and level type.

Underlying Base Objects

The documented base objects joined by the view are all referenced through APPS synonyms in the 12.2.2 metadata:

• CST_ITEM_COST_DETAILS (ICD) — the primary driver table containing unit cost detail rows keyed by organization, inventory item, and cost type.
• CST_COST_TYPES (CT) — joined on COST_TYPE_ID to resolve the cost type name (for example, Frozen, Average, or Standard).
• HR_ALL_ORGANIZATION_UNITS (HR) — joined on ORGANIZATION_ID to supply the organization name.
• MTL_PARAMETERS (MP) — joined on ORGANIZATION_ID to supply the organization code and confirm the inventory organization context.
• MTL_SYSTEM_ITEMS (SY) — joined on ORGANIZATION_ID and INVENTORY_ITEM_ID to validate the item and expose key flexfield item number information.

The joins are essentially decorative lookups: the view filters to rows where the secured organization context ('_SEC:ICD.ORGANIZATION_ID') is not null, ensuring that only organizations visible to the operating responsibility are returned. This is a standard EBS row-level security pattern propagated through the view.

Key Columns

• ORGANIZATION_ID, INVENTORY_ITEM_ID, COST_TYPE_ID — the unique attribute combination that identifies a cost detail row.
• ITEM_UNITS, ACTIVITY_UNITS — quantity measures of the item and activity that drive unit cost computation; ITEM_UNITS is the column most associated with the "item_units" search term.
• USAGE_RATE_OR_AMOUNT, BASIS_FACTOR — the rate or amount applied and the basis factor used in costing.
• NET_YIELD_OR_SHRINKAGE_FACTOR — the yield or shrinkage adjustment applied to the component quantity.
• "_LA:BASIS_TYPE" and "_LA:LEVEL_TYPE" — flexfield-style lookup meanings resolved from MFG_LOOKUPS using the CST_BASIS and CST_LEVEL lookup types.
• ITEM_COST — the resulting item unit cost value for the detail row.
• ORGANIZATION_CODE, ORGANIZATION_NAME, COST_TYPE, "_KF:ITEM_NUMBER:_CO" — descriptive attributes: the organization code, organization name, cost type name, and the item number key flexfield value.
• COST_ELEMENT_ID, DEPARTMENT_ID, ACTIVITY_ID, RESOURCE_ID, BASIS_RESOURCE_ID, OPERATION_SEQUENCE_ID — identifiers linking the detail to cost elements, departments, activities, resources, and routing operations.
• CREATED_DATE, CREATED_BY, UPDATED_DATE, UPDATED_BY — the standard WHO audit columns, aliased here as CREATED_DATE/UPDATED_DATE.

Common Use Cases and Queries

Typical uses include cost rollup analysis, item unit cost verification, and integration extraction for reporting tools. Users searching "item_units" generally want to inspect how quantities and usage rates translate into item unit cost. A representative query is:

• SELECT organization_code, inventory_item_id, cost_type, item_units, activity_units, usage_rate_or_amount, net_yield_or_shrinkage_factor, item_cost FROM apps.cstbv_item_unit_cost_details WHERE organization_id = :org_id AND inventory_item_id = :item_id AND cost_type = :cost_type;
• Cost element analysis: SELECT cost_element_id, resource_id, basis_resource_id, item_cost FROM apps.cstbv_item_unit_cost_details WHERE organization_id = :org_id AND cost_type_id = :ct_id;
• Organization-wide unit cost export: SELECT organization_code, "_KF:ITEM_NUMBER:_CO", cost_type, item_units, item_cost FROM apps.cstbv_item_unit_cost_details;

Because the view enforces organization security and is read-only, it is appropriate for ad hoc queries and downstream ETL. For mass extracts, joining to CST_ITEM_COST_DETAILS directly may be preferable to avoid the descriptive joins; for user-facing reports, the view's resolved names and lookup meanings reduce downstream decoding effort.