Search Results irc_notification_preferences

Overview

The IRC_NOTIFICATION_PREFERENCES table is a core data object within the Oracle E-Business Suite (EBS) Human Resources (HR) module, specifically under the PER (Personnel) product family. Its primary function is to store and manage an applicant's communication preferences regarding contact from the recruiting organization. This table is integral to the iRecruitment functionality, enabling the system to respect candidate choices for how and when they are notified, thereby supporting compliance with communication preferences and enhancing the candidate experience. It acts as a centralized repository for these preferences, linking them to the applicant's profile and related contact information.

Key Information Stored

The table's structure is designed to capture specific contact preferences and their associated metadata. The primary key is NOTIFICATION_PREFERENCE_ID, which uniquely identifies each preference record. A critical foreign key column is ADDRESS_ID, which links to the PER_ADDRESSES table, associating the communication preference with a specific physical or electronic address of the applicant. While the provided metadata does not list all columns, typical data stored in such a table includes the applicant's identifier (likely PERSON_ID), preference types (e.g., for job alerts, application status updates, or marketing communications), the preferred communication channel (such as email, SMS, or phone), and an indicator of consent or opt-in status. Timestamp columns for creation and last update are also standard.

Common Use Cases and Queries

This table is primarily accessed during iRecruitment processes where candidate communication is initiated. Common operational and reporting scenarios include generating contact lists for notifications that respect opt-in preferences, auditing communication consent, and managing candidate profiles. A typical query might retrieve the preferred contact method for an applicant to ensure a job alert is sent via the correct channel. For example:

• Retrieving active email preferences for a candidate: SELECT * FROM hr.irc_notification_preferences WHERE person_id = :1 AND preference_type = 'EMAIL_ALERT' AND opt_in_flag = 'Y';
• Reporting on the distribution of communication channels opted into by applicants for a specific job vacancy.
• Data cleanup or migration scripts that update preferences based on new business rules, often executed via PL/SQL procedures.

Related Objects

The IRC_NOTIFICATION_PREFERENCES table exists within a network of related HR objects. Its most direct relationship, as documented, is with the PER_ADDRESSES table via the ADDRESS_ID foreign key, connecting preferences to a candidate's contact details. It is logically and functionally dependent on core person tables, such as PER_ALL_PEOPLE_F. The table's primary key constraint is IRC_NOTIFICATION_PREFS_PK. It is also closely related to other iRecruitment (IRC) tables that manage applicant data, such as IRC_PENDING_NOTIFICATIONS and IRC_SAVED_SEARCHES, which may consume the preference data to govern notification workflows. Integration with workflow and notification engines within Oracle EBS is also a key aspect of its relationships.