Results for “cost_type_desc”
20 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CST_RESOURCE_COSTS_V is a single-organization view owned by the APPS schema in Oracle E-Business Suite, classified under the BOM (Bills of Material) product family. It exposes resource cost records maintained by the Cost Management module, resolving the relationship between a resource and the cost type assigned to it. As a single-org view, the organization context is not enforced internally by a WHERE predicate on ORGANIZATION_ID; instead, the query retrieves rows for whatever organization the resource cost records belong to, and the caller is responsible for supplying an ORGANIZATION_ID filter. This behavior distinguishes the view from multi-org or security-constrained variants and makes it the lighter-weight choice for point queries, custom reports, and integration extracts where the organization is already known.
Underlying Base Objects
The view is defined over two base objects, both resolved at runtime through APPS synonyms: CST_RESOURCE_COSTS and CST_COST_TYPES. CST_RESOURCE_COSTS is the transactional table holding the resource rate and its descriptive flexfield attributes per resource, cost type, and organization. CST_COST_TYPES is the reference table supplying the cost type code and description, and is joined on the COST_TYPE_ID column common to both tables. The join is expressed as an inner join (CCT.COST_TYPE_ID = CRC.COST_TYPE_ID), so a resource cost row is returned only when a matching cost type exists. The view projects the ROWID of CST_RESOURCE_COSTS, which supports certain updatable-view and duplicate-detection patterns, though no DML should be assumed against the view. The metadata confirms the documented status as VALID for the 12.1.1 and 12.2.2 releases.
Key Columns
- RESOURCE_ID — Identifier of the resource whose rate is recorded; joins to the resource definition tables such as BOM_RESOURCES.
- COST_TYPE_ID — Foreign key to CST_COST_TYPES, identifying the costing method (for example, frozen, average, or standard) under which the rate applies.
- COST_TYPE and DESCRIPTION — The cost type code and its descriptive text, sourced from CST_COST_TYPES. The column list also documents the aliases COST_TYPE_CODE and COST_TYPE_DESC for these fields.
- ORGANIZATION_ID — The inventory organization to which the resource cost record belongs. Because the view is single-org, this column must be filtered explicitly by the caller.
- RESOURCE_RATE — The cost or rate amount assigned to the resource for the given cost type and organization.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield columns carried through from the base cost record for client-specific extensions.
- ALLOW_UPDATES_FLAG — Sourced from CST_COST_TYPES, indicating whether the cost type permits user maintenance of the associated rates.
- Audit and concurrency columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.
Common Use Cases and Queries
Typical uses include cost-rollup validation, resource rate extracts for external costing engines, and reporting on which resources have defined rates for a given cost type. The single-org design means queries should always constrain ORGANIZATION_ID to avoid cross-organization noise. A representative query listing active resource rates for one organization follows:
SELECT resource_id, cost_type, resource_rate, allow_updates_flag
FROM apps.cst_resource_costs_v
WHERE organization_id = :p_org_id
AND cost_type = :p_cost_type
ORDER BY resource_id;
To find resources lacking a rate under a particular cost type, an outer join pattern over the resource master may be used, since this view returns only existing cost rows. When integrating with other BOM objects, join RESOURCE_ID to BOM_RESOURCES to obtain resource codes and descriptions. Because the view exposes descriptive flexfield attributes and audit columns, it is also suitable as a source for extraction programs that need a complete, denormalized picture of resource cost setup without separately querying CST_COST_TYPES.
-
View: CST_RESOURCE_COSTS_V 12.1.1
Resource costs : SINGLE-ORG view
APPS.CST_RESOURCE_COSTS_V·↳ CST_COST_TYPES·↳ CST_RESOURCE_COSTS·Explore BOM module →
-
Departmental overheads : SINGLE-ORG view
APPS.CST_DEPARTMENT_OVERHEADS_V·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CST_ACTIVITIES·Explore BOM module →
-
Departmental overheads : SINGLE-ORG view
APPS.CST_DEPARTMENT_OVERHEADS_V·↳ BOM_DEPARTMENTS·↳ BOM_RESOURCES·↳ CST_ACTIVITIES·Explore BOM module →
-
View: CST_LE_COST_TYPES_V 12.2.2
APPS.CST_LE_COST_TYPES_V·↳ CST_ACCOUNTING_LIBRARIES·↳ CST_COST_TYPES·↳ CST_LE_COST_TYPES·Explore BOM module →
-
Resource based overheads by cost type : SINGLE-ORG view
APPS.CST_RESOURCE_OVERHEADS_V·↳ BOM_RESOURCES·↳ CST_COST_TYPES·↳ CST_RESOURCE_OVERHEADS·Explore BOM module →
-
View: CST_LE_COST_TYPES_V 12.1.1
APPS.CST_LE_COST_TYPES_V·↳ CST_ACCOUNTING_LIBRARIES·↳ CST_COST_TYPES·↳ CST_LE_COST_TYPES·Explore BOM module →
-
View: CST_RESOURCE_COSTS_V 12.2.2
Resource costs : SINGLE-ORG view
APPS.CST_RESOURCE_COSTS_V·↳ CST_COST_TYPES·↳ CST_RESOURCE_COSTS·Explore BOM module →
-
Resource based overheads by cost type : SINGLE-ORG view
APPS.CST_RESOURCE_OVERHEADS_V·↳ BOM_RESOURCES·↳ CST_COST_TYPES·↳ CST_RESOURCE_OVERHEADS·Explore BOM module →
-
eTRM - BOM Tables and Views 12.1.1
Table to map wip transactions to their corresponding event types.
-
eTRM - BOM Tables and Views 12.2.2
Table to map wip transactions to their corresponding event types.