Results for “delivery_balance”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The MRP_ITEM_PURCHASE_ORDERS table is an operational table in the MRP (Master Scheduling/MRP) product of Oracle E-Business Suite, holding purchase order and purchase requisition supply details used by the planning engine. It resides in the MRP schema and, per the documented ETRM metadata for 12.2.2, contains 38 columns. Its primary key is MRP_ITEM_PURCHASE_ORDERS_PK, defined on the TRANSACTION_ID column, and a unique index MRP_ITEM_PURCHASE_ORDERS_U1 provides the same business-key candidate on TRANSACTION_ID. The table captures the inbound supply picture — open purchase order deliveries and requisitions — that Oracle MRP and ASCP consume when netting requirements against supply during planning runs.

The ETRM Data Vault classification heuristic labels this table as satellite-leaning. In Data Vault modeling terms, this suggests treating the object as a descriptive satellite, where TRANSACTION_ID acts as a durable key anchor and the remaining attributes (dates, quantities, vendor details, status flags) represent the changing descriptive context around planned supply records. Modelers should validate this suggestion against actual cardinality and update patterns before committing to a design.

Key Information Stored

The most significant columns in the documented schema are:

• TRANSACTION_ID — Surrogate primary key and business-key candidate (unique index U1); uniquely identifies each supply record.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — The planned item and the inventory organization in which the supply is planned.
• COMPILE_DESIGNATOR — Identifies the MRP plan or compilation context.
• PURCHASE_ORDER_ID and PO_NUMBER — Linkage to the originating purchase order and its human-readable number.
• LINE_ID and PURCH_LINE_NUM — The purchase order line reference.
• VENDOR_ID and VENDOR_SITE_ID — The supplier and supplier site providing the supply.
• DELIVERY_SCHEDULE_DATE and DELIVERY_NEED_DATE — Schedule and need dates used for time-phased netting.
• DELIVERY_BALANCE and PO_UOM_DELIVERY_BALANCE — Remaining open quantity in item and PO units of measure.
• DELIVERY_PRICE and UOM_CODE — Cost and unit of measure for the delivery.
• DELIVERY_STATUS_TYPE and FIRM_PLANNED_STATUS_TYPE — Status indicators distinguishing firm versus planned supply.
• ORDER_TYPE — Identifies the supply document class (purchase order or requisition).
• SOURCE_ORGANIZATION_ID — Source organization for inter-org sourcing.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent program context columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) are also present and support audit and traceability.

Common Use Cases and Queries

Planners and developers query this table to explain netting results, validate planned supply, and reconcile MRP output against actual purchasing data. A typical pattern retrieves open supply for a given plan and item:

SELECT po_number, purch_line_num, delivery_schedule_date,
       delivery_balance, uom_code, vendor_id
  FROM mrp.mrp_item_purchase_orders
 WHERE inventory_item_id = :item_id
   AND organization_id   = :org_id
   AND compile_designator = :plan_id
   AND delivery_balance  > 0
 ORDER BY delivery_schedule_date;

Common reporting scenarios include time-phased supply reports by vendor, analysis of firm versus planned supply (FIRM_PLANNED_STATUS_TYPE), and auditing of requisition versus purchase order origin via ORDER_TYPE. Because MRP_RECOMMENDATIONS.DISPOSITION_ID references this table, planners frequently join the two to trace which recommendation produced or consumed a given supply record.

Related Objects

• MRP_SYSTEM_ITEMS — Referenced via INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR; provides item master and planning attributes.
• MRP_RECOMMENDATIONS — References this table through DISPOSITION_ID, linking recommendations to supply records.
• PO_HEADERS_ALL / PO_LINES_ALL — Base purchasing tables that source PURCHASE_ORDER_ID and LINE_ID.
• PO_VENDORS / PO_VENDOR_SITES_ALL — Supplier tables behind VENDOR_ID and VENDOR_SITE_ID.
• MTL_SYSTEM_ITEMS_B — Item definition source underlying MRP_SYSTEM_ITEMS.

These relationships make MRP_ITEM_PURCHASE_ORDERS the essential bridge between Oracle purchasing data and the MRP planning engine.