Results for “gmi_move_order_header_util”

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

Overview

The APPS.GMI_MOVE_ORDER_HEADER_UTIL package body is a utility-layer PL/SQL component within the Oracle E-Business Suite Process Manufacturing (OPM) module. Its business function is to encapsulate the low-level data manipulation and validation logic used to maintain records in the move order header entity. In OPM terminology, a move order represents an internal request to transfer material between inventory locations, subinventories, or organizations. The header record stores the identifying and status information for that request, while associated detail lines carry the individual item movements.

As an API classified as UTIL, this package is not intended to represent a standalone business transaction endpoint. Rather, it provides reusable procedural building blocks — row insertion, update, deletion, locking, and query operations — that higher-level move order APIs and concurrent processes invoke when processing move order transactions. The package is owned by the APPS schema, carries a status of VALID, and references several standard EBS infrastructure packages including FND_API, FND_GLOBAL, FND_MESSAGE, FND_MSG_PUB, and APP_EXCEPTIONS, indicating that it participates in the standard EBS error-handling and message-stack framework. It also depends on the sibling packages GMI_MOVE_ORDER_GLOBAL and GMI_RESERVATION_UTIL, which supply global constants and reservation-handling logic respectively. The documentation records that this package is referenced by three other database objects and is not itself dependent on external callers.

Key Procedures and Functions

The package body exposes eight documented procedures and functions. Each performs a discrete, narrowly scoped operation on move order header data:

• APPLY_ATTRIBUTE_CHANGES — Applies pending attribute modifications to a move order header record, reconciling changed values against the stored row.
• CONVERT_MISS_TO_NULL — Normalizes incoming values by converting "miss" (blank or placeholder) entries to null, ensuring consistent data storage semantics.
• UPDATE_ROW — Performs the core update operation against an existing move order header row.
• UPDATE_ROW_STATUS — Modifies the status indicator on a move order header, supporting workflow transitions and lifecycle management.
• INSERT_ROW — Creates a new move order header record.
• DELETE_ROW — Removes a move order header record from the underlying table.
• QUERY_ROW — Retrieves move order header data for a given key, typically used for validation or display purposes.
• LOCK_ROW — Acquires a row-level lock on the header record to serialize concurrent access and prevent lost updates during transactional processing.

Collectively these procedures form a complete CRUD envelope around the move order header entity, augmented by locking and attribute-reconciliation utilities.

Tables Accessed

The package operates primarily against IC_TXN_REQUEST_HEADERS, accessed through an APPS synonym. This is the Oracle Inventory transaction request header table that stores move order header information, including the request number, transaction type, source and destination organizations, and processing status. All insert, update, delete, query, and lock operations described above are directed at this table. Reservation-related interactions are delegated to GMI_RESERVATION_UTIL rather than performed directly, preserving separation of concerns.

Usage Notes

GMI_MOVE_ORDER_HEADER_UTIL is typically invoked indirectly rather than called directly by end users. It is consumed by higher-level OPM move order processing logic, by concurrent programs that generate or release move orders, and by custom extensions that must create or maintain move order headers in a manner consistent with Oracle's internal conventions. Because the package participates in the FND_MSG_PUB and APP_EXCEPTIONS frameworks, callers should expect standard EBS error propagation and should inspect the message stack on failure. Direct invocation is appropriate only for custom development that requires the same validated, lock-aware operations Oracle applies internally; bypassing the package in favor of direct DML against IC_TXN_REQUEST_HEADERS is not recommended.