Results for “ghr_assignments_h_v”

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

Overview

The GHR_ASSIGNMENTS_H_V view is an APPS-owned database object in Oracle E-Business Suite, delivered as part of the GHR - US Federal Human Resources product family. Its documented purpose is to map columns from the GHR_PA_HISTORY transaction history structure to the shape and semantics of the PER_ASSIGNMENTS_F assignment entity. In effect, it presents personnel action history information in an assignments-oriented projection, allowing assignment attributes recorded against a personnel action request to be read as though they were assignment rows.

Because GHR_PA_HISTORY stores transactional personnel action data in a generic, denormalized form, the view supplies the decoding logic required to translate that stored data into meaningful, typed assignment columns. It is therefore primarily a reporting and integration object: it supports extracts, conversions, and custom inquiries that need to consume assignment-level data originating from the US Federal personnel action process without navigating the raw history table directly.

Underlying Base Objects

The view is defined over three documented base objects:

• GHR_PA_HISTORY (Synonym) — the primary source of rows. This table holds personnel action history records, including the generic INFORMATION1 through INFORMATION29 columns plus control columns such as PA_HISTORY_ID, PROCESS_DATE, EFFECTIVE_DATE, DML_OPERATION, PRE_VALUES_FLAG, ALTERED_PA_REQUEST_ID, PA_REQUEST_ID, and NATURE_OF_ACTION_ID.
• GHR_GENERAL (Package) — supplies the RETURN_NUMBER function, used to convert the character-based INFORMATION columns into numeric values for identifier and sequence attributes.
• FND_DATE (Package) — supplies CANONICAL_TO_DATE, used to convert canonical date strings stored in the INFORMATION columns into proper DATE values.

The view is a direct column mapping and adds no filtering or joining logic beyond the function calls applied to the generic information columns.

Key Columns

The view exposes the control columns of the source history record alongside decoded assignment attributes. Notable columns include:

• PA_HISTORY_ID, PROCESS_DATE, EFFECTIVE_DATE, DML_OPERATION, PRE_VALUES_FLAG — history-row identity and processing context.
• PA_REQUEST_ID and ALTERED_PA_REQUEST_ID — linkage back to the personnel action request that generated the record.
• NATURE_OF_ACTION_ID — the personnel action type applied.
• ASSIGNMENT_ID, PERSON_ID, ASSIGNMENT_SEQUENCE, ASSIGNMENT_NUMBER, ASSIGNMENT_TYPE, PRIMARY_FLAG — core assignment identification attributes.
• EFFECTIVE_START_DATE and EFFECTIVE_END_DATE — date-effective boundaries of the assignment, decoded via FND_DATE.
• ASSIGNMENT_STATUS_TYPE_ID, PAYROLL_ID, PEOPLE_GROUP_ID, SOURCE_ORGANIZATION_ID, SUPERVISOR_ID, RECRUITER_ID — status and organizational assignments.
• VACANCY_ID, RECRUITMENT_ACTIVITY_ID, PERSON_REFERRED_BY_ID, RECRUITMENT_ACTIVITY_ID — recruitment-related references.
• SOFT_CODING_KEYFLEX_ID, DEFAULT_CODE_COMB_ID, PAY_BASIS_ID, FREQUENCY — payroll and accounting attributes.
• EMPLOYMENT_CATEGORY, CHANGE_REASON, DATE_PROBATION_END, MANAGER_FLAG, INTERNAL_ADDRESS_LINE, COMMENT_ID — descriptive assignment details.

Common Use Cases and Queries

The view is typically queried to extract assignment data derived from personnel action history, for example to audit actions, build conversion extracts, or reconcile history against current assignments. A representative query retrieving assignment identification and effective dates is:

• SELECT pa_history_id, assignment_id, person_id, assignment_number, effective_start_date, effective_end_date, assignment_status_type_id FROM apps.ghr_assignments_h_v WHERE effective_date BETWEEN :start_date AND :end_date;
• SELECT pa_request_id, nature_of_action_id, assignment_id, change_reason FROM apps.ghr_assignments_h_v WHERE dml_operation = 'U';

Typical scenarios include auditing personnel actions by request, identifying assignments affected by a given action type, and supplying assignment-shaped data to downstream interfaces. Because no row-level security predicates are applied within the view itself, consumers should filter by the relevant date, request, or assignment identifiers as required.