Search Results mtl_txn_request_lines_s




Overview
Explore in AI Chat

Overview

GMI_MOVE_ORDER_LINES_PVT is the private PL/SQL package body within the Oracle E-Business Suite Process Manufacturing (OPM) module that implements the line-level business logic for move orders. In EBS 12.1.1 and 12.2.2, move orders are internal replenishment or transfer requests that relocate material between subinventories, locators, or organizations. The public wrapper GMI_MOVE_ORDER_PUB exposes the supported API surface, while GMI_MOVE_ORDER_LINES_PVT contains the private validation, defaulting, and processing routines invoked by that wrapper and by related components such as GMI_MOVE_ORDER_LINE_UTIL, GMI_RESERVATION_UTIL, and GMI_TRANS_ENGINE_PUB.

The package depends on the standard EBS API infrastructure — FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and FND_PROFILE — confirming that it participates in the common error-handling, message-stack, and multi-org security model. It also depends on INV_GLOBALS, WSH_UTIL_CORE, and PLITBLM, indicating involvement in inventory transaction defaults and shipping-related validation. The package body is documented as VALID in the ETRM metadata and is not referenced by any other database object, consistent with its private classification.

Key Procedures and Functions

The ETRM metadata documents two procedures or functions in this package body:

  • PROCESS_MOVE_ORDER_LINES — The principal processing routine. It drives the creation, update, or validation of move order lines, applying the required defaults and enforcing OPM business rules before the line records are committed or passed onward to the transaction engine. It interacts with GMI_TRANS_ENGINE_PUB and GMI_TRAN_PND_DB_PVT to stage and release inventory transactions, and with GMI_RESERVATION_UTIL to manage material reservations.
  • CHECK_REQUIRED — A validation routine that verifies mandatory attributes are present on a move order line before processing proceeds. This pattern is standard in EBS PVT packages, where required-field checks are isolated so that both the public API and internal callers can apply identical validation logic and raise consistent error messages through FND_MESSAGE and FND_MSG_PUB.

The metadata does not expose individual parameter lists, and none should be assumed. Additional private helpers may exist within the body but are not documented.

Tables Accessed

The package operates against both the OPM (GMI/IC) and Oracle Inventory (MTL) data models, reflecting the integration required to move process-manufacturing material:

  • MTL_TXN_REQUEST_LINES_S — The move order line base table in the Oracle Inventory schema. This is the table the user searched for and the primary destination for line records created or updated by PROCESS_MOVE_ORDER_LINES.
  • IC_TXN_REQUEST_LINES — The OPM-side equivalent line table, used to synchronize move order details within the process manufacturing schema.
  • IC_TRAN_PND — The pending transaction table, where inventory transactions generated for the move order are staged before submission to the transaction engine.
  • MTL_SYSTEM_ITEMS and IC_ITEM_MST — Item master tables consulted for item validation, UOM, and defaulting.
  • IC_WHSE_MST — Warehouse master data used to validate source and destination warehouse definitions.
  • DUAL and PLITBLM — Utility objects used for single-row queries and PL/SQL table manipulation within the body.

Usage Notes

Because GMI_MOVE_ORDER_LINES_PVT is a private (PVT) package, it is not intended for direct invocation by customer extensions. It is called internally by the public move order API and related utility packages, and is reached indirectly through OPM move order forms, concurrent programs that process pending inventory transactions, and the transaction engine. Custom code should always call the public API layer — GMI_MOVE_ORDER_PUB — rather than this private body, to preserve validation, message-stack handling, and forward compatibility across 12.1.1 and 12.2.2. When diagnosing move order line issues, this package and its dependency on MTL_TXN_REQUEST_LINES_S are the appropriate starting point for tracing how line data is validated and persisted.