Search Results ghr_complaint_basis_pk

Overview

The GHR_COMPLAINT_BASES table is a core data object within the US Federal Human Resources (GHR) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a child table in the complaint tracking structure, designed to store the specific legal or regulatory bases associated with a complaint issue. In the context of federal HR compliance, a single complaint issue (e.g., harassment, wrongful termination) may be founded on multiple bases, such as discrimination based on race, color, religion, sex, or age. This table enables the system to capture and maintain this detailed, multi-basis information, which is critical for accurate case management, reporting, and adherence to federal equal employment opportunity (EEO) and complaint processing regulations.

Key Information Stored

The table's primary purpose is to establish a relationship between a complaint issue and its bases. Its key columns, as indicated by the provided metadata, are the primary and foreign keys that enforce data integrity. The COMPLAINT_BASIS_ID column serves as the unique identifier (primary key) for each record in this table. The COMPLAINT_ISSUE_ID column is a foreign key that links each basis record back to its parent complaint issue in the GHR_COMPLAINT_ISSUES table. While the specific descriptive column for the basis (e.g., BASIS_CODE or BASIS_DESCRIPTION) is not explicitly listed in the provided excerpt, it is a standard component of such a structure. This column would typically hold a code or description classifying the legal basis of the complaint, such as 'SEX', 'RACE', 'REPRISAL', or 'DISABILITY'.

Common Use Cases and Queries

This table is primarily accessed for detailed compliance reporting and case inquiry. A common operational use case is generating a report that lists all complaints filed within a specific period, broken down by their associated issues and bases for agency-level EEO reporting. Support personnel query this table to understand the full scope of a filed complaint. A typical SQL pattern involves joining to the parent issue and complaint headers:

• Listing Bases for a Specific Complaint Issue: SELECT * FROM GHR_COMPLAINT_BASES WHERE COMPLAINT_ISSUE_ID = <issue_id>;
• Reporting on Complaint Trends by Basis: SELECT cb.BASIS_CODE, COUNT(*) FROM GHR_COMPLAINT_BASES cb, GHR_COMPLAINT_ISSUES ci WHERE cb.COMPLAINT_ISSUE_ID = ci.COMPLAINT_ISSUE_ID GROUP BY cb.BASIS_CODE;

Related Objects

The GHR_COMPLAINT_BASES table has a direct and dependent relationship within the GHR complaint data model, as documented in the provided metadata.

• GHR_COMPLAINT_ISSUES: This is the primary parent table. Each record in GHR_COMPLAINT_BASES must reference a valid COMPLAINT_ISSUE_ID in GHR_COMPLAINT_ISSUES. This relationship ensures that every recorded basis is tied to a defined complaint issue.
• The table itself is the target of the primary key constraint GHR_COMPLAINT_BASIS_PK on the column COMPLAINT_BASIS_ID.

This structure positions GHR_COMPLAINT_BASES as an essential detail table for managing the complex, multi-faceted nature of federal personnel complaints within Oracle EBS.