Search Results per_assignments_extra_info

Overview

The view APPS.GHR_ASSIGNMENT_EXTRA_INFO_H_V is a documented Oracle E-Business Suite database object owned by the APPS schema and classified under the GHR — US Federal Human Resources product family. Its stated purpose in the ETRM metadata is precise: it performs a mapping of GHR_PA_HISTORY columns to PER_ASSIGNMENTS_EXTRA_INFO. In other words, the view takes the generic, information-numbered column structure of the GHR personnel action history table and projects it into a shape that mirrors the column layout of the PER_ASSIGNMENTS_EXTRA_INFO table, renaming INFORMATION1 through INFORMATION34 into semantically meaningful AEI_* columns while applying explicit substring truncation to honour the target column lengths.

Because the view is defined over the GHR personnel action history, it acts as an integration and reporting bridge between the Federal HR personnel action engine and the core Oracle HRMS assignment extra information model. It is commonly used when historical personnel action data must be presented, extracted, or reconciled in the same structure as live extra assignment information.

Underlying Base Objects

The ETRM metadata records three referenced base objects for this view:

• GHR_PA_HISTORY (SYNONYM) — the primary source of data. It supplies the driving columns PA_HISTORY_ID, PROCESS_DATE, EFFECTIVE_DATE, DML_OPERATION, PRE_VALUES_FLAG, ALTERED_PA_REQUEST_ID, PA_REQUEST_ID, NATURE_OF_ACTION_ID, PERSON_ID and the INFORMATION1 through INFORMATION34 columns.
• GHR_GENERAL (PACKAGE) — invoked as GHR_GENERAL.RETURN_NUMBER to convert character information fields into numeric identifiers. It is applied to INFORMATION1 (yielding ASSIGNMENT_EXTRA_INFO_ID) and INFORMATION4 (yielding ASSIGNMENT_ID).
• FND_DATE (PACKAGE) — referenced by the view metadata and associated with the date-oriented columns such as PROCESS_DATE and EFFECTIVE_DATE.

No joins to PER_ASSIGNMENTS_EXTRA_INFO itself are performed in the view text; the relationship is purely a structural mapping, with the INFORMATION columns carrying the source values that correspond to the target table's attributes.

Key Columns

• PA_HISTORY_ID — unique identifier of the personnel action history record.
• PROCESS_DATE / EFFECTIVE_DATE — processing and business-effective dates of the historical action.
• DML_OPERATION / PRE_VALUES_FLAG — indicate the operation type and whether pre-change values are represented.
• ALTERED_PA_REQUEST_ID / PA_REQUEST_ID — links to the originating personnel action request.
• NATURE_OF_ACTION_ID / PERSON_ID — the action category and the person affected.
• ASSIGNMENT_EXTRA_INFO_ID — numeric form of INFORMATION1.
• ASSIGNMENT_ID — numeric form of INFORMATION4, identifying the assignment.
• INFORMATION_TYPE / AEI_INFORMATION_CATEGORY — category descriptors drawn from INFORMATION5 and INFORMATION6.
• AEI_INFORMATION1 … AEI_INFORMATION28 — the mapped extra information attributes, sourced from INFORMATION7 through INFORMATION34, each truncated to 150 characters (INFORMATION5 to 40, INFORMATION6 to 30).

Common Use Cases and Queries

The view is typically queried to surface Federal personnel action history in assignment extra information terms, to audit changes, or to feed downstream extracts. A basic retrieval by person is shown below:

• SELECT pa_history_id, person_id, assignment_id, effective_date, nature_of_action_id, aei_information1 FROM apps.ghr_assignment_extra_info_h_v WHERE person_id = :p_person_id ORDER BY effective_date;
• SELECT pa_history_id, dml_operation, pre_values_flag, assignment_extra_info_id FROM apps.ghr_assignment_extra_info_h_v WHERE pa_request_id = :p_request_id;

Such queries allow reporting on personnel action history using the same attribute naming conventions as PER_ASSIGNMENTS_EXTRA_INFO, simplifying comparisons between historical and current assignment extra information.