Search Results chk_person_type

Overview

APPS.PER_PL_PERSON_EXTRA_INFO is a localization package body within the Oracle E-Business Suite Human Resources (HR) product family. The "PL" component of the name identifies it as a country-specific (localization) extension, in this case associated with the Polish legislation (PL) extensions for person extra information. The package encapsulates the server-side validation and maintenance logic that governs the storage of supplementary, legislation-specific person attributes held in the person extra information framework delivered by Oracle HRMS.

Its principal business role is to enforce legislative business rules before extra person information records are persisted. The most significant of these rules, evidenced by the CHK_PERSON_TYPE procedure, is that certain extra information flexfield details may be recorded only for persons whose person type resolves to a Contact for the effective date range being entered. This prevents users from attaching Polish statutory or registration data to persons who do not qualify as contacts under the applicable person type usage, thereby protecting downstream reporting, statutory interfaces, and data integrity.

Key Procedures and Functions

The ETRM metadata documents two public procedures within the package body. Their purposes are as follows.

• CREATE_PL_PERSON_EXTRA_INFO — Handles creation of a Polish person extra information record. It is the entry point invoked when new localized extra information is being added for a person, applying validation before the row is inserted into the extra information table.
• UPDATE_PL_PERSON_EXTRA_INFO — Handles modification of an existing Polish person extra information record. It supports the update path for the same localized data set, typically revalidating the record against the governing person type and date-range rules.

The package body additionally contains the internal validation routine CHK_PERSON_TYPE, which is the object surfaced by the search term "chk_person_type." Although not listed among the documented public procedures, it is the core rule-enforcement mechanism: it opens a cursor joining PER_PEOPLE_F, PER_PERSON_TYPES, and PER_PERSON_TYPE_USAGES_F to confirm the person is a Contact (the seeded person type key 'CONTACT') across the entered effective start and end dates. When the person fails this test, the routine raises the seeded message HR_CON_INVALID_DETAILS_PL, populating message tokens for the flexfield label, start date, and end date via HR_UTILITY and HR_GENERAL before calling RAISE_ERROR. This produces the user-facing text indicating that these details can be entered only for a Contact and that the person type is not a Contact for the specified date range. A second internal routine, CREATE_CON_DATE_CHK, tests for overlapping person extra information records.

Tables Accessed

The package operates against the following tables, all accessed through APPS synonyms:

• PER_ALL_PEOPLE_F — Read to resolve the person identifier and validate that the person record is effective across the requested date range.
• PER_PERSON_TYPES — Read to match the seeded person type key 'CONTACT', establishing whether the person qualifies as a contact.
• PER_PERSON_TYPE_USAGES_F — Read to confirm the person type usage (assignment of person type to the person) is effective over the same start and end dates.
• PER_PEOPLE_EXTRA_INFO — Read and written as the primary store for the localized extra information attributes, including overlap checking on existing rows.

Usage Notes

This package is a localization-layer component and is typically invoked indirectly rather than called by end users. It is most commonly triggered from the Oracle HRMS person maintenance forms (the person and person extra information windows) when a user enters or amends Polish-specific extra information, and it may equally be called from concurrent programs, Oracle Forms customization, or PL/SQL API wrappers that create or update person extra information on behalf of the Polish localization. Because the validation depends on effective-dated person type usages, callers must supply meaningful flex start and end dates; the package converts them from canonical date strings using FND_DATE.CANONICAL_TO_DATE and defaults an open-ended end date to 31/12/4712. The metadata records that the package is referenced by two other packages, indicating it is itself a dependency in the wider HRMS localization call chain. Error conditions are surfaced through the standard HR_UTILITY message mechanism, so callers should be prepared to handle raised application errors from CHK_PERSON_TYPE when the contact validation or overlap checks fail.