Results for “second_noa_code”

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

Overview

GHR_PA_ROUTING_HISTORY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the GHR – US Federal Human Resources product family. It presents personnel action (PA) routing history details, exposing the full audit trail of how a personnel action request moved through the routing and approval hierarchy. Each row represents a routing history record associated with a PA request, capturing the parties involved (initiator, approver, reviewer, requester, authorizer, personnelist), the approval status, and descriptive context such as the routing list, groupbox, and nature of action.

In both EBS 12.1.1 and 12.2.2 the view is documented as VALID and is intended primarily for reporting and integration rather than for transactional data entry. It is a convenient denormalized access point: instead of joining several GHR configuration tables manually, report developers and integrators query the view and receive the routing history row already enriched with the human-readable names of the routing list, groupbox, action family, and nature of action.

Underlying Base Objects

The view is defined over five base objects, all referenced through synonyms in the APPS schema. As documented in the ETRM metadata, these are:

• GHR_PA_ROUTING_HISTORY — the driving table (aliased PRH), containing the routing history transactional rows.
• GHR_ROUTING_LISTS — aliased RLS, joined on ROUTING_LIST_ID to supply the routing list name.
• GHR_GROUPBOXES — aliased GBX, joined on GROUPBOX_ID to supply the groupbox name.
• GHR_NATURE_OF_ACTIONS — referenced twice as NOA and NOA2, resolving the primary and secondary nature-of-action codes and descriptions.
• GHR_FAMILIES — aliased FAM, joined on NOA_FAMILY_CODE to supply the family name.

All joins are outer joins, with the configuration tables (RLS, GBX, NOA, NOA2, FAM) marked with the (+) operator. This ensures that every routing history row from GHR_PA_ROUTING_HISTORY is retained even when the corresponding routing list, groupbox, nature of action, or family reference is missing or has been deleted. ROW_ID is derived from PRH.ROWID to provide a unique identifier.

Key Columns

The view exposes the primary key PA_ROUTING_HISTORY_ID and the foreign key PA_REQUEST_ID linking each history entry to its personnel action request. Several Boolean-style flags identify the role a participant played in the routing step: INITIATOR_FLAG, APPROVER_FLAG, REVIEWER_FLAG, REQUESTER_FLAG, AUTHORIZER_FLAG, and PERSONNELIST_FLAG. APPROVED_FLAG and APPROVAL_STATUS record the outcome of the approval step.

User identity is captured through USER_NAME, USER_NAME_EMPLOYEE_ID, and the decomposed name columns USER_NAME_EMP_FIRST_NAME, USER_NAME_EMP_LAST_NAME, and USER_NAME_EMP_MIDDLE_NAMES, with a concatenated USER_NAME_EMP_FULL_NAME derived in the view text. Routing context is provided by ROUTING_LIST_ID together with the derived ROUTING_LIST_NAME, GROUPBOX_ID with GROUPBOX_NAME, and ROUTING_SEQ_NUMBER. The action itself is described by NOA_FAMILY_CODE with FAMILY_NAME, NATURE_OF_ACTION_ID with NOA_CODE and NOA_DESCRIPTION, and SECOND_NATURE_OF_ACTION_ID with SECOND_NOA_CODE and SECOND_NOA_DESCRIPTION. Audit and processing columns include ATTACHMENT_MODIFIED_FLAG, ACTION_TAKEN, NOTEPAD, OBJECT_VERSION_NUMBER, DATE_NOTIFICATION_SENT, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE.

Common Use Cases and Queries

The user search term "routing_list_name" maps directly to the ROUTING_LIST_NAME column, which is the derived name of the routing list (from GHR_ROUTING_LISTS). Typical scenarios include auditing the routing history of a specific personnel action request, identifying which routing list was applied, and reporting approval activity by routing list or by participant.

To list the routing history for a single PA request:

• SELECT pa_request_id, routing_list_name, routing_seq_number, user_name_emp_full_name, approval_status, approved_flag, creation_date FROM ghr_pa_routing_history_v WHERE pa_request_id = :p_request_id ORDER BY routing_seq_number;

To summarize routing activity grouped by routing list:

• SELECT routing_list_name, COUNT(*) routing_steps, MAX(date_notification_sent) last_notified FROM ghr_pa_routing_history_v GROUP BY routing_list_name ORDER BY routing_steps DESC;

To retrieve all history entries in which a given employee acted as approver:

• SELECT pa_request_id, routing_list_name, user_name, action_taken, approval_status, creation_date FROM ghr_pa_routing_history_v WHERE approver_flag = 'Y' AND user_name_employee_id = :p_employee_id;

Because the view relies on outer joins, consumers should be prepared for null values in the configuration-derived columns (for example, ROUTING_LIST_NAME or FAMILY_NAME) when the underlying reference data has been removed. Filtering or reporting on those columns should therefore use NVL or IS NULL handling where appropriate.