Search Results per_cagr_log




Overview
Explore in AI Chat

Overview

PER_CAGR_LOG is a Human Resources (PER) module table in the Oracle E-Business Suite, owned by the HR schema. It serves as the audit and activity log for the Career and Grade Request (CAGR) framework — the self-service process by which employees raise requests for career progression, grade changes, or related HR actions. Each row captures a discrete log entry or message associated with a specific CAGR request, providing a chronological trace of what the Career and Grade Request engine recorded as the request flowed through its lifecycle.

The table is standalone rather than embedded in a keyed parent, meaning its Grain is event/message-level: one row per logged entry rather than one row per request. From a Data Vault modeling perspective, the ETRM metadata classifies PER_CAGR_LOG as standalone. In practice this makes it a natural satellite candidate attached to a CAGR request hub, since it stores descriptive, time-stamped attributes about the request rather than defining new business entities or resolving many-to-many relationships. Its single foreign key to PER_CAGR_REQUESTS reinforces this — it is a dependent detail table, not an independent hub.

Three of the nine columns are standard EBS WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) plus audit columns (CREATED_BY, CREATION_DATE), so the table follows the standard EBS audit convention.

Key Information Stored

The most significant columns documented for the 12.2.2 schema are:

  • LOG_ID — Surrogate primary key; uniquely identifies each log entry (PER_CAGR_LOG_PK).
  • CAGR_REQUEST_ID — Foreign key to PER_CAGR_REQUESTS; ties the row to its parent request and is the principal join column.
  • TEXT — Free-form message/description captured for the log entry; the primary human-readable payload.
  • PRIORITY — Severity or ordering indicator distinguishing routine informational entries from higher-priority messages.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording the last modification and the session responsible for it.
  • CREATED_BY, CREATION_DATE — Standard creation audit columns identifying the originating user and timestamp.

LOG_ID is the surrogate key. The only unique index documented is PER_CAGR_LOG_PK on LOG_ID, meaning no separate business-key candidate is exposed; the business linkage is expressed exclusively through CAGR_REQUEST_ID.

Common Use Cases and Queries

Typical usage centers on troubleshooting and auditing Career and Grade Request processing. Common patterns:

  • Retrieving all log entries for a given request:
    SELECT LOG_ID, TEXT, PRIORITY, CREATION_DATE, CREATED_BY FROM HR.PER_CAGR_LOG WHERE CAGR_REQUEST_ID = :request_id ORDER BY CREATION_DATE;
  • Filtering to high-priority messages for exception reporting:
    SELECT * FROM HR.PER_CAGR_LOG WHERE PRIORITY = :p AND CREATION_DATE > :since;
  • Joining to the parent request to enrich the trace with request attributes.
  • Diagnostic tracing of failed or stalled career/grade requests, using TEXT and timestamps to reconstruct sequence.

Because it is not a transactional driving table, it is best treated as an audit trail — queries are read-only, ordered by creation time, and filtered by CAGR_REQUEST_ID.

Related Objects

The dominant relationship is the foreign key to its parent:

  • PER_CAGR_REQUESTS — Parent table; joined on PER_CAGR_LOG.CAGR_REQUEST_ID = PER_CAGR_REQUESTS.CAGR_REQUEST_ID.
  • PER_CAGR_REQUEST_PK — Primary key of the parent, underpinning the FK integrity.
  • PER_CAGR_LOG_PK — This table's own primary key index.
  • Other PER (Human Resources) Career and Grade Request objects and the public CAGR APIs that write log entries are functionally associated, though no additional foreign keys are documented.

No further FK dependencies are recorded, confirming the standalone classification.