Results for “mrp_web_horizontal_plan_v”

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

Overview

MRP_WEB_HORIZONTAL_PLAN_V is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) module, valid in both 12.1.1 and 12.2.2. Its documented description is "Horizontal Plan Information for Web Inquiries," which identifies its purpose: it supplies the denormalized, browser-ready dataset consumed by the MRP Web inquiry pages and related HTML-based planners. A horizontal plan presents planning bucketed quantities along a timeline, one column per bucket, rather than the vertical, one-row-per-bucket layout of the underlying planning tables. This view performs that pivot so that web-tier components can render the plan grid without additional row-to-column transformation logic. Because it is a view rather than a table, it stores no data of its own; all content is derived at runtime from the Material Planner Workbench and material plan tables, making it a read-only reporting and integration surface. It is not part of the documented public interface for external transactions and should be treated as an internal view supporting the MRP web inquiry layer.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: MRP_WORKBENCH_BUCKET_DATES and MRP_MATERIAL_PLANS (both accessed through synonyms), MTL_PARAMETERS, and the views MRP_PROJECT_V and MRP_TASK_V. Supporting packages include FND_PROFILE, MRP_GET_PROJECT, PA_CROSS_BUSINESS_GRP, PA_PROJECT_UTILS, PA_SECURITY, and PA_TASK_UTILS. The view text confirms a UNION ALL of two branches. The first branch selects DISTINCT rows from MRP_WORKBENCH_BUCKET_DATES joined to MRP_MATERIAL_PLANS, MTL_PARAMETERS, MRP_PROJECT_V and MRP_TASK_V, filtered to BUCKET_TYPE = 2, and emits the bucket dates as character-formatted DATE1 through DATE36 columns with placeholder NULLs where quantities or plan types would normally appear. The second branch reads the material plan rows (PLANS) and emits the horizontal plan quantities as QUANTITY1 through QUANTITYn, each converted with TO_CHAR, together with the plan type and plan type text. The dates branch and the quantities branch are aligned column-for-column by position so that the UNION ALL produces a single consistent result shape.

Key Columns

• PLANNED_ORGANIZATION / ORGANIZATION_ID: The planning organization for which the bucket dates or plan rows apply; MTL_PARAMETERS supplies the corresponding ORGANIZATION_CODE.
• COMPILE_DESIGNATOR: Identifies the plan compilation (the named plan) whose data is being presented.
• INVENTORY_ITEM_ID and ITEM_SEGMENTS: The planned item identifier and its concatenated segment display value.
• HORIZONTAL_PLAN_TYPE / HORIZONTAL_PLAN_TYPE_TEXT: Numeric and descriptive codes classifying each horizontal plan row.
• DATE1 … DATE36: Bucket date labels produced by the dates branch, formatted as character strings for direct web display.
• QUANTITY1 … QUANTITYn: Bucketed planning quantities produced by the material plan branch, each cast to character.
• PLANNING_GROUP, PROJECT_ID, TASK_ID, PROJECT_NUMBER, TASK_NUMBER: Project and task context derived from MRP_PROJECT_V and MRP_TASK_V, with NVL defaults of '-', -1 and -1 where no project or task association exists.

Common Use Cases and Queries

Typical use is diagnostic and reporting-oriented: verifying what a specific plan shows for an item across buckets, reconciling web-displayed quantities against MRP_MATERIAL_PLANS, and building custom extracts that require the horizontal layout. A representative query retrieves all rows for one plan and item:

• SELECT organization_code, compile_designator, item_segments, horizontal_plan_type_text, quantity1, quantity2, quantity3 FROM apps.mrp_web_horizontal_plan_v WHERE compile_designator = :plan AND item_segments = :item;
• SELECT DISTINCT organization_code, compile_designator, item_segments FROM apps.mrp_web_horizontal_plan_v WHERE organization_id = :org_id; — enumerate planned items for an organization.
• SELECT item_segments, date1, date2, date3 FROM apps.mrp_web_horizontal_plan_v WHERE compile_designator = :plan AND quantity1 IS NULL; — inspect the bucket-date branch rows where quantity placeholders are NULL.

Because the view reads live planning data and depends on MRP and PA security packages, results reflect the current plan compilation and the querying user's project security profile; recompilation of the plan changes the rows returned.