Search Results fnd_trn_request_id_s

Overview

APPS.FND_TRANSACTION is a valid PL/SQL package body in the Oracle E-Business Suite Applications schema, classified as OTHER within the ETRM repository for releases 12.1.1 and 12.2.2. Its purpose is to provide the runtime services that underpin the EBS Transaction Manager infrastructure. In this context "transactions" refer not to financial or inventory transactions but to the generic event propagation mechanism used by the Applications framework to route work requests, pass payloads between concurrent processes, and record diagnostic trails for those operations.

The package body encapsulates the low-level plumbing that the Transaction Manager relies upon: it captures environment and NLS context, resolves application and responsibility information, manages unique request identifiers, and dispatches events into the Transaction Manager pipeline. Because it is a package body with no documented public API classification, it is treated as an internal framework utility rather than a formally supported customer-facing API. Its status is VALID, indicating the compiled body is present and usable in a standard installation.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions within the package body:

• SYNCHRONOUS — Drives the synchronous execution path for a Transaction Manager transaction, allowing the calling session to post and process a transaction within the same call rather than deferring it to an asynchronous consumer.
• GET_VALUES — Retrieves the contextual values needed to build a transaction payload, drawing on application, responsibility, and profile settings resolved at runtime.
• DEBUG_INFO — Populates or returns diagnostic information used when tracing transaction processing, supporting the concurrent debug facility.
• POST_TM_EVENT — Publishes an event into the Transaction Manager event stream, writing the event record and coordinating with the queue and pipe components so downstream listeners can consume it.

No parameter signatures are documented in the ETRM extract; parameter lists are intentionally omitted here to avoid speculation.

Tables Accessed

The package body references the following objects, primarily through APPS synonyms:

• FND_APPLICATION, FND_RESPONSIBILITY, FND_PROFILE — supply application, responsibility, and profile option context for each transaction.
• FND_CONCURRENT_PROGRAMS, FND_CONCURRENT_QUEUES, FND_CONC_PROCESSOR_PROGRAMS — resolve the concurrent program and queue/processor configuration associated with a transaction request.
• FND_CONCURRENT_DEBUG_INFO — stores debug trace details generated by DEBUG_INFO.
• FND_TM_EVENTS — the Transaction Manager event repository written by POST_TM_EVENT.
• FND_TRN_REQUEST_ID_S — the sequence supplying unique transaction request identifiers.

Utility dependencies include DBMS_RANDOM, DBMS_UTILITY, DUAL, and V$NLS_PARAMETERS, used for session identity, NLS environment detection, and random or deterministic value generation. The package also depends on FND_GLOBAL, FND_MESSAGE, FND_TRANSACTION_PIPE, and FND_TRANSACTION_QUEUE within the Applications schema.

Usage Notes

FND_TRANSACTION is an internal framework component rather than a documented public API. It is typically invoked indirectly — by concurrent managers, the Transaction Manager event pipeline, or framework code that posts and consumes events — rather than being called directly from forms or custom PL/SQL. The ETRM metadata records that the package is referenced by 22 other database objects while not being referenced by any object itself at the top level, confirming its role as a foundational dependency near the base of the EBS concurrency and event stack.

Because it is not classified as a public API, direct invocation from custom code is discouraged; integrators should use supported Transaction Manager or concurrent program interfaces instead. Where debugging is required, the debug information produced via DEBUG_INFO and stored in FND_CONCURRENT_DEBUG_INFO is the appropriate observation point.