Search Results ghr_compl_claims




Overview
Explore in AI Chat

Overview

GHR_COMPL_CLAIMS is a table owned by the HR schema within the GHR — US Federal Human Resources product family of Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store claim information for a given complaint. In the federal HR context, a complaint (such as an equal employment opportunity or administrative grievance matter) may encompass one or more discrete claims, each of which carries its own incident date, procedural phase, source, and disposition trail. GHR_COMPL_CLAIMS is the container for that claim-level detail, operating as a child of the complaint header and as a parent to the bases and incidents that substantiate each claim.

From a heuristic Data Vault classification mined from the foreign key structure, this table is hub-leaning. That is a modeling suggestion rather than a documented property: the surrogate primary key COMPL_CLAIM_ID behaves as a durable business entity identifier, while several of its descriptive attributes (phase, acceptance flags, appeal indicators) are mutable and would more naturally be resolved into an associated satellite if the table were decomposed under Data Vault conventions. The table participates as a link point between the complaint header and two dependent detail tables.

Key Information Stored

The table contains sixteen documented columns. The most significant are listed below, with the surrogate identifier distinguished from business-key candidates.

  • COMPL_CLAIM_ID — the surrogate primary key, enforced by unique index GHR_COMPL_CLAIMS_PK. This is the single documented unique index and therefore the only business-key candidate identified in the metadata; no alternate unique key is recorded.
  • COMPLAINT_ID — foreign key to GHR_COMPLAINTS2, tying the claim to its governing complaint.
  • CLAIM — the substantive description or identifier of the claim itself.
  • INCIDENT_DATE — the date of the underlying incident giving rise to the claim.
  • PHASE — the current procedural phase of the claim within the complaint lifecycle.
  • MIXED_FLAG — indicates whether the claim is a mixed case, typically denoting the presence of both a federal-sector and a separate statutory basis.
  • CLAIM_SOURCE — the origin or channel through which the claim was raised.
  • AGENCY_ACCEPTANCE — the agency's acceptance determination for the claim.
  • AJ_ACCEPTANCE — the acceptance determination recorded at the administrative judge level.
  • AGENCY_APPEAL — the agency appeal status or outcome indicator.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS audit and who-column set, supporting accountability and change tracking.

Common Use Cases and Queries

Typical usage centers on complaint adjudication reporting, case aging, and federal EEO statistical extracts. A common pattern retrieves all claims for a complaint with supporting incidents and bases:

  • Listing claims by complaint: SELECT COMPL_CLAIM_ID, CLAIM, INCIDENT_DATE, PHASE FROM HR.GHR_COMPL_CLAIMS WHERE COMPLAINT_ID = :p_complaint_id ORDER BY INCIDENT_DATE;
  • Counting mixed claims by source: SELECT CLAIM_SOURCE, COUNT(*) FROM HR.GHR_COMPL_CLAIMS WHERE MIXED_FLAG = 'Y' GROUP BY CLAIM_SOURCE;
  • Aggregating claims against the complaint header: join on COMPLAINT_ID to GHR_COMPLAINTS2 for agency, filing date, and complainant context.
  • Detailing substantiating incidents and bases via GHR_COMPL_INCIDENTS and GHR_COMPL_BASES on COMPL_CLAIM_ID.
  • Aging and phase analysis using INCIDENT_DATE and PHASE against SYSDATE for workload and backlog reporting.

Because the table carries OBJECT_VERSION_NUMBER, direct DML should be avoided in favor of the supported GHR forms and APIs, which manage the version counter and audit columns.

Related Objects

  • GHR_COMPLAINTS2 — parent complaint header; joined on GHR_COMPL_CLAIMS.COMPLAINT_ID = GHR_COMPLAINTS2.COMPLAINT_ID.
  • GHR_COMPL_BASES — dependent detail holding the statutory or regulatory bases asserted; references GHR_COMPL_CLAIMS.COMPL_CLAIM_ID.
  • GHR_COMPL_INCIDENTS — dependent detail holding incident records; references GHR_COMPL_CLAIMS.COMPL_CLAIM_ID.
  • GHR_COMPL_CLAIMS_PK — the unique index enforcing the primary key on COMPL_CLAIM_ID.
  • GHR complaint entry forms and the associated GHR business APIs, which manipulate claims through the supported application layer rather than by direct table access.