Search Results pick_release

Overview

INV_WIP_PICKING_PVT is a private (PVT) PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema that supports the picking and release of move order lines against Work In Process (WIP) discrete jobs, repetitive schedules, and flow schedules. Its primary business purpose is to drive the allocation, release, and confirmation of move order material picks that supply WIP demand. The package encapsulates the internal processing logic invoked by the public INV_MOVE_ORDER_PUB layer, particularly around the pick release operation, and coordinates updates against material transaction staging tables and WIP entities. The header comment identifies a version dated 2012/02/10 (120.15), and it maintains no persistent state beyond session-level cursors, indicating it is a worker/utility package rather than a stateful service.

The name "pick_release" maps directly to one of the documented procedures, PICK_RELEASE, which is the central routine for releasing picking activity associated with WIP demand.

Key Procedures and Functions

• RELEASE_PICK_BATCH — Processes a set (batch) of move order lines tied to a move order header for pick release. It consolidates multiple line records so that release activity can be executed in bulk rather than line-by-line. Internally it iterates the move order line table and coordinates the underlying pick release work.
• PICK_RELEASE — The principal procedure performing pick release for a given move order header and its lines. It resolves WIP context (job, schedule, operation), determines allocation status (completely, partially, or not allocated per the g_completely_allocated / g_partially_allocated / g_not_allocated constants), and invokes line-level processing via the forward-declared process_line routine.
• UPDATE_MOL_FOR_WIP — Updates move order line related records for WIP. This includes synchronizing move order line status and allocation outcomes with WIP requirement operations. It coordinates the update of transaction staging data to reflect the released pick.
• GET_WIP_ATTRIBUTES — A function that retrieves WIP-specific attributes (such as job, schedule, department, and operation identifiers) needed to correctly classify and route the move order pick. It provides the WIP context that PICK_RELEASE and related routines depend upon.
• Supporting routines — Forward declarations include process_line, update_mmtt_for_wip, and get_mo_alloc_stat, plus a print_debug helper that routes messages through INV_LOG_UTIL.TRACE subject to the INV_DEBUG_TRACE profile option. A global concatenation mode flag (g_conc_mode) distinguishes concurrent processing from online processing.

Tables Accessed

• MTL_TXN_REQUEST_HEADERS / MTL_TXN_REQUEST_LINES — The move order header and line tables read and updated to reflect pick release and allocation status.
• MTL_MATERIAL_TRANSACTIONS_TEMP — Staging area where pending material transactions generated by the pick release are inserted prior to processing.
• MTL_SYSTEM_ITEMS, MTL_PARAMETERS — Item and organization setup attributes used during allocation and validation.
• WIP_ENTITIES, WIP_REQUIREMENT_OPERATIONS, WIP_OPERATIONS — WIP demand, requirement operation, and routing operation data linking the move order to the manufacturing work.
• WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_FLOW_SCHEDULES — The WIP work order types against which picks are released.
• BOM_DEPARTMENTS, BOM_OPERATIONAL_ROUTINGS, BOM_OPERATION_SEQUENCES — Routing, sequence, and department reference data used to resolve operation context.
• WSH_PICK_SLIP_NUMBERS_S — Pick slip number sequence used to assign identifiers to released picks.
• DUAL — Miscellaneous scalar lookups.

Usage Notes

This package is a private API and is not intended for direct invocation by external integrations. It is called internally by INV_MOVE_ORDER_PUB and associated move order processing logic, which in turn is surfaced through the Move Orders, Pick Confirm, and WIP Material Transaction forms. In concurrent mode (g_conc_mode TRUE), it operates under the pick release concurrent program and inherits the INV_DEBUG_TRACE debugging facility. Custom code should invoke the public INV_MOVE_ORDER_PUB APIs rather than INV_WIP_PICKING_PVT. Because it is referenced by four other packages, modifications here have broad impact. Administrators and developers diagnosing pick release failures should enable INV_DEBUG_TRACE and review the trace messages emitted by print_debug.