Results for “mrpbv_drp_plans”

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

Overview

MRPBV_DRP_PLANS is a read-only APPS view in the Oracle E-Business Suite 12.1.1 / 12.2.2 environment, owned by the APPS schema and belonging to the MRP (Master Scheduling/MRP) product family. It is a "retrofitted" view — a compatibility construct created so that Oracle Applications forms, reports, and concurrent programs can reference a business entity (Distribution Resource Planning plans) without coding directly against physical tables. The view presents a consolidated, user-presentable picture of Distribution Resource Planning plan definitions at the organization level, joining organization parameters, organization names, designator attributes, and current plan state. Because it exposes descriptive attributes rather than operational flags used for internal processing, it is chiefly consumed by inquiry screens, descriptive flexfield-driven lookups, and ad-hoc reporting. Users searching for plan_horizon_date will find that this column maps to MRP_PLANS.CURR_CUTOFF_DATE, the plan's planning horizon cutoff date for the current plan instance.

Underlying Base Objects

The view is defined over four base objects, each referenced through a synonym in 12.2.2:

• MTL_PARAMETERS (PA) — supplies the organization code via ORGANIZATION_CODE.
• HR_ALL_ORGANIZATION_UNITS (AL) — provides the organization NAME exposed as ORGANIZATION_NAME.
• MRP_DESIGNATORS (DE) — the driving table, restricted by DE.DRP_PLAN = 1 so that only DRP-enabled designators qualify.
• MRP_PLANS (PL) — joined to MRP_DESIGNATORS by ORGANIZATION_ID and COMPILE_DESIGNATOR using an outer join (+).

All joins are equijoins on ORGANIZATION_ID, and the designator-to-plan join is outer, meaning DRP designators without a matching plan row still appear. The organizational security predicate '_SEC:DE.ORGANIZATION_ID' IS NOT NULL enforces Multi-Org access. The view is defined WITH READ ONLY, so it supports queries only.

Key Columns

• ORGANIZATION_CODE / ORGANIZATION_NAME — warehouse or organization identifiers from MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS.
• PLAN_NAME, DESCRIPTION, INACTIVE_DATE — designator-level identifiers and lifecycle attributes from MRP_DESIGNATORS.
• PLAN_HORIZON_DATE — the current plan cutoff date (CURR_CUTOFF_DATE) from MRP_PLANS.
• ASSIGNMENT_SET_ID — the current plan assignment set (CURR_ASSIGNMENT_SET_ID).
• FEEDBACK_FLAG, PRODUCTION_FLAG — lookups resolved against MFG_LOOKUPS SYS_YES_NO for readability.
• SNAPSHOT_LOCK_TABLES, PEGGING_FLAG, RESERVATION_LEVEL, HARD_PEGGING_LEVEL — plan-level control attributes resolved via MRP lookups.
• ORGANIZATION_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — audit and key columns.

Common Use Cases and Queries

Typical scenarios include listing all DRP plans for an organization, reviewing horizon dates across warehouses, and feeding downstream reporting. Example queries:

• Plans approaching the horizon: SELECT plan_name, organization_code, plan_horizon_date FROM apps.mrpbv_drp_plans WHERE plan_horizon_date > SYSDATE;
• Organization-scoped inventory of DRP plans: SELECT organization_code, organization_name, plan_name FROM apps.mrpbv_drp_plans WHERE organization_id = :org_id;
• Reservation and pegging configuration review: SELECT plan_name, "_LA:RESERVATION_LEVEL", "_LA:HARD_PEGGING_LEVEL" FROM apps.mrpbv_drp_plans ORDER BY plan_name;

Because the view is read-only and governed by Multi-Org security, queries automatically return only plans for organizations the session is authorized to access.