Search Results mtl_txn_request_headers_s

Overview

GMI_MOVE_ORDER_HEADER_PVT is the private (PVT) package body in the APPS schema that encapsulates the server-side business logic for processing move order headers within the Oracle Process Manufacturing (OPM) and Oracle Inventory integration layer. In Oracle EBS 12.1.1 and 12.2.2, move orders are inventory documents that authorize the transfer of material between subinventories, locators, or organizations. The header record is the controlling entity for a move order, capturing the request number, organization, transaction type, and date required.

This package implements the private API tier of a two-layer architecture; the corresponding public package GMI_MOVE_ORDER_HEADER_PVT (its documented API classification is PVT) provides the internal implementation called by the public wrapper. It is responsible for validating, defaulting, and persisting move order header data, and for coordinating with reservation and transaction utilities before committing changes. Because it operates through the standard FND_API error-handling framework, it returns structured success and error messages consistent with Oracle's PL/SQL API standards.

Key Procedures and Functions

• PROCESS_MOVE_ORDER_HEADER — The principal driver procedure. It orchestrates the creation, update, or processing of a move order header record. It performs required-field validation, applies defaults from GMI_MOVE_ORDER_GLOBAL, coordinates reservation activity through GMI_RESERVATION_UTIL, and writes the resulting header row to the transaction request headers table. It relies on FND_MSG_PUB and FND_MESSAGE to register and report errors to the calling application.
• CHECK_REQUIRED — A validation helper that verifies mandatory attributes on the move order header before processing proceeds. It is invoked as a precondition step, typically by PROCESS_MOVE_ORDER_HEADER, to ensure data completeness and to raise consistent, translatable error messages through the FND message stack.

Detailed parameter signatures are not exposed in the documented metadata and should not be assumed; callers should reference the installed package specification for exact argument lists.

Tables Accessed

• MTL_TXN_REQUEST_HEADERS_S — The core transactional table for move order headers (the sequence-backed table storing header rows). The package reads and writes this table via the APPS synonym to insert and maintain move order header data. This is the object most commonly correlated with the user's search term "mtl_txn_request_headers_s".
• DUAL — Used for single-row scalar lookups and defaulting expressions within the package logic.

Additional dependencies documented at the object level, such as GMI_MOVE_ORDER_HEADER_UTIL and GMI_RESERVATION_UTIL, indicate that supporting utility logic performs much of the underlying row manipulation, while this package governs the API-level flow and error handling. INV_GLOBALS and GMI_MOVE_ORDER_GLOBAL supply organization and environment context.

Usage Notes

This package is an internal (PVT) implementation and is not intended for direct invocation by external custom code. It is normally reached indirectly through the public move order header API or the OPM/Inventory forms and concurrent programs that manage move orders, particularly those originating from process manufacturing flows that require reservations. Typical invocation contexts include the Move Orders form, order pick/release processing, and any concurrent program that programmatically creates or updates move order headers.

The package is documented as referenced by one other database object, confirming its role as a supporting implementation rather than a top-level entry point. It is not referenced by any other database object beyond that caller. When troubleshooting errors such as "mtl_txn_request_headers_s" violations or move order creation failures, developers should trace back to the public API and inspect the FND_MSG_PUB error stack returned by PROCESS_MOVE_ORDER_HEADER. All calls should honor the standard FND_API savepoint and message conventions to preserve transactional integrity. Custom development should always call the public wrapper, never GMI_MOVE_ORDER_HEADER_PVT directly.