Search Results get_move_transaction_lines

Overview

APPS.WIP_SO_RESERVATIONS is a Work in Process (WIP) package that manages the interaction between Work in Process manufacturing activity and Sales Order demand. Its primary purpose is to maintain, transfer, relieve, allocate, and return inventory reservations that link sales order lines to WIP entities such as discrete jobs, repetitive schedules, and flow schedules. The package ensures that the temporary reservation of on-hand inventory for WIP requirements stays synchronized with the corresponding sales order demand that generated those requirements.

A central concern of the package is reservation accounting during manufacturing transactions. When a sales order is created against an assemble-to-order or make-to-order item, the resulting WIP entity consumes inventory that would otherwise be reserved for the sales order. WIP_SO_RESERVATIONS reconciles these two reservation streams so that inventory is not double-committed and that completed assemblies can be allocated back to the originating sales order. The package also supports change-order processing, scrapping, and cancellations — events that require a re-evaluation of reservations already placed against WIP entities.

The record type definitions confirm this dual focus. The package defines a transaction_temp record (with demand_source_header_id, demand_source_line_id, wip_entity_id, lot_number, subinventory_code, locator_id, and lpn_id) and a demand_temp record (carrying source_header_id, source_line_id, source_delivery, requirement_date, and conversion_rate), alongside a move_transaction_intf record modeled on the WIP move transaction interface. These structures document the mapping between sales order demand and WIP transaction data, including support for lot-controlled items (with the lot_number length expanded from 30 to 80 characters under ER 4378835 to accommodate OPM lot-model changes), LPN (license plate number) handling, and revision-level tracking.

Key Procedures and Functions

• GET_TRANSACTION_LINES — Retrieves the material transaction lines relevant to reservation processing for a given WIP context.
• VALIDATE_TXN_LINE_AGAINST_RSV — Validates a proposed transaction line against the existing reservation to confirm quantity and item alignment.
• TRANSFER_RESERVATION — Moves an existing sales order reservation from one source to another within the WIP context; this is the procedure most commonly referenced by the search term "transfer_reservation."
• COMPLETE_FLOW_SCHED_TO_SO — Links the completion of a flow schedule back to the originating sales order.
• ALLOCATE_COMPLETION_TO_SO — Allocates a production completion quantity to a specific sales order line, satisfying that demand.
• RETURN_RESERVATION_TO_WIP — Returns a reservation to the WIP entity, reversing a prior allocation or transfer.
• SPLIT_ORDER_LINE — Splits a sales order line, allowing reservation quantities to be redistributed across the resulting lines.
• MAKE_CALLBACK_TO_WORKFLOW — Invokes a callback into the Oracle Workflow process associated with the order change or reservation event.
• RESPOND_TO_CHANGE_ORDER — Handles the reservation implications of a sales order change, re-validating and reallocating as needed.
• GET_MOVE_TRANSACTION_LINES — Returns move transaction interface lines, used when reservation effects must be synchronized with shop floor moves.
• SCRAP_TXN_RELIEVE_RSV — Processes a scrap transaction by relieving the associated reservation.
• RELIEVE_WIP_RESERVATION — Relieves (releases) a WIP reservation, reducing the quantity reserved against the entity.
• UPDATE_ROW — Performs the physical update of a reservation or interface row.
• LOCK_ROW — Acquires a row-level lock prior to update, preventing concurrent modification of reservation records.

Tables Accessed

The package reads and writes reservation and transaction data primarily through MTL_RESERVATIONS, which stores the actual reservation records, and MTL_MATERIAL_TRANSACTIONS_TEMP, which holds pending material transactions. Item and lot attributes are validated against MTL_SYSTEM_ITEMS and MTL_LOT_NUMBERS, with lot transaction detail carried in MTL_TRANSACTION_LOTS_TEMP. Sales order context is obtained from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL. WIP entity information is drawn from WIP_DISCRETE_JOBS, WIP_ENTITIES, and WIP_FLOW_SCHEDULES, while WIP_JOB_SCHEDULE_INTERFACE and WIP_MOVE_TXN_INTERFACE support scheduling and move transaction integration. Completion and LPN handling is supported by WIP_LPN_COMPLETIONS and WIP_LPN_COMPLETIONS_LOTS. WIP_PARAMETERS supplies organizational WIP configuration settings.

Usage Notes

WIP_SO_RESERVATIONS is not typically called directly by end users. It is invoked by Oracle EBS forms and concurrent programs during sales order entry, WIP job creation and release, completion transactions, scrap and move transactions, and order change-order workflow activity, particularly for assemble-to-order and make-to-order flows. The package is also referenced by six other packages within the application, indicating it functions as a shared utility layer for reservation coordination. Custom code that manipulates sales order reservations against WIP entities should call these procedures rather than updating MTL_RESERVATIONS directly, since the package enforces locking (LOCK_ROW), workflow callbacks, and validation logic. Developers integrating with this package should note its reliance on the WIP move transaction interface record structure and on lot and LPN handling, and must respect the LOCK_ROW/UPDATE_ROW pattern to avoid concurrent update conflicts.