Search Results dual_overlap_id

Overview

The GHR_DUAL_PROC_METHODS table is a core data structure within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) releases 12.1.1 and 12.2.2. It is owned by the HR schema and is designated as VALID, indicating its active role in the application. This table serves a specific regulatory function by storing the processing method associated with pairs of Notice of Action (NOA) codes. In the context of US federal personnel actions, where complex rules govern the sequencing and interaction of different personnel transactions, this table defines how the system should process scenarios involving two specific NOAs, ensuring compliance with federal guidelines.

Key Information Stored

The table's primary purpose is to link a combination of two NOA codes to a defined processing method. Based on the provided metadata, the key structural elements include:

• DUAL_OVERLAP_ID: Serves as the primary key for the table, uniquely identifying each rule that defines the process method for a specific NOA pair.
• NOA_FAMILY_CODE: A foreign key column that links to the GHR_FAMILIES table. This connection likely associates the NOA code pair with a broader family or category of personnel actions, providing context and grouping for the processing rules.
• While the explicit column names for the first and second NOA codes are not listed in the excerpt, the description confirms the table stores the process method for "the first and the second noa codes." Therefore, columns to hold these specific NOA_CODE values are a fundamental part of the table's structure.
• A column (or columns) defining the PROCESS_METHOD, which dictates the system's behavior (e.g., allow, disallow, require specific validation) when the two referenced NOA codes are involved in a personnel action.

Common Use Cases and Queries

This table is primarily accessed by the GHR application's business logic to enforce processing rules during the creation or modification of federal personnel actions. A common use case is validation: when a user attempts to initiate a personnel action with a specific NOA, the system may query this table to check if a prior or concurrent action with another NOA requires a specific processing method. Sample query patterns include retrieving the process method for a known pair of NOA codes or listing all rules within a specific NOA family.

-- Example: Find the process method for two specific NOA codes.
SELECT process_method
FROM hr.ghr_dual_proc_methods
WHERE noa_code_1 = 'XYZ'
  AND noa_code_2 = 'ABC';

-- Example: List all dual-processing rules for a family.
SELECT dpm.noa_code_1, dpm.noa_code_2, dpm.process_method, f.family_name
FROM hr.ghr_dual_proc_methods dpm
JOIN hr.ghr_families f ON dpm.noa_family_code = f.family_code
WHERE f.family_code = 'PAY_ADJ';

Related Objects

The GHR_DUAL_PROC_METHODS table has defined relationships with other key GHR tables, as per the metadata.

• GHR_FAMILIES: This is the primary related table, connected via the foreign key on the NOA_FAMILY_CODE column. The GHR_FAMILIES table categorizes NOA codes, and this relationship allows dual process methods to be organized and understood within those broader categories.
• GHR_DUAL_PROC_METHODS_PK: The primary key constraint ensuring the uniqueness of each rule.
• The table is integral to the GHR module's underlying packages and APIs that execute the business logic for processing federal personnel actions, particularly those handling validation and sequencing of multiple NOAs.