Results for “ams_channel_type”

16 results




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

Overview

APPS.AMS_CHANNELS_VL is a multilingual (VL) view in the Oracle E-Business Suite Oracle Marketing (AMS) module. It presents a consolidated, user-facing representation of marketing channels — the communication vehicles such as email, direct mail, telemarketing, fax, and web — used to execute marketing campaigns and deliver campaign activities. Because it is a VL view, it resolves translated (language-dependent) descriptive text from the translation table while merging it with language-independent attributes from the base table, filtering to the session language via USERENV('LANG'). The view additionally decorates each channel with a decoded lookup meaning, giving consumers a ready-to-use channel type label without requiring a separate join to the lookup table.

This view is the standard read interface for channels in reports, concurrent programs, and integration extracts. It is the object applications and external systems query to enumerate the channels defined in a given environment, and it is central to the user's search term ams_channel_type, since the AMS_CHANNEL_TYPE lookup classification is exposed here as a decoded column.

Underlying Base Objects

The view is defined over three referenced objects, as documented in the ETRM 12.2.2 metadata: the base table AMS_CHANNELS_B and the translation table AMS_CHANNELS_TL (both surfaced as synonyms), plus the AMS_LOOKUPS view. The join conditions are:

  • B.CHANNEL_ID = T.CHANNEL_ID links each base channel row to its translation row.
  • T.LANGUAGE = USERENV('LANG') restricts retrieved names and descriptions to the current session language.
  • L.LOOKUP_TYPE = 'AMS_CHANNEL_TYPE' AND L.LOOKUP_CODE = B.CHANNEL_TYPE_CODE joins to the lookup view to resolve the coded channel type into its display meaning.

AMS_CHANNELS_B holds the language-independent and transactional attributes, AMS_CHANNELS_TL holds the translatable name and description, and AMS_LOOKUPS supplies lookup meanings for the seeded AMS_CHANNEL_TYPE lookup type.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all active channels for campaign setup, validating channel availability by date, and extracting channel metadata with type decoding. A representative query is:

SELECT channel_id, channel_name, channel_type_code, channel_type,
       outbound_flag, inbound_flag, active_from_date, active_to_date
FROM   apps.ams_channels_vl
WHERE  channel_type_code = :p_channel_type
AND    TRUNC(SYSDATE) BETWEEN active_from_date AND NVL(active_to_date, TRUNC(SYSDATE));

Integration programs join this view to campaign activity tables on CHANNEL_ID to attribute responses to specific channels, and reporting extracts use the decoded CHANNEL_TYPE to group activity without an additional lookup join, since the translation and lookup resolution are already applied by the view definition.