Results for “per_people_info_types”

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

Overview

PER_PEOPLE_INFO_TYPES is a Human Resources (PER) product table residing in the HR schema. It holds the definitions of extra information types that may be held against a person. In Oracle EBS 12.1.1 and 12.2.2, this table functions as the configuration-level repository that describes the categories of supplementary or "extra" person data captured during hire, employee maintenance, and self-service transactions. Each row defines one information type, which is subsequently instantiated as actual data in the transactional extra information table.

The table contains 16 documented columns and is classified under a heuristic Data Vault model as hub-leaning. As a modeling suggestion, this reflects the fact that the table carries a defined business key and serves as a reference entity for extra person information, while the descriptive and audit attributes could alternatively be segregated into a satellite structure. The table is edition-enabled in 12.2.2 through the ZD_EDITION_NAME column, supporting the editioning architecture introduced in that release.

Key Information Stored

The primary key of the table is defined by the constraint PER_PEOPLE_INFO_TYPES_PK, whose unique index comprises INFORMATION_TYPE and ZD_EDITION_NAME in the documented 12.2.2 physical schema. INFORMATION_TYPE is the core surrogate identifier and business key that distinguishes each extra information type.

• INFORMATION_TYPE — Surrogate primary key and foreign key target for the transactional extra information table.
• ACTIVE_INACTIVE_FLAG — Determines whether the information type is available for use in the application.
• MULTIPLE_OCCURENCES_FLAG — Indicates whether multiple instances of this information type may be recorded for a single person.
• DESCRIPTION — The display name or description of the information type.
• LEGISLATION_CODE — Restricts the information type to a specific legislative context.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the framework during concurrent updates.
• ZD_EDITION_NAME — Edition identifier supporting 12.2.2 edition-based redefinition.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit and who-columns for tracking modifications.
• CREATION_DATE, CREATED_BY — Standard creation audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program context columns identifying the process that last touched the row.

Common Use Cases and Queries

This table is typically queried to enumerate the available extra information types or to validate configuration before loading person data. Reported uses include auditing which types are active for a given legislation and identifying types that permit multiple occurrences.

A common pattern joins the definition to its transactional counterpart:

• SELECT pit.INFORMATION_TYPE, pit.DESCRIPTION, pit.ACTIVE_INACTIVE_FLAG FROM PER_PEOPLE_INFO_TYPES pit WHERE pit.ACTIVE_INACTIVE_FLAG = 'Y' AND (pit.LEGISLATION_CODE IS NULL OR pit.LEGISLATION_CODE = :legislation).
• Join to transactional data: SELECT pei.PERSON_ID, pei.INFORMATION_TYPE, pit.DESCRIPTION FROM PER_PEOPLE_EXTRA_INFO pei JOIN PER_PEOPLE_INFO_TYPES pit ON pei.INFORMATION_TYPE = pit.INFORMATION_TYPE.

Reporting use cases include validating that every populated INFORMATION_TYPE in the transactional table exists as a defined type, and describing extra information configurations in HR data models.

Related Objects

• PER_PEOPLE_EXTRA_INFO — The principal dependent table; its INFORMATION_TYPE column references PER_PEOPLE_INFO_TYPES, establishing the definition-to-instance relationship.
• PER_PEOPLE_INFO_TYPES_PK — The primary key constraint and unique index on INFORMATION_TYPE and ZD_EDITION_NAME.
• PER_PEOPLE_INFO_TYPES_F and associated views — Interface and translation views commonly exposed for the setup UI.
• FND_LOOKUPS / HR_LOOKUPS — Frequently referenced for related lookup values such as legislation or flag validation.
• HR_EXTRA_INFO_TYPES_API — The business API family used to define and maintain information types programmatically.

Together these objects form the configuration and transactional backbone for person extra information processing in Oracle HRMS.