Search Results ghr_complaint_people_pk
Overview
The GHR_COMPLAINT_PEOPLE 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 serves as the central repository for storing information about complainants associated with formal complaint actions. In the context of federal HR processes, a single complaint case can involve multiple individuals. This table is designed to manage that many-to-one relationship, linking each complainant record directly to a specific complaint case. Its primary role is to ensure accurate tracking of all parties involved in a complaint, which is critical for case management, reporting, and compliance with federal personnel regulations.
Key Information Stored
The table's structure is anchored by a system-generated primary key, COMPLAINT_PERSON_ID, which uniquely identifies each complainant record. The most critical foreign key column is COMPLAINT_ID, which links the person to a specific case in the parent GHR_COMPLAINTS table. While the provided ETRM excerpt does not list all columns, standard design patterns for such junction tables suggest it would also store key identifiers for the person involved. This typically includes a PERSON_ID linking to the core HR person tables (like PER_ALL_PEOPLE_F) and potentially role-specific attributes (e.g., complainant type, contact details for the case). The table essentially acts as the intersection between a complaint case and the individuals associated with it.
Common Use Cases and Queries
The primary use case is supporting comprehensive complaint management workflows. HR specialists use this data to generate contact lists, manage communications, and ensure all parties are properly documented for audits or investigations. Common reporting needs include listing all complainants for a specific case or identifying all cases a particular person is involved in. A typical SQL query to retrieve this information would join GHR_COMPLAINT_PEOPLE to GHR_COMPLAINTS and the core person tables.
- Sample Query:
SELECT cp.COMPLAINT_PERSON_ID, c.COMPLAINT_NUMBER, p.FULL_NAME FROM GHR_COMPLAINT_PEOPLE cp, GHR_COMPLAINTS c, PER_ALL_PEOPLE_F p WHERE cp.COMPLAINT_ID = c.COMPLAINT_ID AND cp.PERSON_ID = p.PERSON_ID AND c.COMPLAINT_NUMBER = 'CASE-12345'; - Reporting: Reports often aggregate this data to show complaint volumes per person or department, or to track the status of cases involving specific individuals.
Related Objects
The GHR_COMPLAINT_PEOPLE table has defined relationships with other key GHR entities, forming an integral part of the complaint data model.
- Primary Key: GHR_COMPLAINT_PEOPLE_PK on the COMPLAINT_PERSON_ID column.
- Foreign Key (Parent Table): The table has a mandatory foreign key relationship to GHR_COMPLAINTS via the COMPLAINT_ID column. This enforces referential integrity, ensuring every complainant is associated with a valid complaint record.
- Implied Relationships: While not explicitly listed in the provided metadata, in a full implementation, the table would also link to core HR person tables (e.g., PER_ALL_PEOPLE_F) via a PERSON_ID column to retrieve the complainant's name and other personal details.
-
Table: GHR_COMPLAINT_PEOPLE
12.1.1
product: GHR - US Federal Human Resources , description: GHR_COMPLAINT_PEOPLE holds the complainants who are involved in thecomplaint action. , implementation_dba_data: Not implemented in this database ,
-
Table: GHR_COMPLAINT_PEOPLE
12.2.2
product: GHR - US Federal Human Resources , description: GHR_COMPLAINT_PEOPLE holds the complainants who are involved in thecomplaint action. , implementation_dba_data: Not implemented in this database ,