Search Results gmi_auto_allocation_batch




Overview
Explore in AI Chat

Overview

The GMI_AUTO_ALLOCATION_BATCH table is a parameter table in the Oracle E-Business Suite Process Manufacturing Inventory module (GMI). It stores the selection and filter criteria that drive automatic lot allocation batch processes. In Oracle Process Manufacturing, automatic allocation is a batch-oriented engine that reserves on-hand lot inventory against sales order delivery lines based on rules such as lot status, expiration, scheduling dates, and pick confirmation. Rather than requiring a user to re-enter filter criteria each time the allocation engine runs, the batch parameter table captures a named, reusable allocation request. Each row describes one allocation batch definition, including its inbound order range, lot range, order type, item and warehouse scope, and the behavioral flags that govern how the engine executes.

This table sits at the center of a batch-driven reservation workflow. It is populated when a planner or inventory supervisor defines an allocation run, and it is consumed by concurrent programs that read the parameters, scan candidate delivery details and lots, and post allocations. The ETRM schema documents 50 columns, and the object is classified as VALID under the GMI schema in both 12.1.1 and 12.2.2. From a Data Vault modeling perspective, the metadata heuristic classifies this object as standalone, which suggests modeling it as a standalone hub or reference table rather than as a link joining multiple business entities. The single documented foreign key to SO_ORDER_TYPES_115_ALL indicates the table is primarily a self-contained parameter definition with one outbound reference to the order type lookup.

Key Information Stored

The documented columns divide into an identity/primary key, business filter ranges, scope qualifiers, and processing flags.

Common Use Cases and Queries

Typical scenarios include reviewing which allocation batches are defined, auditing the criteria applied in prior runs, and joining the parameter row to its order type description. A basic lookup returns the batch and its scope:

  • SELECT b.batch_id, b.name, b.whse_code, b.item_id, b.lot_status FROM gmi.gmi_auto_allocation_batch b WHERE b.name = :p_name;
  • Join to resolve order type: SELECT b.batch_id, b.name, ot.order_type_name FROM gmi.gmi_auto_allocation_batch b, oe.so_order_types_115_all ot WHERE b.order_type_id = ot.order_type_id;
  • Filter by date windows: query rows where the scheduled ship or expiration ranges overlap a reporting period, supporting month-end allocation audits.
  • Flag analysis: aggregate on PICK_CONFIRM_FLAG, OVERRIDE_RULES, and DELETE_EXISTING_ALOC_FLAG to identify batches configured to override standard rules or clear prior allocations.

Related Objects

The most significant relationships center on the order type lookup and the transactional allocation and delivery tables the batch parameters drive.

These joins support both operational monitoring of the allocation engine and historical reporting on how batch parameters affected reservation outcomes.