Results for “pei_attribute_category”

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

Overview

GHR_MT_PEOPLE_EI_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, defined as a member of the GHR (US Federal Human Resources) product family. Its documented purpose is to support mass transfer-in and mass transfer-out processing for data transfer operations. The view projects the contents of the GHR_INTERFACE staging table into a column layout that is consumed by the mass transfer concurrent programs, normalizing the generic INFORMATION1 through INFORMATION52 columns of the interface table into semantically named fields such as MT_NAME, MT_STATUS, MT_PERSON_ID, and the PEI_ATTRIBUTE / PEI_INFORMATION series.

Because the mass transfer processes operate on a generic interface structure, the view performs the essential role of aliasing and ordering that structure into a predictable shape. For reporting and integration purposes, this makes GHR_MT_PEOPLE_EI_V the authoritative read interface into pending or processed mass-transfer activity for a person, including any person extra information (PEI) attributes carried alongside each transfer row. Users searching for the "pei_attribute2" identifier typically arrive here because that descriptor is exposed in the view as INFORMATION16.

Underlying Base Objects

ETRM metadata for this view documents a single referenced base object: GHR_INTERFACE, resolved through a synonym. Every column projected by the view traces directly to a column in that interface table, with no joins, unions, or aggregations. This one-to-one mapping means each row of GHR_MT_PEOPLE_EI_V corresponds to exactly one row of GHR_INTERFACE, and the view simply re-labels the interface columns.

Consequently, the view cannot be used to insert, update, or delete data. Mass transfer data is loaded into GHR_INTERFACE by the transfer programs, and the view is layered on top to present that data in business terms. Row counts, volume, and performance characteristics therefore mirror the underlying interface table rather than any separate storage.

Key Columns

The view exposes two distinct names for each underlying interface column: a business alias and the original INFORMATIONn name. Important business aliases include GHR_INTERFACE_ID (from INTERFACE_ID), MT_PROCESS_DATE (PROCESS_DATE), MT_SOURCE (SOURCE_NAME), MT_EFFECTIVE_DATE (DATE_FROM), MT_NAME (INFORMATION1), MT_STATUS (INFORMATION2), MT_PERSON_ID (INFORMATION3), MT_TABLE_NAME (INFORMATION4), MT_INFORMATION_TYPE (INFORMATION5), and MT_INTER_BG_TRANSFER (INFORMATION6).

The person extra information block is exposed in parallel. PERSON_EXTRA_INFO_ID, PERSON_ID, INFORMATION_TYPE, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE map from INFORMATION7 through INFORMATION13. The PEI attribute set follows from INFORMATION14 onward: PEI_ATTRIBUTE_CATEGORY is INFORMATION14, PEI_ATTRIBUTE1 is INFORMATION15, PEI_ATTRIBUTE2 is INFORMATION16, and PEI_ATTRIBUTE3 through PEI_ATTRIBUTE20 continue sequentially through INFORMATION17 to INFORMATION34. The PEI_INFORMATION series then begins at INFORMATION35 with PEI_INFORMATION_CATEGORY, followed by PEI_INFORMATION1 in INFORMATION36 and onward through INFORMATION52, which carries the trailing PEI_I column truncated in the documented view text.

Common Use Cases and Queries

• Auditing pending or completed mass transfer rows for a person, including status and effective date.
• Extracting the PEI attribute values carried with each transfer row, particularly when a descriptive flexfield segment must be reconciled against the transfer record.
• Diagnosing transfer failures by joining the view back to GHR_INTERFACE on GHR_INTERFACE_ID.
• Reconciling the generic INFORMATIONn columns against their business aliases during interface troubleshooting.

To locate rows by the second PEI attribute, query the aliased column or its INFORMATION equivalent:

SELECT ghr_interface_id, mt_person_id, mt_status, pei_attribute_category, pei_attribute2
FROM apps.ghr_mt_people_ei_v
WHERE pei_attribute2 IS NOT NULL;

An equivalent form using the underlying name is:

SELECT ghr_interface_id, mt_person_id, information16
FROM apps.ghr_mt_people_ei_v
WHERE information16 = :pei_attribute2_value;

Because the view is not indexed independently, filters on PEI_ATTRIBUTE2 and other INFORMATION-derived columns rely on any indexes present on GHR_INTERFACE and on the selectivity of the transfer cycle being investigated. Restricting by MT_PROCESS_DATE or GHR_INTERFACE_ID is generally advisable when scanning large transfer volumes.