Results for “pa_notification_id”

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

Overview

GHR_PA_REQUESTS_V1 is an Oracle EBS 12.1.1 / 12.2.2 view owned by the APPS schema within the GHR – US Federal Human Resources product. It holds Remuneration and Personnel Action (RPA) and Non-Personnel Action (NPA) request information, consolidating a set of personnel action requests together with the routing, family, and nature-of-action attributes needed to interpret and report on them. The view exposes a horizontal picture of each request line, enriched by correlated lookups for the routing group name, the nature-of-action family name, and the order of processing.

The view is primarily a reporting and integration surface. Rather than querying the base personnel action tables and performing the joins between requests, routing groups, families, and nature-of-action codes manually, consumers can select from GHR_PA_REQUESTS_V1 to obtain a denormalized request record. The embedded query text confirms that the view performs a sub-select over the request data and then joins outward to routing groups, families, and nature-of-actions to supply descriptive names.

Underlying Base Objects

The documented base objects referenced by the view are:

• GHR_PA_REQUESTS (SYNONYM) — the primary source of personnel action request rows, supplying request identifiers, effective dates, approval dates, person identifiers, and the derived NOA code, ID, and description.
• GHR_ROUTING_GROUPS (SYNONYM) — supplies the routing group name exposed as ROUTING_GROUP_NAME via the RGP alias, joined on ROUTING_GROUP_ID.
• GHR_FAMILIES (SYNONYM) — supplies the nature-of-action family name exposed as NOA_FAMILY_NAME via the FAM alias, joined on NOA_FAMILY_CODE.
• GHR_NATURE_OF_ACTIONS (SYNONYM) — supplies the order of processing via the NOA alias, joined on NOA_ID.

The inner sub-select performs DECODE logic against FIRST_NOA_CODE and SECOND_NOA_CODE so that the effective NOA code, ID, and description reflect the correct nature of action depending on whether the first code is '001' or '002'. It also assigns ROWNUM and LEVEL (hierarchy level) values, indicating the view supports hierarchical traversal of request relationships.

Key Columns

• PA_REQUEST_ID / ALTERED_PA_REQUEST_ID / FIRST_NOA_PA_REQUEST_ID — request identifiers, including linkage back to an original or altered request.
• ROUTING_GROUP_ID / ROUTING_GROUP_NAME — the routing group to which the request is assigned and its descriptive name (the column implicated by the search term "routing_group_name").
• NOA_CODE / NOA_ID / NOA_DESC / NOA_FAMILY_CODE / NOA_FAMILY_NAME — the nature of action and its family, both coded and described.
• EFFECTIVE_DATE, APPROVAL_DATE, STATUS, ACTION_TYPE — core lifecycle attributes of the request.
• PERSON_ID, PERSONNEL_OFFICE_ID, REQUEST_NUMBER — the subject person and administrative references.
• WHICH_NOA, FIRST_NOA_CANCEL_OR_CORRECT, INDENT, ROW_NUM, HIERARCHY_LEVEL — positional and hierarchical indicators.
• ORDER_OF_PROCESSING — sequencing supplied by GHR_NATURE_OF_ACTIONS.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical scenarios include listing requests by routing group, tracing the chain of first and subsequent nature of actions, and reporting on a person's personnel actions by family or status.

Requests by routing group name:

• SELECT PA_REQUEST_ID, REQUEST_NUMBER, ROUTING_GROUP_NAME, NOA_DESC, STATUS FROM APPS.GHR_PA_REQUESTS_V1 WHERE ROUTING_GROUP_NAME = :p_group;

Personnel actions for a person with family and processing order:

• SELECT NOA_CODE, NOA_DESC, NOA_FAMILY_NAME, ORDER_OF_PROCESSING, EFFECTIVE_DATE FROM APPS.GHR_PA_REQUESTS_V1 WHERE PERSON_ID = :p_person ORDER BY EFFECTIVE_DATE;

Active or approved requests within a date range:

• SELECT REQUEST_NUMBER, ROUTING_GROUP_NAME, APPROVAL_DATE FROM APPS.GHR_PA_REQUESTS_V1 WHERE APPROVAL_DATE BETWEEN :from_date AND :to_date ORDER BY APPROVAL_DATE;

These queries benefit from the view's pre-joined descriptive columns, avoiding the need to resolve ROUTING_GROUP_ID, NOA_FAMILY_CODE, or NOA_ID against their base tables manually.