Search Results ghr_complaints




Overview
Explore in AI Chat

Overview

The GHR_COMPLAINTS table is a core data object within the Oracle E-Business Suite (EBS) US Federal Human Resources (GHR) module. It serves as the master record for tracking and processing formal complaints, a critical function for federal agency compliance with personnel regulations. The table acts as the central hub in a relational structure, storing the primary complaint header information. Each record represents a distinct complaint case, which is then elaborated upon through related detail tables for actions, issues, involved parties, and associated costs. Its implementation is specific to the GHR product family, designed to meet the unique reporting and procedural requirements of US federal government human capital management.

Key Information Stored

While the provided metadata does not list specific columns beyond key identifiers, the table's role and relationships define its critical data elements. The primary key, COMPLAINT_ID, uniquely identifies each complaint case. A significant foreign key, DISCRIM_ORG_ID, links the complaint to an organization unit within the HR_ALL_ORGANIZATION_UNITS table, typically identifying the office where the alleged discrimination or incident occurred. Based on standard complaint tracking, the table would also be expected to store foundational attributes such as the complaint case number, filing date, status (e.g., Open, Investigating, Closed), description, the complainant's employee or contact identifier, and relevant dates for procedural milestones. These fields collectively establish the complaint's administrative context.

Common Use Cases and Queries

This table is central to operational reporting and case management workflows. Common use cases include generating agency-wide reports on complaint volumes and statuses for Equal Employment Opportunity (EEO) compliance, tracking the lifecycle of individual cases for management oversight, and associating all related financial transactions. A typical query might join GHR_COMPLAINTS with its related detail tables to produce a comprehensive case summary. For example, to list all open complaints with their associated issues and primary organization, a SQL statement would leverage the documented foreign key relationships:

Related Objects

The GHR_COMPLAINTS table maintains defined relationships with several other GHR tables, forming a cohesive data model for complaint management. It references one master table and is referenced by four detail tables, as per the provided metadata:

  • Referenced Foreign Key: GHR_COMPLAINTS.DISCRIM_ORG_ID references HR_ALL_ORGANIZATION_UNITS. This links the complaint to the organizational hierarchy.
  • Referencing Foreign Keys (Child Tables):
    • GHR_COMPLAINT_ACTIONS.COMPLAINT_ID → GHR_COMPLAINTS: Tracks procedural steps and milestones.
    • GHR_COMPLAINT_COSTS.COMPLAINT_ID → GHR_COMPLAINTS: Records financial expenditures related to the case.
    • GHR_COMPLAINT_ISSUES.COMPLAINT_ID → GHR_COMPLAINTS: Captures the specific allegations or issues raised.
    • GHR_COMPLAINT_PEOPLE.COMPLAINT_ID → GHR_COMPLAINTS: Manages data for all individuals involved (complainants, witnesses, responsible officials).

This structure ensures data integrity and supports comprehensive reporting by anchoring all complaint-related transactions to a single master record.