Search Results ghr_dual_actions_pk




Overview
Explore in AI Chat

Overview

The HR.GHR_DUAL_ACTIONS table is a configuration table within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the U.S. Federal Human Resources (GHR) module. Its primary function is to define valid combinations of personnel actions that can be processed together as a "dual action." The table stores a master list of first Nature of Actions (NOAs) and all associated second NOAs that are permissible for concurrent processing. This ensures data integrity and enforces business rules during complex personnel transaction processing, such as a promotion coupled with a relocation. The table is stored in the APPS_TS_SEED tablespace, indicating it is part of the seeded reference data delivered with the application.

Key Information Stored

The table's structure is focused on defining relationships between NOAs. The core data columns are FIRST_NOA_ID and SECOND_NOA_ID, both foreign keys to the GHR_NATURE_OF_ACTIONS table, which store the specific action identifiers. The NOA_FAMILY_CODE column, a foreign key to GHR_FAMILIES, provides a grouping mechanism, potentially for categorization or reporting. Standard EBS audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE) track changes. The primary key constraint GHR_DUAL_ACTIONS_PK is a composite key on (FIRST_NOA_ID, SECOND_NOA_ID), guaranteeing the uniqueness of each defined dual-action pairing.

Common Use Cases and Queries

This table is central to validating personnel transactions in the GHR module. When a user initiates a complex action, the application logic queries this table to verify if the proposed combination of NOAs is allowed. Common reporting and validation queries include identifying all permissible second actions for a given first action, or checking the validity of a specific pair. The following are sample SQL patterns:

  • Retrieve all valid second NOAs for a specific first NOA (ID: 123):
    SELECT SECOND_NOA_ID FROM HR.GHR_DUAL_ACTIONS WHERE FIRST_NOA_ID = 123;
  • Validate a specific NOA pairing:
    SELECT 'VALID' FROM HR.GHR_DUAL_ACTIONS WHERE FIRST_NOA_ID = 123 AND SECOND_NOA_ID = 456;
  • Full data extraction for analysis, as per the provided ETRM query:
    SELECT FIRST_NOA_ID, SECOND_NOA_ID, NOA_FAMILY_CODE, LAST_UPDATE_DATE, CREATED_BY FROM HR.GHR_DUAL_ACTIONS;

Related Objects

HR.GHR_DUAL_ACTIONS has defined dependencies within the GHR schema. Its two main foreign key relationships are with GHR_NATURE_OF_ACTIONS (via FIRST_NOA_ID and SECOND_NOA_ID) to resolve the action codes, and with GHR_FAMILIES (via NOA_FAMILY_CODE). The table is referenced by the APPS.GHR_DUAL_ACTIONS and PUBLIC.GHR_DUAL_ACTIONS synonyms, which facilitate standard access. The existence of the GHR_DUAL_ACTIONS_WHO object suggests there is likely a database trigger on the table to populate the audit (WHO) columns automatically, a common pattern in EBS.