Results for “preference_meaning”

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

Overview

IGS_PE_HZ_CONT_PREF_V is a seeded Oracle E-Business Suite database view owned by the APPS schema and shipped as part of the IGS – Student System product family. Its documented purpose is to expose Contact Preference information in a reportable form. In EBS 12.1.1 and 12.2.2, contact preferences record how a party (typically a student, applicant, or related person) wishes to be contacted — for example whether they consent to a visit, a phone call, or an email — and the period during which that preference is valid.

The view is an integration and reporting convenience layer. Rather than forcing report developers and interface programs to reconstruct the multi-table joins between HZ_CONTACT_PREFERENCES, HZ_PARTIES, and the FND lookup infrastructure, the view presents a single flattened row per contact preference with decoded (meaning-level) values for the contact type, preference code, and reason code. This makes it suitable for concurrent-program extracts, OAF/Forms regions, and inbound/outbound student-system interfaces that need human-readable contact preference data.

Underlying Base Objects

The view is defined over three logical sources:

• HZ_CONTACT_PREFERENCES — the primary table (alias HZPREF) holding one row per contact preference, including its identifier, dates, status, and audit columns.
• HZ_PARTIES — the party master (alias HP), joined on the party identifier to supply PERSON_NUMBER (the party number).
• FND_LOOKUP_VALUES — referenced three times (LK, LK1, LK3) to translate codes into meanings for CONTACT_TYPE, PREFERENCE_CODE, and REASON_CODE respectively, all constrained to VIEW_APPLICATION_ID = 222, SECURITY_GROUP_ID = 0, and LANGUAGE = USERENV('LANG').

The join to HZ_PARTIES is driven by the predicate HZPREF.CONTACT_LEVEL_TABLE = 'HZ_PARTIES', and the row identifier exposed as ROW_ID is the ROWID of HZ_CONTACT_PREFERENCES, supporting downstream update or drill-back logic. The REASON_CODE lookup is outer-joined, so rows with no reason code are still returned. Note the documented filter LK.LOOKUP_CODE = 'VISIT', which constrains returned rows to the VISIT contact type in the shipped definition.

Key Columns

• ROW_ID — ROWID of the underlying HZ_CONTACT_PREFERENCES row.
• CONTACT_PREFERENCE_ID — primary key of the contact preference record.
• CONTACT_LEVEL_TABLE / PERSON_ID — the entity level at which the preference applies and its identifier (mapped from CONTACT_LEVEL_TABLE_ID).
• CONTACT_TYPE / CONTACT_TYPE_M — the contact type code and its decoded meaning (e.g., VISIT).
• PERSON_NUMBER — the party number of the associated person.
• PREFERENCE_CODE / PREFERENCE_MEANING — the preference (consent) code and its decoded description.
• START_DATE / END_DATE — the effective window of the preference.
• REQUESTED_BY — the requesting party or user.
• REASON_CODE / REASON_CODE_M — reason for the preference and its decoded meaning.
• STATUS, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY_MODULE, APPLICATION_ID — standard EBS audit and ownership attributes.

Common Use Cases and Queries

Typical uses include extracting current contact consents for a student cohort, populating BI Publisher reports, and validating preferences during interface load. A basic inquiry by person number:

• Select PERSON_NUMBER, CONTACT_TYPE_M, PREFERENCE_MEANING, START_DATE, END_DATE, STATUS from IGS_PE_HZ_CONT_PREF_V where PERSON_NUMBER = :party_number and SYSDATE BETWEEN START_DATE AND NVL(END_DATE, SYSDATE + 1), ordered by START_DATE DESC.
• Aggregate currently valid preferences by type for a reporting period using the decoded meanings.

Because lookup access is language- and application-scoped, the decoded columns return values only in the session language and for application 222; report logic should therefore join the view rather than re-deriving lookups independently.