Results for “ams_clik_thru_actions_b”

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

Overview

The AMS.AMS_CLIK_THRU_ACTIONS_B table is a foundational metadata repository within the Oracle E-Business Suite Marketing (AMS) module. It stores the definition records for Click Through Destination Actions — the configurable behaviors executed when a recipient interacts with a tracked link in a marketing campaign or HTML email. Each row describes an action definition, including the code that identifies it, the executable or Java class that implements it, the target URL behavior, and various control flags that govern enablement and parameter handling.

The table serves as the master (base) entity in a typical Oracle EBS multilingual, multi-org design. It holds language-independent attributes, while translatable text is stored in the companion AMS_CLIK_THRU_ACTIONS_TL table. The primary key is the surrogate identifier ACTION_ID, enforced by the AMS_CLIK_THRU_ACTIONS_B_PK constraint. In Data Vault modeling terms, the documented foreign-key structure suggests this object behaves as a hub-leaning entity: it holds the durable business key (ACTION_CODE) and receives references from dependent tables, aligning it with a hub pattern.

Key Information Stored

Of the 22 documented columns, the following are the most significant for functional and integration purposes:

• ACTION_ID — the surrogate primary key, uniquely identifying each click-through action definition.
• ACTION_CODE — the business-key candidate, a user-meaningful code along with ZD_EDITION_NAME in the unique index AMS_CLIK_THRU_ACTIONS_B_U1 (ACTION_ID, ZD_EDITION_NAME).
• EXECUTABLE_NAME and JAVA_CLASS_NAME / NEW_JAVA_CLASS_NAME — specify the implementation entry points invoked at click-through time.
• SERVER_URL and PROFILE_FOR_SERVER_URL — define the destination endpoint and the profile option sourcing the URL.
• APPLICATION_ID and DEPENDS_ON_APP — link the action to an Oracle application and express application dependencies.
• TRACK_FLAG, ENABLED_FLAG, DYNAMIC_PARAMS_FLAG, and ADHOC_PARAMS_FLAG — control tracking, activation, and parameter resolution behavior.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, enforcing data-level security.
• Standard Who columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and ZD_EDITION_NAME support auditing, concurrency control, and editioning.

Common Use Cases and Queries

Administrators and developers query this table to audit available click-through actions, diagnose campaign link behavior, and validate that enabled actions reference valid applications. A representative query joins the base and translation tables to retrieve localized descriptions:

SELECT b.action_id, b.action_code, b.enabled_flag,
       t.action_name, t.description
FROM   ams.ams_clik_thru_actions_b b,
       ams.ams_clik_thru_actions_tl t
WHERE  b.action_id = t.action_id
AND    b.enabled_flag = 'Y';

Reporting scenarios include listing all actions tied to a specific APPLICATION_ID, identifying actions with dynamic or ad-hoc parameter support, and reconciling click-through usages against their definitions via AMS_CLIK_THRU_USAGES.

Related Objects

• AMS_CLIK_THRU_ACTIONS_TL — holds translated name and description text; joined on ACTION_ID.
• AMS_CLIK_THRU_USAGES — records usage relationships; references AMS_CLIK_THRU_ACTIONS_B.ACTION_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID to enforce security group associations.
• FND_APPLICATION — implied lookup for APPLICATION_ID and application dependency resolution.
• FND_PROFILE_OPTION_VALUES — relevant where PROFILE_FOR_SERVER_URL resolves destination URLs.