Search Results std_usage_uom

Overview

The PMIBV_RESOURCE_PLAN_V view is a read-only reporting object owned by the APPS schema within the Process Manufacturing Intelligence (PMI) product family. It provides a consolidated presentation of the availability and planned usage of Process Manufacturing resources, joining resource master and detail definitions with batch-step-level resource consumption records. The view is designed as a business intelligence (BV) layer, meaning it flattens normalized transactional and setup data into a single denormalized structure optimized for reporting, dashboards, and downstream integration extracts.

The view carries a WITH READ ONLY clause, confirming that it is not intended for direct DML. Its primary role is to expose resource planning information across organizational, resource, and batch execution dimensions, allowing process manufacturers to reconcile nominal resource capacity against the actual and planned consumption recorded during batch execution.

Underlying Base Objects

PMIBV_RESOURCE_PLAN_V is defined over five synonym-referenced base objects, resolved to the following tables at runtime:

• CR_RSRC_MST — resource master definition (regular attributes).
• CR_RSRC_DTL — resource detail, holding organization, capacity, and cost attributes.
• GME_BATCH_STEP_RESOURCES — batch-step-level resource assignment and usage.
• GME_BATCH_STEP_ACTIVITIES — activity records linking batch steps to resources.
• GME_BATCH_STEPS — batch step header information.

The joins are driven from CR_RSRC_MST, with outer joins ((+)) applied to CR_RSRC_DTL, GME_BATCH_STEP_RESOURCES, GME_BATCH_STEP_ACTIVITIES, and GME_BATCH_STEPS. This ensures that resources defined in the master are returned even when no corresponding detail or batch-step usage exists, which is appropriate for availability reporting where a resource may be idle.

Key Columns

The view exposes resource-level attributes sourced from CR_RSRC_MST and CR_RSRC_DTL, alongside execution-level attributes from the batch tables. Notable columns include:

• RESOURCES / RESOURCE_DESC — resource identifier and description.
• STD_USAGE_UOM — the standard unit of measure for the resource's usage; directly relevant to the user's search term.
• RESOURCE_CLASS / RESOURCE_COST_COMP_CLASS_ID — classification and cost component class.
• ORGANIZATION / GROUP_RESOURCE — owning organization and resource grouping.
• ASSIGNED_QTY, DAILY_AVAIL_USE, RESOURCE_USAGE_UOM — availability and usage metrics.
• NOMINAL_COST, INACTIVE_IND — costing and status flags.
• IDEAL_CAPACITY, MIN_CAPACITY, MAX_CAPACITY, CAPACITY_UOM — capacity bounds.
• BATCH_ID, BATCHSTEP_NO, ACTIVITY — batch execution context.
• PLAN_RSRC_QTY, ACTUAL_RSRC_QTY, PLAN_RSRC_USAGE, ACTUAL_RSRC_USAGE — planned versus actual resource consumption.
• PLAN_START_DATE, ACTUAL_START_DATE, PLAN_CMPLT_DATE, ACTUAL_CMPLT_DATE — scheduling reconciliation points.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY).

Common Use Cases and Queries

Typical usage includes resource capacity planning, batch utilization analysis, and cost-driver reporting. The following query retrieves standard usage UOM and planned usage per resource for a given organization:

SELECT resources, resource_desc, std_usage_uom,
       plan_rsrc_usage, actual_rsrc_usage, plan_start_date
FROM   apps.pmibv_resource_plan_v
WHERE  organization = :p_org
AND    plan_start_date >= :p_from_date
ORDER BY resources, plan_start_date;

To identify resources exceeding nominal capacity, filter on IDEAL_CAPACITY versus PLAN_RSRC_QTY. For inactive-resource audits, filter INACTIVE_IND = 'Y'. Because the view is read-only and joins five tables, queries should apply organization and date predicates to limit row counts on large batch histories.