Search Results ghr_families_pk

Overview

The GHR_FAMILIES table is a core data structure within the Oracle E-Business Suite (EBS) US Federal Human Resources (GHR) module. It functions as a master reference table, centrally storing and defining the distinct "families" of Notifications of Personnel Actions (NOAs) used across the federal HR lifecycle. An NOA family represents a logical grouping of related personnel actions, such as appointments, separations, or pay adjustments, which share common processing rules and approval workflows. The table's primary role is to provide a controlled, referential source for these family codes, ensuring data integrity and consistency in the processing of complex federal personnel transactions within EBS releases 12.1.1 and 12.2.2.

Key Information Stored

While the provided ETRM metadata does not list specific column definitions, the documented primary and foreign key relationships clearly identify the table's critical data element. The central column is NOA_FAMILY_CODE, which serves as the table's primary key (GHR_FAMILIES_PK). This column holds the unique alphanumeric identifier for each personnel action family. The table's purpose is to maintain a valid list of these codes. Associated descriptive columns, typical for such reference tables, would likely include fields for the family name, effective dates, and possibly an inactivation flag, though these are inferred based on standard EBS design patterns rather than the explicit documentation provided.

Common Use Cases and Queries

This table is predominantly used for validation, reporting, and as a join condition in queries related to federal personnel actions. Common operational and reporting scenarios include validating NOA family codes during data entry, generating summaries of personnel actions grouped by family, and supporting the routing and approval logic for PA (Personnel Action) Requests. A fundamental query pattern involves joining GHR_FAMILIES to transactional tables to retrieve action details with their family descriptions.

• Basic Validation/Lookup: SELECT noa_family_code FROM hr.ghr_families WHERE SYSDATE BETWEEN effective_start_date AND effective_end_date;
• Reporting Actions by Family: SELECT f.noa_family_code, COUNT(*) action_count FROM hr.ghr_pa_requests p, hr.ghr_families f WHERE p.noa_family_code = f.noa_family_code GROUP BY f.noa_family_code;

Related Objects

The GHR_FAMILIES table is a key parent table referenced by numerous transactional and configuration tables within the GHR module, as detailed in the foreign key metadata. Key dependent objects include:

• GHR_PA_REQUESTS: The core transactional table for personnel action requests, which categorizes each request by its NOA family.
• GHR_DUAL_ACTIONS and GHR_DUAL_PROC_METHODS: Tables related to dual employment processing rules, linked to specific action families.
• GHR_NOA_FAMILIES and GHR_NOA_FAM_PROC_METHODS: Tables that likely define detailed attributes and processing methods for each NOA family.
• GHR_PA_REQUEST_INFO_TYPES and GHR_PA_ROUTING_HISTORY: Tables storing supplemental request data and approval routing records, both tied to the base action family.