Search Results gml_batch_so_reservations




Overview
Explore in AI Chat

Overview

GML_BATCH_SO_RESERVATIONS is a Process Manufacturing Logistics (GML) table that stores batch-level sales order reservation records. In Oracle EBS 12.1.1 and 12.2.2, it acts as the bridge between Process Manufacturing batch transactions and Oracle Order Management reservations, recording the quantity of a specific batch that has been reserved, allocated, or fulfilled against a sales order line. This table supports the batch reservation workflow that lets process manufacturers commit discrete batches to discrete sales order demand, enabling lot-controlled and potency-controlled fulfillment.

Following the heuristic Data Vault classification supplied in the ETRM metadata, this object is modeled as a standalone structure rather than a formal hub, link, or satellite. That classification reflects the FK topology: no other table's primary key is embedded here as a foreign key, and the table itself is a descriptive transactional entity keyed by a single surrogate. Modelers should treat it as an event/detail table rather than a pure dimension or association.

Key Information Stored

The table contains 29 documented columns in the ETRM 12.2.2 physical schema, owned by the GML schema. The most significant columns are:

No business-key candidate other than the surrogate primary key is documented; uniqueness of reservations is therefore enforced solely via BATCH_RES_ID.

Common Use Cases and Queries

Typical reporting scenarios include batch reservation audits, allocation-versus-fulfillment reconciliation, and open reservation tracking by sales order or warehouse.

  • Retrieve all reservations for a given sales order line: SELECT BATCH_RES_ID, BATCH_ID, RESERVED_QTY, FULFILLED_QTY, ALLOCATED_IND FROM GML.GML_BATCH_SO_RESERVATIONS WHERE SO_LINE_ID = :so_line_id AND DELETE_MARK = 0;
  • Summarize reserved versus fulfilled quantity per batch: SELECT BATCH_ID, SUM(RESERVED_QTY), SUM(FULFILLED_QTY) FROM GML.GML_BATCH_SO_RESERVATIONS WHERE ORGANIZATION_ID = :org_id GROUP BY BATCH_ID;
  • Identify unfulfilled reservations with an approaching scheduled ship date: SELECT * FROM GML.GML_BATCH_SO_RESERVATIONS WHERE ALLOCATED_IND = 'Y' AND FULFILLED_QTY = 0 AND SCHEDULED_SHIP_DATE < SYSDATE + 7;
  • Join to historical allocation movement via GML_BATCH_SO_ALLOC_HISTORY.BATCH_RES_ID to reconstruct allocation changes over time.

Related Objects

The documented FK relationships identify the following dependent objects, joined on BATCH_RES_ID:

  • GML_BATCH_TMP — temporary/processing table carrying BATCH_RES_ID for batch reservation staging.
  • GML_BATCH_SO_ALLOC_HISTORY — historical audit of allocation activity referencing BATCH_RES_ID.

Additionally, standard EBS integration points include Oracle Order Management (OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL) via ORDER_ID and SO_LINE_ID, Oracle Inventory (MTL_SYSTEM_ITEMS_B) via ITEM_ID, and shipping (WSH_DELIVERY_DETAILS) via DELIVERY_DETAIL_ID. These joins support end-to-end reporting from sales order through batch reservation to shipment.