Search Results po_move

Overview

APPS.WIP_TRANSACTION_PVT is the private implementation package body that supports the public Work in Process transaction API layer in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It encapsulates the internal business logic used to validate, default, and execute shop floor and outside processing (OSP) transactions against work orders and repetitive schedules. Because it is a Private (PVT) classified package, it is not intended for direct invocation by external or customer-written code; instead it is called by the corresponding public package interfaces and by other EBS products that require WIP transaction processing.

The package operates within the standard EBS API framework, accepting initialization flags such as p_init_msg_list, returning standard API status values (p_return_status), and populating the FND message stack through p_msg_count and p_msg_data. The header comment identifies it as WIPVTXNB.pls, and the body includes global constants and logging infrastructure used to trace execution. The excerpt confirms extensive use of WIP_Transaction_PUB record types (Res_Rec_Type and ShopFloorMove_Rec_Type) and G_MISS default record constants, indicating that the package participates actively in the WIP public API architecture rather than acting as a standalone utility.

Key Procedures and Functions

ETRM documents three procedures and functions within this package body.

• PROCESS_OSP_TRANSACTION — Handles outside processing transactions. It accepts an OSP resource record (Res_Rec_Type), a validation level, and the standard API messaging parameters, then performs validation and processing of OSP moves. The source excerpt shows it initializes both an OSP record and a ShopFloorMove record from G_MISS constants, and passes an "old" OSP record into wip_validate_res, referencing Enhancement 2665334. This confirms the procedure performs attribute-level validation and interfaces with the WIP resource validation logic.
• GET_TRANSACTION — Retrieves transaction information, typically used to query the current state or attributes of a WIP transaction before or after processing.
• PROCESS_RESOURCE_TRANSACTION — Processes resource transactions on work orders, applying resource usage or charges associated with shop floor activity.

No parameter lists are fabricated here; only documented procedure names and their described purposes are reported.

Tables Accessed

The documented metadata for this package lists no tables referenced via APPS synonyms. This is consistent with a PVT package whose data access is largely channeled through companion validation and publication packages. In practice, WIP transaction processing of this kind ultimately touches core WIP and BOM tables, but the ETRM metadata does not enumerate specific tables for this object, and none are asserted here.

Usage Notes

The package is referenced by four other packages, confirming that it functions as an internal dependency rather than a directly called API. Typical invocation occurs indirectly when Oracle Forms, concurrent programs, or the public WIP_Transaction_PUB API validate and execute shop floor and OSP transactions. The "po_move" search term suggests user interest in purchase-order-linked OSP moves, which fall under PROCESS_OSP_TRANSACTION. Custom code should invoke the public API rather than this private package, as its signature and behavior are subject to change and are not part of the supported external interface.