Search Results cn_process_audits_all




Overview
Explore in AI Chat

Overview

The CN_PROCESS_AUDITS_ALL table is a core data object within the Oracle E-Business Suite Incentive Compensation (CN) module. It functions as a comprehensive execution log and audit trail for key compensation processes. Its primary role is to record detailed metadata about the initiation, execution, and status of batch operations such as compensation plan calculations, payment processing, statement generation, and notification runs. This table is critical for troubleshooting, performance analysis, and maintaining a historical record of all automated and manual processing events within the Incentive Compensation engine, supporting both operational and compliance needs across organizations (as indicated by the '_ALL' suffix and ORG_ID column).

Key Information Stored

The table stores metadata that characterizes each process execution instance. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships reveal its core structure. The primary key, PROCESS_AUDIT_ID, uniquely identifies each process execution record. The table supports hierarchical process logging through the PARENT_PROCESS_AUDIT_ID foreign key, which points to the parent record in the same table, allowing for nested or multi-step processes. Key foreign key columns include OBJECT_ID (linking to CN_OBJECTS_ALL, likely identifying the compensation object being processed), MODULE_ID (linking to CN_MODULES_ALL_B, identifying the functional module), and ORG_ID (identifying the operating unit). Other typical columns in such audit tables, though not explicitly listed, would include timestamps for start and end times, process status (e.g., 'RUNNING', 'COMPLETE', 'ERROR'), the initiating user ID, request ID, and parameters used for the run.

Common Use Cases and Queries

This table is primarily queried for process monitoring, debugging, and historical reporting. Common scenarios include identifying failed processes, analyzing process duration for performance tuning, and tracing the lineage of a specific calculation. A typical query would join to related tables to get descriptive information. For example, to find long-running compensation calculation processes for a specific module, one might use a pattern like:

  • SELECT cpa.PROCESS_AUDIT_ID, cpa.CREATION_DATE, cm.MODULE_NAME, cpa.STATUS FROM CN_PROCESS_AUDITS_ALL cpa JOIN CN_MODULES_ALL_B cm ON cpa.MODULE_ID = cm.MODULE_ID AND cpa.ORG_ID = cm.ORG_ID WHERE cm.MODULE_NAME LIKE '%CALCULATION%' AND cpa.CREATION_DATE > SYSDATE - 7 ORDER BY cpa.CREATION_DATE DESC;

Another critical use case is investigating a specific transaction batch or notification error by joining to the CN_TRX_BATCHES_ALL or CN_NOT_TRX_ALL tables via the PROCESS_AUDIT_ID.

Related Objects

Based on the documented foreign key relationships, CN_PROCESS_AUDITS_ALL has integral links to several key CN tables:

  • CN_PROCESS_AUDITS_ALL (Self-Referential): Via PARENT_PROCESS_AUDIT_ID to PROCESS_AUDIT_ID. This creates a hierarchy for sub-processes.
  • CN_OBJECTS_ALL: Via OBJECT_ID and ORG_ID. Links the process to the specific compensation object (e.g., a plan, formula, or rule).
  • CN_MODULES_ALL_B: Via MODULE_ID and ORG_ID. Identifies the functional module (e.g., 'Compensation Calculation', 'Payment Processing') that executed the process.
  • CN_PROCESS_AUDIT_LINES_ALL: Via PROCESS_AUDIT_ID. This child table holds detailed line-level log messages, errors, or results for the parent process audit record.
  • CN_TRX_BATCHES_ALL: Via PROCESS_AUDIT_ID. Associates the audit record with a specific batch of compensation transactions.
  • CN_NOT_TRX_ALL: Via NOTIFICATION_RUN_ID to PROCESS_AUDIT_ID. Links the process to a notification run.