Search Results amv_c_chl_perspectives




Overview
Explore in AI Chat

Overview

AMV_C_CHL_PERSPECTIVES is a table in the AMV schema belonging to the Oracle Marketing Encyclopedia System (MKS) module, which underpins channel management and segmentation in Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores all perspectives associated with a specific channel; these perspective assignments can participate in matching criteria used by the Marketing Encyclopedia to determine which content, offers, or collateral are surfaced to a given audience. In this role, the table acts as the intersection between channels and perspectives, and thus carries the attributes that define channel-to-perspective eligibility.

From a Data Vault modeling perspective, the heuristic classification of this table is link. This is derived from its structure as a many-to-many association table: it carries a surrogate primary key (CHANNEL_PERSPECTIVE_ID) plus two foreign key columns (CHANNEL_ID and PERSPECTIVE_ID), which together resolve relationships between independent business entities rather than storing descriptive satellite history. Treating it as a link aligns with the underlying relational design and supports integration patterns that separate hubs, links, and satellites.

Key Information Stored

The table is documented with 10 physical columns in the AMV schema, spanning surrogate identity, foreign key relationships, and standard audit attributes.

Two unique indexes exist as business-key candidates. AMV_C_CHL_PERSPECTIVES_U1 covers CHANNEL_PERSPECTIVE_ID (effectively the surrogate), while AMV_C_CHL_PERSPECTIVES_U2 covers the composite (CHANNEL_ID, PERSPECTIVE_ID). The latter is the true business key and enforces the rule that a given perspective may be associated with a given channel only once.

Common Use Cases and Queries

The most common purpose is retrieving all perspectives attached to a channel for segmentation, targeting, or matching logic. A representative query joins the table to its channel header:

  • List perspectives for a channel:
    SELECT p.CHANNEL_ID, p.PERSPECTIVE_ID, p.SECURITY_GROUP_ID FROM AMV.AMV_C_CHL_PERSPECTIVES p WHERE p.CHANNEL_ID = :channel_id;
  • Verify uniqueness constraints before insert to avoid violating AMV_C_CHL_PERSPECTIVES_U2.
  • Audit recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY for reconciliation or troubleshooting.
  • Feed downstream matching criteria reporting that determines which content is eligible for a channel.

Because SECURITY_GROUP_ID is present, queries in multi-org or secured environments should constrain by security group to avoid leaking rows across groups.

Related Objects

  • AMV_C_CHANNELS_B — parent channel table; join on AMV_C_CHL_PERSPECTIVES.CHANNEL_ID = AMV_C_CHANNELS_B.CHANNEL_ID.
  • Perspective table referenced by PERSPECTIVE_ID — resolves the perspective definition used in matching criteria.
  • FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security scoping.
  • AMV_C_CHL_PERSPECTIVES_PK / _U1 / _U2 — primary and unique indexes enforcing identity and the channel-perspective business key.
  • Marketing Encyclopedia channel and matching APIs — consume this association when evaluating channel content eligibility.