Search Results schedule_alloc

Overview

WIP_MOVPROC_PRIV is a private PL/SQL package in the APPS schema that encapsulates the low-level processing logic for Work in Process (WIP) material movement transactions in Oracle E-Business Suite. It functions as the internal execution engine that validates, processes, and commits move transactions originating from a variety of WIP sources: discrete work orders, repetitive schedules, flow schedules (mixed-model and rate-based), batch moves, and WIP material interface loads. The package sits beneath the public-facing API layer, most notably WIP_MOVPROC_PUB, and performs the detailed work of resolving transaction types, allocating material, calculating variances, updating balances, and writing rows to the material transaction tables. It is classified in the ETRM repository as an OTHER API, indicating it is not intended for direct customer invocation but rather as a support package for Oracle's delivered programs and a small set of companion private packages.

Key Procedures and Functions

The package exposes seven documented procedures. Each performs a discrete step in the move transaction lifecycle:

• MOVE_WORKER — the principal worker routine that drives the processing of a single move transaction record, orchestrating validation and update logic.
• PROCESSINTF — processes move transactions arriving through the WIP material transaction interface, handling records staged for open interface processing.
• PROCESSOATXN — processes move transactions associated with outside (subcontracted) processing operations, managing the return and consumption of items at the supplier.
• REPETITIVE_SCRAP — handles scrap transactions against repetitive schedules, applying the appropriate scrap accounting and quantity adjustments.
• SCHEDULE_ALLOC — performs allocation logic for schedules, resolving quantities and resources tied to a specific schedule during movement.
• INSERT_RECORD — inserts a new move transaction record into the temporary or staging structures used during processing.
• CLEAN_UP — removes residual temporary records and releases working storage after transaction processing completes.

Because the package is private and these routines are internal, no public parameter signatures are documented for customer use; Oracle does not guarantee them as an extension point.

Tables Accessed

WIP_MOVPROC_PRIV reads and writes a wide array of WIP, inventory, costing, and HR tables (referenced through APPS synonyms). Material transaction tables — MTL_MATERIAL_TRANSACTIONS, MTL_MATERIAL_TRANSACTIONS_S, MTL_MATERIAL_TRANSACTIONS_TEMP, and MTL_MATERIAL_TXN_ALLOCATIONS — are central, since move transactions ultimately create and allocate inventory material movements. MTL_ITEM_LOCATIONS, MTL_LOT_NUMBERS, and MTL_ITEM_REVISIONS supply location, lot, and revision validation for the items being moved. Resource and routing data come from BOM_RESOURCES, BOM_DEPARTMENTS, BOM_CALENDAR_DATES, and ENG_REVISED_ITEMS. Costing information is drawn from CST_ACTIVITIES and CST_DEPARTMENT_OVERHEADS to compute overhead and activity charges. Employee and organization context is resolved through FND_USER and HR_ORGANIZATION_INFORMATION. These tables together allow the package to validate the transaction, determine quantities and costs, and persist the resulting inventory and WIP accounting entries.

Usage Notes

WIP_MOVPROC_PRIV is not intended for direct invocation by end users or custom code. It is referenced by eight other packages, including WIP_MOVPROC_PUB, WIP_BFLPROC_PRIV, WIP_CPLPROC_PRIV, WIP_DISCRETE_WS_MOVE, WIP_MOVPROC_GRP, WIP_BATCH_MOVE, WIP_MTLTEMPPROC_PRIV, and WMA_MOVE, and it references the SYS.STANDARD package. In practice it is invoked indirectly when users perform move transactions through the WIP Material Transactions form, when the WIP Material Transaction Interface concurrent program processes staged records, and when batch, flow, or repetitive move operations are submitted. Custom developers should always call the supported public API (WIP_MOVPROC_PUB) rather than this private package, as its procedures, parameters, and logic are subject to change without notice across releases and patches.