Search Results gml_batch_so_alloc_history




Overview
Explore in AI Chat

Overview

GML_BATCH_SO_ALLOC_HISTORY is a table owned by the GML schema within the Process Manufacturing Logistics module of Oracle E-Business Suite, documented consistently across releases 12.1.1 and 12.2.2. The table functions as an order management batch reservation history store: it records the allocation and reservation activity that occurs when sales order lines are reserved against process manufacturing batches. In process manufacturing, inventory is often managed in lots and batches rather than discrete serialized units, so reservation events must be tracked against a specific batch, plant, warehouse, and lot combination. This table preserves those historical allocation records so that reservation outcomes—successful allocations as well as failures with their reasons—can be audited and reported after the fact.

From a data-modeling perspective, the ETRM metadata classifies this object heuristically as standalone in the Data Vault sense. As a modeling suggestion, a standalone classification indicates the table is not structurally dependent on multiple parent hubs through its foreign-key footprint; it can be treated as an independent historical (satellite-like) record set anchored by its own surrogate key. Note that the documented foreign-key relationship to GML_BATCH_SO_RESERVATIONS is implemented through a column (BATCH_RES_ID) that the FK metadata itself lists, rather than through the declared primary key.

Key Information Stored

The table contains 29 documented columns. The surrogate primary key is ALLOC_REC_ID, enforced by the GML_BATCH_SO_ALLOC_HISTORY_PK unique index; it uniquely identifies each allocation history record and is the only documented unique index/business-key candidate. The most significant columns include:

Common Use Cases and Queries

Typical uses center on auditing and diagnosing sales order batch reservations. A common pattern traces all history for a given order line:

SELECT alloc_rec_id, batch_res_id, batch_no, plant_code,
       reserved_qty, alloc_qty, failure_reason
FROM   gml_batch_so_alloc_history
WHERE  order_no = :order_no
AND    line_id  = :line_id
ORDER BY creation_date;

Analysts also report failed allocations by failure reason to identify recurring reservation problems, reconcile reserved versus allocated quantities by plant or warehouse, and reconstruct the reservation lifecycle for a specific batch via BATCH_RES_ID or BATCH_ID. Historical trend reports on allocation activity over time leverage CREATION_DATE, while troubleshooting queries filter on FAILURE_REASON being non-null.

Related Objects

  • GML_BATCH_SO_RESERVATIONS — the principal parent object; joined on GML_BATCH_SO_ALLOC_HISTORY.BATCH_RES_ID = GML_BATCH_SO_RESERVATIONS.BATCH_RES_ID.
  • GML_BATCHES / batch master tables — referenced through BATCH_ID and BATCH_NO for batch attributes.
  • GML_LOTS / lot master — referenced through LOT_ID for lot-level reporting.
  • Sales order tables (OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL) — linked via ORDER_NO and LINE_ID for order context.
  • Inventory organizations and subinventories — resolved via PLANT_CODE, WHSE_CODE, and LOCATION.
  • GML_BATCH_TRANSACTIONS / batch transaction tables — referenced through BATCH_TRANS_ID and BATCH_LINE_ID.
  • Reservation rule definitions — referenced through RULE_ID to interpret which allocation rule produced each record.