Results for “channel_id”

50+ results




Overview
Explore in AI Chat

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

Overview

AMV_C_CONTENT_TYPES is a transactional configuration table in the Oracle E-Business Suite Marketing Encyclopedia System (AMV) module. It stores the association between a specific channel and the content types that can participate in content matching criteria. In practical terms, the table answers the question: "which content types are eligible for a given channel?" This is a foundational mapping used by the Marketing Encyclopedia System when evaluating how marketing content is categorized, filtered, and matched against channel-specific business rules.

Under the ETRM 12.1.1 and 12.2.2 data models, the table resides in the AMV schema and is marked VALID. It contains ten documented columns and is protected by both a surrogate primary key and a composite unique constraint, ensuring that no duplicate channel-to-content-type pairing can exist. Because the table's rows represent relationships between two independent entities (channels and content types), the heuristic Data Vault classification derived from the foreign key structure is link. This is a modeling suggestion rather than a directive: AMV_C_CONTENT_TYPES behaves as an associative entity joining AMV_C_CHANNELS_B and the content type definition, and it carries its own surrogate key plus audit metadata rather than descriptive attributes about either parent.

Key Information Stored

The most significant columns are the identifiers that define the relationship and the standard audit trail columns that Oracle EBS applies to nearly all transactional tables.

The business-key candidate is defined by the unique index AMV_C_CONTENT_TYPES_U2 on (CHANNEL_ID, CONTENT_TYPE_ID), which enforces that a content type appears at most once per channel. A second unique index, AMV_C_CONTENT_TYPES_U1, exists on the surrogate key CHANNEL_CONTENT_TYPE_ID itself. The distinction matters: U2 is the natural key from a business perspective, while the surrogate PK is the technical join key.

Common Use Cases and Queries

Typical use cases center on validating channel configuration, reporting which content types are enabled per channel, and confirming that content matching will not fail due to missing associations.

  • List all content types for a given channel: SELECT content_type_id FROM amv_c_content_types WHERE channel_id = :channel_id;
  • Confirm a specific channel/content-type pairing exists before matching: SELECT channel_content_type_id FROM amv_c_content_types WHERE channel_id = :channel_id AND content_type_id = :content_type_id;
  • Audit recently changed associations: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace configuration drift.
  • Security-scoped reporting: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to restrict output to the caller's accessible groups.

Reporting generally joins this table to AMV_C_CHANNELS_B to return channel names alongside the associated content types.

Related Objects

The following objects are most directly involved with AMV_C_CONTENT_TYPES through foreign key or primary key relationships:

  • AMV_C_CHANNELS_B — referenced via CHANNEL_ID; the parent channel definition.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces data security.
  • AMV_C_CONTENT_TYPES_PK — the primary key constraint on CHANNEL_CONTENT_TYPE_ID.
  • AMV_C_CONTENT_TYPES_UK1 / U2 — the unique constraint on (CHANNEL_ID, CONTENT_TYPE_ID).

Content type definitions themselves reside in the AMV content type master and are referenced through CONTENT_TYPE_ID; channel-driven matching logic in the Marketing Encyclopedia System consumes these associations at runtime.