Results for “party_number”

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

Overview

The view APPS.AHL_HZ_PER_EMPLOYEES_V is a reporting and integration construct delivered with the Oracle E-Business Suite product AHL — Complex Maintenance Repair and Overhaul. As documented in the ETRM metadata for release 12.1.1 and 12.2.2, the object is a VALID database view owned by the APPS schema and is described simply as storing employee information. Functionally, it presents a unified, de-duplicated list of persons — employees and, depending on the installation state of the PER (Human Resources) product, party records from the Trading Community Architecture — so that AHL components and related modules can resolve an individual to a single identifier, number, and display name without hard-coding a dependency on either HZ_PARTIES or the HR person tables.

The view therefore acts as an abstraction layer. Rather than querying Human Resources or TCA tables directly, AHL code and custom reports can select from AHL_HZ_PER_EMPLOYEES_V and receive a consistent party-style key (PARTY_ID), a business identifier (PARTY_NUMBER), and a formatted name (PARTY_NAME). This is particularly valuable in Complex MRO scenarios where maintenance personnel, requesters, and document-index owners may originate from either the HR employee base or the broader TCA person registry.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following referenced base objects:

• AHL_DI_DOC_INDEX_PVT (PL/SQL package) — supplies GET_PRODUCT_INSTALL_STATUS('PER'), the function that governs which branch of the UNION is active based on whether the PER product is not installed (N), licensed (L), installed (I), or shared (S).
• HZ_PARTIES (synonym to the TCA parties table) — source of PERSON-type party records (PARTY_ID, PARTY_NUMBER, PARTY_NAME).
• PER_PEOPLE_F (view) — the effective-dated HR person record providing PERSON_ID, EMPLOYEE_NUMBER, and dates.
• PER_PERSON_TYPES (synonym) — classified person types; the SYSTEM_PERSON_TYPE = 'EMP' filter restricts records to employees.
• HR_GENERAL, HR_PERSON_NAME, HR_SECURITY (packages) — supporting HR utilities referenced by the view's definition, including name formatting and security predicates.

The UNION structure means the view never returns both branches for one installation simultaneously: when PER is not installed or merely licensed, party records are returned; when PER is installed or shared, effective, current employees are returned.

Key Columns

• PARTY_ID — the unique identifier for the person. In the TCA branch this is HZ_PARTIES.PARTY_ID; in the HR branch it is PER_PEOPLE_F.PERSON_ID. This is the primary join key to AHL and TCA entities.
• PARTY_NUMBER — the human-readable business identifier. For TCA parties it is the party number; for employees it is EMPLOYEE_NUMBER.
• PARTY_NAME — the display name. In the TCA branch this is PARTY_NAME; in the HR branch it is FULL_NAME resolved through HR name-formatting utilities.

These three columns form a stable, product-agnostic projection, which is why custom code should reference only these columns rather than the underlying sources.

Common Use Cases and Queries

Typical uses include LOV (list of values) population for employee or party selection, resolving an owner or requester name on maintenance work orders and document index records, and joining AHL transaction data to a display name.

SELECT party_id, party_number, party_name
FROM   apps.ahl_hz_per_employees_v
WHERE  UPPER(party_name) LIKE UPPER(:p_name || '%')
ORDER  BY party_name;

SELECT v.party_number, v.party_name
FROM   apps.ahl_hz_per_employees_v v
WHERE  v.party_id = :p_party_id;

Because the branch selection is driven by AHL_DI_DOC_INDEX_PVT.GET_PRODUCT_INSTALL_STATUS('PER'), the view requires the AHL package to be compiled and valid; reports run against it inherit the same PER-installation behavior as the base application. Queries should be schema-qualified and filtered on indexed columns such as party_id for performance.