Search Results table_application_id

Overview

AD_MERGE_ACTION_TABLES is an Applications DBA (AD) repository table that stores the actual table-level parameters associated with merge actions defined in AD_MERGE_ACTIONS. It records which database tables participate in a given merge action and the context in which they are processed. In Oracle EBS 12.1.1 and 12.2.2, this object supports the AD Merge/utility infrastructure used during patching, Online Patching (adop) phases, and table-level data migration or consolidation operations. Its role is to bridge an abstract merge action with the concrete set of tables that the action manipulates.

Based on the mined foreign-key structure, the heuristic Data Vault classification for this object is a link table. This classification is a modeling suggestion: AD_MERGE_ACTION_TABLES exists primarily to resolve relationships between two parent entities—the merge action (AD_MERGE_ACTIONS) and the table definition (FND_TABLES)—rather than serving as a standalone hub of business entities. This link-based design reflects its junction-style purpose within the AD schema.

Key Information Stored

Documentation for this table is limited. The metadata identifies a composite primary key, AD_MERGE_ACTION_TABLES_PK, defined over four columns: APPLICATION_ID, ACTION_ID, TABLE_APPLICATION_ID, and TABLE_ID. Because the entire primary key is composite and no separate surrogate key column is documented, the primary key itself functions as the identifying key for each row.

• APPLICATION_ID — The application identifier for the merge action; part of the primary key and the leading column of the foreign key to AD_MERGE_ACTIONS.
• ACTION_ID — The identifier of the specific merge action; the second component of the primary key and part of the foreign key to AD_MERGE_ACTIONS.
• TABLE_APPLICATION_ID — The application identifier for the referenced table; part of the primary key and the leading column of the foreign key to FND_TABLES.
• TABLE_ID — The identifier of the referenced table; the final component of the primary key and part of the foreign key to FND_TABLES.

Together these four columns are both surrogate-identifying (the documented primary key) and business-key candidates, since they map directly to the parent entities in AD_MERGE_ACTIONS and FND_TABLES. No additional descriptive columns are documented in the supplied metadata.

Common Use Cases and Queries

Typical usage centers on identifying which tables are targeted by a given merge action and confirming the table-to-action associations during patch or merge validation. DBA teams may query this table to audit merge action scope, to trace why a particular table was modified during a merge operation, and to reconcile AD_MERGE_ACTIONS definitions against the concrete FND_TABLES entries they reference.

• Listing all tables for a specific merge action:

  SELECT table_application_id, table_id FROM ad_merge_action_tables WHERE application_id = :app_id AND action_id = :action_id;

• Joining to FND_TABLES to resolve table names:

  SELECT a.application_id, a.action_id, t.table_name FROM ad_merge_action_tables a, fnd_tables t WHERE a.table_application_id = t.application_id AND a.table_id = t.table_id;

• Joining to AD_MERGE_ACTIONS to enrich with action-level attributes for reporting and diagnostics.

Related Objects

The most significant related objects are those referenced by the documented foreign keys, plus nearby AD merge infrastructure.

• AD_MERGE_ACTIONS — Parent of this table via AD_MERGE_ACTION_TABLES.APPLICATION_ID and AD_MERGE_ACTION_TABLES.ACTION_ID; defines the merge action whose table parameters are stored here.
• FND_TABLES — Parent via AD_MERGE_ACTION_TABLES.TABLE_APPLICATION_ID and AD_MERGE_ACTION_TABLES.TABLE_ID; supplies the table definition referenced by each row.
• AD_MERGE_ACTION_COLUMNS — Sibling object holding column-level parameters for the same merge actions, complementing the table-level scope captured here.
• AD_MERGE_ACTIONS_PK / AD_MERGE_ACTION_TABLES_PK — Key constraints governing the relationship and uniqueness of rows.