Search Results wip_movproc_grp




Overview
Explore in AI Chat

Overview

WIP_MOVPROC_GRP is a packaged PL/SQL grouping (the "_GRP" suffix denotes a "group" package in Oracle EBS naming convention) owned by the APPS schema. It encapsulates the server-side processing logic that supports Work in Process (WIP) move transactions, particularly the interface and backflush processing that occurs when discrete jobs, repetitive schedules, or lot/serial controlled assemblies are transacted through the shop floor. The package is classified as an API group in ETRM 12.2.2 and carries a VALID status in both 12.1.1 and 12.2.2.

The package sits between the WIP transaction interface tables and the core WIP move transaction engine. Its primary business function is to validate, process, and post move transactions—including backflush of component material and lot/serial assignment—so that shop floor activity is reflected accurately in inventory and job balances. WIP_MOVPROC_GRP depends on the WIP_LOT_SERIAL_OBJ_T object type (SYS.STANDARD and SYSTEM dependencies are also declared), confirming its role in serial and lot controlled transaction handling.

Key Procedures and Functions

The documented API surface comprises five procedures/functions: BACKFLUSH, BACKFLUSHINTOMMTT, BACKFLUSHINTOMTI, and PROCESSINTERFACE (with the fifth entry corresponding to the package body wrapper).

  • BACKFLUSH — Performs the backflush of component requirements against a WIP job or schedule. It supplies the core logic for relieving component inventory based on the bill of material and the quantity completed.
  • BACKFLUSHINTOMMTT — Drives backflush processing into the material transaction interface (MTI) area, enabling backflushed material movements to be staged for the inventory transaction manager.
  • BACKFLUSHINTOMTI — A variant that routes backflush results into the material transaction interface, supporting the flow of component issues generated by move processing.
  • PROCESSINTERFACE — The central routine that reads pending rows from the WIP move transaction interface, validates them, invokes the appropriate backflush logic, and posts the resulting transactions or errors.

These routines are not intended as a public, freely callable API—their presence in a "_GRP" package indicates they are grouped internal processors invoked by higher-level WIP public APIs and concurrent programs.

Tables Accessed

Per the documented metadata, WIP_MOVPROC_GRP references two tables through APPS synonyms:

  • WIP_MOVE_TXN_INTERFACE — the staging table holding unprocessed move transactions. PROCESSINTERFACE reads, validates, and updates rows here as move transactions are consumed and posted.
  • WIP_TXN_INTERFACE_ERRORS — the error repository where rows that fail validation are recorded with their associated error messages, enabling users to review and correct rejected transactions.

Additionally, the package relies on the WIP_LOT_SERIAL_OBJ_T object type to manage lot and serial number assignment during backflush and move processing.

Usage Notes

WIP_MOVPROC_GRP is not designed for direct invocation from custom code; it is an internal grouping package. It is referenced by other packages including CSD_HV_WIP_JOB_PVT, WSMPLBMI, and WSM_SERIAL_SUPPORT_GRP (and self-references within WIP_MOVPROC_GRP). These callers confirm integration with job maintenance, shop floor interface, and serial support flows.

In practice, the package is triggered indirectly: move transactions pending in WIP_MOVE_TXN_INTERFACE are processed by the Move Transaction Manager / transaction worker concurrent programs, or through WIP public APIs (such as WIP_MOVE_TXN_PUB) that internally route work to PROCESSINTERFACE and the backflush routines. Administrators and developers should treat it as a supporting internal component—diagnosing failures typically means inspecting the two interface tables for stranded or errored rows rather than calling the package directly.