Search Results input_designator_name




Overview
Explore in AI Chat

Overview

APPS.MRP_PLAN_SCHEDULES_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that exposes the association between a plan compile designator and the schedule that is currently in effect for a given organization. In the Oracle Advanced Supply Chain Planning (ASCP) and Material Requirements Planning data model, a plan may be compiled multiple times, and each compile produces a designator that references a specific schedule. The "current" schedule for an organization is identified by CURR_SCHEDULE_TYPE and CURR_SCHEDULE_DESIGNATOR on MRP_PLANS. This view flattens those relationships into a single result set, allowing consumers to resolve which schedule is active without navigating the multi-level plan hierarchy directly. It is typically used by planning reports, interfaces, and custom concurrent programs that need to enumerate plan schedules per organization.

Underlying Base Objects

The documented base objects for this view are MRP_PLANS and MRP_PLAN_SCHEDULES, both referenced through APPS synonyms. The view is a UNION ALL of three SELECT branches, each contributing rows from a different perspective of the same relationship:

  • Branch 1 — MRP_PLANS (plan-level rows): Selects ORGANIZATION_ID, COMPILE_DESIGNATOR, CURR_SCHEDULE_TYPE, and CURR_SCHEDULE_DESIGNATOR from MRP_PLANS where NVL(ORGANIZATION_SELECTION, 1) = 1. This restricts the result to plans whose organization selection flag is 1 (or null), i.e., plans that are not explicitly restricted to a different organization scope.
  • Branch 2 — MRP_PLAN_SCHEDULES (schedule-level rows): Selects ORGANIZATION_ID, COMPILE_DESIGNATOR, INPUT_TYPE, INPUT_ORGANIZATION_ID, and INPUT_NAME where PLAN_LEVEL = 2. This branch surfaces the schedule hierarchy one level below the top plan level, using MRP_PLAN_SCHEDULES columns to populate the same five-column projection.
  • Branch 3 — Self-join of MRP_PLANS: Joins MRP_PLANS to itself on PLANS1.ORGANIZATION_ID = PLANS2.ORGANIZATION_ID and PLANS1.CURR_SCHEDULE_DESIGNATOR = PLANS2.COMPILE_DESIGNATOR, again filtering with NVL(PLANS1.ORGANIZATION_SELECTION, 1) = 1. This resolves the link between a plan's current schedule designator and the compile designator of the referenced schedule.

Because the three branches are combined with UNION ALL, duplicated rows are preserved; consumers should apply DISTINCT or additional predicates where uniqueness is required.

Key Columns

  • ORGANIZATION_ID — The inventory organization for which the plan and schedule association is defined. In branch 3 this comes from PLANS1; in branch 2 from MRP_PLAN_SCHEDULES.
  • COMPILE_DESIGNATOR — The identifier of the plan compile instance. In branch 3 this is PLANS1.COMPILE_DESIGNATOR, matching PLANS1.CURR_SCHEDULE_DESIGNATOR of the paired plan.
  • CURR_SCHEDULE_TYPE — The type of the currently active schedule for the organization (for example the schedule classification defined in the planning data model). This is the column most commonly searched for as "curr_schedule_type".
  • CURR_SCHEDULE_DESIGNATOR — The designator of the current schedule, i.e., the reference to the schedule that the plan currently points to. In branch 2 the analogous value is drawn from INPUT_NAME / INPUT_ORGANIZATION_ID.
  • INPUT_TYPE / INPUT_ORGANIZATION_ID / INPUT_NAME — Populated only from MRP_PLAN_SCHEDULES (branch 2), describing the input schedule's type, owning organization, and name.

Common Use Cases and Queries

Typical scenarios include determining the active schedule for each organization before running a planning report, reconciling compile designators across plans, and driving custom extracts that must align to the schedule currently referenced by a plan.

List current schedule types per organization:

SELECT organization_id,
       compile_designator,
       curr_schedule_type,
       curr_schedule_designator
  FROM apps.mrp_plan_schedules_v
 WHERE organization_id = :p_org_id;

Find all rows referencing a specific schedule type:

SELECT DISTINCT organization_id,
       compile_designator,
       curr_schedule_designator
  FROM apps.mrp_plan_schedules_v
 WHERE curr_schedule_type = :p_schedule_type;

Resolve schedules at the lower plan level (branch 2 rows):

SELECT organization_id,
       compile_designator,
       input_type,
       input_organization_id,
       input_name
  FROM apps.mrp_plan_schedules_v
 WHERE input_name IS NOT NULL;

Because the view is defined with UNION ALL and filters only on the organization selection flag and PLAN_LEVEL = 2, queries should add DISTINCT or explicit predicates when a one-to-one schedule resolution is required.