Search Results process_move_order

Overview

APPS.INV_MOVE_ORDER_PUB is the public PL/SQL API for creating, retrieving, and processing move orders within Oracle Inventory. Move orders are internal material movement requests that relocate material from a source subinventory/locator to a destination subinventory/locator, and they underpin replenishment, subinventory transfer, and staging activities across Oracle E-Business Suite 12.1.1 and 12.2.2. The package is classified as a PUB (public) API, meaning it is intended by Oracle as a supported entry point for external and custom callers, unlike private internal APIs that are subject to change without notice.

The package defines the Trohdr_Rec_Type record structure, which carries the move order header attributes — source subinventory, required date, description, organization, header status, and the DFF attribute columns. This record type, together with the missing-value constants (g_miss_char, g_miss_num, g_miss_date) drawn from FND_API, confirms the package follows the standard EBS API programming model: a record-based interface plus the G_MISS convention for distinguishing "not supplied" from genuine values.

Key Procedures and Functions

• CREATE_MOVE_ORDER_HEADER — Creates a move order header record, accepting the header attributes defined in Trohdr_Rec_Type and populating MTL_TXN_REQUEST_HEADERS.
• CREATE_MOVE_ORDER_LINES — Creates one or more move order lines against an existing move order header, populating MTL_TXN_REQUEST_LINES.
• PROCESS_MOVE_ORDER — Processes the move order, advancing it toward approval, allocation, and/or transaction execution. This is the procedure surfaced by the user's search term "process_move_order" and is the primary orchestration point of the package.
• PROCESS_MOVE_ORDER_LINE — Processes a single move order line, providing finer-grained control than the header-level processing call.
• LOCK_MOVE_ORDER — Applies a lock to the move order, guarding against concurrent or conflicting modifications.
• GET_MOVE_ORDER — Retrieves move order header (and related) data for query or for passing into downstream logic.
• STAMP_CART_ID — Writes a cart identifier onto the move order, supporting the "shopping cart" style workflow used when move orders are built interactively.

Tables Accessed

The package reads and writes the core Inventory move order tables: MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES (with its _S shadow), which store the header and line definitions. Validation and resolution logic draws on MTL_SYSTEM_ITEMS, MTL_SECONDARY_INVENTORIES, MTL_SECONDARY_LOCATORS, and MTL_ITEM_SUB_INVENTORIES to confirm the item and the source/destination subinventory–locator combinations are valid. MTL_TRANSACTION_TYPES supplies the transaction type governing the resulting material movement. OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL are referenced for the sales-order-related move order flows (for example, staging against order demand). DUAL and PLITBLM are used for scalar evaluation and PL/SQL table handling respectively.

Usage Notes

INV_MOVE_ORDER_PUB is typically invoked from the Oracle Inventory move order forms and related concurrent programs, and it is a common integration point for custom code performing automated replenishment, WIP staging, or inter-org/internal transfers. Because it is a PUB API, it should be called in preference to direct DML against the MTL_TXN_REQUEST_* tables: the API enforces the standard validation, defaults, and WHO-column maintenance that direct inserts would bypass. The package is referenced by 57 other packages in the E-Business Suite, indicating that significant native functionality — including order management and inventory replenishment flows — depends on its processing routines.