Search Results auto_lot_alpha_prefix

Overview

The view MRP_RHX_PLANNED_ITEMS_V belongs to the Oracle E-Business Suite Master Scheduling/MRP (MRP) module and is part of the Oracle Integration Toolkit (often referred to internally by the "RHX" prefix, denoting the "Report/Repository HTML eXtension" style of standardized, denormalized integration views). It exposes a consolidated, reporting-friendly snapshot of planned items — that is, inventory items that participate in a given master production schedule or material requirements plan. Because planning decisions depend on a broad set of item attributes (make/buy codes, lead times, fences, safety stock rules, lot sizing controls, and planner/buyer assignments), the view flattens these attributes into a single queryable surface, sparing the consumer the burden of joining dozens of MTL and MRP tables manually.

In Oracle EBS 12.1.1 and 12.2.2, the Oracle Integration Toolkit views are intended not for the transactional application screens but for external integration, data warehouse, and custom reporting consumption. They present a stable column contract that integration developers and BI tools can rely on, insulating them from frequent underlying schema changes.

Underlying Base Objects

Per the ETRM metadata, this view has no documented referenced base objects — the metadata explicitly records "none documented." This is characteristic of the Integration Toolkit views, whose definitions are frequently generated and whose source tables (the MTL_SYSTEM_ITEMS family, MTL_ITEM_FLEXFIELDS, and related planning tables providing fields such as MRP_PLANNING_CODE, WIP_SUPPLY_TYPE, and the lead-time columns) are referenced indirectly. The view text shown in the documentation references an internal alias, MIF, which corresponds to the item/master-item source, and calls two helper functions — MRP_RHX_UTILITIES.GET_CAT_ID and MRP_RHX_UTILITIES.GET_CAT_NAME — to derive category identifiers and names at runtime rather than through a stored join. The metadata notes the object is "Not implemented in this database," meaning it is defined in the toolkit but not necessarily deployed in every environment, a fact integration developers must verify before referencing it in custom code.

Key Columns

The view exposes a wide range of planning-relevant attributes. Notable columns include:

• CONCATENATED_SEGMENTS — the item's concatenated, flexfield-formatted identifier, the human-readable item key.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, BASE_ITEM_ID — the primary keys identifying the item and the inventory organization context.
• DESCRIPTION — the item description.
• PLANNING_MAKE_BUY_CODE, WIP_SUPPLY_TYPE, BOM_ITEM_TYPE — determine whether the item is manufactured, purchased, or both, and how WIP supplies it.
• MRP_PLANNING_CODE, INVENTORY_PLANNING_CODE — whether MRP, MPS, or no planning applies.
• Lead-time columns — FULL_LEAD_TIME, CUMULATIVE_TOTAL_LEAD_TIME, CUM_MANUFACTURING_LEAD_TIME, FIXED_LEAD_TIME, VARIABLE_LEAD_TIME, PREPROCESSING_LEAD_TIME, POSTPROCESSING_LEAD_TIME.
• Fence columns — derived planning and demand time fences computed via DECODE logic on PLANNING_TIME_FENCE_CODE and DEMAND_TIME_FENCE_CODE.
• Safety stock and lot sizing — MRP_SAFETY_STOCK_CODE, MRP_SAFETY_STOCK_PERCENT, SAFETY_STOCK_BUCKET_DAYS, FIXED_ORDER_QUANTITY, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, ROUNDING_CONTROL_TYPE, STD_LOT_SIZE.
• Planner and buyer — PLANNER_CODE, BUYER_ID.
• Flags — CUSTOMER_ORDER_FLAG, PURCHASING_ENABLED_FLAG, BUILD_IN_WIP_FLAG, REPLENISH_TO_ORDER_FLAG, MTL_TRANSACTIONS_ENABLED_FLAG.

Common Use Cases and Queries

Typical uses include feeding planning attributes into an external planning engine, building item-level planning dashboards, or auditing lead-time and lot-sizing setups across organizations.

• List planned make items in an organization:

  SELECT CONCATENATED_SEGMENTS, DESCRIPTION, PLANNING_MAKE_BUY_CODE
  FROM   MRP_RHX_PLANNED_ITEMS_V
  WHERE  ORGANIZATION_ID = :org_id
  AND    MRP_PLANNING_CODE IS NOT NULL;

• Audit safety stock and lot-sizing setup:

  SELECT CONCATENATED_SEGMENTS, MRP_SAFETY_STOCK_CODE,
         MRP_SAFETY_STOCK_PERCENT, FIXED_ORDER_QUANTITY
  FROM   MRP_RHX_PLANNED_ITEMS_V
  WHERE  ORGANIZATION_ID = :org_id;

• Extract lead-time data for integration: select the cumulative and fixed lead-time columns joined to item identifiers to publish to an external system.

Because the object may not be deployed in every database, developers should confirm its presence in the target instance and validate column availability before relying on it in production reports or interfaces.