Search Results cost_type_name




Overview
Explore in AI Chat

Overview

CSTBV_MFG_RESOURCE_COSTS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered in the application design data under the product short name BOM with the FND Design Data identifier BOM.CSTBV_MFG_RESOURCE_COSTS, and its status is VALID in both the 12.1.1 and 12.2.2 releases. The view presents the resource and outside processing resource unit costs maintained within Oracle Cost Management, exposing the costing rate assigned to each manufacturing resource for a given cost type and organization. Because it is a denormalized reporting view rather than a base transactional table, it does not carry the full set of internal foreign keys and audit columns found on the underlying cost tables. Instead, it surfaces the descriptive identifiers — cost type name and resource name — alongside the numeric rate, which makes it directly consumable by BI Publisher reports, Oracle Discoverer workbooks, and custom SQL extracts without the need for additional joins to resolve names from IDs.

Underlying Base Objects

The ETRM metadata documents three referenced base objects, all resolved through synonyms in the APPS schema: BOM_RESOURCES, CST_COST_TYPES, and CST_RESOURCE_COSTS. CST_RESOURCE_COSTS is the primary cost repository and supplies the resource rate, the cost type, the organization context, and the audit columns. CST_COST_TYPES supplies the cost type definition, which the view surfaces as COST_TYPE_NAME. BOM_RESOURCES is the resource master and supplies the resource identifier and resource name displayed as RESOURCE_NAME. The view therefore consolidates a costing fact (the rate) with two dimension sources (cost type and resource) into a single flattened structure. No database object references CSTBV_MFG_RESOURCE_COSTS, confirming that it sits at the top of the dependency chain and is intended strictly as a read-only reporting surface rather than as input to further object definitions.

Key Columns

  • COST_TYPE_ID — Numeric identifier of the cost type under which the resource rate is defined.
  • COST_TYPE_NAME — VARCHAR2(10) descriptive name of the cost type; this is the column most commonly searched for when filtering rates by costing method or frozen cost type.
  • RESOURCE_ID — Numeric identifier of the manufacturing or outside processing resource.
  • RESOURCE_NAME — VARCHAR2(10) descriptive resource name associated with the rate.
  • RESOURCE_RATE — The unit cost or rate applied to the resource for the specified cost type and organization.
  • ORGANIZATION_ID — Numeric identifier of the inventory organization in which the cost is valid, enabling multi-organization comparison.
  • CREATED_DATE, CREATED_BY, UPDATED_DATE, UPDATED_BY — Standard audit columns recording the creation and last modification of the cost record.

Common Use Cases and Queries

The view is most frequently used to audit and compare resource rates across cost types and organizations, and to feed cost rollup extracts. A typical query filters by the cost type name of interest, which corresponds directly to the user's search term:

  • List all rates for a named cost type: SELECT cost_type_name, resource_name, resource_rate, organization_id FROM apps.cstbv_mfg_resource_costs WHERE cost_type_name = :cost_type;
  • Compare one resource across organizations: SELECT organization_id, resource_rate FROM apps.cstbv_mfg_resource_costs WHERE resource_name = :resource ORDER BY organization_id;
  • Identify recently changed rates: SELECT resource_name, cost_type_name, resource_rate, updated_date FROM apps.cstbv_mfg_resource_costs WHERE updated_date > SYSDATE - 30;
  • Exclude outside processing resources where a distinct naming convention applies by constraining RESOURCE_NAME with a pattern predicate.

Because the view hides internal joins and keys, it is well suited to ad hoc reporting and integration interfaces that require ready-to-publish name and rate pairs. Reports demanding full costing detail, such as basis type or activity data, should instead query CST_RESOURCE_COSTS directly.