Search Results process_resource_transaction

Overview

APPS.WIP_TRANSACTION_PVT is a private (PVT) PL/SQL package within the Oracle E-Business Suite Work in Process (WIP) application module. It forms the internal implementation layer that supports the public transaction API, WIP_TRANSACTION_PUB, by encapsulating the low-level processing logic for Work in Process transactions. The package is declared with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the calling user rather than the package owner, a design choice consistent with EBS API conventions that rely on APPS synonyms and invoker's rights security.

The package serves as the engine that validates, defaults, and persists WIP transaction records originating from shop floor activity, resource charges, outside processing operations, and related manufacturing events. It is not intended to be called directly by external consumers; rather, it is invoked by the public API layer and other internal WIP components that orchestrate transactional integrity across the manufacturing execution process. The header comment indicates a version of 1.0 with a $Header tag dated 2002, reflecting the long-standing stability of this interface across EBS releases including 12.1.1 and 12.2.2.

Key Procedures and Functions

The documented package exposes three procedures, each addressing a distinct segment of the WIP transaction lifecycle:

• PROCESS_RESOURCE_TRANSACTION — The procedure most relevant to the user query "process_resource_transaction". It accepts a resource transaction record (p_res_txn_rec of type WIP_Transaction_PUB.Res_Rec_Type) and processes a resource charge against a work order or job. It supports a validation level parameter (defaulting to COMPLETE, with constants NONE = 0, REQUIRED = 5, and COMPLETE = 10 defined in the package) and returns standard API messaging outputs including return status, message count, and message data. This procedure underpins resource cost collection and shop floor resource usage entry.
• PROCESS_OSP_TRANSACTION — Handles outside processing (OSP) transactions, accepting an OSP record (p_OSP_rec) of type Res_Rec_Type alongside the same validation and messaging parameters. OSP transactions represent services performed by external suppliers against a work order, and this procedure validates and persists those events.
• GET_TRANSACTION — A retrieval procedure that returns WIP transaction data across three collection outputs: WIPTransaction_tbl, Res_tbl, and ShopFloorMove_tbl. It accepts an API version number, initialization flag, and a dummy parameter, and returns messaging outputs along with the populated table collections for downstream consumption.

The validation level constants (NONE, REQUIRED, COMPLETE) allow callers to control the depth of validation performed during processing, a common EBS pattern balancing performance against data integrity.

Tables Accessed

The ETRM metadata does not enumerate specific base tables referenced through APPS synonyms. Based on the package's function and the WIP schema, the procedures operationally interact with core WIP tables such as WIP_TRANSACTIONS, WIP_MOVE_TRANSACTIONS, WIP_RESOURCE_TRANSACTIONS (or equivalent resource charge staging tables), WIP_ENTITIES, and BOM resource definitions. GET_TRANSACTION clearly reads transaction, resource, and shop floor move data to construct its output collections. Because the package uses AUTHID CURRENT_USER and synonyms, all underlying table access resolves through the APPS schema at runtime. The absence of a documented table list indicates the package is classified purely as a private implementation artifact rather than a documented integration point.

Usage Notes

WIP_TRANSACTION_PVT is referenced by four other packages according to the ETRM metadata, confirming its role as a shared internal dependency. It is typically invoked indirectly through WIP_TRANSACTION_PUB, which is the sanctioned public interface used by Oracle Work in Process forms (such as the Move Transactions, Resource Transactions, and Completion Transactions windows), the Shop Floor Material and Resource transaction flows, and interface concurrent programs. Customizations and extensions should always call the public API layer rather than this private package, since Oracle does not guarantee backward compatibility for PVT objects across patches or point releases. Developers performing diagnostics on resource transaction processing (the "process_resource_transaction" search term) will find this package in the call stack beneath WIP_TRANSACTION_PUB, but direct invocation is discouraged in favor of the supported public entry points that enforce validation level, initialization, and message handling consistently.