Search Results pln_rsrc_usage




Overview
Explore in AI Chat

Overview

VIEW: APPS.OPI_EDW_RSRC_EFFICIENCY_V is a reporting view in the Oracle E-Business Suite Process Manufacturing (OPM) intelligence layer. It exposes resource efficiency information by joining transactional resource usage records to conformed EDW dimension members for inventory locations, time, resources, and units of measure. The view is designed to support enterprise data warehouse (EDW) style analysis of production resource consumption across the OPM inventory and bill-of-material structures. Users searching for the column or term pln_rsrc_usage will find it surfaced here as PLN_RSRC_USAGE, representing the planned resource usage quantity measured against corresponding actual and standard quantities. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a semantic bridge between the raw OPI_EDW_JOB_RSRC_F fact table and the reporting star schemas used for manufacturing performance dashboards.

Underlying Base Objects

The view is defined over five objects. The primary fact source is OPI_EDW_JOB_RSRC_F (aliased JR), which stores resource usage by job. It is enriched by four dimension members: EDW_MTL_INVENTORY_LOC_M (INV) for inventory location context, EDW_TIME_M (TIME) for the calendar hierarchy, EDW_BOM_RES_M (RES) for the resource and department hierarchy, and EDW_MTL_UOM_M (UOM) for unit-of-measure descriptions. The joins operate on surrogate foreign keys: INV.INVL_LOCATOR_PK_KEY to JR.LOCATOR_FK_KEY, TIME.CDAY_CAL_DAY_PK_KEY to JR.TRX_DATE_FK_KEY, RES.RSRC_RESOURCE_PK_KEY to JR.RSRC_FK_KEY, and JR.QTY_UOM_FK_KEY to UOM.UOM_EDW_UOM_PK_KEY. Although the documented metadata lists no referenced base objects, the preformatted view text confirms these five tables as the definitional sources. This join pattern is consistent with the Oracle Manufacturing Analytics and OPM Intelligence data model, in which the _F suffix denotes a fact table and the _M suffix denotes a dimension master.

Key Columns

The view returns nineteen columns organized around identifiers and measures.

Together these three usage columns allow variance analysis between planned, standard, and actual consumption.

Common Use Cases and Queries

Typical usage centers on resource efficiency reporting and variance analysis. Analysts compare PLN_RSRC_USAGE against ACT_USAGE to quantify schedule adherence, or against STD_USAGE to evaluate standard-cost performance. A representative query aggregates planned usage by plant and period:

  • SELECT plant_id, cal_period_id, SUM(pln_rsrc_usage) FROM apps.opi_edw_rsrc_efficiency_v GROUP BY plant_id, cal_period_id;
  • SELECT res_dept_id, SUM(act_usage) - SUM(pln_rsrc_usage) variance FROM apps.opi_edw_rsrc_efficiency_v GROUP BY res_dept_id;
  • SELECT uom_name, SUM(std_usage), SUM(act_usage) FROM apps.opi_edw_rsrc_efficiency_v GROUP BY uom_name;

Because the view resolves all surrogate keys to EDW dimension members, it is well suited for loading presentation-layer fact tables or querying directly from BI Publisher and OBIEE reports.