Results for “gme_batch_sales_orders”

24 results




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

Overview

GME_BATCH_SALES_ORDERS is a table in the GME schema (Process Manufacturing Process Execution) within Oracle EBS 12.1.1 and 12.2.2. Its documented purpose is to track the sales order(s) used to generate the batch(es), meaning it functions as the association point between a production batch and the sales order demand that caused it to be created. In process manufacturing environments, batches are frequently produced to fulfill specific customer demand, and this table preserves that linkage for audit, traceability, cost-to-serve analysis, and order-driven production reporting.

The ETRM metadata classifies this object as standalone under the heuristic Data Vault classification mined from its foreign key structure. Interpreted as a modeling suggestion, that classification reflects that no declarative FK dependencies were detected around this table; its role is essentially associative, so a Data Vault design would most naturally treat it as a link table connecting batch and sales order entities, with its descriptive columns (audit fields) optionally split into a satellite. Note that GME_BATCH_SALES_ORDERS is not a pure link because it also carries WHO-columns that describe row maintenance rather than the relationship itself.

Key Information Stored

The table is documented with 8 columns at 12.2.2. The most significant are:

  • BATCH_ID — Reference to the batch (production) generated against sales order demand. Part of the composite primary key.
  • ORDER_ID — Reference to the sales order header associated with the batch. Part of the composite primary key.
  • LINE_ID — Reference to the specific sales order line. Part of the composite primary key.
  • CREATION_DATE — Date the linkage row was first created.
  • LAST_UPDATE_DATE — Date of the most recent update to the row.
  • CREATED_BY — User ID that created the row.
  • LAST_UPDATED_BY — User ID that last modified the row.
  • LAST_UPDATE_LOGIN — Login ID associated with the last update.

The surrogate primary key is not a generated ID; the documented index GME_BATCH_SALES_ORDERS_PK is composite, defined on (BATCH_ID, ORDER_ID, LINE_ID). This composite key also serves as the business-key candidate, because it consists entirely of meaningful business references rather than synthetic values. The remaining five columns (the audit/WHO-columns) supply row-level traceability. Because there is no single-column surrogate and no additional unique index, the three key columns together enforce uniqueness at the batch/order/line granularity.

Common Use Cases and Queries

Typical use cases center on traceability from sales demand to production output, cost and yield attribution to specific orders, and reporting on batches that serve multiple sales orders (or multiple lines served by one batch). A representative query retrieving all batches tied to a given sales order:

  • SELECT b.batch_id, b.order_id, b.line_id FROM gme_batch_sales_orders b WHERE b.order_id = :p_order_id;
  • Join to batch headers (for example, GME_BATCH_HEADERS on BATCH_ID) to add batch number, plant, and status.
  • Join to OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL on ORDER_ID / LINE_ID for customer and item context.
  • Aggregate to determine how many sales orders a single batch satisfies, or how many batches back a single order line.
  • Use CREATED_BY / CREATION_DATE audit columns for change-tracking and lineage reporting in FDA/audit contexts.

Because the PK is composite, queries filtering on BATCH_ID are the most selective and benefit from the primary key index.

Related Objects

Although the heuristic Data Vault classification is standalone (no declarative FKs detected), the practical dependencies are implied through shared columns:

  • GME_BATCH_HEADERS — joined on BATCH_ID; the parent batch record.
  • GME_BATCH_HEADERS_B — base-table equivalent carrying batch identifiers.
  • OE_ORDER_HEADERS_ALL — joined on ORDER_ID (HEADER_ID); the sales order header.
  • OE_ORDER_LINES_ALL — joined on LINE_ID (LINE_ID); the sales order line.
  • GME_BATCH_STEPS / GME_BATCH_STEP_ACTIVITIES — batch execution detail reached via BATCH_ID.
  • GME_MATERIAL_DETAILS — consumption detail linked by BATCH_ID for cost analysis.
  • ONT / OE Order Management APIs (OE_ORDER_PUB) — source of sales order creation that ultimately triggers batch linkage.
  • WSH_DELIVERY_DETAILS — downstream shipment lines where order-line demand depends on the batch.

All references should be validated against the GME and OE schemas in the target 12.1.1 or 12.2.2 instance, since the documented ETRM entry contains no explicit foreign key constraints.