Results for “campaign_name”

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

Overview

The AST_CAMPAIGNS_LOV_V view is a TeleSales (AST) module object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a filtered list-of-values (LOV) source that exposes only those campaigns eligible to be selected within the TeleSales application. Rather than presenting the full campaign master, the view applies a strict set of business predicates so that agents and application code see a curated subset of active, non-private, non-template eCampaigns with a valid execution window.

Because the view is oriented toward LOV population and lookup rather than transactional processing, it is commonly consumed by form-based agents, concurrent programs, and reporting layers that require a compact, validated list of campaign identifiers and descriptions. The view is defined as a join of two base objects and returns six columns: CAMPAIGN_SOURCE_CODE, CAMPAIGN_NAME, CAMPAIGN_DESCRIPTION, CAMPAIGN_ID, SOURCE_PROMOTION_ID, and SCRIPT_NAME. Users searching for "campaign_description" will find that semantic content exposed here as the CAMPAIGN_DESCRIPTION column, sourced from the DESCRIPTION attribute of the underlying campaign view.

Underlying Base Objects

The view is defined over two documented base objects:

• AMS_CAMPAIGNS_VL (VIEW) — the multilingual, translation-enabled campaign view aliased as C. It supplies the campaign name, description, campaign identifier, source code, DScript name, and the flag columns used to filter the LOV result set.
• AMS_SOURCE_CODES (SYNONYM) — the source code lookup aliased as S. It provides the SOURCE_CODE_ID value mapped to the campaign through the SOURCE_CODE_FOR_ID relationship.

The two objects are joined on matching SOURCE_CODE values, and the view further enforces that S.SOURCE_CODE_FOR_ID equals C.CAMPAIGN_ID, ensuring the source code record corresponds to the campaign itself. The result set is ordered by C.SOURCE_CODE. The reference to AMS_SOURCE_CODES resolves through a synonym to the underlying source code table, reflecting Oracle's standard practice of exposing base tables through synonyms in the APPS schema.

Key Columns

• CAMPAIGN_SOURCE_CODE — the source code string associated with the campaign; also the ORDER BY key for the LOV.
• CAMPAIGN_NAME — the descriptive campaign name presented to users in the LOV list.
• CAMPAIGN_DESCRIPTION — the campaign's description text, answering the "campaign_description" lookup requirement.
• CAMPAIGN_ID — the unique campaign identifier used as the LOV return value and as a foreign key in downstream TeleSales records.
• SOURCE_PROMOTION_ID — the source code identifier linked to the campaign, useful for joining to source code and promotion logic.
• SCRIPT_NAME — the name of the associated DScript, relevant for TeleSales agents launching a scripted interaction tied to the campaign.

Common Use Cases and Queries

The view is typically queried to populate campaign LOVs, to validate a campaign selection, or to report against currently active campaigns. A representative query retrieving campaign identifiers and descriptions is:

SELECT campaign_id, campaign_name, campaign_description, script_name FROM apps.ast_campaigns_lov_v ORDER BY campaign_source_code;

A targeted lookup by description, matching the common user search, might read:

SELECT campaign_id, campaign_description FROM apps.ast_campaigns_lov_v WHERE UPPER(campaign_description) LIKE UPPER('%&keyword%');

Because filtering is encapsulated within the view, callers inherit the ACTIVE status, eCampaign rollup type, active flag, non-private, show-campaign, non-template, and current-date execution-window constraints automatically, reducing the risk of selecting expired or internal campaigns within TeleSales interfaces.