Search Results process_move_order_header

Overview

The APPS.GMI_MOVE_ORDER_HEADER_PUB package is the public PL/SQL application programming interface for the header portion of Process Manufacturing (OPM) Move Orders within Oracle E-Business Suite. Move orders are internal inventory documents used to request and stage the transfer of material between subinventories, locators, or organizations. In the Process Manufacturing model, the move order header carries the top-level attributes of the request—such as the move order number, type, transaction date, and source and destination organizations—while associated detail lines identify the specific items and quantities to be moved.

This package belongs to the GMI module (Process Manufacturing Inventory) and is classified as a Public API, indicating that it is intended for external invocation by other Oracle modules, customizations, and integration code rather than for internal use only. It provides a controlled, validated entry point so that inbound move order data is subjected to the same business rules, defaults, and validation logic applied by the standard OPM Inventory forms. The package header carries the version string $Header: GMIPMOHS.pls 115.10 2003/04/18 and a creation history dating to April 2000, confirming its role as a long-standing component of the OPM integration surface. It is declared AUTHID CURRENT_USER, so it executes with the privileges of the calling schema, relying on APPS synonyms for any underlying table access.

Key Procedures and Functions

The ETRM metadata documents a single public procedure for this package:

• PROCESS_MOVE_ORDER_HEADER — This is the sole documented public entry point. It accepts a move order header record as input and returns the processed header record along with the standard Oracle API return values: a return status, a message count, and message data. The procedure also exposes the common API control parameters for API version number, initialization of the message list, a validation level flag, and a commit flag. The presence of the x_mo_hdr_rec output parameter (declared NOCOPY for performance) indicates that the procedure populates generated or defaulted values—such as identifiers and derived attributes—that the caller must retain. Its purpose is to create or process a move order header in accordance with OPM inventory validation rules.

No additional public functions or procedures are documented in the ETRM metadata for this package, and no other packages are recorded as referencing it.

Tables Accessed

The ETRM metadata excerpt does not enumerate any base tables, and the documentation states that no tables are referenced through APPS synonyms. In practice, OPM move order headers are persisted in the shared Process Manufacturing inventory tables (such as the move order header table family), but this summary is grounded solely in the documented facts. The absence of documented table references may reflect the deliberate abstraction of the public API: the actual DML is executed by related private packages, so callers need not be coupled to specific table structures.

Usage Notes

As a PUB-classified global API, GMI_MOVE_ORDER_HEADER_PUB.Process_Move_Order_Header is typically invoked from four contexts:

• Standard OPM Inventory forms, which call the procedure to validate and save move order header data entered through the user interface.
• Concurrent programs and interfaces that load move orders in bulk from external or legacy systems.
• Workflow and integration routines that programmatically raise internal material transfer requests.
• Custom PL/SQL code and Oracle Application Framework (OAF) pages that require validated creation of move order headers.

Callers should supply the API version number, request a validation level (typically full validation), initialize the message list where errors must be collected, and decide explicitly whether the procedure should commit. Because the procedure returns status, message count, and message data, callers must check x_return_status and iterate the message stack on failure. In EBS 12.1.1 and 12.2.2 the package behaves identically, being an OPM component unaffected by the file system changes introduced by the online patching architecture of 12.2. The package’s continued use in both releases underscores its stability as the supported interface for move order header processing.