Search Results wip_processor

Overview

APPS.WMS_WIP_INTEGRATION is a PL/SQL package in Oracle E-Business Suite that mediates between Oracle Warehouse Management (WMS) and Oracle Work in Process (WIP). It provides the integration surface through which warehouse-side operations—move order manipulation, LPN-driven processing, lot and serial capture, backflushing, completion, and putaway preparation—are reconciled with WIP job and material transaction data. The package is declared AUTHID CURRENT_USER, meaning its unqualified references resolve under the privileges of the invoking schema, and it relies on APPS synonyms to reach the underlying base tables. In release 12.1.1 and 12.2.2 the package is classified as API type OTHER within the ETRM repository, and it is referenced by eight other packages, indicating it sits on a shared integration path rather than being an isolated utility.

The procedures fall into three broad families: material movement and reservation handling for WIP jobs, attribute capture for lot- and serial-controlled items, and transaction posting or validation routines that prepare WMS data for inventory consumption.

Key Procedures and Functions

The package exposes fifteen documented procedures and functions. Their purposes are summarized below.

• UPDATE_MO_LINE — Updates a move order line, typically in response to warehouse processing activities tied to an LPN.
• BACKFLUSH — Copies WIP backflush data into the inventory transaction tables, driving component consumption for a job or schedule.
• CAPTURE_SERIAL_ATTS — Records serial number attributes, including from/to serial ranges, into the temporary serial structures used during WMS processing.
• CAPTURE_LOT_ATTS — Records lot attribute information for a given reference and temporary identifier.
• UPDATE_SERIAL — Applies serial number updates in the context of a WIP header.
• INSERT_LOT — Inserts or establishes lot number information for a WIP header. This is the routine most commonly associated with the search term "insert_lot," and it is the entry point used when WMS must create lot context for a job before downstream validation and posting.
• PERFORM_LOT_VALIDATIONS — Validates a lot number against an item and organization, returning standard return status, message count, and message data outputs.
• POST_COMPLETION — Posts completion transactions for an item and organization, carrying serial range and quantity information through to inventory.
• GET_WIP_JOB_INFO — Retrieves WIP job information for use by warehouse-side processing and putaway logic.
• GET_WIP_INFO_FOR_PUTAWAY — Supplies the WIP-derived data required to determine putaway behavior for completed material.
• UNALLOCATE_MATERIAL — Releases material previously allocated to a WIP job.
• TRANSFER_RESERVATION — Moves a reservation from one context to another within the WIP/WMS flow.
• MYDEBUG — An internal diagnostic routine used to emit debug information during package execution.
• UPDATE_MMTT_FOR_WIP — Maintains the material transaction temporary records associated with WIP processing.
• WIP_PROCESSOR — The principal driver routine that orchestrates WIP-side processing of warehouse transactions.

Tables Accessed

Access is performed through APPS synonyms. The tables divide into three groups.

• WIP and routing reference data: BOM_DEPARTMENTS, BOM_OPERATIONAL_ROUTINGS, and BOM_OPERATION_SEQUENCES provide department and routing context for job operations.
• Lot and serial data: MTL_LOT_NUMBERS, MTL_TRANSACTION_LOTS_TEMP, MTL_SERIAL_NUMBERS, and MTL_SERIAL_NUMBERS_TEMP hold the lot and serial identifiers and their temporary staging equivalents used during capture and validation.
• Inventory transaction and item data: MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_PARAMETERS, MTL_SECONDARY_INVENTORIES, MTL_TXN_REQUEST_LINES, and MTL_GEN_OBJECT_ID_S provide the transaction sequencing, item validation, organization parameters, subinventory context, move order lines, and object identifier generation required to post inventory activity.

Usage Notes

WMS_WIP_INTEGRATION is not intended for direct end-user invocation. It is called from WMS mobile and desktop processing flows, from WIP completion and backflush logic, and from other integration packages—eight packages reference it in the ETRM repository. Custom code should call the documented procedures rather than manipulating the underlying temporary tables directly, and callers must always inspect the returned x_return_status, x_msg_count, and x_msg_data outputs to detect validation failures, particularly from INSERT_LOT and PERFORM_LOT_VALIDATIONS when lot control is enabled.