Results for “from_basic_pay”

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

Overview

GHR_PA_REQUESTS_V is an APPS-owned database view in Oracle E-Business Suite, delivered as part of the GHR - US Federal Human Resources product family. It is defined in both Oracle EBS 12.1.1 and 12.2.2 and is registered as VALID in the ETRM metadata repository. The view is a form-support construct: it is defined over the GHR_PA_REQUESTS base table (referenced through a synonym) so that the associated GHR personnel action form can retrieve personnel action request records together with decoded descriptive attributes that would otherwise require runtime lookups.

Personnel action requests (PARs) represent the federal HR transactions that drive appointments, promotions, separations, pay adjustments, and similar actions. Because such transactions must be reviewed, approved, and audited, the form requires the request header, the requested action, and the nature-of-action context in a single denormalized result set. GHR_PA_REQUESTS_V provides exactly that shape. In reporting and integration terms, the view is a convenient, pre-joined read layer over the PAR table and its reference lookups, and it is frequently used whenever PAR data must be extracted without re-deriving the join logic against GHR_FAMILIES and GHR_NATURE_OF_ACTIONS.

Underlying Base Objects

The documented base objects referenced by GHR_PA_REQUESTS_V are:

• GHR_PA_REQUESTS (SYNONYM) — the primary table holding one row per personnel action request. It supplies the overwhelming majority of the columns exposed by the view.
• GHR_FAMILIES (SYNONYM) — the reference table joined to GHR_PA_REQUESTS on the family code (PAR.NOA_FAMILY_CODE = FAM.NAME relationship), supplying the human-readable ACTION_REQUESTED description.
• GHR_NATURE_OF_ACTIONS (SYNONYM) — the nature-of-action reference joined to supply the FIRST_NOA_CODE (NOA1.CODE) associated with the request's first nature of action.

The view also aliases PAR.ROWID as ROW_ID, preserving the row identifier from the base table so that form-based updates can target the correct GHR_PA_REQUESTS row. No data is stored in the view itself; all values are derived at execution time from the referenced objects.

Key Columns

The view exposes the full PAR attribute set. Significant columns include:

• PA_REQUEST_ID — primary identifier of the personnel action request.
• PERSON_ID / EMPLOYEE_ASSIGNMENT_ID — the person and assignment to which the action applies.
• NOA_FAMILY_CODE / ACTION_REQUESTED — the action family and its decoded name from GHR_FAMILIES.
• FIRST_NOA_ID / FIRST_NOA_CODE / FIRST_NOA_DESC — the first nature of action, its code, and description.
• ROUTING_GROUP_ID — the routing group governing workflow of the request.
• EFFECTIVE_DATE / APPROVAL_DATE / CONCURRENCE_DATE — key dates for the action lifecycle.
• AUTHORIZED_BY_PERSON_ID / AUTHORIZED_BY_TITLE / APPROVING_OFFICIAL_* — authorization and approval identifying attributes.
• FROM_* and TO_* pay, position, grade, and agency columns — the before-and-after state of the action, including FROM_POSITION_ID, FROM_GRADE_OR_LEVEL, FROM_BASIC_PAY, and related locality and pay-basis fields.
• Employee name, DOB, and national identifier columns — denormalized employee demographics carried on the request.

Although the metadata excerpt does not enumerate a REQUESTED_BY_PERSON_ID column in the visible projection, request-ownership and requester attributes are commonly represented in the PAR table; consumers searching for requested_by_person_id should verify the exact projection against the deployed view text using ALL_VIEWS in their instance, since the excerpted DDL is truncated.

Common Use Cases and Queries

Typical scenarios include form-driven maintenance of PAR records, operational reporting on pending and approved actions, and inbound/outbound integration extracts.

Example: retrieve requests for a person, decoded with the action family name.

• SELECT pa_request_id, person_id, effective_date, action_requested, first_noa_code FROM apps.ghr_pa_requests_v WHERE person_id = :p_person_id ORDER BY effective_date DESC;

Example: approved actions within a date range for audit review.

• SELECT pa_request_id, employee_last_name, first_noa_desc, approval_date FROM apps.ghr_pa_requests_v WHERE approval_date BETWEEN :p_from AND :p_to AND approval_date IS NOT NULL;

Example: locating a request by its action family and routing group.

• SELECT pa_request_id, noa_family_code, routing_group_id FROM apps.ghr_pa_requests_v WHERE noa_family_code = :p_family AND routing_group_id = :p_group;

Because the view carries ROW_ID from GHR_PA_REQUESTS, it is also the appropriate source for forms that must lock and update the underlying request row directly.