Results for “mass_action_id”

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

Overview

GHR_PA_REQUESTS is a core transactional table in the Oracle E-Business Suite US Federal Human Resources (GHR) module, owned by the HR schema. It stores all information relating to a Request to Personnel Action — the electronic instrument through which a federal agency documents, routes, and approves a personnel action before it becomes an official Notification of Personnel Action (NOA). In Oracle EBS 12.1.1 and 12.2.2 deployments with federal HR functionality enabled, this table is the central repository of the pending-action lifecycle, capturing the requested change, the approving and requesting officials, the from/to position and pay attributes, and the routing status of each request.

From a data-modeling perspective, the metadata's heuristic Data Vault classification identifies GHR_PA_REQUESTS as a hub. Each row represents a distinct business object keyed by a single surrogate identifier, and the table participates in numerous outbound and inbound foreign-key relationships rather than merely describing another entity. This classification is a modeling suggestion derived from the FK topology, not a physical implementation requirement.

Key Information Stored

The table is defined with 234 documented columns. The surrogate primary key is PA_REQUEST_ID, enforced by the GHR_PA_REQUESTS_PK unique index. Business-key candidates are documented separately: PA_NOTIFICATION_ID (GHR_PA_REQUESTS_UK1) and the composite name-based indexes GHR_PA_REQUESTS_UK2 and UK3, which concatenate employee name components with PA_REQUEST_ID.

• PA_REQUEST_ID — surrogate primary key uniquely identifying each request.
• PA_NOTIFICATION_ID — unique business identifier for the notification associated with the request.
• REQUEST_NUMBER and STATUS — human-readable request reference and workflow/approval status.
• PERSON_ID and EMPLOYEE_ASSIGNMENT_ID — the employee and assignment affected by the action.
• EMPLOYEE_LAST_NAME, EMPLOYEE_FIRST_NAME, EMPLOYEE_MIDDLE_NAMES — denormalized employee name, also used in the name-based unique indexes.
• FIRST_NOA_ID, SECOND_NOA_ID, FIRST_NOA_CODE, SECOND_NOA_CODE — nature-of-action codes for the primary and secondary actions.
• FROM_PAY_PLAN, TO_PAY_PLAN, TO_GRADE_ID, TO_JOB_ID, TO_ORGANIZATION_ID — from/to compensation, grade, job, and organizational attributes.
• FROM_POSITION_NUMBER, TO_POSITION_NUMBER, TO_POSITION_TITLE — position data for the affected assignment.
• EFFECTIVE_DATE, PROPOSED_EFFECTIVE_DATE, REQUESTED_DATE, APPROVAL_DATE — key dates in the action lifecycle.
• ROUTING_GROUP_ID, PERSONNEL_OFFICE_ID, NOA_FAMILY_CODE — routing, servicing personnel office, and NOA family configuration.
• ALTERED_PA_REQUEST_ID, FIRST_NOA_PA_REQUEST_ID, SECOND_NOA_PA_REQUEST_ID — self-referencing links to related or superseding requests.
• MASS_ACTION_ID, MASS_ACTION_ELIGIBLE_FLAG, MASS_ACTION_SELECT_FLAG — participation in mass realignment, salary, or transfer processing.
• Standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER) and the ATTRIBUTE1–20 and ATTRIBUTE_CATEGORY descriptive-flexfield columns.

Common Use Cases and Queries

Typical reporting includes pending-action queues by routing group or personnel office, aging of unapproved requests, and reconciliation between requests and the resulting NOAs. A representative query joins the request to its nature of action and pay plan:

• Pending actions by routing group: SELECT r.pa_request_id, r.request_number, r.status, r.requested_date FROM ghr_pa_requests r WHERE r.routing_group_id = :p_routing_group_id AND r.status = :p_status;
• Employee action history: SELECT r.pa_request_id, r.effective_date, r.first_noa_code, r.to_grade_id, r.to_pay_plan FROM ghr_pa_requests r WHERE r.person_id = :p_person_id ORDER BY r.effective_date DESC;
• Requests linked to mass actions: SELECT pa_request_id, mass_action_id FROM ghr_pa_requests WHERE mass_action_id IS NOT NULL AND mass_action_eligible_flag = 'Y';
• Altered or corrected requests: SELECT a.pa_request_id, a.alteration_reason FROM ghr_pa_requests a WHERE a.ALTERED_PA_REQUEST_ID = :p_pa_request_id;

Because the table carries 234 columns and is heavily referenced, queries should be constrained on the indexed keys (PA_REQUEST_ID, PA_NOTIFICATION_ID) or on PERSON_ID for best performance.

Related Objects

GHR_PA_REQUESTS is a hub with extensive inbound and outbound relationships. The most significant dependent and referenced tables include:

• GHR_NATURE_OF_ACTIONS — joined via FIRST_NOA_ID and SECOND_NOA_ID; supplies nature-of-action descriptions.
• GHR_PAY_PLANS — joined via FROM_PAY_PLAN and TO_PAY_PLAN; validates pay plan codes.
• PER_JOBS, PER_GRADES, HR_ALL_ORGANIZATION_UNITS — joined via TO_JOB_ID, TO_GRADE_ID, and TO_ORGANIZATION_ID for target position attributes.
• GHR_ROUTING_GROUPS and GHR_POIS — joined via ROUTING_GROUP_ID and PERSONNEL_OFFICE_ID for routing and servicing office.
• GHR_PA_HISTORY — references PA_REQUEST_ID and ALTERED_PA_REQUEST_ID, recording the audit trail of changes.
• GHR_PA_REMARKS, GHR_PA_REQUEST_EXTRA_INFO, and GHR_PA_ROUTING_HISTORY — child tables keyed by PA_REQUEST_ID holding remarks, additional data, and routing steps.
• GHR_EVENTS, GHR_MASS_REALIGNMENT, GHR_MASS_SALARIES, GHR_MASS_TRANSFERS — reference PA_REQUEST_ID to associate events and mass processing with individual requests.