Search Results ghr_dual_actions_pk

Overview

The GHR_DUAL_ACTIONS table is a core data structure within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves a specific regulatory function by defining valid combinations of personnel actions that can be processed together as a "dual action." In the context of US federal personnel management, a dual action refers to a scenario where a primary personnel action (the first Nature of Action or NOA) is legally or procedurally required to be accompanied by a secondary, supporting action (the second NOA). This table acts as a validation and configuration repository, ensuring that only pre-defined, compliant combinations of NOAs can be entered and processed within the system, thereby enforcing complex federal personnel rules.

Key Information Stored

The table's structure is relatively simple, focusing on the relationships between action codes. Its primary data columns are the foreign keys that define these relationships. The FIRST_NOA_ID column stores the identifier for the primary Nature of Action. The SECOND_NOA_ID column stores the identifier for the associated, secondary Nature of Action that must accompany the first. Together, these two columns form the table's primary key (GHR_DUAL_ACTIONS_PK), meaning each valid combination is unique. The table also includes a NOA_FAMILY_CODE column, which links the dual action combination to a broader category or family of personnel actions, likely for grouping and reporting purposes. The data itself is typically maintained via the application's setup screens, not through transactional data entry.

Common Use Cases and Queries

The primary use case is the validation of personnel action requests. When a user attempts to initiate a dual action transaction, the application references this table to verify if the proposed first and second NOA codes constitute a valid pair. Common queries involve retrieving all permissible secondary actions for a given primary action, or checking for the existence of a specific combination. For example, to find all valid secondary NOAs for a specific first NOA ID, one might use:

• SELECT second_noa_id FROM hr.ghr_dual_actions WHERE first_noa_id = <specific_id>;

Conversely, to validate a specific pair during a process, the query would check for the existence of the record:

• SELECT 'VALID' FROM hr.ghr_dual_actions WHERE first_noa_id = <id1> AND second_noa_id = <id2>;

Reporting use cases often involve auditing setup data or generating lists of configured dual-action rules for compliance reviews.

Related Objects

The GHR_DUAL_ACTIONS table has direct dependencies on several other key GHR setup tables, as defined by its foreign key constraints. It references the GHR_NATURE_OF_ACTIONS table twice: once via the FIRST_NOA_ID column and once via the SECOND_NOA_ID column. This ensures that both codes defined in a dual action relationship are valid, established Nature of Action codes within the system. Furthermore, it references the GHR_FAMILIES table through the NOA_FAMILY_CODE column, linking the action pair to a broader classification. This table is foundational for any transactional or validation logic within the GHR module that processes dual personnel actions.