Search Results mrp_plan_schedules_v




Overview
Explore in AI Chat

Overview

MRP_PLAN_SCHEDULES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the MRP (Master Scheduling/MRP) product family and presents supply and demand schedule information for planners. The view consolidates schedule identifiers — the compile designator, the current schedule type, and the current schedule designator — across multiple planning contexts, so that a single query can enumerate every schedule a planner may need to reference, whether that schedule is defined directly on a plan or assigned to a specific organization within a plan.

Because the view is defined with a UNION ALL of three separate SELECT statements, it acts as a harmonized projection rather than a simple table wrapper. It exposes a consistent column shape regardless of which internal source produced the row, which makes it well suited as a lookup source for concurrent programs, custom reports, and integrations that must resolve a plan name, schedule type, and organization into a single schedule reference. The user search term curr_schedule_type maps directly to the view's CURR_SCHEDULE_TYPE column, one of its primary output attributes.

Underlying Base Objects

The documented base objects are the synonyms MRP_PLANS and MRP_PLAN_SCHEDULES, both resolving to objects in the MRP schema. The view definition combines them as follows:

  • First branch — MRP_PLANS: Selects ORGANIZATION_ID, COMPILE_DESIGNATOR, CURR_SCHEDULE_TYPE, ORGANIZATION_ID, and CURR_SCHEDULE_DESIGNATOR where NVL(ORGANIZATION_SELECTION, 1) = 1. This yields plan-level schedules for plans whose organization selection defaults to, or is explicitly, 1.
  • Second branch — MRP_PLAN_SCHEDULES: Selects ORGANIZATION_ID, COMPILE_DESIGNATOR, INPUT_TYPE, INPUT_ORGANIZATION_ID, and INPUT_NAME where PLAN_LEVEL = 2. This supplies organization-level schedule inputs defined inside a plan.
  • Third branch — MRP_PLANS self-join: Joins two instances of MRP_PLANS on ORGANIZATION_ID and on PLANS1.CURR_SCHEDULE_DESIGNATOR = PLANS2.COMPILE_DESIGNATOR, again filtered by NVL(ORGANIZATION_SELECTION, 1) = 1. This resolves the schedule chain, matching each plan's current schedule designator to the plan that defines it.

Each branch contributes five positional columns that align to the view's column list.

Key Columns

  • ORGANIZATION_ID: The inventory organization to which the schedule row applies. For the second branch this is the organization of the plan schedule record itself.
  • COMPILE_DESIGNATOR: The plan or schedule identifier used as the compile key. In the self-join branch it is drawn from the second plan instance.
  • CURR_SCHEDULE_TYPE (INPUT_DESIGNATOR_TYPE): The schedule type in effect — for example a plan's current schedule type from MRP_PLANS, or the INPUT_TYPE from MRP_PLAN_SCHEDULES. This is the column planners filter on when identifying a schedule's classification.
  • INPUT_ORGANIZATION_ID: For organization-level schedule inputs, the source organization supplying the schedule; in the first and third branches it carries the plan's ORGANIZATION_ID.
  • INPUT_DESIGNATOR_NAME: The schedule or plan name, derived from CURR_SCHEDULE_DESIGNATOR or INPUT_NAME depending on the branch.

Common Use Cases and Queries

Typical uses include resolving a plan name and organization into the correct schedule type, populating LOVs for planner-facing forms and concurrent programs, and driving custom supply/demand reports. A representative query filtering on the search term is:

  • SELECT organization_id, compile_designator, input_designator_type, input_organization_id, input_designator_name FROM apps.mrp_plan_schedules_v WHERE input_designator_type = '&curr_schedule_type' ORDER BY organization_id, compile_designator;
  • To list all schedules for a single plan or organization: SELECT * FROM apps.mrp_plan_schedules_v WHERE organization_id = :org_id;
  • Join the view to MRP_PLANS or to MRP_SCHEDULE_DATES to correlate schedule context with planning dates, or use it in a BI Publisher data set as the schedule lookup for a planner dashboard.

Because the view is built on UNION ALL, no de-duplication is performed; consumers should expect a row per contributing schedule source and apply DISTINCT or restrictive predicates as needed.