Results for “system_person_type”

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

Overview

PER_PERSON_TYPES is a core Human Resources (PER) module table in Oracle E-Business Suite that defines the person types visible to specific Business Groups. Person types classify individuals tracked in Oracle HRMS — for example Employee, Applicant, Contingent Worker, or Ex-Employee — and determine which system behaviors and data-entry rules apply to a person record. In Oracle EBS 12.1.1 and 12.2.2, the table resides in the HR schema and is registered with a VALID status in the ETRM repository.

Because person types are defined per Business Group, the same logical classification can exist independently across multiple Business Groups, each carrying its own activation and defaulting rules. The table is central to person lifecycle processing: it gates which person types are available during hire, applicant registration, and placement workflows. A Data Vault classification heuristic mined from its foreign-key structure labels this object hub-leaning. Under that modeling suggestion, PER_PERSON_TYPES would function as a hub, with its PERSON_TYPE_ID key anchored to links and satellites such as PER_ALL_PEOPLE_F and the upgrade usage table.

Key Information Stored

The documented physical schema for 12.2.2 lists 13 columns. The most significant are summarized below.

• PERSON_TYPE_ID — the surrogate primary key, enforced by the unique index PER_PERSON_TYPES_PK.
• BUSINESS_GROUP_ID — the owning Business Group; a foreign key to HR_ALL_ORGANIZATION_UNITS, it scopes each person type to a specific enterprise group.
• ACTIVE_FLAG — indicates whether the person type is currently available for use.
• DEFAULT_FLAG — marks the person type defaulted during person entry when no explicit selection is made.
• SYSTEM_PERSON_TYPE — the seeded system person type underlying the record (for example, Employee or Applicant).
• USER_PERSON_TYPE — the user-defined person type, allowing Business Group-specific naming and configuration.
• SEEDED_PERSON_TYPE_KEY — the seeded key identifying the delivered person type from which a user person type derives.
• ZD_EDITION_NAME — an editioning column, part of the business-key candidate in the unique index alongside PERSON_TYPE_ID.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns, with LAST_UPDATE_DATE carrying special significance for incremental ETL.

Common Use Cases and Queries

Typical scenarios include resolving the person type attached to a person record, validating that a person type is active before enrolling a new hire, and reporting headcount by system person type. A common join pattern links PER_PERSON_TYPES to PER_ALL_PEOPLE_F on PERSON_TYPE_ID:

• SELECT p.person_id, p.person_type_id, pt.user_person_type FROM per_all_people_f p JOIN per_person_types pt ON pt.person_type_id = p.person_type_id WHERE p.effective_end_date = '4712-12-31';
• Filtering by ACTIVE_FLAG = 'Y' restricts results to currently usable person types, and DEFAULT_FLAG = 'Y' isolates the default designation.
• Grouping by SYSTEM_PERSON_TYPE supports comparative reporting across Business Groups and person type configurations.

Related Objects

The following objects participate in documented primary/foreign-key relationships with PER_PERSON_TYPES.

• PER_ALL_PEOPLE_F — references PERSON_TYPE_ID; the primary person record for every individual tracked in HRMS.
• HR_ALL_ORGANIZATION_UNITS — referenced by BUSINESS_GROUP_ID; defines the Business Group that owns the person type.
• PER_PERSON_TYPE_USAGES_UPGRADE — references PERSON_TYPE_ID, APP_PERSON_TYPE_ID, and EMP_PERSON_TYPE_ID; used during person type upgrade processing.
• PER_PERSON_TYPES_PK — the composite unique index over PERSON_TYPE_ID and ZD_EDITION_NAME, functioning as the business-key candidate.