Search Results pa_cint_rate_multipliers




Overview
Explore in AI Chat

Overview

The FND_APPLICATION table is a core repository table within the Oracle E-Business Suite Application Object Library (FND). It serves as the master registry for all applications, modules, and products registered within the Oracle EBS 12.1.1 and 12.2.2 instances. Every discrete software component, from major product families like General Ledger (GL) to underlying technology stacks, must have a corresponding entry in this table. Its primary role is to provide a centralized, unique identifier for all applications, enabling the EBS architecture to manage and reference them consistently across the entire system for functions like data partitioning, security, navigation, and module integration.

Key Information Stored

The table's structure is designed to uniquely identify and describe each registered application. The most critical columns, as indicated by the primary and unique keys in the metadata, are APPLICATION_ID and APPLICATION_SHORT_NAME. APPLICATION_ID is the numeric primary key (FND_APPLICATION_PK) used as a foreign key by hundreds of other tables throughout the EBS database. APPLICATION_SHORT_NAME is a unique, abbreviated identifier (FND_APPLICATION_UK2), such as 'SQLAP' for Payables or 'FND' for the Application Object Library itself, frequently used in API calls and seed data scripts. While the provided metadata excerpt does not list all columns, standard implementations of this table also typically include columns for the full APPLICATION_NAME, a BASE_PATH, and product version information.

Common Use Cases and Queries

This table is fundamental for technical administration, reporting, and development. Common use cases include resolving module-specific data by joining to transaction tables, generating application-level inventory reports, and writing conditional logic in database scripts or concurrent programs. A foundational query retrieves all registered applications:

  • SELECT application_id, application_short_name, application_name FROM fnd_application ORDER BY application_id;

To identify the source application for specific transactional data, a developer would join FND_APPLICATION to a related table using the APPLICATION_ID foreign key. For instance, querying alerts might involve joining ALR_DISTRIBUTION_LISTS to FND_APPLICATION. The APPLICATION_SHORT_NAME is essential when using many FND APIs, such as FND_GLOBAL.APPS_INITIALIZE, to set the correct application context.

Related Objects

As the central application registry, FND_APPLICATION has extensive dependencies. The provided metadata lists a subset of foreign key relationships, demonstrating its reach across diverse modules like Alert Manager (ALR_DISTRIBUTION_LISTS), Application Desktop Integrator (AD_MERGE_ACTIONS), and Marketing (AMS_CAMPAIGNS_ALL_B). This pattern repeats across virtually all EBS modules, confirming that any table storing data specific to a product module will typically include an APPLICATION_ID column referencing FND_APPLICATION. Key related views include FND_APPLICATION_TL for translated names and FND_APPLICATION_VL. The table is also intrinsically linked to the FND_PRODUCT_INSTALLATIONS table, which tracks installation status and version details for each registered application.