Search Results mrp_i2_part_master_v




Overview
Explore in AI Chat

Overview

MRP_I2_PART_MASTER_V is a database view shipped within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. Its documented purpose is to serve as a "Rhythm view" that supplies information regarding parts planned in Rhythm. In the context of Oracle EBS 12.1.1 and 12.2.2, this view belongs to the integration surface used by Oracle's advanced planning and scheduling offerings (historically associated with the Rhythm collaborative planning products, including Advanced Supply Chain Planning and related planning engines), which read item master and planning attribute data from the transactional EBS schema and expose it in a denormalized, planning-friendly structure.

Unlike core application views such as MTL_SYSTEM_ITEMS_B, MRP_I2_PART_MASTER_V is not a general-purpose item inquiry view. It is a targeted interface construct: it assembles the subset of item attributes that a planning engine requires, applies organization-specific parameter defaults, and normalizes several optional columns so that downstream planning processes receive consistent values. Because it is documented as "not implemented in this database" in the ETRM metadata excerpt, its presence and population depend on whether the relevant planning integration components have been deployed. It is therefore best understood as an interface view rather than a reporting view for end users.

Underlying Base Objects

The documented view text defines MRP_I2_PART_MASTER_V over two referenced objects:

  • MRP_RHX_PLANNED_ITEMS_V — the primary source of item and planning attribute data, aliased as I in the view definition. This view supplies item identifiers, description, organization, planning make/buy code, lead times, time fence values, lot sizing attributes, planner code, and item attributes.
  • MFG_LOOKUPS — joined as LU to resolve the planning make/buy code into a translatable meaning. The join is constrained by LOOKUP_TYPE = 'MTL_PLANNING_MAKE_BUY' and matches LOOKUP_CODE to the item's PLANNING_MAKE_BUY_CODE.

The ETRM documented metadata lists no base tables for this view, since MRP_RHX_PLANNED_ITEMS_V is itself a view. The view also calls the helper function MRP_I2_ERP.GET_PARAMETER to retrieve organization-level planning parameters, including DEFAULT_PLANNING_TF_OFFSET, CONSIDER_DEMAND_TF, and MRP_I2_P_BUF_STYLE_ATTR_NUM. A filter restricts output to items whose MRP_PLANNING_CODE is one of 3, 4, 7, or 8, which corresponds to items actively planned by the MRP planning process.

Key Columns

Common Use Cases and Queries

This view is primarily consumed by the Rhythm planning integration and by developers diagnosing planning data issues. Typical scenarios include verifying which items are eligible for planning, auditing derived time fence and lead-time values, and confirming lot-sizing defaults.

Example query listing planned parts with make/buy meaning:

  • SELECT PART_NUMBER, ORGANIZATION_ID, MAKE_OR_BUY_MEANING, PLANNER_CODE FROM MRP_I2_PART_MASTER_V WHERE ORGANIZATION_ID = 101;

Example query auditing time fence and lead-time derivation for a specific item:

  • SELECT PART_NUMBER, PLANNING_TIME_FENCE_DAYS, DEMAND_TIME_FENCE_DAYS, RELEASE_TIME_FENCE_DAYS FROM MRP_I2_PART_MASTER_V WHERE PART_NUMBER = 'AS54888';

Because output is filtered to planning-relevant items and depends on organization parameters, results can differ across organizations and after parameter changes, making the view valuable for reconciliation between the item master and the planning engine's view of the same parts.