Search Results cstbv_matl_cost_sub_element




Overview

The APPS.CSTBV_MATL_COST_SUB_ELEMENT view is a reporting and integration construct within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, owned by the APPS schema and associated with the BOM (Bills of Material) product family. As documented in the ETRM metadata, the object is a VIEW with a status of VALID and carries the description "Retrofitted," indicating that it was re-engineered or reintroduced to support cost sub-element extraction against the standard BOM schema. The view exposes material cost sub-element attributes derived from BOM resources, specifically those linked to a cost element, and is defined WITH READ ONLY, signalling its intended use as a query-only, read-consistent surface for reporting, integration, and drill-down rather than transactional maintenance.

Underlying Base Objects

Per the documented metadata, the view is defined over a single referenced base object: the BOM_RESOURCES synonym. The view text selects from BOM_RESOURCES (aliased BR) with a fixed filter predicate of BR.COST_ELEMENT_ID = 1 and an additional security predicate expressed as '_SEC:BR.ORGANIZATION_ID' IS NOT NULL. The COST_ELEMENT_ID = 1 restriction constrains the result set to resources whose cost element corresponds to Material, effectively isolating material-type resource cost sub-elements from the broader BOM_RESOURCES population. The security predicate is a standard EBS row-level security substitution token resolved at runtime, ensuring that rows are returned only for organizations the querying responsibility is authorized to access.

Key Columns

The view projects a curated set of resource attributes alongside derived and descriptive columns:

Common Use Cases and Queries

This view is typically used in cost sub-element reporting, cost rollup validation, and integration extracts that require material cost sub-elements by organization. Because it is read-only and secured by organization, it is suitable for concurrent-program extracts and BI Publisher data models.

Example: retrieve active material cost sub-elements for a given organization.

  • SELECT resource_code, description, expenditure_type, default_activity_id
  •   FROM apps.cstbv_matl_cost_sub_element
  •  WHERE organization_id = :p_org_id
  •    AND (disable_date IS NULL OR disable_date > SYSDATE)
  •  ORDER BY resource_code;

Example: join to lookups for cost basis interpretation.

  • SELECT c.resource_code, c."_LA:DEFAULT_BASIS_TYPE" basis, c."_LA:COST_CODE_TYPE" cost_code
  •   FROM apps.cstbv_matl_cost_sub_element c
  •  WHERE c.organization_id = :p_org_id;

In all cases, the effective result set is bounded by the COST_ELEMENT_ID = 1 filter and by the organization security token enforced within the view definition.