Search Results ams_list_cont_restrictions




Overview
Explore in AI Chat

Overview

AMS_LIST_CONT_RESTRICTIONS is a Marketing (AMS) module table that stores "Do Not Contact" list information within Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AMS schema and holds a status of VALID in the ETRM object registry. The table captures restrictions that suppress specific contacts from marketing campaigns, telemarketing activities, or other outbound communications, thereby supporting regulatory compliance and customer preference management.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests the table functions as an independent entity without strong parent-child link dependencies beyond its single documented foreign key. The table contains 14 documented columns and is uniquely identified by the primary key constraint AMS_LIST_CONT_RESTRICTIONS_PK1, defined on the LIST_CONTACT_RESTRICTIONS_ID column.

Key Information Stored

The central identifier is LIST_CONTACT_RESTRICTIONS_ID, the surrogate primary key that guarantees each restriction record is uniquely addressable. A second unique index, AMS_LIST_CONT_RESTRICTIONS_U1, is defined on the composite of LIST_CONTACT_RESTRICTIONS_ID and ZD_EDITION_NAME, marking ZD_EDITION_NAME as a business-key candidate used in edition-aware configurations.

Common Use Cases and Queries

Typical scenarios include validating whether a given contact is eligible for a campaign, auditing do-not-contact coverage, and reporting on suppression volumes by list or security group. A query to retrieve active restrictions for a specific list follows:

  • SELECT LIST_CONTACT_RESTRICTIONS_ID, LIST_HEADER_ID, DO_NOT_CONTACT_FLAG, MEDIA_ID FROM AMS.AMS_LIST_CONT_RESTRICTIONS WHERE LIST_HEADER_ID = :p_list_header_id AND DO_NOT_CONTACT_FLAG = 'Y';
  • Audit query: SELECT LIST_USED_BY, LIST_USED_BY_ID, COUNT(*) FROM AMS.AMS_LIST_CONT_RESTRICTIONS GROUP BY LIST_USED_BY, LIST_USED_BY_ID;
  • Security-scoped reporting: join to FND_SECURITY_GROUPS using SECURITY_GROUP_ID to filter records visible to a given operating unit or responsibility.

Because the table is edition-enabled, reports should account for ZD_EDITION_NAME when querying across editions to avoid reading non-current rows.

Related Objects

The documented foreign key establishes the primary dependency chain. The following objects are most significant:

  • FND_SECURITY_GROUPS — Referenced via AMS_LIST_CONT_RESTRICTIONS.SECURITY_GROUP_ID, controlling multi-org access.
  • AMS_LIST_HEADERS — Related through LIST_HEADER_ID, providing list context.
  • AMS_LIST_CONTACT_RESTRICTIONS_PK1 and AMS_LIST_CONT_CONTACT_RESTRICTIONS_U1 — Constraints governing uniqueness.
  • AMS Media and list usage objects referenced through MEDIA_ID, LIST_USED_BY, and LIST_USED_BY_ID for channel and usage resolution.

Consumers should treat this table as the authoritative source of contact-level suppression and join through LIST_HEADER_ID and SECURITY_GROUP_ID where campaign eligibility or security scoping is required.