Results for “per_cagr_log_pk”

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

Overview

HR.PER_CAGR_LOG is a transactional logging table within the Oracle E-Business Suite Human Resources (HR) schema, associated with the FND Design Data object PER.PER_CAGR_LOG. The table resides in the APPS_TS_TX_DATA tablespace and holds status, audit, and diagnostic messages generated during the execution of Concurrent Assignment Grade/Requisition (CAGR) processes. Each record captures a single log entry tied to a parent CAGR request, with a text message, a priority level, and full standard "Who" audit columns.

The object is documented as VALID in ETRM for both 12.1.1 and 12.2.2. Oracle classifies it as Internal Use Only — access is supported only through standard Oracle Applications programs, not direct SQL. From a heuristic Data Vault modeling perspective, PER_CAGR_LOG is best classified as a satellite attached to the CAGR request hub: it carries descriptive, timestamped, and non-volatile diagnostic attributes keyed to a parent business entity rather than acting as an independent hub or a many-to-many link.

Key Information Stored

• LOG_ID — Surrogate primary key, NUMBER(15), enforced by the unique index PER_CAGR_LOG_PK. No separate business-key candidate exists beyond this surrogate.
• CAGR_REQUEST_ID — Foreign key to HR.PER_CAGR_REQUESTS, identifying the CAGR run to which the log entry belongs. This is the principal join column.
• TEXT — VARCHAR2(2000), the human-readable log message describing an event, error, or progress note.
• PRIORITY — NUMBER(11), indicating the severity or routing priority of the log entry, useful for filtering errors versus informational messages.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording the latest modification timestamp, user, and login session.
• CREATED_BY, CREATION_DATE — Standard audit columns capturing row insertion context.

A total of nine columns are documented. Because the only unique index is the LOG_ID surrogate, no natural business key is exposed at the schema level; the effective business relationship is expressed through CAGR_REQUEST_ID.

Common Use Cases and Queries

Typical usage centers on troubleshooting and monitoring CAGR processing. Support engineers and HR administrators query the table to retrieve the message trail for a specific request. A representative pattern:

• Retrieve all log rows for a request, newest first: SELECT log_id, text, priority, creation_date FROM hr.per_cagr_log WHERE cagr_request_id = :request_id ORDER BY creation_date DESC;
• Isolate high-priority or error entries: SELECT * FROM hr.per_cagr_log WHERE priority >= :threshold;
• Audit volume per request: SELECT cagr_request_id, COUNT(*) FROM hr.per_cagr_log GROUP BY cagr_request_id;
• Track user activity via the CREATED_BY and LAST_UPDATED_BY audit columns.

Reporting use cases include error-rate dashboards, SLA monitoring of long-running CAGR requests, and post-run diagnostics. Direct access should be avoided in production integrations; standard Oracle Applications programs are the supported access path.

Related Objects

• HR.PER_CAGR_REQUESTS — Parent entity. Joined via PER_CAGR_LOG.CAGR_REQUEST_ID = PER_CAGR_REQUESTS.CAGR_REQUEST_ID.
• HR.PER_CAGR_LOG# — The underlying base table object referenced by the editioning/synonym view HR.PER_CAGR_LOG in an EBR-enabled schema.

The documented dependency set is limited: PER_CAGR_LOG does not reference any database object other than through the CAGR_REQUEST_ID foreign key, and the only downstream reference recorded is the base object PER_CAGR_LOG#. Consequently, joins and lookups should be driven from the CAGR_REQUESTS side, and no additional documented dependents extend beyond that chain.