Search Results per_startup_person_types_tl_uk

Overview

PER_STARTUP_PERSON_TYPES_TL is a predefined, seed-data translation table in the Oracle E-Business Suite Human Resources (PER) product, owned by the HR schema. It stores the translated (multi-language) list of startup person types that Oracle delivers with the application, and is used by the person-type setup and lookup infrastructure to present localized person type names and descriptions to users during implementation and day-to-day operation.

Because the table is seeded and its translation rows are keyed by language, it functions primarily as a reference and lookup source rather than a transactional entity. Under the heuristic Data Vault classification supplied in the metadata, this object is modelled as a standalone structure — it carries no foreign-key dependencies to other tables in the mined relationship data, which is consistent with its role as an independent, self-contained reference list of seeded person types and their translations. In Data Vault terms a modelling suggestion would be to treat it as a standalone reference or lookup structure rather than a hub, link, or satellite, though the descriptive name/translation columns could optionally be modelled as a satellite of a person-type key if a broader warehouse model is built around it.

Key Information Stored

The table contains 15 documented columns on Oracle EBS 12.2.2. The most significant are:

• USER_PERSON_TYPE — the user-defined person type code, forming part of the primary key and identifying each seeded person type.
• LANGUAGE — the language in which the person type translation is stored; combined with user person type it forms the primary key.
• SYSTEM_PERSON_TYPE — the internal system name for the person type, alongside the user-facing equivalent.
• SOURCE_LANG — the source language from which the translation row was derived.
• DEFAULT_FLAG — indicates whether the person type is the default; it also participates in the PER_STARTUP_PERSON_TYPES_TL_UK unique key.
• CURRENT_APPLICANT_FLAG, CURRENT_EMP_OR_APL_FLAG, CURRENT_EMPLOYEE_FLAG — flags controlling whether the type is valid for applicants, employees, or both.
• SEEDED_PERSON_TYPE_KEY — identifies the seeded origin of the person type.
• ZD_EDITION_NAME — the editioning column introduced for Oracle EBS 12.2 online patching support.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

The surrogate/primary key is PER_STARTUP_PERSON_TYPES_TL_PK on (USER_PERSON_TYPE, LANGUAGE). The documented unique business-key candidates are PER_STARTUP_PERSON_TYPES_TL_UK on (DEFAULT_FLAG, LANGUAGE, SYSTEM_PERSON_TYPE) and the editioning-aware key PER_STARTUP_PERSON_TYPES_TL_PK on (USER_PERSON_TYPE, LANGUAGE, ZD_EDITION_NAME).

Common Use Cases and Queries

Typical usage centers on reporting and localization. A frequent pattern retrieves translated person type names for a given language:

• Validating seeded person types against configured person types during implementation.
• Building LOVs or value sets that drive person type selection in HR forms.
• Auditing which person types are flagged as default, applicant, or employee types.
• Reconciling translations across languages.

A representative query joining the translation table to language context might select USER_PERSON_TYPE, SYSTEM_PERSON_TYPE, and DEFAULT_FLAG filtered on LANGUAGE and ZD_EDITION_NAME. Because the table is seeded, direct DML is not supported; use the documented HR setup APIs or DFF supporting objects for changes.

Related Objects

The seeded metadata classifies this table as standalone, so no explicit foreign keys are documented. Related objects in the PER schema that conceptually reference or depend on the startup person types include:

• PER_PERSON_TYPES — the runtime person type definition table that mirrors the seeded startup values.
• PER_PERSON_TYPES_TL — the translation counterpart used after seeding.
• PER_STARTUP_PERSON_TYPES — the non-translated base table for the seeded list.
• PER_PEOPLE_F / PER_APPLICANTS — consuming person and applicant records keyed by person type.
• HR person-type setup and lookup APIs (e.g., HR_PERSON_TYPE_API).

Join columns center on USER_PERSON_TYPE and LANGUAGE, with SYSTEM_PERSON_TYPE serving as the cross-reference to system-resolved person type values.