Results for “cst_xla_res_ovh_ref_v”

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

Overview

The CST_XLA_RES_OVH_REF_V view is a public Oracle E-Business Suite database object owned by the APPS schema and registered under the Bills of Material (BOM) product family. It functions as a denormalized reference view that exposes resource definitions from the BOM_RESOURCES table joined to the cost element classification held in CST_COST_ELEMENTS. The view exists primarily to satisfy the sourcing requirements of Oracle Subledger Accounting (XLA) within the Cost Management (CST) application, which is why the naming convention carries the CST_XLA prefix. In both release 12.1.1 and 12.2.2 the object is reported as VALID, and no structural differences between the two releases are documented.

In practical terms, the view is a lookup surface. It allows SLA accounting rule definitions, journal line type assignments, and cost accounting configurations to reference resources by a stable, readable set of attributes — resource code, description, cost element, and expenditure type — without embedding multiple joins into each rule. Because it consolidates descriptive and classification data, it is also widely used for ad hoc reporting and for feeds into downstream integration or data-warehouse layers.

Underlying Base Objects

The view is defined over two base objects, both accessed through APPS synonyms:

• BOM_RESOURCES — the resource master, supplying the resource identifier, code, description, purchasing item, functional currency flag, resource type, expenditure type, and the descriptive flexfield attribute columns.
• CST_COST_ELEMENTS — the cost element definition, supplying the cost element name assigned to the resource.

The two objects are joined with an equality on COST_ELEMENT_ID. This inner join means that a resource row appears in the view only when its cost element foreign key successfully resolves to a valid cost element record. Resources with a null or orphaned cost element reference are therefore excluded, which is significant when auditing expected resource counts.

Key Columns

• RESOURCE_ID, RESOURCE_CODE, RES_DESCRIPTION — the primary identifier and human-readable labels for the resource.
• RES_COST_ELEMENT — the cost element name derived from CST_COST_ELEMENTS; the principal classification used in accounting rules.
• RES_TYPE — the resource type column (sourced from BOM_RESOURCES.RESOURCE_TYPE). This is the column returned when a user searches on the term res_type. It categorizes the resource for costing and capacity purposes — for example, whether the resource is treated as a person, machine, or other resource class.
• RES_EXPENDITURE_TYPE — the expenditure type associated with the resource, used to drive WIP and cost transaction accounting.
• RES_PURCHASE_ITEM_ID — links an outside-processing resource to a purchasing item.
• RES_FUNC_CURRENCY_FLAG — indicates whether the resource is defined in the functional currency.
• RES_ATTRIBUTE_CATEGORY and RES_ATTRIBUTE1 through RES_ATTRIBUTE15 — the descriptive flexfield context and segment values carried through from BOM_RESOURCES.
• RES_OVH_ABSORPTION_ACCT — the absorption account used when overhead is applied against the resource.

Note that the join column COST_ELEMENT_ID is not projected; consumers must rely on the derived cost element name instead.

Common Use Cases and Queries

A typical use is retrieving the cost element and expenditure type that SLA will apply to a given resource:

• SELECT RESOURCE_CODE, RES_TYPE, RES_COST_ELEMENT, RES_EXPENDITURE_TYPE FROM CST_XLA_RES_OVH_REF_V WHERE RESOURCE_CODE = :p_code;

An audit query lists all resources of a given type for cost element review:

• SELECT RESOURCE_ID, RESOURCE_CODE, RES_COST_ELEMENT FROM CST_XLA_RES_OVH_REF_V WHERE RES_TYPE = :p_res_type ORDER BY RESOURCE_CODE;

A reconciliation query compares view rows against the resource master to identify resources missing a cost element mapping, corroborating the inner-join behavior described above. Because the view is read-only and non-materialized, each execution reflects the current state of BOM_RESOURCES and CST_COST_ELEMENTS, making it suitable for real-time validation logic as well as scheduled reporting.