Search Results mrpfv_plan_schedules

Overview

MRPFV_PLAN_SCHEDULES is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. In the ETRM reference for releases 12.1.1 and 12.2.2, the object is registered as a VALID VIEW and carries the description marker "Retrofitted," indicating that the view was carried forward into the current schema through the ETRM retrofit process rather than being introduced as a new design artifact. Functionally, the view presents a consolidated listing of planning schedules across organizations. It flattens data drawn from production planning configuration (MRP_PLANS), organization-level schedule inputs (MRP_PLAN_SCHEDULES), inventory parameters (MTL_PARAMETERS), organization names (HR_ALL_ORGANIZATION_UNITS), and lookup meanings (MFG_LOOKUPS) into a single queryable surface.

Because the view resolves multiple physical organizations into human-readable organization codes and names, it serves as a convenient reporting and integration layer for planners, BI extracts, and custom concurrent programs that must enumerate the schedules associated with every organization rather than a single planning instance.

Underlying Base Objects

Per the documented 12.2.2 metadata, MRPFV_PLAN_SCHEDULES is defined over the following referenced base objects:

• MRP_PLANS (SYNONYM) — supplies plan-level attributes such as COMPILE_DESIGNATOR, CURR_SCHEDULE_DESIGNATOR, CURR_SCHEDULE_TYPE, and ORGANIZATION_SELECTION.
• MRP_PLAN_SCHEDULES (SYNONYM) — supplies organization-level schedule rows, including INPUT_NAME, INPUT_TYPE, PLAN_LEVEL, and INPUT_ORGANIZATION_ID.
• MTL_PARAMETERS (SYNONYM) — the inventory organization parameters table, joined on ORGANIZATION_ID to source ORGANIZATION_CODE for both the planning organization and any input organization.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — provides the organization NAME used for display alongside the code.
• MFG_LOOKUPS (VIEW) — supplies the MEANING for lookup codes restricted to LOOKUP_TYPE = 'MRP_SCHEDULE_TYPE'.

The view text is a UNION ALL of three branches. The first branch reports plans where NVL(ORGANIZATION_SELECTION,1) = 1. The second branch reports schedule rows where PLAN_LEVEL = 2, joining both the organization and its input organization to MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS. The third branch correlates plan-level and schedule-level designators. Each branch applies a security predicate of the form '_SEC:<alias>.ORGANIZATION_ID' IS NOT NULL, which enforces organization-level access control.

Key Columns

• ORGANIZATION_CODE — organization code from MTL_PARAMETERS, appearing in multiple positions for the organization and, where applicable, the input organization.
• NAME — organization name from HR_ALL_ORGANIZATION_UNITS, aligned to each organization code.
• COMPILE_DESIGNATOR — the plan identifier associated with the schedule.
• CURR_SCHEDULE_DESIGNATOR / INPUT_NAME — the schedule designator, sourced either from the plan's current schedule or from the schedule input name depending on the branch.
• MEANING — decoded schedule type from MFG_LOOKUPS for LOOKUP_TYPE 'MRP_SCHEDULE_TYPE'.
• ORGANIZATION_ID — the planning organization identifier; the view emits this once per branch, with the second occurrence representing the input organization in applicable rows.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns for change tracking and data lineage.

Common Use Cases and Queries

Typical uses include listing all schedules for a planning organization, verifying schedule types via lookup meanings, and feeding organization-aware schedule data into extracts. A representative query:

SELECT organization_code, name, compile_designator,
       curr_schedule_designator, meaning, organization_id,
       last_update_date
FROM   apps.mrpfv_plan_schedules
WHERE  compile_designator = :plan
ORDER BY organization_code;

To audit schedule configuration across organizations, constrain by the decoded meaning or join back to MRP_PLANS on COMPILE_DESIGNATOR. Because access is gated by the embedded _SEC predicates, results automatically reflect the querying user's organization security profile; tests run as a privileged or seeded user may therefore return a different row set than a restricted planner account.