Results for “usage_uom”

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

Overview

GMF_RESOURCE_COSTS_V is a reporting view owned by the APPS schema within the Process Manufacturing Financials (GMF) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents resource cost information drawn from the Process Manufacturing cost detail tables and resolves each row to a valid, active organization. The view exposes a unified result set combining resource identity, unit of measure, cost type, calendar and period context, organization, and the resulting nominal cost. Its primary role is to provide a stable, query-ready projection of resource costs for reporting, cost analysis, and downstream integrations, while abstracting the more complex organization-resolution and precedence logic contained in its defining SQL.

A notable design characteristic is the view's precedence rule: where an organization-specific cost exists, it is preferred, and the globally defined cost is used as a fallback. This prioritization is implemented through the NVL expression over the ORGS_NCOST and GLOBAL_NCOST derived columns, ensuring each resource, cost type, and period combination returns a single nominal cost value.

Underlying Base Objects

According to the documented view metadata, GMF_RESOURCE_COSTS_V is defined over two referenced base objects, both exposed as synonyms: CM_RSRC_DTL and GMF_PROCESS_ORGANIZATIONS_GT. CM_RSRC_DTL supplies the core resource cost records, including resource name, usage unit of measure, cost type, period, organization, calendar, period code, and nominal cost. The view filters these rows with a DELETE_MARK = 0 predicate, ensuring only active, non-deleted cost records are returned.

GMF_PROCESS_ORGANIZATIONS_GT functions as the organization reference set, used to resolve and validate organization identifiers and to supply organization code context. The defining SQL joins resource costs to this organization set and applies an analytic ROW_NUMBER ranking partitioned by resource, cost type, period, and the resolved organization (using NVL to substitute the organization from the global set where the source record's organization is null). Only the highest-ranked row (ROW_RANK = 1) per partition is retained, with null organization identifiers ordered last. This guarantees a single, deterministic cost row per resource, cost type, period, and organization.

Key Columns

• RESOURCES — Identifier of the process manufacturing resource whose cost is represented.
• USAGE_UOM — Unit of measure associated with the resource's usage, relevant to interpreting the cost basis.
• COST_TYPE_ID — Identifier of the cost type, distinguishing between cost categories maintained for the resource.
• PERIOD_ID — Identifier of the cost period to which the record applies.
• ORGANIZATION_ID — The resolved organization for the cost record, derived through the view's organization resolution logic.
• ORGANIZATION_CODE — Human-readable code for the corresponding organization.
• CALENDAR_CODE — Code of the accounting calendar governing the period.
• PERIOD_CODE — Human-readable identifier of the period.
• NOMINAL_COST — The resulting nominal cost, computed as NVL(ORGS_NCOST, GLOBAL_NCOST), favoring the organization-specific value and falling back to the global value when no organization-specific cost exists.

Common Use Cases and Queries

Typical scenarios include reporting resource costs by organization and period, comparing organization-specific costs against global defaults, and feeding cost data into analysis or integration routines. A representative query retrieving costs for a given resource and cost type across periods might resemble:

• SELECT resources, organization_code, calendar_code, period_code, usage_uom, nominal_cost FROM apps.gmf_resource_costs_v WHERE resources = :resource AND cost_type_id = :cost_type ORDER BY period_code;
• SELECT organization_code, period_code, SUM(nominal_cost) FROM apps.gmf_resource_costs_v GROUP BY organization_code, period_code ORDER BY organization_code, period_code;
• SELECT resources, organization_code, nominal_cost FROM apps.gmf_resource_costs_v WHERE period_code = :period AND cost_type_id = :cost_type ORDER BY resources;

Because the view resolves organization precedence and eliminates duplicate ranking rows internally, consumers can rely on it directly for consistent, single-valued resource cost reporting without replicating the underlying join and ranking logic.