Search Results put_values

Overview

FNDCP_TMSRV is the Transaction Manager server package body in the Oracle E-Business Suite Concurrent Processing architecture. In Oracle EBS 12.1.1 and 12.2.2, the Transaction Manager (TM) is the middle-tier component that receives requests from the Concurrent Manager (CM) and performs the privileged work of launching, monitoring, and terminating operating-system level concurrent processes. FNDCP_TMSRV encapsulates the server-side logic that the TM executes when it services jobs placed on its queue by the Concurrent Manager.

The package belongs to the APPS schema, is documented with a status of VALID, and is classified under API classification OTHER. It exposes eleven documented procedures and functions and is referenced by two other packages. Its dependency list confirms its role as an infrastructure component: it references Concurrent Processing dictionary tables rather than application business tables.

Key Procedures and Functions

• INITIALIZE — Performs startup initialization for the Transaction Manager service, establishing the runtime context required before messages are processed.
• MONITOR_SELF and MONITOR_SELF2 — Monitor the health and status of the Transaction Manager process itself, providing the self-check mechanism used for liveness and availability tracking.
• READ_MESSAGE and WRITE_MESSAGE — Read from and write to the Transaction Manager queue, which is the communication channel between the Concurrent Manager and the Transaction Manager.
• DEBUG and DEBUG_INFO — Emit diagnostic information for troubleshooting the Transaction Manager, with DEBUG_INFO interacting with the FND_CONCURRENT_DEBUG_INFO table.
• GET_ORACLE_ACCOUNT — Resolves the Oracle database account information required by the Transaction Manager, drawing on FND_ORACLE_USERID.
• PUT_VALUE — Stores a value in the internal state or pipe used by the Transaction Manager service loop.
• STOP_TM — Shuts down the Transaction Manager, allowing an orderly termination of the service process.

As with all ETRM-documented objects, parameter lists are not reproduced here; only the documented names and purposes are described.

Tables Accessed

• FND_CONCURRENT_QUEUES — Provides the definition of the queue that the Transaction Manager services, including the association between the queue and the Transaction Manager.
• FND_CONCURRENT_PROCESSES — Supplies information about running concurrent processes so that the Transaction Manager can monitor and manage them.
• FND_CONCURRENT_DEBUG_INFO — Stores debugging information emitted by the DEBUG and DEBUG_INFO routines.
• FND_ORACLE_USERID — Used by GET_ORACLE_ACCOUNT to resolve Oracle account credentials.
• FND_DATA_GROUP_UNITS — Provides the data group unit definitions associated with the environment in which the Transaction Manager operates.

The package additionally references DBMS_UTILITY under both PUBLIC and SYS, together with DUAL, FND_GLOBAL, FND_MESSAGE, FND_PROFILE, and the internal FND_CP_TMSRV_PIPE and FND_CP_TMSRV_QUEUE objects that implement the TM communication mechanism.

Usage Notes

FNDCP_TMSRV is internal infrastructure and is not intended for direct invocation from Oracle Forms or custom application code. It is invoked as part of Transaction Manager startup and its service loop on the concurrent processing tier, where the TM interacts with the Concurrent Manager through the pipe and queue objects named in its dependency list.

In 12.1.1 and 12.2.2 the Transaction Manager continues to be started through the standard Concurrent Processing administration scripts. Because FNDCP_TMSRV is referenced by two other packages, it should be treated as a dependency when diagnosing Concurrent Processing or Transaction Manager issues; disabling or modifying it is unsupported. The presence of DBMS_UTILITY in its dependency chain is expected for a low-level TM service that must manipulate and inspect database-level constructs while executing OS-level process operations.