Results for “activity_units”

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

Overview

The CSTFV_ITEM_UNIT_COST_DETAILS view is a Business Intelligence (BI) style database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is catalogued under the BOM – Bills of Material product family and is flagged in the ETRM repository with the description "Retrofitted," indicating that it was migrated from an earlier Oracle environment into the current release under the standard ETRM retrofit convention. The view presents item-level unit cost detail records in a denormalized, reporting-friendly form, joining the core costing detail table to the many descriptive and lookup tables required to render cost driver, activity, department, resource, and operation information without further user-side joins. Because it resolves foreign keys inline—returning organization codes, department codes, cost type and cost element names, resource codes, and operation descriptions—it is well suited to ad hoc reporting, BI Publisher data sources, and interface extracts where the goal is to deliver human-readable unit cost breakdowns rather than raw identifiers.

Underlying Base Objects

The view is defined over eleven base objects, all accessed through APPS synonyms. Its driving table is CST_ITEM_COST_DETAILS (aliased ICD), which supplies organization, item, cost type, resource, activity, department, and operation sequence identifiers along with the numeric cost attributes. Descriptive lookups are joined as outer joins where the relationship is optional: CST_COST_ELEMENTS, BOM_DEPARTMENTS, CST_ACTIVITIES, BOM_RESOURCES (joined twice, once as the primary resource and once as the basis resource), and BOM_OPERATION_SEQUENCES. Inner joins enforce mandatory context: HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS on organization, and MTL_SYSTEM_ITEMS on organization plus inventory item. CST_COST_TYPES is joined on cost type identifier. The final WHERE clause includes a security predicate on ICD.ORGANIZATION_ID, and the view is declared WITH READ ONLY.

Key Columns

The unique key is the combination of ORGANIZATION_ID, INVENTORY_ITEM_ID, and COST_TYPE_ID. Regular attributes include ITEM_UNITS, ACTIVITY_UNITS, USAGE_RATE_OR_AMOUNT, ITEM_COST, and the lookup-derived BASIS_TYPE and LEVEL_TYPE (resolved against CST_BASIS and CST_LEVEL respectively). Resolved descriptive columns include ORGANIZATION_CODE, ORGANIZATION_NAME, COST_TYPE, COST_ELEMENT, DEPARTMENT_CODE, ACTIVITY, OPERATION_DESCRIPTION, and notably two resource code columns—RESOURCE_CODE from BR1 (the primary resource) and a second RESOURCE_CODE from BR2 (the basis resource). Because both derive from BOM_RESOURCES, applications referencing the resource code must disambiguate by column position or alias. Identifier columns retained for key flexfield and security use include COST_ELEMENT_ID, DEPARTMENT_ID, ACTIVITY_ID, RESOURCE_ID, BASIS_RESOURCE_ID, and OPERATION_SEQUENCE_ID, plus standard WHO audit columns.

Common Use Cases and Queries

Typical uses are unit cost roll-up reporting, resource rate analysis, and cost detail extracts. The resource code is a frequent search term, so queries commonly filter on it, as in:

• SELECT organization_code, cost_type, cost_element, resource_code, item_units, item_cost FROM cstfv_item_unit_cost_details WHERE resource_code = :resource_code AND organization_id = :org_id;
• Comparing primary and basis resources for activity-driven costs by selecting both resource code columns with distinct aliases.
• Feeding costing detail into BI Publisher layouts where resolved descriptions (department code, activity, operation description) are required, avoiding manual joins to BOM and CST tables.
• Reconciling item-level unit costs by cost element across cost types for a given organization, restricted by the built-in organization security predicate.

Because the view is read-only and includes organization-level security, it is safe for reporting duty but should not be used for transactional writes.