Search Results mrp_ap_shift_times_v




Overview
Explore in AI Chat

Overview

The view MRP_AP_SHIFT_TIMES_V belongs to the Oracle Master Scheduling/MRP (MRP) product family and exposes shift-time definitions associated with a manufacturing calendar. It is one of the auxiliary "AP" (Advanced Planning) reporting views that surface the internal shift and resource-parameter records used by the planning and capacity engines. The view presents, for each calendar code and shift number, the shift start and end times together with a set of derived ranking columns sourced from material-parameter and MRP-parameter snapshot tables. Its principal role is to give reporting and integration consumers a denormalized, read-only window into shift-time data without requiring direct joins against the underlying snapshot tables.

The ETRM metadata records that the view is not implemented in this database, meaning it exists as a seeded Oracle Applications object definition rather than as a customer-specific modification. This is consistent with standard EBS 12.1.1 and 12.2.2 behavior, where many shipping/reporting views are defined in the application schema and are usable only when the relevant snapshot data exists.

Underlying Base Objects

The documented view text is defined over three objects:

The two parameter snapshots are joined to each other on ORGANIZATION_ID and grouped by CALENDAR_CODE to yield the highest rank per calendar. That derived inline view (Y) is then joined to the shift-times snapshot (X) on the shared CALENDAR_CODE. The ETRM metadata lists no separately documented referential constraints, and the two parameter tables are correlated by organization rather than by calendar in the inner query, with the calendar grouping applied at the outer level.

The user search term "mrp_ap_mtl_paras_sn" corresponds to MRP_AP_MTL_PARAS_SN, one of the referenced base objects, confirming that this view is the join path that connects material-parameter snapshot data to shift-time definitions.

Key Columns

  • CALENDAR_CODE — identifier of the manufacturing/planning calendar to which the shift belongs; the principal join key across all three underlying objects.
  • SHIFT_NUM — the ordinal number of the shift within the calendar (for example, shift 1, 2, or 3).
  • FROM_TIME — the start time of the shift.
  • TO_TIME — the end time of the shift.
  • RN3 — rank value carried from the shift-times snapshot record.
  • RN2 — maximum rank derived from MRP_AP_MTL_PARAS_SN for the calendar.
  • RN1 — maximum rank derived from MRP_AP_MRP_PARAS_SN for the calendar.

Common Use Cases and Queries

Typical uses include validating shift schedules against planning parameters, extracting calendar shift windows for capacity or scheduling reports, and reconciling snapshot ranks between the material- and MRP-parameter tables. A representative query is:

  • SELECT CALENDAR_CODE, SHIFT_NUM, FROM_TIME, TO_TIME, RN1, RN2, RN3 FROM MRP_AP_SHIFT_TIMES_V WHERE CALENDAR_CODE = :calendar_code ORDER BY SHIFT_NUM;
  • SELECT CALENDAR_CODE, MIN(FROM_TIME), MAX(TO_TIME), COUNT(*) FROM MRP_AP_SHIFT_TIMES_V GROUP BY CALENDAR_CODE;
  • SELECT v.* FROM MRP_AP_SHIFT_TIMES_V v WHERE v.RN1 = v.RN2; to isolate calendars whose parameter snapshots are aligned.

Because the underlying _SN tables are snapshot objects, availability of rows depends on the planning snapshot being populated in the environment. Query results should be treated as point-in-time and refreshed in line with the MRP snapshot cycle.