Search Results fnd_cp_tmsrv_pipe




Overview
Explore in AI Chat

Overview

FND_CP_TMSRV_PIPE is a PL/SQL package body owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. The package forms part of the Oracle Application Object Library (FND) infrastructure that supports the concurrent manager and its timestamp server framework. Its designation as a "PIPE" package indicates that its primary purpose is to broker inter-process communication between concurrent manager processes through the DBMS_PIPE facility supplied by Oracle Database. The concurrent processing subsystem relies on such pipe-based messaging to synchronise process status, heartbeat and timestamp information across sessions rather than through direct SQL polling. FND_CP_TMSRV_PIPE therefore serves as the low-level transport layer that the higher-level timestamp service logic (contained in FNDCP_TMSRV) uses to initialise a communication channel, transmit messages onto it, and read messages from it.

Key Procedures and Functions

The documented metadata identifies three public program units within the package body:

  • INITIALIZE — Establishes the internal state and pipe resources required before any message exchange takes place. It is typically called once by the invoking process to prepare the package for subsequent reads and writes, ensuring that the timestamp server has a consistent channel to work with.
  • WRITE_MESSAGE — Encapsulates a message payload and places it on the DBMS_PIPE channel for consumption by the receiving concurrent manager or timestamp server session. It abstracts the pipe-specific mechanics from the calling code.
  • READ_MESSAGE — Retrieves a message from the pipe channel and returns its contents to the caller. Together with WRITE_MESSAGE it provides the symmetric send/receive interface used by the timestamp service.

The metadata does not document parameter signatures, and no parameter lists should be assumed beyond the purposes described above.

Tables Accessed

FND_CP_TMSRV_PIPE does not reference any application tables. Its only documented external object is DBMS_PIPE, the Oracle-supplied PL/SQL package for session-to-session communication. Reference is made to DBMS_PIPE through an APPS synonym. Persistent data storage is not the concern of this package; the "messages" it handles are transient in-memory payloads travelling across a named database pipe, and the package's own state is held in package globals rather than in tables.

Usage Notes

This package is internal infrastructure and is not intended for direct invocation from forms, concurrent programs or customer extensions. It is referenced by at least one other package — FNDCP_TMSRV, the timestamp server implementation — which calls INITIALIZE, WRITE_MESSAGE and READ_MESSAGE to manage its pipe traffic. Dependency information further shows FND_CP_TMSRV_PIPE depending on FND_CONC_GLOBAL, the global state package for concurrent processing, and on the STANDARD package. Notably, the object is not referenced by any other database object beyond its listed dependents, confirming its position at the edge of the dependency graph.

Because pipe operations are session-scoped, correct use requires that the pipe be created, written to and read from within compatible database sessions; the concurrent manager processes running on the application tier satisfy this requirement. During upgrades or patching, the object is validated as part of the FND product set, and its VALID status in 12.1.1 and 12.2.2 indicates no outstanding compilation errors. Administrators diagnosing concurrent manager communication faults may encounter this package in dependency traces, but remediation should be directed at the concurrent processing configuration rather than at the package itself.