Results for “aei_information13”

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

Overview

The APPS.PER_QH_EIT_V view is a Human Resources (PER) dictionary object that consolidates person-level and assignment-level extra information into a single, uniform result set for consumption by the People Management form. In Oracle EBS 12.1.1 and 12.2.2, Extra Information Types (EITs) allow implementers to attach flexible, descriptive attributes to people and assignments without modifying the core HR schema. Each EIT stores its values in a set of generic columns (PEI_INFORMATION1 through PEI_INFORMATION30 for persons, and the parallel AEI_INFORMATION1 through AEI_INFORMATION30 for assignments), with the meaning of each column driven by the information type's configuration.

Because person extra information resides in PER_PEOPLE_EXTRA_INFO and assignment extra information resides in PER_ASSIGNMENT_EXTRA_INFO, a form or report that must present both would otherwise require two separate queries. PER_QH_EIT_V removes that burden by exposing a normalized structure in which both sources appear as a single logical row set. The columns that do not apply to a given source are populated with typed NULLs (via TO_NUMBER(NULL)) or empty strings, preserving the shape of the result set across both branches of the UNION. The description in the ETRM metadata confirms this purpose: "View of person and assignment extra information used by People Management form."

Underlying Base Objects

The documented base objects referenced by the view are:

• PER_PEOPLE_EXTRA_INFO (SYNONYM) — the first branch of the UNION, contributing person extra information rows.
• PER_ASSIGNMENT_EXTRA_INFO (SYNONYM) — the second branch of the UNION, contributing assignment extra information rows.

The view is defined as a UNION of two SELECT statements over these tables. In the person branch, PERSON_EXTRA_INFO_ID, PERSON_ID, INFORMATION_TYPE, OBJECT_VERSION_NUMBER, PEI_INFORMATION_CATEGORY, and PEI_INFORMATION1 through PEI_INFORMATION30 are selected directly, while the assignment-related columns (ASSIGNMENT_EXTRA_INFO_ID, ASSIGNMENT_ID, and all AEI_INFORMATION1 through AEI_INFORMATION30 values) are supplied as TO_NUMBER(NULL) or empty strings. Conversely, the assignment branch selects ASSIGNMENT_EXTRA_INFO_ID, ASSIGNMENT_ID, INFORMATION_TYPE, OBJECT_VERSION_NUMBER, and the AEI_INFORMATION columns, with the person identifiers and PEI_INFORMATION columns nulled or blanked. This design keeps both branches column-count and datatype compatible.

Key Columns

• PERSON_EXTRA_INFO_ID / ASSIGNMENT_EXTRA_INFO_ID — Primary key of the originating extra information record. Exactly one is populated per row.
• PERSON_ID / ASSIGNMENT_ID — Identifiers linking the row to a person or assignment. Exactly one is populated per row.
• INFORMATION_TYPE — The EIT (Extra Information Type) code that governs which information columns carry meaningful data.
• OBJECT_VERSION_NUMBER — Optimistic locking value propagated from the base table.
• PEI_INFORMATION_CATEGORY so on through PEI_INFORMATION30 — Person extra information attribute values.
• AEI_INFORMATION_CATEGORY through AEI_INFORMATION30 — Assignment extra information attribute values.

Notably, the user's search value pei_information2 corresponds directly to one of these exposed columns. In many implementations, PEI_INFORMATION2 is used to store a second descriptive attribute for a person-level EIT, such as a name, code, or secondary date, depending on the DDF (Descriptive Flexfield) definition for the given INFORMATION_TYPE. Querying on this column is therefore a common way to filter person EIT records by a configured attribute value.

Common Use Cases and Queries

PER_QH_EIT_V is typically used where a single SQL statement must retrieve both person and assignment extra information in a form-compatible layout. Representative scenarios include personalization of the People Management form, custom concurrent programs, and ad-hoc reporting on configured EIT attributes.

A basic query filtering on a specific information type and the PEI_INFORMATION2 column might appear as follows:

• SELECT PERSON_ID, INFORMATION_TYPE, PEI_INFORMATION_CATEGORY, PEI_INFORMATION1, PEI_INFORMATION2 FROM APPS.PER_QH_EIT_V WHERE INFORMATION_TYPE = 'MY_EIT_CODE' AND PEI_INFORMATION2 = 'SOME_VALUE';

To retrieve assignment-level EIT data, query the AEI_INFORMATION columns while filtering on ASSIGNMENT_ID. Because the view consolidates both sources with non-applicable columns nulled, report logic can test whether PERSON_ID or ASSIGNMENT_ID is populated to determine the row's origin. This makes PER_QH_EIT_V a convenient, query-friendly abstraction over the underlying HR Extra Information tables, while remaining consistent with the standard People Management form's expectations.