Search Results ad_merge_actions_pk

Overview

AD_MERGE_ACTIONS is a configuration and metadata table within the Applications DBA (AD) product of Oracle E-Business Suite. It stores parameter sets used by the DataExtract and DataMerge utilities, which are infrastructure components leveraged during patching, cloning, and application data migration operations. Each row in AD_MERGE_ACTIONS defines a named action that the extract and merge engine can invoke, scoped to a specific Oracle application registered in FND_APPLICATION.

From a Data Vault modeling perspective, the mined relationship structure classifies AD_MERGE_ACTIONS as satellite-leaning. It functions primarily as a descriptive attribute holder attached to an application-level parent, with dependent child tables keyed back to it. It is not a transactional hub, but rather a reference construct that carries descriptive context (action names, short names, and associated parameter definitions) around an APPLICATION_ID boundary.

Per the ETRM metadata, this object is noted as "Not implemented in this database," indicating that in the specific environment scanned, the table exists in the data model dictionary but is not physically populated or deployed. This is common for utility tables that are only materialized during specific patching or merging operations.

Key Information Stored

The documented metadata exposes a constrained but important set of columns. The most significant are:

• APPLICATION_ID — Identifies the owning Oracle application (FK to FND_APPLICATION). Part of every primary key on the table.
• ACTION_ID — Surrogate identifier for the merge/extract action. Combined with APPLICATION_ID, forms the surrogate primary key AD_MERGE_ACTIONS_PK.
• ACTION_NAME — The descriptive, user-facing name of the action. Together with APPLICATION_ID, forms business key AD_MERGE_ACTIONS_UK1.
• ACTION_SHORTNAME — The abbreviated form of the action name. With APPLICATION_ID, forms business key AD_MERGE_ACTIONS_UK2 — the object the user searched for. This column serves as the alternate unique identifier used by lookup routines and scripts.

Additional parameter-related columns are typically present in the physical implementation (such as parameter strings consumed by DataExtract/DataMerge), but the ETRM excerpt documents only the keys above. The surrogate key is clearly AD_MERGE_ACTIONS_PK (APPLICATION_ID, ACTION_ID); the business keys are ACTION_NAME and ACTION_SHORTNAME, each unique within an application.

Common Use Cases and Queries

Typical use cases include auditing which merge actions are defined for a given application, verifying uniqueness of short names, and joining to child tables to trace parameter sets. Sample patterns:

• Lookup by short name: SELECT * FROM ad_merge_actions WHERE application_id = :app_id AND action_shortname = :sn;
• Application-scoped listing: SELECT action_id, action_name, action_shortname FROM ad_merge_actions WHERE application_id = :app_id ORDER BY action_name;
• Duplicate detection: SELECT action_shortname, COUNT(*) FROM ad_merge_actions GROUP BY application_id, action_shortname HAVING COUNT(*) > 1;
• Dependency trace: join to AD_MERGE_ACTION_TABLES on APPLICATION_ID and ACTION_ID to enumerate affected tables per action.

Reporting use cases focus on patch impact analysis — determining which tables a given merge action will touch before executing an AD utility.

Related Objects

• FND_APPLICATION — referenced via AD_MERGE_ACTIONS.APPLICATION_ID; supplies application context.
• AD_MERGE_ACTION_TABLES — child table referencing AD_MERGE_ACTIONS on (APPLICATION_ID, ACTION_ID); defines which tables each action operates on.
• AD_MERGE_ACTIONS_PK / _UK1 / _UK2 — primary and unique constraints enforcing integrity.
• Adjacent AD utility tables (e.g., AD_MERGE_ACTION_COLUMNS, where implemented) that extend parameter definitions for DataExtract and DataMerge.