Search Results restrict_reason

Overview

The HZ_CONTACT_RESTRICTIONS view is a critical data object within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Receivables (AR) module. It serves as a logical representation of "Do Not Contact" preferences, centralizing the management of customer communication restrictions. The view is built directly on the foundational Trading Community Architecture (TCA) table HZ_CONTACT_PREFERENCES, filtering for records where the preference code is explicitly 'DO_NOT'. Its primary role is to provide a standardized, application-specific interface for querying active contact prohibitions, ensuring that sales, marketing, and customer service activities comply with documented customer wishes and regulatory requirements.

Key Information Stored

The view exposes a set of columns that map to the underlying preference data, renaming several for contextual clarity within the restriction domain. The core columns define the restriction's scope and validity. SUBJECT_TABLE and SUBJECT_ID identify the entity (e.g., a party or party site) to which the rule applies. CONTACT_TYPE specifies the channel being restricted, such as phone or email. The temporal enforcement is managed through RESTRICT_START_DATE and RESTRICT_END_DATE. The RESTRICT_REASON column captures the justification for the restriction. Key audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) track the record's lifecycle, while STATUS indicates its current effectiveness. A notable technical column is WH_UPDATE_DATE, which is hard-coded to NULL in this view definition.

Common Use Cases and Queries

The primary use case is to screen customer interactions to prevent communication on restricted channels. A common operational query would retrieve all active "Do Not Contact" entries for a specific customer account or site before initiating a collection call or marketing campaign. For example:

• Identifying active restrictions for a party: SELECT * FROM HZ_CONTACT_RESTRICTIONS WHERE SUBJECT_TABLE = 'HZ_PARTIES' AND SUBJECT_ID = :p_party_id AND STATUS = 'A' AND SYSDATE BETWEEN RESTRICT_START_DATE AND NVL(RESTRICT_END_DATE, SYSDATE+1);
• Reporting on all "Do Not Email" preferences: SELECT subject_id, restrict_reason, creation_date FROM HZ_CONTACT_RESTRICTIONS WHERE contact_type = 'EMAIL' AND status = 'A';

These queries help enforce compliance and are often integrated into customer-facing application logic.

Related Objects

The view has a direct and singular dependency on the TCA base table HZ_CONTACT_PREFERENCES, from which it selects and transforms data. The relationship is defined by the filter WHERE PREFERENCE_CODE = 'DO_NOT' AND CONTACT_LEVEL_TABLE <> 'HZ_CONTACT_POINTS'. This filter is crucial; it excludes restrictions defined at the contact point level, indicating this view is intended for restrictions at higher entity levels like parties or party sites. As a view within the AR product, it is inherently related to the suite of TCA-based customer data objects and is likely referenced by custom reports or integrations that need to respect communication preferences in the context of order management and receivables processes.