Search Results ghr_compl_ca_details




Overview
Explore in AI Chat

Overview

GHR_COMPL_CA_DETAILS is a table owned by the HR schema in Oracle E-Business Suite, delivered as part of the GHR — US Federal Human Resources product family. It stores corrective action detail line information associated with a corrective action header record. In the context of Oracle EBS 12.1.1 and 12.2.2, this table functions as a subordinate (child) transactional store under the GHR_COMPL_CA_HEADERS table, capturing the individual line items that make up a corrective action, including monetary amounts, key dates, categorization, phase, and action/payment classifications. It supports the federal HR corrective action process, where each header represents a case and each detail row represents a discrete corrective action element or payment tied to that case.

Based on the foreign key structure mined from the ETRM metadata, this object is classified heuristically as satellite-leaning in Data Vault modeling terms. That is a modeling suggestion only: the table carries a surrogate primary key and a single foreign key to a parent header, with descriptive and measurable attributes (dates, amounts, categories) that are characteristic of satellite-style detail records. It is not modeled as a hub or link because it does not itself define a business entity key or a many-to-many relationship between independent hubs.

Key Information Stored

The documented physical schema contains 18 columns. The most operationally significant are:

  • COMPL_CA_DETAIL_ID — the surrogate primary key, backed by the unique index GHR_COMPL_CA_DETAILS_PK. This is the row-level identifier and is not itself a business key.
  • COMPL_CA_HEADER_ID — the foreign key referencing GHR_COMPL_CA_HEADERS. This is the join column that links each detail line to its parent corrective action header and is the primary business-key candidate for grouping rows.
  • AMOUNT — the monetary value associated with the corrective action detail, such as a payment or adjustment amount.
  • ORDER_DATE — the date the corrective action detail was ordered or directed.
  • DUE_DATE — the date by which the corrective action detail is expected to be completed.
  • REQUEST_DATE — the date the action was requested.
  • COMPLETE_DATE — the date the action was completed, used for closure and aging tracking.
  • CATEGORY and PHASE — classification attributes describing the type and current stage of the corrective action.
  • ACTION_TYPE and PAYMENT_TYPE — further classify the nature of the action and any associated payment.
  • DESCRIPTION — free-text narrative for the detail line.
  • OBJECT_VERSION_NUMBER — supports optimistic locking in the OAF/ADF middleware tier.

The remaining columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are standard WHO-column audit fields, consistent with other EBS transactional tables.

Common Use Cases and Queries

Typical reporting scenarios include listing all corrective action lines for a case, tracking overdue actions, summing amounts by category or payment type, and reconciling completed versus outstanding items. Because the table is satellite-leaning, most queries join to the header for case context.

SELECT d.COMPL_CA_DETAIL_ID, d.COMPL_CA_HEADER_ID, d.CATEGORY,
       d.PHASE, d.AMOUNT, d.DUE_DATE, d.COMPLETE_DATE
FROM   HR.GHR_COMPL_CA_DETAILS d
WHERE  d.COMPL_CA_HEADER_ID = :header_id;

A common aging query filters on DUE_DATE versus COMPLETE_DATE to identify actions past due. Aggregation by CATEGORY or PAYMENT_TYPE supports federal reporting requirements, and ORDER_DATE/REQUEST_DATE ranges drive period-based extracts. The OBJECT_VERSION_NUMBER should be included in update paths when used through the OAF framework.

Related Objects

The key related objects, derived from the documented FK metadata and the GHR corrective action module, include:

  • GHR_COMPL_CA_HEADERS — parent table, joined via GHR_COMPL_CA_DETAILS.COMPL_CA_HEADER_ID = GHR_COMPL_CA_HEADERS.COMPL_CA_HEADER_ID. This is the only documented foreign key relationship.
  • GHR_COMPL_CA_DETAILS_PK — the unique index enforcing the primary key on COMPL_CA_DETAIL_ID.
  • PER_ALL_PEOPLE_F and related person/assignment tables, reached indirectly through the header, for associating corrective actions with employees.
  • GHR corrective action view and OAF entity objects that expose the header-detail hierarchy to the US Federal HR user interface.

Because the ETRM extract documents a single foreign key, the authoritative relationship is the header-to-detail association; other linkages should be validated against the live 12.1.1 or 12.2.2 data dictionary before relying on them.