Search Results per_nl_full_name

Overview

HR_NL_UTILITY is a Netherlands-localized (NL) Oracle Human Resources utility package owned by the APPS schema. Its declared purpose is to centralize name-formatting logic required by Dutch statutory and regional HR requirements — in particular the assembly of a person's full name from the individual name attributes stored on the Oracle HR person record. Because the Dutch conventions for first name, middle names (voorvoegsel/aanhef), last name, known-as name, title, suffix, and pre-name adjunct differ from the default Western name-formatting rules shipped with Oracle HRMS, Oracle provides a country-specific routine so that forms, reports, and business processes operating in a Dutch legislation context can render names in the expected national format.

The package is defined with AUTHID CURRENT_USER, meaning that its SQL statements execute with the privileges of the invoking user rather than the definer, which is consistent with a utility routine invoked from within the APPS execution context. The header comment identifies the source file as hrnlutil.pkh at version 120.0.12010000.1, shipped 2008/07/28, indicating the package has been stable across the 12.1.1 and 12.2.2 release lines.

Key Procedures and Functions

• PER_NL_FULL_NAME — The single documented function in the package. It returns a VARCHAR2 containing the formatted full name for a Dutch person record. Its input signature accepts the standard Oracle HR name components — first name, middle names, last name, known-as name, title, suffix, and pre-name adjunct — followed by a further set of thirty generic p_per_information1 through p_per_information30 parameters. These thirty slots correspond to the PER_INFORMATIONn descriptive flexfield segments on the person record, allowing Dutch-specific legislation attributes (for example, name particles, noble predicates, or partner name conventions) to be passed into the formatting routine without hard-coding each one as a named parameter.
• The function is the only exposed program unit; the package specification contains no other procedures, confirming it is a focused, single-purpose utility rather than a general HR library.

Tables Accessed

The ETRM metadata records the following tables as referenced through APPS synonyms:

• FND_SESSIONS — the standard Oracle Application Object Library session table, typically consulted to obtain session context such as language or session identifiers that influence name rendering.
• PER_ALL_PEOPLE_F — the core dated person table holding the name attributes (first name, last name, known-as, title, suffix, pre-name adjunct) that the function formats.
• PER_CONTACT_RELATIONSHIPS — the contact/relationship table, consulted where the name being formatted belongs to a contact or related person rather than a primary employee or applicant.
• PER_PERSON_TYPES — used to determine the person type, since name formatting and legislation applicability may depend on whether the person is an employee, applicant, contingent worker, or contact.
• DUAL — the standard single-row dummy table, used for expression evaluation and simple lookups.

Usage Notes

HR_NL_UTILITY is classified as an OTHER API, not a public supported business API, and is referenced by zero other documented packages. It is therefore best understood as an internal helper invoked indirectly — for example by Oracle Forms personalizations, Descriptive Flexfield validation, or seeded Dutch-localized reports and concurrent programs that need a consistent full-name string. Custom code in a Dutch legislation environment may call HR_NL_UTILITY.PER_NL_FULL_NAME directly, passing the person's name columns and the thirty PER_INFORMATION segments; the function then returns the assembled name. Because the package is not a documented public interface, customization should treat the signature as stable but unsupported, and any direct dependency should be reviewed against Oracle's naming and upward-compatibility guidance for the 12.1.1 and 12.2.2 releases.