Search Results get_transaction

Overview

WIP_TRANSACTION_PUB is the public (PUB classification) PL/SQL package body owned by APPS that exposes the Work in Process (WIP) transaction API surface in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal purpose is to provide a stable, version-controlled entry point through which external callers — Oracle Forms, concurrent programs, and custom extensions — can query and manipulate WIP shop floor transactions without invoking the underlying private implementation directly. The package body declares the global constant G_PKG_NAME as 'WIP_TRANSACTION_PUB' and follows the standard EBS API architecture in which the public package validates call compatibility and delegates all substantive business logic to the corresponding private package, WIP_TRANSACTION_PVT.

Key Procedures and Functions

ETRM documents a single public procedure for this package: GET_TRANSACTION.

• GET_TRANSACTION — the public query API for retrieving WIP transaction data. It accepts standard EBS API control parameters including an API version number, an initialization message list flag, and a return-values flag, and returns the standard outcome triplet of return status, message count, and message data. Beyond these boilerplate parameters it returns strongly typed PL/SQL record collections covering WIP transactions and their validation information, resource transactions and their validation information, and shop floor move transactions and their validation information. Internally it first calls FND_API.Compatible_API_Call against the local API version (1.0), API name, and package name, raising FND_API.G_EXC_UNEXPECTED_ERROR on a mismatch, then delegates to WIP_TRANSACTION_PVT.GET_TRANSACTION, passing normalized values such as NVL(p_init_msg_list, FND_API.G_FALSE).

No other public procedures or functions are documented for this package body in the ETRM metadata.

Tables Accessed

The ETRM metadata for this object lists no directly referenced tables through APPS synonyms. This is consistent with the package's design: WIP_TRANSACTION_PUB performs no direct SQL against base tables. All table access occurs in the delegated private layer, WIP_TRANSACTION_PVT, which reads and writes the WIP transaction, resource transaction, and shop floor move entities. Callers therefore receive table data exclusively through the typed OUT NOCOPY collection parameters, and this package should not be treated as a data access point for ad hoc SQL.

Usage Notes

WIP_TRANSACTION_PUB is referenced by nine other packages, indicating it is a commonly consumed dependency within the WIP and manufacturing execution stack. Typical invocation patterns include:

• Oracle Forms-based WIP transaction entry and inquiry screens that need to populate blocks with existing transaction records.
• Concurrent programs and batch interfaces that reconcile, report on, or migrate WIP transaction history.
• Custom PL/SQL integrations that require a supported, upgrade-safe API rather than direct table access.

Because GET_TRANSACTION is a read-oriented API returning collection types, callers must declare matching variables of the package's public types (Wiptransaction_Tbl_Type, Wiptransaction_Val_Tbl_Type, Res_Tbl_Type, Res_Val_Tbl_Type, Shopfloormove_Tbl_Type, and Shopfloormove_Val_Tbl_Type), pass p_api_version_number as 1.0, and inspect x_return_status before consuming the returned data. The presence of the p_dummy parameter reflects the standard EBS convention for preserving signature stability across API versions and should be passed as NULL.