Results for “ghr_complaints”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GHR_COMPLAINTS is a transaction-level table within the Oracle E-Business Suite US Federal Human Resources (GHR) module. It stores the master record for an individual complaint filed within a federal agency, capturing the facts required to initiate, track, and resolve a complaint through its full lifecycle. In Oracle EBS 12.1.1 and 12.2.2, the table functions as the operational anchor for Equal Employment Opportunity (EEO), discrimination, and related grievance workflows managed by federal HR and legal staff.

The ETRM metadata classifies GHR_COMPLAINTS under a heuristic Data Vault model as hub-leaning. In practical terms, this suggests the table behaves as a hub: a central entity keyed by a single surrogate identifier, with surrounding transaction details distributed into satellite-style child tables. The table is documented as "Not implemented in this database" in the metadata excerpt, meaning no concrete column-level DDL was exposed; the columns cited below are limited to those identified through primary key and foreign key definitions. The table is not part of the base HRMS installation and is licensed and deployed only with the GHR federal product family.

Key Information Stored

The only documented column-level facts for GHR_COMPLAINTS are its primary key and its foreign key columns. The table's principal identifier is:

• COMPLAINT_ID — the surrogate primary key, defined by the constraint GHR_COMPLAINTS_PK. This is a system-generated, non-intelligent key that uniquely identifies each complaint record and is the value propagated to all child tables.
• DISCRIM_ORG_ID — a foreign key referencing HR_ALL_ORGANIZATION_UNITS. This column identifies the organization unit associated with the discrimination complaint, providing the organizational context (agency, bureau, or office) in which the complaint arose.

No unique business-key index is documented in the available metadata. Because the primary key is a surrogate, business-key candidates for a complaint in a federal environment would typically include natural identifiers such as a complaint number or case number, but these are not confirmed in the supplied documentation and should be verified against the actual table DDL in a deployed instance. Likewise, descriptive attributes such as complaint type, filing date, statute, status, and resolution are expected to reside in the table or its satellites but are not enumerated here because the metadata does not identify them explicitly.

Common Use Cases and Queries

GHR_COMPLAINTS is queried primarily to retrieve complaint headers, join complaint activity and cost detail, and drive federal EEO reporting. A basic retrieval by organization would join the complaint header to the organization table:

• SELECT c.COMPLAINT_ID, c.DISCRIM_ORG_ID FROM GHR_COMPLAINTS c WHERE c.DISCRIM_ORG_ID = :org_id;
• Complaint actions, costs, issues, and people are attached by joining child tables on COMPLAINT_ID, for example GHR_COMPLAINTS c JOIN GHR_COMPLAINT_ACTIONS a ON a.COMPLAINT_ID = c.COMPLAINT_ID.
• Reporting use cases include open/closed complaint counts by agency, discrimination basis and issue analysis, cost tracking for settlements and investigations, and timelines of complaint events.

Because the primary key is surfaced as the sole documented column, queries should always drive from COMPLAINT_ID to guarantee correct cardinality when aggregating child records.

Related Objects

The following objects are the most significant dependents and references documented for GHR_COMPLAINTS:

• HR_ALL_ORGANIZATION_UNITS — referenced by GHR_COMPLAINTS.DISCRIM_ORG_ID; supplies the organizational unit for the complaint.
• GHR_COMPLAINT_ACTIONS — child table joined on COMPLAINT_ID; stores action history for the complaint.
• GHR_COMPLAINT_COSTS — child table joined on COMPLAINT_ID; stores cost elements associated with the complaint.
• GHR_COMPLAINT_ISSUES — child table joined on COMPLAINT_ID; stores the issues or bases alleged in the complaint.
• GHR_COMPLAINT_PEOPLE — child table joined on COMPLAINT_ID; stores individuals associated with the complaint, such as complainants or representatives.

These relationships confirm the hub-leaning model: GHR_COMPLAINTS holds the complaint identity, while actions, costs, issues, and people form the surrounding detail. Any integration, extraction, or report should treat COMPLAINT_ID as the stable join key across the complaint subject area.