Results for “cutoff_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.MRP_ORGANIZATIONS_V is a public Oracle E-Business Suite view owned by the APPS schema and shipped as part of the MRP (Master Scheduling/MRP) product family. As documented in ETRM for releases 12.1.1 and 12.2.2, its status is VALID and its purpose is to expose the MPS/MRP plans defined for an organization together with the organization against which each plan is actually executed. The view resolves the relationship between a plan's owning organization (the organization that owns the plan definition in MRP_PLANS) and the planned organization (the organization whose supply and demand the plan processes), so that report, inquiry, and integration logic can address a plan by its effective planning organization rather than by its definitional owner alone.

Because it is a view rather than a table, it carries no storage of its own; it is a read-only projection intended for concurrent program reports, custom SQL, and inbound/outbound integrations that need a compact list of plan-to-organization assignments.

Underlying Base Objects

The documented base objects are MRP_PLANS and MRP_PLAN_ORGANIZATIONS, both referenced through public synonyms in the APPS schema. The view text is a UNION of two queries:

• First branch — joins MRP_PLAN_ORGANIZATIONS MPO to MRP_PLANS PLANS on ORGANIZATION_ID and COMPILE_DESIGNATOR, with the constraint MPO.PLAN_LEVEL = 2. The outer-join syntax ((+)) means this branch returns only plan-level-2 organizational rows.
• Second branch — selects directly from MRP_PLANS and substitutes PLANS.ORGANIZATION_ID as the planned organization.

The UNION de-duplicates results. Effectively, MRP_PLAN_ORGANIZATIONS details are used where they exist at plan level 2; otherwise the plan's own organization is returned. This design accommodates single-organization plans and multi-organization (plan-level) plans within one consistent result set.

Key Columns

• ORGANIZATION_ID — the organization that owns the plan definition in MRP_PLANS; identifies the plan's home organization.
• COMPILE_DESIGNATOR — the plan name (compile designator). Together with ORGANIZATION_ID, it forms the logical key of a plan.
• PLANNED_ORGANIZATION — the organization actually planned. Resolved via NVL(MPO.PLANNED_ORGANIZATION, PLANS.ORGANIZATION_ID), so it falls back to the plan owner when no plan-organization row exists.
• CUTOFF_DATE — exposed from PLANS.CURR_CUTOFF_DATE; the current cutoff date for the plan, governing the scheduling horizon boundary.
• PLAN_COMPLETION_DATE — exposed from PLANS.PLAN_COMPLETION_DATE; the timestamp at which the plan last completed a planning run.

Common Use Cases and Queries

Typical uses include building LOVs of available plans, driving custom reports of plan status, and feeding planning metadata into downstream integrations. To list plans with their effective planned organization:

• SELECT organization_id, compile_designator, planned_organization, cutoff_date, plan_completion_date FROM apps.mrp_organizations_v ORDER BY organization_id, compile_designator;
• To restrict to plans that have completed at least one run: add WHERE plan_completion_date IS NOT NULL.
• To identify multi-organization plans where the planned organization differs from the owning organization: WHERE planned_organization <> organization_id.

Joins to MRP_PLANS on ORGANIZATION_ID and COMPILE_DESIGNATOR provide access to additional plan attributes, while joins to HR_ALL_ORGANIZATION_UNITS resolve organization names for reporting.