Results for “append_planned_orders”

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

Overview

MRP_PLAN_ORGANIZATIONS_V is a seeded Oracle Application Object Library view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the MRP — Master Scheduling/MRP product family and is documented in ETRM as the "MPS/MRP plan organizations view." The view consolidates planning attributes held on the plan header (MRP_PLANS) with organization-specific planning parameters held on MRP_PLAN_ORGANIZATIONS, producing one row per plan-and-organization combination. Its defining characteristic is the use of the current (CURR_) columns from MRP_PLANS as the default source of planning option values, and the outer-joined values from MRP_PLAN_ORGANIZATIONS as organization-level overrides. In this sense the view behaves as a resolved planning-options perspective rather than a raw table image. It is typically consumed by concurrent programs, planning workbench logic, and custom reporting or integration code that must determine which options — netting, safety stock, WIP, purchasing, simulation set, BOM, and reservation level — are actually in force for a given organization within a given plan.

Underlying Base Objects

ETRM documents the view as defined over two referenced base objects, both exposed to APPS through synonyms: MRP_PLANS (SYNONYM) and MRP_PLAN_ORGANIZATIONS (SYNONYM). The view text confirms this, selecting from MRP_PLAN_ORGANIZATIONS MPO and MRP_PLANS PLANS, with an outer join on MPO characterized by the predicates MPO.PLAN_LEVEL(+) = 2, MPO.COMPILE_DESIGNATOR(+) = PLANS.COMPILE_DESIGNATOR, and MPO.ORGANIZATION_ID(+) = PLANS.ORGANIZATION_ID. Because MRP_PLAN_ORGANIZATIONS is outer-joined, every plan row in MRP_PLANS is preserved, and the NVL expressions substitute plan-level CURR_ values wherever no organization-level row exists. A fixed index hint, /* INDEX(MPO MRP_PLAN_ORGANIZATIONS_U1) */, directs the optimizer to the MRP_PLAN_ORGANIZATIONS unique key index, which is consistent with the join keys above. The join also restricts override rows to PLAN_LEVEL = 2, distinguishing the organization-level planning records from other plan-level rows.

Key Columns

The view exposes 25 columns. ORGANIZATION_ID and COMPILE_DESIGNATOR identify the owning plan and organization context inherited from MRP_PLANS. PLANNED_ORGANIZATION is resolved as NVL(MPO.PLANNED_ORGANIZATION, PLANS.ORGANIZATION_ID), so it returns the organization-level planned organization when present and falls back to the plan organization otherwise. Planning option columns — OPERATION_SCHEDULE_TYPE, PLAN_TYPE, OVERWRITE_OPTION, APPEND_PLANNED_ORDERS, CUTOFF_DATE, PART_INCLUDE_TYPE, PLANNING_TIME_FENCE_FLAG, DEMAND_TIME_FENCE_FLAG, ASSIGNMENT_SET_ID, SCHEDULE_TYPE, PLAN_CAPACITY_FLAG, USE_NEW_PLANNER — are drawn from the corresponding CURR_ columns on MRP_PLANS. The columns most visibly subject to override are NET_RESERVATIONS, PLAN_SAFETY_STOCK, NET_WIP, NET_PURCHASING, SIMULATION_SET, and BILL_OF_RESOURCES, each expressed through NVL against its CURR_ counterpart. ORGANIZATION_SELECTION defaults to 1, and RESERVATION_LEVEL defaults to 4 via NVL(PLANS.CURR_RESERVATION_LEVEL, 4). PLAN_START_DATE and PLAN_COMPLETION_DATE retain their plan-level values for scheduling context.

Common Use Cases and Queries

The view is commonly queried to enumerate every organization a plan spans and to inspect the effective planning options per organization, which supports audit, migration verification, and customized planning reports. Because it resolves overrides, it is preferable to joining the two base tables manually when the goal is to obtain effective values.

• List all plans and their organizations: SELECT compile_designator, organization_id, planned_organization FROM mrp_plan_organizations_v ORDER BY compile_designator, organization_id;
• Inspect netting options for a plan: SELECT organization_id, net_reservations, net_wip, net_purchasing, plan_safety_stock FROM mrp_plan_organizations_v WHERE compile_designator = :plan_id;
• Audit overrides by comparing view values to base MRP_PLAN_ORGANIZATIONS rows for a plan and organization.
• Drive concurrent or integration extracts where per-organization planning behavior must be determined before submitting MPS/MRP.

No DML is permitted against the view; it is read-only and reflects current plan and organization planning state.