Search Results lock_move_order

Overview

INV_MOVE_ORDER_PUB is the public PL/SQL API package for Oracle Inventory move orders (also referred to as transaction requests) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its business function is to provide a supported, layered interface for creating, modifying, processing, and querying move orders without requiring direct DML against the underlying MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES tables. The package encapsulates the validation, defaulting, identifier-to-value conversion, and transaction processing logic required to move material between subinventories and locators within a warehouse. Move orders are commonly used for replenishment, staging, and internal transfers where a formal transfer order is not required. Because the package is classified as a public (PUB) API in the APPS schema, Oracle supports its documented procedures as an integration point for forms, concurrent programs, and custom code.

Key Procedures and Functions

The package exposes seven documented procedures and functions:

• CREATE_MOVE_ORDER_HEADER — Creates a move order header record, establishing the transaction request that subsequent lines are attached to. It provides the header-level entry point and uses standard FND_API parameter conventions for API version, initialization of the message list, return values, commit control, and message stack output.
• CREATE_MOVE_ORDER_LINES — Creates one or more line records for an existing move order header, specifying the item, quantities, and source and destination subinventory or locator information.
• PROCESS_MOVE_ORDER — Processes the move order as a whole, driving the transaction request to completion through the inventory transaction engine.
• PROCESS_MOVE_ORDER_LINE — Processes individual move order lines, allowing line-level control over the processing operation.
• LOCK_MOVE_ORDER — Applies locking semantics to a move order so that concurrent modifications are prevented during processing or maintenance.
• GET_MOVE_ORDER — Retrieves move order header and line information for inquiry or downstream processing.
• STAMP_CART_ID — Populates a cart identifier on the move order, supporting cart-based selection and workflow scenarios.

The package also contains internal utilities, including a debug/trace wrapper (print_debug), and forward declarations for the Id_To_Value and Value_To_Id conversion routines. The user search term "trolin_tbl_type" refers to the Trolin_Tbl_Type PL/SQL record table type used as the line-level input structure for the Id_To_Value and Value_To_Id conversions, paired with Trohdr_Rec_Type at the header level; these correspond to the Trolin_Val_Tbl_Type and Trohdr_Val_Rec_Type output structures that carry descriptive values rather than internal identifiers.

Tables Accessed

The package reads and writes the following tables via APPS synonyms:

• MTL_TXN_REQUEST_HEADERS and MTL_TXN_REQUEST_LINES — the primary move order header and line tables that store the transaction request definition.
• MTL_TXN_REQUEST_LINES_S — the sequence/identifier source supporting line numbering.
• MTL_SYSTEM_ITEMS — item validation, including primary unit of measure resolution.
• MTL_ITEM_SUB_INVENTORIES, MTL_SECONDARY_INVENTORIES, and MTL_SECONDARY_LOCATORS — validation and defaulting of source and destination subinventories and locators, including restriction flags such as g_restrict_subinventories_code and g_restrict_locators_code.
• MTL_TRANSACTION_TYPES — resolution of the transaction type used when the move order is processed.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — used to link move orders to sales order demand, typically for pick/replenishment scenarios.
• DUAL and PLITBLM — utility access for scalar selection and PL/SQL table operations.

Usage Notes

INV_MOVE_ORDER_PUB is invoked from the Inventory move order forms, from concurrent programs that generate or process move orders in bulk, and from custom PL/SQL integration code. Callers should follow the standard FND_API pattern: initialize the message list, pass a valid API version, check x_return_status after every call, and only commit when p_commit is set to FND_API.G_TRUE. Referenced by 57 other packages, it is a widely depended-upon interface, so custom code should call the public procedures rather than manipulating the move order tables directly. The Trolin_Tbl_Type and Trohdr_Rec_Type structures are the correct vehicles for line- and header-level data when using the conversion routines.