Search Results ad_merge_action_tables
Overview
The FND_TABLES table is a core metadata repository within the Application Object Library (FND) of Oracle E-Business Suite. It serves as the central registry for all application tables, providing a unified catalog that the EBS framework uses to manage and reference database objects. Its primary role is to decouple the logical application table name from the physical database table name, enabling a layer of abstraction. This abstraction is fundamental for features like multiple reporting currencies, auditing, and descriptive flexfields, as it allows the application logic to reference a consistent logical object while the underlying physical implementation may vary by installation or context.
Key Information Stored
The table's structure is defined by its primary and unique keys, which enforce critical business rules for table registration. The primary key (FND_TABLES_PK) is a composite of APPLICATION_ID and TABLE_ID, providing a unique numeric identifier within the application. Two additional unique keys ensure logical naming consistency: FND_TABLES_UK1 on APPLICATION_ID and USER_TABLE_NAME (the logical name used within the application), and FND_TABLES_UK2 on APPLICATION_ID and TABLE_NAME (the physical database table name). While the provided metadata does not list all columns, standard columns typically include TABLE_NAME, USER_TABLE_NAME, DESCRIPTION, and various control columns for who and when data was created or last updated.
Common Use Cases and Queries
This table is essential for technical administration, reporting, and development within EBS. A common use case is identifying the physical table name when only the application's logical name is known, or vice-versa. For instance, developers often query it to understand table relationships or to verify registration. Sample queries include finding all registered tables for a specific module or locating a table by its logical name.
- Find Physical Name by Logical Name: SELECT table_name, description FROM applsys.fnd_tables WHERE user_table_name = 'RA_CUSTOMER_TRX_ALL' AND application_id = 222;
- List Tables for an Application: SELECT user_table_name, table_name FROM applsys.fnd_tables WHERE application_id = (SELECT application_id FROM fnd_application WHERE application_short_name = 'AR') ORDER BY 1;
- Check Table Registration: SELECT * FROM applsys.fnd_tables WHERE table_name = 'GL_JE_HEADERS';
Related Objects
As indicated by its extensive foreign key relationships, FND_TABLES is a foundational parent table for numerous other Application Object Library metadata tables. Key dependent objects include FND_COLUMNS, which stores column-level metadata for registered tables, and FND_PRIMARY_KEYS and FND_FOREIGN_KEYS, which define key relationships. It is also referenced by flexfield structures (FND_DESCRIPTIVE_FLEXS, FND_ID_FLEXS), audit configurations (FND_AUDIT_TABLES), and alert mechanisms (ALR_ALERTS). The table has a direct foreign key to FND_APPLICATION, linking each registered table to its owning product application.
-
Table: FND_TABLES
12.1.1
owner:APPLSYS, object_type:TABLE, fnd_design_data:FND.FND_TABLES, object_name:FND_TABLES, status:VALID, product: FND - Application Object Library , description: Tables registered in applications , implementation_dba_data: APPLSYS.FND_TABLES ,
-
Table: FND_TABLES
12.2.2
owner:APPLSYS, object_type:TABLE, fnd_design_data:FND.FND_TABLES, object_name:FND_TABLES, status:VALID, product: FND - Application Object Library , description: Tables registered in applications , implementation_dba_data: APPLSYS.FND_TABLES ,