Results for “mrpbv_mrp_plans”

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

Overview

MRPBV_MRP_PLANS is a read-only Oracle EBS view owned by the APPS schema in the Master Scheduling/MRP (MRP) product family. It presents a denormalized, user-facing projection of planning designator definitions joined to their associated organization and plan context. The view is marked "Retrofitted," indicating it was created to preserve a legacy interface while conforming to the multi-org security model. It is defined with a WITH READ ONLY clause, so it is intended strictly for querying and reporting, not for DML. The suffix "BV" typically denotes a business view, and this object surfaces attributes — such as plan name, organization code, descriptive text, feedback flags, pegging flags, and the plan horizon date — that report developers, concurrent programs, and integration layer code can consume. Because the view joins MRP_DESIGNATORS to MRP_PLANS with outer joins on organization and compile designator, it can expose designators even where a corresponding plan row does not yet exist, making it useful for enumerating configured planning environments across organizations. Report consumers frequently target it for plan-horizon and pegging-related inquiries.

Underlying Base Objects

The view is constructed over four documented base objects, all referenced through APPS synonyms: HR_ALL_ORGANIZATION_UNITS, MRP_DESIGNATORS, MRP_PLANS, and MTL_PARAMETERS. The primary FROM clause anchors on MTL_PARAMETERS (PA), joined to HR_ALL_ORGANIZATION_UNITS (AL) on ORGANIZATION_ID to retrieve the organization name. MRP_DESIGNATORS (DE) supplies the plan designator definition and drives the join, filtered by DRP_PLAN = 2. MRP_PLANS (PL) is outer-joined to MRP_DESIGNATORS on both ORGANIZATION_ID and COMPILE_DESIGNATOR, so designators persist even when plan rows are absent. The view also applies a multi-org security predicate on DE.ORGANIZATION_ID, ensuring only permitted organizations are visible. Fields such as FEEDBACK_FLAG, PRODUCTION, CURR_SNAPSHOT_LOCK, CURR_FULL_PEGGING, CURR_RESERVATION_LEVEL, and CURR_HARD_PEGGING_LEVEL are exposed as lookups, with several carrying _LA (lookup attribute) style naming conventions that resolve code values to descriptive meanings at runtime.

Key Columns

• ORGANIZATION_CODE / ORGANIZATION_NAME — Organization identifier shown on the planning organization.
• PLAN_NAME / DESCRIPTION — Plan designator name and its descriptive text.
• "_LA:FEEDBACK_FLAG" / "_LA:PRODUCTION_FLAG" — Lookup-driven YES/NO indicators derived from designator feedback and production settings.
• INACTIVE_DATE — Date on which the designator becomes inactive (DISABLE_DATE in the base table).
• "_LA:SNAPSHOT_LOCK_TABLES" / "_LA:PEGGING_FLAG" — Snapshot lock and full-pegging indicators.
• "_LA:RESERVATION_LEVEL" / "_LA:HARD_PEGGING_LEVEL" — Reservation and hard-pegging level meanings.
• PLAN_HORIZON_DATE — Column corresponding to CURR_CUTOFF_DATE in MRP_PLANS; represents the current planning horizon cutoff date for the plan. This is the column most commonly searched by report authors defining horizon-based queries.
• ASSIGNMENT_SET_ID, ORGANIZATION_ID — Assignment set reference and organization foreign key.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns sourced from MRP_DESIGNATORS.

Common Use Cases and Queries

Typical usage includes listing all active plan designators per organization, resolving the plan horizon date for a given plan, and driving horizon-window reports. A representative query filtering on the horizon date follows:

SELECT ORGANIZATION_CODE, ORGANIZATION_NAME, PLAN_NAME,
       PLAN_HORIZON_DATE, INACTIVE_DATE
  FROM APPS.MRPBV_MRP_PLANS
 WHERE PLAN_HORIZON_DATE >= SYSDATE
 ORDER BY ORGANIZATION_CODE, PLAN_NAME;

To list configured plans with pegging and feedback attributes for a specific organization:

SELECT PLAN_NAME, DESCRIPTION, "_LA:PEGGING_FLAG",
       "_LA:FEEDBACK_FLAG", "_LA:PRODUCTION_FLAG"
  FROM APPS.MRPBV_MRP_PLANS
 WHERE ORGANIZATION_CODE = :org_code;

Because the view enforces multi-org security and is defined READ ONLY, it is safe for concurrent reporting and integration extracts. Report authors should note the quoted lookup columns require double-quote delimiters in SQL. The view does not expose transactional plan output; for supply/demand detail, developers join onward to MRP plan tables using ORGANIZATION_ID and COMPILE_DESIGNATOR as the linkage.