Results for “action_taken”

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

Overview

GHR_PD_ROUTING_HISTORY is a table in the HR schema of Oracle E-Business Suite, belonging to the GHR — US Federal Human Resources product. It stores the routing history details of Position Descriptions, capturing the approval workflow activity that a position description passes through as it moves across reviewers, approvers, and routing lists. In federal HR implementations, position descriptions require formal, auditable sign-off before they become effective; this table is the persistent record of that movement and of the roles and individuals involved at each step.

Within the documented physical schema (ETRM 12.2.2), the table contains 26 columns and is owned by HR. Its primary key, GHR_PD_ROUTING_HISTORY_PK, is defined on the single column PD_ROUTING_HISTORY_ID. The foreign keys position the table beneath GHR_POSITION_DESCRIPTIONS, GHR_ROUTING_LISTS, and GHR_GROUPBOXES. A heuristic Data Vault classification mined from this foreign-key structure suggests the table behaves as a link — an associative structure that records relationships and events between position descriptions, routing lists, and groupboxes rather than serving as a standalone hub. This classification is offered as a modeling observation, not as a documented attribute of the EBS table itself.

Key Information Stored

The table is anchored by its surrogate primary key, PD_ROUTING_HISTORY_ID, generated under the GHR_PD_ROUTING_HISTORY_PK unique index. No alternate business-key unique index is documented beyond this primary key.

The most significant columns fall into three groups:

• Position description linkage: POSITION_DESCRIPTION_ID references GHR_POSITION_DESCRIPTIONS and identifies the description being routed. ITEM_KEY provides an additional identifying value for the routed item.
• Routing and participant context: ROUTING_LIST_ID and GROUPBOX_ID link to their respective parent objects; ROUTING_SEQ_NUMBER records the position of the step within the routing sequence. INITIATOR_FLAG, APPROVER_FLAG, REQUESTER_FLAG, PERSONNELIST_FLAG, REVIEWER_FLAG, and AUTHORIZER_FLAG classify the role played at each routing step.
• User and action detail: USER_NAME, USER_NAME_EMPLOYEE_ID, and the denormalized USER_NAME_EMP_FIRST_NAME, USER_NAME_EMP_LAST_NAME, and USER_NAME_EMP_MIDDLE_NAMES capture the person involved. ACTION_TAKEN and APPROVED_FLAG record the outcome, while DATE_NOTIFICATION_SENT records when notification occurred.
• Standard audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE, and OBJECT_VERSION_NUMBER support auditing and optimistic locking.

Common Use Cases and Queries

Typical reporting scenarios include reconstructing the approval trail for a position description, identifying pending approvals by reviewer or approver, and auditing who acted and when.

A common query returns the routing history for a given position description, joined to the parent description and routing list:

• Join GHR_PD_ROUTING_HISTORY to GHR_POSITION_DESCRIPTIONS on POSITION_DESCRIPTION_ID to report by description.
• Join to GHR_ROUTING_LISTS on ROUTING_LIST_ID to resolve the routing list applied.
• Filter on APPROVED_FLAG or ACTION_TAKEN to isolate completed versus outstanding steps.
• Order by ROUTING_SEQ_NUMBER to present steps in the intended sequence.
• Filter on APPROVER_FLAG, REVIEWER_FLAG, or AUTHORIZER_FLAG to build role-specific worklists.
• Use DATE_NOTIFICATION_SENT to analyze notification timing versus action dates.

Related Objects

The following objects are most significant through the documented foreign-key relationships:

• GHR_POSITION_DESCRIPTIONS — referenced via POSITION_DESCRIPTION_ID; the parent position description.
• GHR_ROUTING_LISTS — referenced via ROUTING_LIST_ID; the routing list governing the approval path.
• GHR_GROUPBOXES — referenced via GROUPBOX_ID; the groupbox associated with the routing step.
• GHR_PD_ROUTING_HISTORY_PK — the primary-key unique index on PD_ROUTING_HISTORY_ID.
• Related GHR position description and routing tables and the corresponding GHR position description APIs, which together manage and expose the lifecycle data recorded here.