Results for “partner_flag”

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

Overview

AST_LS_CAMPAIGNS_V is a TeleSales (AST) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It consolidates campaign, source code, channel, media, schedule, and product hierarchy information into a single denormalized projection, allowing TeleSales agents, campaign managers, and reporting tools to query marketing campaign attributes without navigating the underlying normalized AMS (Marketing) and MTL (Inventory) tables directly. The view joins source codes, offers, channels, schedules, media, categories, and campaign header/detail tables, and applies DISTINCT to suppress duplicate rows produced by the multi-table outer-join structure. The STATUS column of the view is marked VALID in the data dictionary, confirming the object compiles successfully and is available for runtime use. Because it draws on public synonyms and views rather than private base table references alone, it is safe to reference from custom reports, BI Publisher data templates, and concurrent programs within the APPS schema. The inclusion of the LKUP.MEANING CHANNEL_TYPE column is directly relevant to the common search term "channel_type," since it exposes a human-readable channel classification derived from AMS_LOOKUPS with LOOKUP_TYPE 'AMS_SYS_ARC_QUALIFIER'.

Underlying Base Objects

The view is defined over the following documented objects:

• AMS_P_SOURCE_CODES_V — source code and offer metadata (referenced twice, as SC and OFR)
• AMS_ACT_OFFERS and AMS_ACT_PRODUCTS — offer and offer-product associations
• AMS_CAMPAIGNS_ALL_B, AMS_CAMPAIGNS_ALL_TL, and AMS_CAMPAIGNS_VL — campaign base, translation, and language views
• AMS_CAMPAIGN_SCHEDULES_VL — schedule names and activities
• AMS_CHANNELS_VL, AMS_MEDIA_VL, and AMS_LOOKUPS — channel, media, and lookup descriptions
• MTL_CATEGORIES_V, MTL_CATEGORY_SETS_VL, and ENI_PROD_DEN_HRCHY_PARENTS_V — product category and hierarchy paths

The join structure is strongly outer-join driven (using the (+) operator), which permits campaigns that lack associated offers, media, or channel records to still appear in the result set. Source codes are filtered to STATUS in ('ACTIVE','ONHOLD','COMPLETED') and SOURCE_TYPE != 'OFFR', while offer-side rows are restricted to SOURCE_TYPE = 'OFFR' and STATUS = 'ACTIVE'. Channel and media attributes are resolved through VL (language) views, so descriptions reflect the current session language.

Key Columns

• SOURCE_CODE_ID, SOURCE_CODE, NAME — identifier and descriptive label for the campaign source code.
• CAMPAIGN_NAME, SCHEDULE_NAME — campaign and schedule identification.
• CHANNEL_ID (alias for MARKETING_MEDIUM_ID) and CHANNEL_NAME — the marketing channel assigned to the schedule.
• CHANNEL_TYPE — the lookup meaning derived from AMS_LOOKUPS using LOOKUP_TYPE 'AMS_SYS_ARC_QUALIFIER'; this is the column most commonly targeted by the search term "channel_type."
• MEDIA_ID (alias for ACTIVITY_ID), MEDIA_NAME, MEDIA_TYPE_CODE, MEDIA_TYPE_NAME — media activity attributes.
• STATUS_CODE, STATUS_DATE, ACTIVE_FLAG, PARTNER_FLAG, ROLLUP_TYPE, PRIORITY — campaign lifecycle and classification flags.
• OWNER_USER_ID, CC_MANAGER_USER_ID, CC_CALL_STRATEGY — ownership and call center strategy data.
• CATEGORY_ID, CATEGORY_SET_ID, and the NVL(CATEGORY_DESC, CATEGORY_CONCAT_SEGS) expression — category description fallback logic.
• ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments carried through from AMS_CAMPAIGNS_ALL_B.

Common Use Cases and Queries

Typical uses include campaign channel reporting, media mix analysis, and agent-facing campaign selection lists. A representative query filtering on channel type is:

• SELECT campaign_name, channel_name, channel_type, media_name, status_code FROM ast_ls_campaigns_v WHERE channel_type = 'Direct Mail';
• SELECT source_code, name, schedule_name, media_type_name FROM ast_ls_campaigns_v WHERE active_flag = 'Y';
• SELECT channel_type, COUNT(*) FROM ast_ls_campaigns_v GROUP BY channel_type ORDER BY 2 DESC;

Because the view performs DISTINCT aggregation across multiple joins, queries should avoid adding further heavy joins where possible, and performance can be improved by filtering on SOURCE_CODE or STATUS_CODE, both of which are indexed at the base table level. For exhaustive channel-type enumeration, AMS_LOOKUPS with LOOKUP_TYPE = 'AMS_SYS_ARC_QUALIFIER' remains the authoritative source.