Search Results gme_common_pvt




Overview
Explore in AI Chat

Overview

The APPS.GME_MOVE_ORDERS_PVT package is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite Process Manufacturing (OPM) module. It provides the internal programmatic foundation for creating, retrieving, updating, and deleting move orders associated with process manufacturing batches. A move order is the inventory transaction request that authorizes the physical or logical movement of material from a source subinventory and locator to a destination subinventory and locator. Within the OPM context, move orders link batch-driven material requirements — recorded in GME_MATERIAL_DETAILS — to standard Oracle Inventory move order documents stored in MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES. Because the package is classified as PVT, it is not intended as a public extension point; it is consumed by higher-level public APIs such as GME_CREATE_BATCH_PVT, GME_RELEASE_BATCH_PVT, GME_CANCEL_BATCH_PVT, GME_PICKING_PVT, and GME_MATERIAL_DETAIL_PVT. The package depends on GME_COMMON_PVT, FND_API, and the public INV_MOVE_ORDER_PUB, indicating that it delegates the actual Inventory-side document creation to the standard move order public API while managing the batch-specific logic itself.

Key Procedures and Functions

ETRM documents nine procedures and functions within the package:

  • CREATE_MOVE_ORDER_HDR — Creates the move order header record, establishing the transaction request document that carries the batch-related movement.
  • CREATE_MOVE_ORDER_LINES — Creates the detail lines associated with a move order header, capturing item, quantity, and subinventory/locator information.
  • CREATE_BATCH_MOVE_ORDER — Drives creation of move orders for an entire batch, iterating across the batch's material detail requirements.
  • GET_MOVE_ORDER_LINES — Retrieves existing move order line information, typically returning the lines linked to a given header or batch.
  • DELETE_MOVE_ORDER_LINES — Removes move order lines that are no longer required, used during batch modification or rollback.
  • UPDATE_MOVE_ORDER_LINES — Modifies existing move order line attributes in response to changes in batch material requirements.
  • PENDING_MOVE_ORDERS_EXIST — Boolean-style check determining whether any open or pending move orders remain against a batch.
  • GET_PENDING_MOVE_ORDER_QTY — Returns the outstanding quantity not yet fully transacted or relieved on move orders.
  • DELETE_BATCH_MOVE_ORDERS — Removes all move orders tied to a batch, supporting batch cancellation and cleanup.

Tables Accessed

The package reads and writes the following documented tables via APPS synonyms:

  • GME_BATCH_HEADER — Batch master record, providing the batch context for each move order.
  • GME_MATERIAL_DETAILS — Batch material requirements that drive move order line generation.
  • MTL_TXN_REQUEST_HEADERS / MTL_TXN_REQUEST_LINES — The core Inventory move order document and detail records created and maintained by this package.
  • MTL_SYSTEM_ITEMS_B / MTL_SYSTEM_ITEMS_KFV — Item attribute validation and descriptive flexfield lookups.
  • MTL_PARAMETERS — Organization-level inventory parameters, used for defaults and validation.
  • WSH_DELIVERY_GROUP_S — Delivery grouping information that may apply to move order documents.
  • DUAL — Utility queries; PLITBLM — PL/SQL index-by table storage.

Usage Notes

GME_MOVE_ORDERS_PVT is invoked internally rather than called directly by end users. It fires when a batch is created, released, picked, or cancelled, and when material details change. Typical triggers are the OPM batch forms and batch-related concurrent programs, as well as custom code that legitimately calls the enclosing public batch APIs. The package is referenced by ten other packages, including GME_API_GRP, confirming its role as a shared internal utility. Developers extending OPM should call public batch APIs rather than this PVT package, since its signature and behavior are not guaranteed across releases.