Results for “ams_clik_thru_act_params_vl”

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

Overview

The AMS_CLIK_THRU_ACT_PARAMS_VL view is a seeded, VALID database object in the APPS schema, owned by Oracle Applications and delivered as part of the AMS – Marketing product module. It belongs to the Oracle E-Business Suite click-through (interaction tracking) subsystem, which drives campaign execution, telemarketing scripts, and marketing action processing. The _VL suffix identifies it as a "view with language" — a translated (MLS) view that joins a base (_B) table to its translation (_TL) table so that the descriptive columns are returned in the session's current language.

Functionally, the view presents the parameter definitions that govern a click-through action. Each row describes one parameter that a marketing action exposes to the caller or UI, together with attributes such as whether it is enabled, whether it is mandatory, and whether its value must be encrypted. Because it resolves language automatically via USERENV('LANG'), the view is the preferred access path for reporting, extensions, and integrations that must display parameter meanings and descriptions to a user without hard-coding a language code. It is a read-only projection of the two underlying tables; no DML is performed against the view itself.

Underlying Base Objects

ETRM documents the view as defined over two referenced base objects, both exposed to APPS as synonyms:

• AMS_CLIK_THRU_ACT_PARAMS_B — the base (non-translated) table holding the primary keys, foreign keys to the action, and the flag columns.
• AMS_CLIK_THRU_ACT_PARAMS_TL — the translation table holding language-dependent descriptive text, keyed by ACTION_PARAM_ID plus LANGUAGE.

The view text confirms a simple equi-join on ACTION_PARAM_ID between the two tables, with the filter T.LANGUAGE = USERENV('LANG'). All non-translated columns (flags, identifiers, audit columns, and the object version number) originate from the _B table, while ACTION_PARAM_CODE_MEANING and DESCRIPTION originate from the _TL table. The join is not outer-joined in the documented view text, so a parameter row appears only when a translation exists for the current session language.

Key Columns

• SECURITY_GROUP_ID — multi-tenant/security grouping attribute inherited from the base table; relevant to row-level access and data segregation.
• ACTION_PARAM_ID — primary key and join key. Uniquely identifies the parameter and links the _B and _TL rows.
• ACTION_PARAM_CODE and ACTION_PARAM_CODE_MEANING — the internal parameter identifier and its translated display text.
• ACTION_ID and ACTION_CODE — the parent click-through action to which the parameter belongs.
• ENABLED_FLAG, MANDATORY_FLAG, ENCRYPT_FLAG — Y/N indicators controlling whether the parameter is active, required, and must be encrypted at capture.
• DESCRIPTION — translated long description of the parameter's purpose.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY, OBJECT_VERSION_NUMBER — standard EBS audit and optimistic-locking columns.

Common Use Cases and Queries

Typical uses include validating click-through action configuration before campaign execution, building custom marketing reports, and extracting parameter metadata into external integrations. A representative query lists all enabled, mandatory parameters for a given action:

• SELECT action_param_id, action_param_code, action_param_code_meaning, action_id, encrypt_flag FROM apps.ams_clik_thru_act_params_vl WHERE action_id = :p_action_id AND enabled_flag = 'Y' AND mandatory_flag = 'Y';
• Reporting parameter usage by action: SELECT action_code, COUNT(*) FROM apps.ams_clik_thru_act_params_vl GROUP BY action_code;
• Identifying secure parameters: SELECT action_param_code, action_param_code_meaning FROM apps.ams_clik_thru_act_params_vl WHERE encrypt_flag = 'Y';

Because the view is language-sensitive, ensure the concurrent request or session language is set correctly so that the expected translation rows are returned.