Search Results ad_merge_action_tables

Overview

The AD_MERGE_ACTION_TABLES table is a core metadata repository within the Applications DBA (AD) product family of Oracle E-Business Suite (EBS). It functions as a parameter store, defining the specific database tables that are the targets of actions registered in the AD_MERGE_ACTIONS table. This object is integral to the architecture of EBS patching and maintenance utilities, providing a structured link between high-level administrative actions and the underlying database objects they are designed to modify. Its role is to ensure that merge and data fix operations are executed against the correct tables with the appropriate parameters, thereby maintaining data integrity during system updates.

Key Information Stored

The table's structure is defined by a composite primary key that precisely identifies a table-action relationship. The key columns are APPLICATION_ID and ACTION_ID, which together reference a specific record in the AD_MERGE_ACTIONS table. The TABLE_APPLICATION_ID and TABLE_ID columns form a foreign key to the FND_TABLES registry, uniquely identifying the target database table within the EBS data model. While the exact parameter columns are not detailed in the provided excerpt, the table's description indicates it stores the "actual parameters" for the tables involved in merge actions. This typically includes data necessary for the merge operation, such as conditional logic, column mappings, or specific data values required by the associated AD_MERGE_ACTIONS script.

Common Use Cases and Queries

This table is primarily accessed by the EBS patching engine (AD Merge Patch driver) during the application of patches. Common use cases involve querying the configuration of a specific merge action for diagnostic or audit purposes. For instance, an Applications DBA might run a query to list all target tables for a particular action to understand the patch's scope before execution. A sample diagnostic query would join AD_MERGE_ACTION_TABLES with AD_MERGE_ACTIONS and FND_TABLES to provide a readable report.

SELECT amat.action_id,
       ama.action_type,
       ft.table_name,
       ft.application_id
  FROM ad_merge_action_tables amat,
       ad_merge_actions ama,
       fnd_tables ft
 WHERE amat.application_id = ama.application_id
   AND amat.action_id = ama.action_id
   AND amat.table_application_id = ft.application_id
   AND amat.table_id = ft.table_id
   AND ama.action_id = <specific_action_id>;

Related Objects

AD_MERGE_ACTION_TABLES maintains documented foreign key relationships with two critical EBS metadata tables, forming a core part of the AD utilities' data model.

• AD_MERGE_ACTIONS: This is the parent table. The relationship is defined on the composite key (APPLICATION_ID, ACTION_ID). AD_MERGE_ACTIONS contains the definition of the merge action itself, while AD_MERGE_ACTION_TABLES stores the table-specific execution parameters for that action.
• FND_TABLES: This relationship links to the central EBS table registry. The foreign key on columns (TABLE_APPLICATION_ID, TABLE_ID) ensures that every record in AD_MERGE_ACTION_TABLES points to a valid, registered table within the applications, guaranteeing referential integrity for the target objects of merge operations.