Search Results source_code_suffix

Overview

AMS_CUSTOM_SETUPS_VL is a seeded, read-only view owned by the APPS schema within the Oracle E-Business Suite Marketing (AMS) module. It is classified as a "VL" (Value List) view, a naming convention used throughout Oracle EBS to denote a view that combines a base ("_B") table with its translation ("_TL") table and exposes a single, language-filtered row per logical record. In the context of Oracle EBS 12.1.1 and 12.2.2, this view presents the master data and descriptive attributes of custom marketing setups — configuration records that control how specific marketing objects, media, and activities behave within the Oracle Marketing application.

Because the view resolves the translated name and description columns automatically according to the session's language, it is the recommended interface for reporting, forms, and integration. Developers should not query the underlying tables directly when translated setup names are required; the VL view guarantees that the correct language row is returned via the USERENV('LANG') predicate.

Underlying Base Objects

The view is defined over two synonyms that resolve to base application tables:

• AMS_CUSTOM_SETUPS_B — the base table (alias B) holding the non-translatable attributes, primary key, object version, and administrative columns.
• AMS_CUSTOM_SETUPS_TL — the translation table (alias T) holding the language-dependent SETUP_NAME and DESCRIPTION columns.

The two tables are joined on CUSTOM_SETUP_ID, with the translation side filtered by T.LANGUAGE = USERENV('LANG'). The view text also exposes B.ROWID as ROW_ID. Both underlying objects are documented in ETRM 12.2.2 as synonyms referenced by this view.

Key Columns

• CUSTOM_SETUP_ID — Primary identifier for the custom setup record; join key between the _B and _TL tables.
• SETUP_NAME — Language-specific translated name of the setup; the primary descriptive column used in value lists.
• DESCRIPTION — Translated long description of the setup.
• ACTIVITY_TYPE_CODE / MEDIA_ID / OBJECT_TYPE — Codes identifying the marketing activity type, media, and object context to which the setup applies.
• SOURCE_CODE_SUFFIX — Suffix used to derive or match source codes for the setup.
• ENABLED_FLAG — Indicates whether the setup is currently active ('Y'/'N').
• APPLICATION_ID — Owning application identifier.
• ALLOW_ESSENTIAL_GROUPING — Flag governing whether essential grouping is permitted for the setup.
• USAGE — Usage classification for the setup record.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO/audit and optimistic locking columns.

Common Use Cases and Queries

Typical scenarios include value-list population for setup selection fields, reporting on active marketing configurations, and integration extracts that require translated setup names. A representative query returning active setups is:

SELECT custom_setup_id, setup_name, description, activity_type_code, enabled_flag FROM apps.ams_custom_setups_vl WHERE enabled_flag = 'Y' ORDER BY setup_name;

To filter by object type or activity type:

SELECT custom_setup_id, setup_name, object_type, media_id FROM apps.ams_custom_setups_vl WHERE object_type = :p_object_type;

Because the view already applies the language predicate, callers do not need to add a LANGUAGE filter. Joins to AMS_CUSTOM_SETUPS_B should be avoided for name/description retrieval, as the VL view supersedes them for display purposes. Access is read-only; DML must target the underlying base and translation tables through supported APIs.