Results for “table_name”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AD_MERGED_TABLES is a metadata table owned by the APPLSYS schema within the Applications DBA (AD) product of Oracle E-Business Suite. It records the database tables that have been processed by the DataMerge utility, an AD administrative program used to consolidate data across Oracle IDs and applications during cloning, migration, and multi-organization operations. Each row documents a specific combination of application, table name, and Oracle schema under which a merge action has occurred.

Because the table stores the associations between an application, a physical table, and the Oracle user (schema) that owns or has participated in the merge, the ETRM relationship data classifies this object heuristically as a link table in a Data Vault modeling sense. It connects two independent hub entities — FND_APPLICATION and FND_ORACLE_USERID — through a single table that also carries the merged table identity. This classification is a modeling suggestion rather than a declared constraint.

Key Information Stored

The documented physical schema contains three columns, all of which form the primary key and the unique business key. There is no separate surrogate key; the composite key serves as the natural identifier.

  • APPLICATION_ID — The numeric identifier of the Oracle EBS application to which the merged table belongs. This is a foreign key to FND_APPLICATION and distinguishes, for example, tables belonging to General Ledger versus Inventory.
  • TABLE_NAME — The physical name of the database table that was subject to a DataMerge operation. This is the descriptive business attribute of the row.
  • ORACLE_ID — The identifier of the Oracle user (schema) associated with the merge, foreign keyed to FND_ORACLE_USERID. It indicates which Oracle account's data was consolidated or targeted.

The primary key AD_MERGED_TABLES_PK and the unique index AD_MERGED_TABLES_U1 both cover the identical column set (APPLICATION_ID, TABLE_NAME, ORACLE_ID), confirming that no other business-key candidates exist in the documented schema. Every column is therefore both a key component and a meaningful attribute.

Common Use Cases and Queries

DBAs and technical consultants query this table to audit which tables have already undergone DataMerge processing, to determine whether a merge was performed for a given application or schema, and to troubleshoot data inconsistencies following a clone or migration. Because a table can be merged separately for multiple Oracle IDs, the ORACLE_ID column is essential when verifying the completeness of a merge.

A typical query returns all merged tables for a specific application:

  • SELECT TABLE_NAME, ORACLE_ID FROM APPLSYS.AD_MERGED_TABLES WHERE APPLICATION_ID = :app_id ORDER BY TABLE_NAME;

To resolve schema names for a merged table, join to FND_ORACLE_USERID:

  • SELECT m.TABLE_NAME, u.ORACLE_USERNAME FROM APPLSYS.AD_MERGED_TABLES m, APPLSYS.FND_ORACLE_USERID u WHERE m.ORACLE_ID = u.ORACLE_ID AND m.APPLICATION_ID = :app_id;

These patterns support reporting on merge coverage, pre-upgrade validation, and reconciliation of objects across the APPLSYS and product schemas.

Related Objects

The following objects are the most significant referenced by or referencing AD_MERGED_TABLES, based on the documented foreign keys and primary key definitions:

  • FND_APPLICATION — joined on AD_MERGED_TABLES.APPLICATION_ID = FND_APPLICATION.APPLICATION_ID; supplies the application short name and description.
  • FND_ORACLE_USERID — joined on AD_MERGED_TABLES.ORACLE_ID = FND_ORACLE_USERID.ORACLE_ID; supplies the Oracle schema/user name.
  • AD_MERGED_TABLES_PK — the primary key constraint enforcing uniqueness on (APPLICATION_ID, TABLE_NAME, ORACLE_ID).
  • AD_MERGED_TABLES_U1 — the unique index mirroring the primary key columns and serving as the sole business-key candidate.
  • FND_TABLES — commonly referenced alongside AD_MERGED_TABLES when validating that a merged table exists in the application dictionary for the same APPLICATION_ID and TABLE_NAME.

Together these relationships establish AD_MERGED_TABLES as a narrow but authoritative link between applications, physical tables, and Oracle schemas within the Applications DBA administrative model.