Search Results register_database

Overview

The package body APPS.FND_CONC_DATABASE belongs to the Oracle E-Business Suite Applications Object Library and is owned by the APPS schema. Its header stamp ($Header: AFCPDBMB.pls 115.1 2003/10/24) indicates it is an original Release 11i-era concurrent processing component that has been carried forward, unchanged in behavior, into both 12.1.1 and 12.2.2. The package encapsulates the registration layer of the Oracle EBS concurrent processing environment. In a multi-tier deployment, the concurrent managers, concurrent programs, and their associated database connections must be declared to the application tier so that the concurrent processing subsystem can route work correctly. FND_CONC_DATABASE provides the programmatic entry points used to declare a database, to declare an instance (including its task, host, port, and SID details), and to assign a database to a concurrent processing context.

Notably, the shipped implementation is a stub. Each function returns a literal TRUE without executing any DML. This confirms that the package is a placeholder retained for interface compatibility rather than an active component in the standard Oracle EBS data model; the equivalent registration data is maintained through the Concurrent Managers and Nodes setup forms and their underlying FND tables.

Key Procedures and Functions

The ETRM metadata documents three callable functions in this package body:

• REGISTER_DATABASE — Declares a database to the concurrent processing subsystem. The signature accepts a database name and domain, a two-task indicator, a host name, and a port number, reflecting the connection attributes needed to reach the database from the application tier.
• REGISTER_INSTANCE — Declares a specific database instance within a registered database. Its parameters extend the database identity with the instance name and number, the task designation, host and port information, the instance SID, plus configuration and description text.
• ASSIGN_DATABASE — Associates a previously declared database with an assignment context, taking the database name and an assignment indicator.

All three functions return a BOOLEAN success flag. Because the bodies simply return TRUE, no validation, lookup, or persistence is performed in the delivered code.

Tables Accessed

The documented metadata lists no tables referenced via APPS synonyms for this package body. Every function is a no-op stub, and no INSERT, UPDATE, SELECT, or DELETE statements are executed. Consequently, no FND concurrent processing tables — such as the concurrent manager, node, or database registration tables that one would expect a functional implementation to touch — are read or written by this package in its shipped form.

Usage Notes

Because the functions are inert stubs, invoking FND_CONC_DATABASE produces no system change and always reports success. Oracle does not call it from standard concurrent manager startup or from the Concurrent Managers setup forms. Its practical relevance today is limited to two scenarios. First, custom or third-party code that historically referenced APPS.FND_CONC_DATABASE can continue to compile and execute without raising errors, preserving upward compatibility across 12.1.1 and 12.2.2. Second, the source serves as a template for sites that wish to supply their own registration logic by reimplementing the package body. The metadata records zero dependent packages, so removing or overriding it would not cascade to other documented objects. The package has no impact on concurrent processing behavior and should not be relied upon to register databases or instances in a production environment.