Search Results mrp_ap_op_resource_seqs_v




Overview
Explore in AI Chat

Overview

MRP_AP_OP_RESOURCE_SEQS_V is a view within the Oracle EBS Master Scheduling/MRP (MRP) module. Its name follows the convention of the "MRP_AP" family of objects, which are the Application Program interface (API) components used by the MRP engine to read shop-floor routing and resource data during the planning and scheduling cycle. The view presents a flattened, join-ready projection of operation sequence data combined with resource sequence assignments, enabling the MRP engine (and reporting or integration routines) to evaluate which resources are attached to a given operation sequence, their scheduling behaviour, and their offset percentages.

In Oracle EBS 12.1.1 and 12.2.2, this object belongs to the MRP schema. Per the ETRM metadata, it is documented as "Not implemented in this database," meaning it is defined in the database dictionary but is not populated or used in every EBS instance. The object is a view, not a base table, and exposes no independently governed primary key. It is a derived read-only structure compiled from the underlying MRP_AP staging tables.

Underlying Base Objects

The view text shows it is defined over five source objects, all of which are the MRP "AP" staging snapshots:

The join conditions tie items to routings, routings to operation sequences, operation sequences to operation resources, and the organization to MRP parameters. Although the ETRM record lists "Referenced base objects: none documented," the view text clearly establishes these five staging snapshots as its effective sources. The "SN" suffix indicates snapshot tables refreshed by the snapshot loader before a planning run. The "RN" columns are internal row-number artifacts used during the snapshot merge process.

Key Columns

  • ROUTING_SEQUENCE_ID — Identifier of the routing sequence to which the operation belongs.
  • OPERATION_SEQUENCE_ID — Identifier linking the operation sequence to its assigned resources.
  • RESOURCE_SEQ_NUM — Sequence number of the resource within the operation resource list.
  • SCHEDULE_FLAG — Indicates whether the resource is considered during scheduling.
  • RESOURCE_OFFSET_PERCENT — Percentage offset applied to the resource relative to the operation start (also called resource offset percent).
  • DEPARTMENT_ID — The department that owns the operation sequence.

Internal columns RN1 through RN5 correspond to the row numbers from the source snapshots and are generally not referenced by consumers.

Common Use Cases and Queries

Typical uses include MRP internal processing, resource-capacity analysis, and diagnostic reporting of routing/resource relationships. Because the view is documented as not implemented in this database, a query must be tested against the target instance; if the view resolves, it can be joined to item and department views for reporting.

  • List resources with scheduling flags and offsets for a given routing sequence.
  • Audit department assignment of operation resources across items.
  • Validate snapshot consistency between items, routings, and operation sequences before a planning run.
SELECT ROUTING_SEQUENCE_ID,
       OPERATION_SEQUENCE_ID,
       RESOURCE_SEQ_NUM,
       SCHEDULE_FLAG,
       RESOURCE_OFFSET_PERCENT,
       DEPARTMENT_ID
  FROM MRP_AP_OP_RESOURCE_SEQS_V
 WHERE ROUTING_SEQUENCE_ID = :routing_seq_id
 ORDER BY OPERATION_SEQUENCE_ID, RESOURCE_SEQ_NUM;

When the view is unavailable or unpopulated, equivalent output can be assembled directly from the underlying MRP_AP_OPR_RESS_SN, MRP_AP_OPR_SEQS_SN, and MRP_AP_OPR_RTNS_SN snapshots using the join structure documented above.