Search Results line_reserved_qty

Overview

APPS.GML_SO_RESERVATIONS_V is a reporting view in the Oracle E-Business Suite Process Manufacturing (GML) module that consolidates batch-level reservation information for sales order fulfillment. The view aggregates reservation and planned quantity data held in the temporary batch structure GML_BATCH_TMP, presenting a grouped, filtered result set that reflects only those batches with active reservation or planning activity. Because the view derives its content dynamically from a temporary staging object, it functions primarily as an operational query interface rather than as a persistent reporting table.

The view is documented in ETRM metadata for release 12.2.2 and applies equally to 12.1.1 deployments. The user search term batch_res_id corresponds directly to the leading column of the view, which serves as the primary grouping key for batch reservation records. The view is owned by APPS and is therefore accessible to standard EBS responsibilities without additional grants.

Underlying Base Objects

The view is defined over a single referenced base object: GML_BATCH_TMP (SYNONYM). In Oracle EBS, GML_BATCH_TMP is a temporary table used during batch reservation and planning processes to stage intermediate results before final commitment. The synonym resolves to the underlying table owned by the GML schema, exposing it to the APPS layer for view construction.

Because the source is a temporary object, data visibility is typically scoped to the session or process that populated it. Rows persisted or materialized by concurrent processes may not be visible to other sessions, depending on the temporary table's ON COMMIT semantics. This characteristic is important when designing reports or integration points against the view.

Key Columns

• BATCH_RES_ID — Reservation identifier for the batch, the primary grouping and join key.
• BATCH_ID — Internal identifier of the batch.
• BATCH_NO — User-facing batch number.
• BATCH_LINE_ID — Line-level identifier linking the reservation to a specific batch line.
• WHSE_CODE — Warehouse in which the batch resides.
• DELIVERY_DETAIL_ID — Foreign key to the delivery detail record that the reservation supports.
• BATCH_TYPE, BATCH_STATUS — Classification and lifecycle status of the batch.
• START_DATE, PLAN_CMPLT_DATE — Planned start and completion dates for the batch.
• SUM(LINE_RESERVED_QTY), SUM(LINE_RESERVED_QTY2) — Aggregated line-level reserved quantities (primary and secondary UOM).
• SUM(NVL(PLANNED_QTY,0)), SUM(NVL(PLANNED_QTY2,0)) — Aggregated planned quantities.
• Total reserved columns — SUM(NVL(RESERVED_QTY,0)) + SUM(NVL(LINE_RESERVED_QTY,0)) and the corresponding QTY2 expression, which combine header-level and line-level reservations.

Common Use Cases and Queries

Typical uses include auditing reservations against sales order delivery details, verifying planned versus reserved quantities for a batch, and identifying batches awaiting fulfillment. The HAVING clause restricts output to batches with positive line-reserved or planned quantities, eliminating empty records.

• Retrieve all active reservations for a delivery: SELECT BATCH_RES_ID, BATCH_NO, SUM(LINE_RESERVED_QTY) FROM APPS.GML_SO_RESERVATIONS_V WHERE DELIVERY_DETAIL_ID = :detail_id GROUP BY BATCH_RES_ID, BATCH_NO;
• List reservations by warehouse: SELECT WHSE_CODE, BATCH_NO, BATCH_STATUS FROM APPS.GML_SO_RESERVATIONS_V WHERE WHSE_CODE = :whse ORDER BY BATCH_NO;
• Track planned completion: SELECT BATCH_NO, START_DATE, PLAN_CMPLT_DATE FROM APPS.GML_SO_RESERVATIONS_V WHERE PLAN_CMPLT_DATE BETWEEN :from_date AND :to_date;

Because the view aggregates from a temporary source, queries should be executed within the same session context that populated GML_BATCH_TMP to ensure consistent results.