Search Results wip_cplproc_priv




Overview
Explore in AI Chat

Overview

WIP_CPLPROC_PRIV is an internal, private PL/SQL package in the APPS schema that supports Oracle Work in Process (WIP) transaction processing in Oracle E-Business Suite 12.1.1 and 12.2.2. Its name combines "WIP" (Work in Process) with "CPL" (complete/completion) and "PROC" (processing), indicating that it exists to process completion transactions — the movement of assemblies from work in process into finished-goods inventory, along with the associated backflushing of components and the allocation of material to those transactions. The "_PRIV" suffix marks the package as a private implementation unit rather than a published public API; it is not intended for direct customer invocation and exposes no supported interface.

In the EBS WIP architecture, completion processing is a multi-step activity that must validate the discrete job or repetitive schedule, confirm operation sequence and completion status, calculate and allocate component quantities (including lot-controlled items), write rows to the transaction interface tables, and finally hand the records to the cost and inventory transaction managers. WIP_CPLPROC_PRIV encapsulates those private steps, which allows the public packages that drive completion — WIP_MOVPROC_PRIV, WIP_MTI_PUB, WIP_MTLTEMPPROC_PRIV, WMA_COMPLETION, and its own recursive reference — to share a single implementation of the completion logic. This design mirrors the standard Oracle pattern of separating a thin public API from a heavier private worker package.

Key Procedures and Functions

The ETRM metadata documents four procedures or functions within WIP_CPLPROC_PRIV. Parameter lists are not reproduced here because the documented metadata does not expose them; the descriptions below are limited to purpose.

  • PROCESSTEMP — Processes temporary or staged records that have been assembled in preparation for a completion transaction. This is the workhorse routine that turns pending interface data into finalized transaction rows, and it is the reason the package's dependency list includes WIP_MTL_ALLOCATIONS_TEMP and MTL_MATERIAL_TRANSACTIONS_TEMP.
  • PREALLOCATESCHEDULES — Performs pre-allocation of material requirements against repetitive schedules (and, in the discrete context, against jobs). Pre-allocation reserves component supply so that completion and backflush transactions can consume it deterministically rather than contending for inventory at transaction time.
  • PROCESSOVERCPL — Handles over-completion: the case where the quantity completed exceeds the quantity the job or schedule was authorized to produce. Over-completion requires validation against the WIP entity, tolerance rules, and the underlying item and parameter settings, all of which are reflected in the package's table dependencies.
  • PROCESSOATXN — Processes the "OA" (operation/assembly) transaction variant associated with completion activity, coordinating the completion record with its related WIP operation and requirement rows.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

  • MTL_TRANSACTIONS_INTERFACE and MTL_TRANSACTION_LOTS_INTERFACE — the transaction interface tables into which completion and component-issue rows (including lot/serial detail) are written for downstream processing by the inventory transaction manager.
  • MTL_MATERIAL_TRANSACTIONS_TEMP and WIP_MTL_ALLOCATIONS_TEMP — temporary staging tables that hold material allocations before they are committed.
  • MTL_MATERIAL_TXN_ALLOCATIONS — the permanent allocation record that ties a transaction to the specific on-hand lots and locators it consumed.
  • WIP_DISCRETE_JOBS, WIP_REPETITIVE_SCHEDULES, WIP_ENTITIES, WIP_OPERATIONS, and WIP_REQUIREMENT_OPERATIONS — the WIP definition tables that establish what was authorized to be built, at which operation, and with which component requirements.
  • MTL_SYSTEM_ITEMS, MTL_LOT_NUMBERS, MTL_PARAMETERS, and MTL_TRANSACTIONS_INTERFACE — item attributes, lot validation, and organization-level parameters that govern completion and backflush behavior.
  • WIP_TRANSACTIONS_S — the WIP transaction table (and its sequence) into which the completion record is ultimately written.
  • PLITBLM — the standard Oracle PL/SQL table-handling package used for array processing, indicating that the procedures operate in bulk against collections of records.

Usage Notes

WIP_CPLPROC_PRIV is invoked indirectly. The ETRM metadata records it as referenced by APPS.WIP_MOVPROC_PRIV, APPS.WIP_MTI_PUB, APPS.WIP_MTLTEMPPROC_PRIV, and the WMA_COMPLETION package (listed twice), and as referencing only SYS.STANDARD. In practice, completion transactions originating in the Work in Process forms (such as the Move Transactions and Completion Transactions windows), from the Material Transaction or WIP Mass Load concurrent programs, or from the Mobile Supply Chain / Warehouse Management completion flows reach this package through those callers. Because the package is private and its procedures are not published as a supported API, customizations should not call it directly; developers needing programmatic completion should use the public interfaces (for example WIP_MTI_PUB or WIP_MOVPROC_PRIV) that Oracle documents and supports. Any change to the package's behavior is exposed to all four referencing packages, making it a sensitive point of impact during patching or upgrade between 12.1.1 and 12.2.2.