Search Results per_startup_person_types




Overview
Explore in AI Chat

Overview

PER_STARTUP_PERSON_TYPES is an Oracle E-Business Suite view owned by the APPS schema and registered under the PER (Human Resources) product family. The ETRM documentation classifies it with a status of VALID and describes its purpose simply as "Used to support user-interface." This designation places the view within the family of startup and seed-data helper objects that Oracle Forms-based pages in Oracle HRMS rely upon when rendering person-type selection lists, especially during initial implementation and configuration of the human resources module.

Because the object is a view rather than a table, it does not store data of its own. It presents a language-filtered, read-consistent projection of seeded person-type definitions for display and lookup purposes. It is primarily a UI-support object, but because it resides in the APPS schema and is exposed through standard EBS security, it can also be referenced in custom reports, concurrent programs, and integrations that need to enumerate or validate person-type values. The columns CURRENT_APPLICANT_FLAG, CURRENT_EMP_OR_APL_FLAG, and CURRENT_EMPLOYEE_FLAG are of particular interest to developers because they encode the category and default behavior of each person type in a form that queries can filter on directly.

Underlying Base Objects

The documented ETRM metadata lists a single referenced base object: the table PER_STARTUP_PERSON_TYPES_TL, accessed through a synonym. The "_TL" suffix identifies this as a translated (language) table, which is the standard Oracle EBS design pattern for storing user-facing, translatable text. The view therefore acts as a thin wrapper that selects the rows for the session's current language only.

The view definition confirms this relationship:

SELECT SEEDED_PERSON_TYPE_KEY, DEFAULT_FLAG, SYSTEM_PERSON_TYPE,
       USER_PERSON_TYPE, CURRENT_APPLICANT_FLAG, CURRENT_EMP_OR_APL_FLAG,
       CURRENT_EMPLOYEE_FLAG, LAST_UPDATED_BY, LAST_UPDATE_DATE,
       LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE
FROM PER_STARTUP_PERSON_TYPES_TL
WHERE LANGUAGE = USERENV('LANG')

The WHERE clause restricts output to the language of the current session as determined by USERENV('LANG'), the standard EBS mechanism for language-dependent queries. This means results vary by user session language, and any query against the view automatically respects the logged-in user's language preference without additional filtering. No joins to other tables appear in the documented definition, so the view is effectively a single-table projection over the translated table.

Key Columns

  • SEEDED_PERSON_TYPE_KEY — The identifier for the seeded person type, used as the lookup key when mapping UI selections back to underlying definitions.
  • DEFAULT_FLAG — Indicates whether the person type is the default selection presented to the user.
  • SYSTEM_PERSON_TYPE — The system-level (language-independent) person-type designation.
  • USER_PERSON_TYPE — The user-facing, translated name of the person type displayed in the interface.
  • CURRENT_APPLICANT_FLAG — Flags the person type as applicable to applicants.
  • CURRENT_EMP_OR_APL_FLAG — Indicates that the person type serves both current employees and applicants. This is the column most frequently searched for, and it is the practical discriminator when filtering for person types that cover the combined employee/applicant use case.
  • CURRENT_EMPLOYEE_FLAG — Flags the person type as applicable to current employees.
  • Audit columns — LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE provide standard EBS who-columns for change-tracking.

Common Use Cases and Queries

Typical uses include validating person-type values during data conversion, driving custom LOVs, and auditing which seeded person types map to employee, applicant, or combined categories. To list all person types appropriate for current employees as well as applicants:

SELECT SEEDED_PERSON_TYPE_KEY, USER_PERSON_TYPE, DEFAULT_FLAG
FROM   APPS.PER_STARTUP_PERSON_TYPES
WHERE  CURRENT_EMP_OR_APL_FLAG = 'Y';

To retrieve the default person type for the session language:

SELECT USER_PERSON_TYPE
FROM   APPS.PER_STARTUP_PERSON_TYPES
WHERE  DEFAULT_FLAG = 'Y';

Because the view is restricted to USERENV('LANG'), queries are inherently language-safe. Developers should treat it as read-only, avoid reliance on row ordering without an ORDER BY clause, and remember that the underlying data is seeded configuration rather than transactional HR data. Its narrow scope makes it reliable for lookup logic and interface support, but unsuitable as a substitute for the full HR person-type model in complex reporting.