Results for “irc_notification_preferences”

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

Overview

IRC_NOTIFICATION_PREFERENCES is a Human Resources (PER) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the contact and notification preferences that an applicant or candidate has established with respect to being contacted by the recruiting organization or by external agencies. In functional terms, the table governs which communication channels an applicant permits, where correspondence should be directed, and whether the applicant consents to external parties accessing or contacting them regarding open positions. Because recruitment workflows in Oracle iRecruitment and Oracle Human Resources depend heavily on consent and channel records, this table acts as the authoritative record of how and whether an individual may be reached.

Heuristically, the foreign-key structure suggests this object is satellite-leaning within a Data Vault model. Its primary key is a surrogate identifier, and its foreign keys point outward to party, address, agency, and attempt entities, indicating that it primarily carries descriptive and preference attributes attached to a parent business entity rather than acting as a pure hub or link. This classification is offered as a modeling suggestion and should be validated against actual usage patterns.

Key Information Stored

The table's surrogate primary key is NOTIFICATION_PREFERENCE_ID, enforced through the unique index IRC_NOTIFICATION_PREFS_PK. This identifier is the value most commonly referenced when searching for a specific preference record, and it is the join key used by dependent objects. Business-key candidates documented as unique are limited to this same identifier column, so the table does not expose an independent natural business key beyond its foreign-key relationships.

• NOTIFICATION_PREFERENCE_ID — Surrogate primary key for the preference record.
• PARTY_ID — Reference to the party (applicant or person) whose preferences are captured.
• PERSON_ID — Identifier of the person record associated with the preference.
• ADDRESS_ID — Foreign key to PER_ADDRESSES, indicating the address used for contact.
• AGENCY_ID — Foreign key to FV_DMS_AGENCY_DEFINITIONS_ALL, identifying an agency permitted to contact the applicant.
• ATTEMPT_ID — Foreign key to OTA_ATTEMPTS, tying the preference to a specific recruitment attempt.
• MATCHING_JOBS — Flag indicating whether the applicant wishes to receive matching job notifications.
• MATCHING_JOB_FREQ — Frequency setting for matching job notifications.
• RECEIVE_INFO_MAIL — Flag indicating consent to receive informational mailings.
• ALLOW_ACCESS — Flag controlling whether external access or contact is permitted.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield (DFF) columns for customer-defined extensions.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — Standard WHO audit columns tracking record creation and change history.

Common Use Cases and Queries

Typical use cases include auditing applicant consent, reporting on contactable candidates, and validating agency access rights. A common query retrieves preferences for a known person or party:

• Retrieve a single preference row by its surrogate key: SELECT * FROM HR.IRC_NOTIFICATION_PREFERENCES WHERE NOTIFICATION_PREFERENCE_ID = :pref_id;
• List all preferences tied to a person: SELECT * FROM HR.IRC_NOTIFICATION_PREFERENCES WHERE PERSON_ID = :person_id;
• Join to addresses to resolve the contact destination: SELECT n.NOTIFICATION_PREFERENCE_ID, a.ADDRESS1, a.CITY FROM HR.IRC_NOTIFICATION_PREFERENCES n JOIN HR.PER_ADDRESSES a ON n.ADDRESS_ID = a.ADDRESS_ID;
• Report agency-permitted candidates: filter on ALLOW_ACCESS and AGENCY_ID.

Reporting use cases center on recruitment compliance dashboards, contact-preference analytics, and iRecruitment applicant self-service screens that read and write these records.

Related Objects

The documented foreign keys and dependencies identify the following significant related objects:

• PER_ADDRESSES — Joined via IRC_NOTIFICATION_PREFERENCES.ADDRESS_ID to resolve contact addresses.
• FV_DMS_AGENCY_DEFINITIONS_ALL — Joined via AGENCY_ID to identify the agency granted access.
• OTA_ATTEMPTS — Joined via ATTEMPT_ID to associate the preference with a recruitment attempt.
• IRC_NOTIFICATION_PREFS_PK — The unique index enforcing the primary key.
• Party and person entities referenced by PARTY_ID and PERSON_ID provide the applicant context for preference records.

These relationships make IRC_NOTIFICATION_PREFERENCES a dependent satellite of applicant, address, agency, and attempt entities within the Oracle iRecruitment data model.