Search Results supply_scrap_quantity

Overview

APPS.MRP_PO_SUPPLY_VIEW is an Oracle E-Business Suite internal view that consolidates purchase-order supply information for consumption by the Material Requirements Planning (MRP), Master Production Scheduling (MPS), and Distribution Requirements Planning (DRP) engines. It exposes scheduled receipts associated with purchase orders, requisitions converted to POs, shipments, and receiving activity in a form that the planning processes can read as a unified supply record. The view is registered in FND Design Data as MRP.MRP_PO_SUPPLY_VIEW, is owned by the APPS schema, and carries a status of VALID in both 12.1.1 and 12.2.2.

The object is flagged "Oracle Internal Use Only." Oracle Corporation does not support direct access to this view except from standard Oracle Applications programs. As a result, the view is best understood as a planning integration artifact rather than a supported reporting interface; any external query against it must be treated as custom and subject to change across patches or releases.

Underlying Base Objects

The view draws on a mixture of tables, synonyms, packages, and other views. Documented base objects include AP_SUPPLIER_SITES_ALL and MRP_SYSTEM_ITEMS, both referenced through synonyms, along with MTL_UNITS_OF_MEASURE and OE_DROP_SHIP_SOURCES. Supplier identification is resolved through PO_VENDORS_VIEW and VENDOR_SITE_ID via AP_SUPPLIER_SITES_ALL.

The bulk of the supply content is derived from a family of PO supply views: PO_PO_SUPPLY_VIEW, PO_RCV_SUPPLY_VIEW, PO_REQ_SUPPLY_VIEW, PO_SHIP_RCV_SUPPLY_VIEW, and PO_SHIP_SUPPLY_VIEW. These delegate the individual upstream supply sources — purchase orders, receipts, requisitions, and shipment/receipt combinations — which are then unioned or joined into the single MRP-facing record set. Operational profile values and unit conversion logic are pulled in through the FND_PROFILE package and PO_UNITEFF_PKG respectively. This layered design lets Oracle change the underlying PO supply logic without altering the MRP interface contract.

Key Columns

• INVENTORY_ITEM_ID — the planned item.
• COMPILE_DESIGNATOR — the plan identifier (MPS, MRP, or DRP) for which the supply row was compiled.
• MPS_ORGANIZATION_ID / ORGANIZATION_ID — the MPS organization and the owning inventory organization.
• SUPPLY_HEADER_ID / SUPPLY_LINE_ID — header- and line-level identifiers linking the supply back to its PO or receiving document. SUPPLY_LINE_ID is the column most commonly searched for when tracing a planning supply record to its source PO line.
• SUPPLY_TYPE / SUPPLY_STATUS / SUPPLY_FIRM_PLANNED_STATUS — numeric indicators of the supply category, its lifecycle state, and whether the PO was firmed.
• MPS_SUPPLY_QUANTITY / SUPPLY_QUANTITY / SUPPLY_SCRAP_QUANTITY / MPS_SUPPLY_SCRAP_QUANTITY — planned and actual quantities, with separate MPS-aligned values.
• MPS_DELIVERY_SCHEDULE_DATE / DELIVERY_SCHEDULE_DATE / DOCK_DATE — MPS date, PO expected delivery date, and expected receipt (dock) date.
• SUPPLY_UNIT_PRICE, UOM_CODE, REVISION_NUM, SUPPLY_NUMBER, SUPPLY_LINE_NUM — pricing, unit of measure, revision, and descriptive PO line references.
• VENDOR_ID / VENDOR_SITE_ID — supplier and supplier site.
• MRP_DESTINATION_TYPE_CODE / DESTINATION_TYPE_CODE, PROJECT_ID, TASK_ID, END_ITEM_UNIT_NUMBER, TO_SUBINVENTORY, FROM_ORGANIZATION_ID — destination and project/task context, including the PO subinventory value.

Common Use Cases and Queries

Typical scenarios involve reconciling planner supply quantities against actual PO lines, investigating why a scheduled receipt did not appear in a plan, or tracing a supply record to its originating PO line using SUPPLY_LINE_ID. Because the object is internal, such queries are used for diagnostics and data research rather than production reporting.

SELECT supply_line_id,
       supply_header_id,
       inventory_item_id,
       organization_id,
       compile_designator,
       supply_quantity,
       delivery_schedule_date,
       dock_date,
       vendor_id,
       supply_status
  FROM apps.mrp_po_supply_view
 WHERE compile_designator = :plan
   AND organization_id    = :org
 ORDER BY delivery_schedule_date;

A second common pattern keys directly on the line identifier to resolve a single planning row back to its PO context:

SELECT v.supply_line_id,
       v.supply_line_num,
       v.supply_number,
       v.supply_quantity,
       v.mps_supply_quantity,
       v.supply_unit_price,
       v.uom_code,
       v.to_subinventory
  FROM apps.mrp_po_supply_view v
 WHERE v.supply_line_id = :supply_line_id;

Given the unsupported status of the object, reports should prefer supported MRP and PO interfaces where equivalent data is available, reserving direct queries against MRP_PO_SUPPLY_VIEW for internal investigation.