Results for “resource_usage”

2 results




Overview
Explore in AI Chat

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

Overview

MRP_AP_OPERATION_RESOURCES_V is a view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It presents operation resource information as consumed by the Advanced Planning and Scheduling (AP) engine and exposes the relationship between routing operations, resources, and their assigned units. The view is not implemented as a physical database object in the standard install; ETRM documents its metadata as a defined view text rather than a deployed database entity. This status is typical of internal planning views that are referenced during the material requirements planning and scheduling computation cycle to resolve resource consumption at the operation level.

The view’s principal purpose is to expose RESOURCE_UNITS (the assigned units of a resource at a given operation) alongside resource usage, basis type, and unit of measure. Integration and reporting consumers use it to trace resource loading from the routing sequence through to the operation sequence, and to reconcile planned resource consumption against capacity. Because it draws exclusively from MRP/AP snapshot tables (identified by the _SN suffix), it represents a point-in-time snapshot of planning data rather than live transactional data.

Underlying Base Objects

The view is defined over six MRP/AP snapshot tables, joined on organization, item, routing, operation sequence, and resource identifiers:

The joins link the routing header to its operation sequences, each sequence to its operation resources, and each resource to its master definition. Item and parameter snapshots anchor the records to a specific organization and planning run. No physical base tables outside the AP snapshot family are documented, and ETRM lists no separately documented referenced base objects.

Key Columns

  • ROUTING_SEQUENCE_ID — Identifies the routing sequence header.
  • OPERATION_SEQUENCE_ID — Identifies the specific operation within the routing.
  • RESOURCE_SEQ_NUM — Ordering of the resource within the operation.
  • RESOURCE_ID — Foreign key to the resource master.
  • RESOURCE_USAGE — Sourced from USAGE_RATE_OR_AMOUNT, the quantity or rate at which the resource is consumed.
  • BASIS_TYPE — Indicates whether usage is expressed per item or per lot.
  • RESOURCE_UNITS — Sourced from ASSIGNED_UNITS, the number of resource units assigned to the operation; this is the column most directly associated with the user’s search term.
  • UOM_CODE — The unit of measure for the resource, taken from the resource snapshot.

Common Use Cases and Queries

Typical scenarios include capacity analysis, resource-load reconciliation, and validating resource assignments per operation. The following query lists resource assignments for a routing:

  • SELECT routing_sequence_id, operation_sequence_id, resource_seq_num, resource_id, resource_usage, basis_type, resource_units, uom_code FROM mrp_ap_operation_resources_v WHERE routing_sequence_id = :routing_id ORDER BY operation_sequence_id, resource_seq_num;

To aggregate assigned resource units by operation:

  • SELECT operation_sequence_id, SUM(resource_units) total_units FROM mrp_ap_operation_resources_v GROUP BY operation_sequence_id;

Because the view is not implemented in the database, these queries execute only in environments where the AP snapshot objects are populated and the view definition exists. In standard 12.1.1 and 12.2.2 installations, equivalent data is more commonly retrieved from the planning engine’s runtime tables or the routing/resource base tables.