Results for “mrpbv_plan_resource_loads”

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

Overview

The APPS.MRPBV_PLAN_RESOURCE_LOADS view is a reporting and integration object within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It exposes planned resource load information generated by the planning engine, combining capacity requirements calculated for discrete and repetitive manufacturing with scheduling details produced by the MRP/MPS planning run. Its primary role is to surface, for each planning transaction, the resource consumption in terms of hours and load rate across a date range, allowing planners and downstream reports to analyze capacity loading by organization, department, resource, and assembly.

The view is read-only and is intended to present data that would otherwise require joining resource planning records with recommendation and scheduling data. Because it consolidates discrete and repetitive planning contexts through a UNION ALL structure, it serves as a unified interface for resource load reporting.

Underlying Base Objects

The view is defined over the following documented base objects, all referenced through APPS synonyms: BOM_DEPARTMENTS, BOM_RESOURCES, CRP_RESOURCE_PLAN, HR_ALL_ORGANIZATION_UNITS, MRP_RECOMMENDATIONS, MRP_SUGG_REP_SCHEDULES, MTL_PARAMETERS, MTL_SYSTEM_ITEMS, and WIP_LINES.

The central driving table is CRP_RESOURCE_PLAN (aliased RES), which holds the computed resource load records. This is joined to MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS on ORGANIZATION_ID to establish organization context, to BOM_DEPARTMENTS on DEPARTMENT_ID, and to BOM_RESOURCES on RESOURCE_ID. Two references to MTL_SYSTEM_ITEMS supply assembly and source item descriptions. MRP_RECOMMENDATIONS (aliased MR) supplies scheduling and quantity data through SOURCE_TRANSACTION_ID. The UNION ALL branch extends coverage to repetitive schedules via MRP_SUGG_REP_SCHEDULES and WIP_LINES. A predicate excludes records where RESOURCE_ID equals -1 and enforces the organization security filter.

Key Columns

• LOAD_RATE — The rate of resource loading, central to the user's search; expresses load intensity for the resource record.
• OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM — Sequence identifiers for the operation and resource within the routing.
• RESOURCE_DATE, RESOURCE_END_DATE — The date range over which the resource load applies.
• RESOURCE_HOURS, DAILY_RESOURCE_HOURS — Total and per-day resource hours consumed.
• NEW_SCHEDULE_DATE, LAST_UNIT_COMPLETION_DATE — Scheduling dates sourced from MRP_RECOMMENDATIONS.
• NEW_ORDER_QUANTITY, DAILY_RATE — Planned order quantity and daily production rate.
• ORGANIZATION_ID, DEPARTMENT_ID, RESOURCE_ID, DESIGNATOR — Organizational and resource identity keys.
• ASSEMBLY_ITEM_ID, SOURCE_ITEM_ID — The assembly and originating item identifiers.
• TRANSACTION_ID, SOURCE_TRANSACTION_ID — Planning transaction keys linking to recommendations.

Common Use Cases and Queries

Typical usages include capacity load reports by department or resource, load-rate analysis across planning horizons, and integration extracts feeding external scheduling tools.

To analyze resource loading by rate:

• SELECT ORGANIZATION_ID, DEPARTMENT_ID, RESOURCE_ID, RESOURCE_DATE, RESOURCE_HOURS, LOAD_RATE FROM MRPBV_PLAN_RESOURCE_LOADS WHERE ORGANIZATION_ID = :org_id ORDER BY RESOURCE_DATE;

To review daily load rates for a specific assembly:

• SELECT ASSEMBLY_ITEM_ID, RESOURCE_DATE, DAILY_RESOURCE_HOURS, LOAD_RATE FROM MRPBV_PLAN_RESOURCE_LOADS WHERE ASSEMBLY_ITEM_ID = :item_id;

Because the view applies organization security and excludes RESOURCE_ID = -1, queries consistently return valid planning resource loads suitable for direct reporting.