Search Results maximum_order_quantity




Overview
Explore in AI Chat

Overview

The view MRP_I2_PART_SUPPLIER_V is a Rhythm-family database object delivered within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It is designed to expose sourcing information that links inventory items to their approved vendor list, as derived from autosource rules. Functionally, the view flattens planning-related item attributes into a single result set alongside the resolved supplier name, making it convenient for reporting, integration, and downstream planning logic that needs to know which supplier is associated with a given item and organization.

Because the object name carries the MRP_I2_ prefix, it belongs to a family of interchangeable (I2) compatibility views that Oracle supplies to abstract and normalize underlying planning data. Rather than requiring consumers to join the item master to supplier tables directly, the view encapsulates that join logic and gracefully handles items that have no qualified supplier by substituting an "undefined vendor" placeholder. This design supports consistent results across the ETRM (Enterprise Resource Planning and Transactional Management) reporting layer in both 12.1.1 and 12.2.2.

Note that the ETRM documentation records this view as "Not implemented in this database" for the captured environment, which indicates the view may be created only in certain configurations or not physically present in all instances. The view text and column metadata, however, remain authoritative references for its intended structure.

Underlying Base Objects

The view is not defined directly over base tables but is constructed as a UNION ALL of two queries. The documented referenced base objects are listed as "none documented," reflecting the layer of compatibility views interposed between this object and the physical schema. The first query joins two underlying views:

  • MRP_RHX_ITEM_SUPPLIERS_V (aliased ISV) — supplies the approved supplier name and organization context.
  • MRP_I2_PART_MASTER_V (aliased PM) — supplies the planning item attributes such as lead time and lot-sizing parameters.

The join is performed on ORGANIZATION_ID and INVENTORY_ITEM_ID, with additional date-window predicates that compare START_DATE and END_DATE against the current planning start date returned by MRP_I2_ERP.GET_START_DATE. The second query selects from MRP_I2_PART_MASTER_V alone for items whose MAKE_OR_BUY_CODE is 2 (buy items) and for which no active supplier row exists, substituting the parameterized value from MRP_I2_ERP.GET_PARAMETER('MRP_I2_L_UNDEFINED_VENDOR', ...) as the vendor name. This structure ensures a vendor is always returned for buy items, even in the absence of a defined autosource-approved supplier.

Key Columns

  • PART_NUMBER — The user-facing item number.
  • INVENTORY_ITEM_ID — The internal unique identifier for the item; used in all joins.
  • ORGANIZATION_ID — The inventory organization context.
  • LEADTIME — Item lead time, computed as LEADTIME + NVL(POSTPROCESSING_LEADTIME, 0).
  • MINIMUM_ORDER_QUANTITY — Minimum quantity that may be ordered for the item.
  • MAXIMUM_ORDER_QUANTITY — Maximum order quantity permitted; the column referenced by users investigating order-quantity planning constraints.
  • FIXED_DAYS_SUPPLY — Fixed supply interval in days used by planning calculations.
  • INCREMENTAL_LOT_SIZE — The lot-size increment applied when orders are rounded.
  • UOM — Unit of measure for the item.
  • VENDOR_NAME — Approved supplier name, or the undefined-vendor placeholder when no active supplier applies.

Common Use Cases and Queries

A frequent scenario is validating maximum order quantity constraints per item and supplier. A representative query is:

SELECT part_number, organization_id, vendor_name, minimum_order_quantity, maximum_order_quantity FROM mrp_i2_part_supplier_v WHERE maximum_order_quantity IS NOT NULL ORDER BY part_number;

Other practical uses include identifying buy items that fall back to the undefined vendor, reconciling autosource-approved supplier assignments, and exporting lead-time and lot-sizing attributes for planning integrations. Because the view normalizes the union of sourced and unsourced items, it is well suited to reporting that must present a complete picture of item-supplier relationships regardless of whether an active approved vendor exists.