Search Results supply_type




Overview
Explore in AI Chat

Overview

MRP_I2_PROCUREMENT_V is a Rhythm-family database view delivered within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It exposes procurement supply information specifically for purchased parts, presenting scheduled receipts, purchase order references, vendor details, and dock dates in a form suited to planning and reporting consumers. The view is not a base application object; it is a supporting view created in the context of the Rhythm integration layer that complements Oracle Advanced Supply Chain Planning and the MRP planning engine. It is not implemented in every database, so its presence depends on whether the relevant integration components have been deployed.

Functionally, the view answers the question: "what supply is inbound for a purchased item at a given organization?" By joining the purchasing supply view to the part master view, it enriches raw supply rows with part numbers, postprocessing lead time, and demand-side context. It is read-only in practice, consumed by downstream reports, extracts, or integration programs rather than maintained directly.

Underlying Base Objects

The view is defined over exactly two referenced objects: MRP_RHX_PURCHASING_SUPPLY_V and MRP_I2_PART_MASTER_V. The documented metadata lists no additional base tables, though both underlying views themselves rest on planning and purchasing source tables in the MRP and PO schemas.

The join is a full scan (hint /*+FULL*/) between the two views on ORGANIZATION_ID and INVENTORY_ITEM_ID, with restrictive predicates limiting rows to DESTINATION_TYPE_CODE = 'INVENTORY' and non-null supply line, item, and line identifiers.

Key Columns

  • PART_NUMBER, INVENTORY_ITEM_ID, ORGANIZATION_ID — item and organization identity; the join keys that tie supply to the part master.
  • SUPPLY_TYPE — the central discriminator for procurement supply category. It drives DECODE logic elsewhere, notably mapping supply type 11 to 12 when resolving the configured receipt prefix, and controlling scheduled receipt numbering. Supply type 2 identifies rows that carry a SUPPLY_LINE_ID.
  • QUANTITY (PS.SUPPLY_QUANTITY) — inbound supply quantity from the purchasing supply view.
  • PO_NUMBER — a computed column; it concatenates a configured prefix (MRP_I2_L_SCHED_RECEIPT_PREFIX, resolved per organization and supply type), the supply number, and the supply line number, truncated to 240 characters.
  • SCHEDULE_DATE — derived as the greater of the next workday after DOCK_DATE plus postprocessing lead time, and the organization's planning start date, ensuring receipts are never scheduled before the planning horizon opens.
  • VENDOR — vendor name for the inbound supply.
  • LINE_ID — populated only when SUPPLY_TYPE equals 2, otherwise NULL.
  • ORDER_TYPE — substring of the configured scheduled receipt prefix; characterises the order category.
  • POSTPROCESSING_LEADTIME — lead time added to dock date before scheduling.
  • ATTRIBUTE_ALIAS — conditional column: when MRP_I2_P_ENABLE_ABP is 'Y', it returns the ATTRIBUTEn selected by MRP_I2_P_PO_AA_ATTR_NUM; otherwise NULL.

Common Use Cases and Queries

Typical consumers use this view to reconcile planned purchase receipts against item master data, to build vendor receipt schedules, or to validate supply type classification. Because SUPPLY_TYPE was the searched term, several queries revolve around it.

  • Filtering inbound supply by classification:
SELECT part_number, organization_id, quantity, supply_type, schedule_date
FROM   mrp_i2_procurement_v
WHERE  supply_type IN (2, 11)
ORDER BY schedule_date;
  • Aggregating scheduled receipts per item and vendor:
SELECT part_number, vendor, SUM(quantity) inbound_qty
FROM   mrp_i2_procurement_v
GROUP BY part_number, vendor;
  • Retrieving purchase order references and attribute aliases for advanced planning:
SELECT part_number, po_number, order_type, attribute_alias
FROM   mrp_i2_procurement_v
WHERE  po_number IS NOT NULL;

Because the view is documented as not implemented in all databases, existence checks against ALL_VIEWS should precede deployment of dependent objects.