Results for “per_contact_info_types_pk”

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

Overview

The PER_CONTACT_INFO_TYPES table resides in the HR schema and belongs to the PER (Human Resources) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as a configuration or reference table that defines the categories of supplementary information that can be captured against a contact relationship. In Oracle HRMS, contacts are persons associated with an employee or applicant for purposes such as emergency notification, dependent tracking, or benefits designation. While the core contact relationship records the association itself, this table governs which additional data elements — for example, phone numbers, addresses, or descriptive attributes — may be recorded for that relationship type.

The ETRM metadata classifies this object heuristically as standalone under the Data Vault modeling convention. This suggests it is best modeled as a reference or lookup set rather than as a hub, link, or satellite, because it neither drives transactional relationships nor stores descriptive history of a business entity. It is a controlled vocabulary consumed by dependent tables through foreign key references.

Key Information Stored

The table contains 15 documented columns. The structural core is the surrogate primary key PER_CONTACT_INFO_TYPES_PK, defined on the INFORMATION_TYPE column. A unique index combining INFORMATION_TYPE and ZD_EDITION_NAME serves as the business-key candidate, supporting the editioning feature introduced in the 12.2.x data model.

• INFORMATION_TYPE — The primary identifier and business key component; names the category of extra contact information.
• ACTIVE_INACTIVE_FLAG — Controls whether the information type is currently selectable in contact maintenance.
• MULTIPLE_OCCURENCES_FLAG — Indicates whether more than one value may be stored for this information type against a single contact relationship.
• LEGISLATION_CODE — Restricts the information type to a specific legislative or country context, supporting localization.
• ZD_EDITION_NAME — Editioning column supporting online patching in 12.2.x environments.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework (OAF) and PL/SQL APIs.
• LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — Standard audit trail columns.
• CREATED_BY / CREATION_DATE — Creation audit columns.
• REQUEST_ID / PROGRAM_APPLICATION_ID / PROGRAM_ID / PROGRAM_UPDATE_DATE — Concurrent program and multi-org reporting context columns.

Common Use Cases and Queries

Typical usage involves the Contact Information Types setup form, where HR administrators extend the set of extra fields available for contacts. Reporting queries commonly join this table to contact information data to resolve the type's meaning and to filter by active status or legislation.

SELECT information_type,
       active_inactive_flag,
       multiple_occurences_flag,
       legislation_code
  FROM hr.per_contact_info_types
 WHERE active_inactive_flag = 'A'
   AND (legislation_code IS NULL OR legislation_code = :leg_code);

Extracts feeding downstream systems frequently need the active configuration list, while debugging queries inspect OBJECT_VERSION_NUMBER and audit columns to detect stale or patched records.

Related Objects

Although the ETRM metadata records this object as standalone with no mined foreign keys, it participates in the HRMS contact model through logical references. The most significant related objects include:

• PER_CONTACT_RELATIONSHIPS — The core contact relationship table that consumes INFORMATION_TYPE values.
• PER_CONTACT_INFO — Stores the actual extra information values keyed by information type.
• PER_CONTACT_INFO_TYPES_TL — Translation table supplying multilingual type names where implemented.
• FND_LOOKUP_VALUES — Frequently paired with information types for related coded values.
• HR_LOOKUPS — HRMS lookup framework used alongside contact information configuration.
• PER_CONTACT_RELATIONSHIPS_API — PL/SQL API validating information types during contact maintenance.