Results for “audit_id”

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

Overview

CS_CTR_AUDIT is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores audit information for counters. Controllers in Oracle Service track the sequencing and consumption of numbered or counted business processes — service request numbers, task counters, and similar constructs — and CS_CTR_AUDIT records the audit trail generated when those counters are processed, adjusted, or consumed. The object is owned by the CS schema and is documented as VALID in the ETRM repository.

From a Data Vault modeling perspective, the documented foreign-key structure suggests a hub-leaning classification. The primary key AUDIT_ID is a surrogate identifier that does not carry business meaning, and the table holds descriptive attributes describing the action taken against a counter, while a dependent child table (CS_CTR_AUDIT_LINES) references it. In a Data Vault design, the parent table would typically be modeled as a hub for audit events, with the descriptive columns carried in a satellite, and CS_CTR_AUDIT_LINES modeled as a link or dependent satellite. This classification is a heuristic derived from the FK topology and should be treated as a modeling suggestion rather than a documented EBS design principle.

Key Information Stored

CS_CTR_AUDIT contains twelve documented columns. The most significant are:

• AUDIT_ID — The surrogate primary key, enforced by CS_CTR_AUDIT_PK. It uniquely identifies each counter audit record and is the column referenced by CS_CTR_AUDIT_LINES.AUDIT_ID. No alternative unique business key is documented for this table; the source-identifying columns below function as descriptive attributes rather than enforced unique indexes.
• SOURCE_CODE — Codes the source or subsystem from which the audited counter activity originated.
• SOURCE_ID — The identifier of the originating record or entity in that source system.
• SOURCE_OBJECT_VERSION_NUM — The version number of the source object at the time of the audit, useful for detecting concurrent modifications.
• ACTION_TYPE and ACTION — Classify and describe the operation performed against the counter (for example, generation, adjustment, or rollback) and the specific action taken.
• PROCESSING_TEXT — Free-form or diagnostic text captured during counter processing, frequently used for troubleshooting failed or partial counter updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS who-columns recording the last modification, the application user, and the login responsible.
• CREATION_DATE, CREATED_BY — Standard who-columns recording the initial insertion of the audit row.

Common Use Cases and Queries

CS_CTR_AUDIT supports audit and reconciliation reporting over counter activity in Oracle Service. Typical scenarios include tracing why a service request or task received an unexpected number, reviewing manual adjustments to counters, and reconstructing the sequence of counter operations for a given source object.

A common query pattern joins the parent audit record to its lines to see the full audit detail:

• SELECT a.audit_id, a.source_code, a.source_id, a.action_type, a.action, l.* FROM cs.cs_ctr_audit a, cs.cs_ctr_audit_lines l WHERE a.audit_id = l.audit_id AND a.source_id = :source_id;
• SELECT audit_id, action_type, action, processing_text, creation_date FROM cs.cs_ctr_audit WHERE source_code = :source_code AND creation_date >= :from_date ORDER BY creation_date DESC;
• SELECT audit_id, last_updated_by, last_update_date FROM cs.cs_ctr_audit WHERE source_object_version_num <> :expected_version;

Reporting use cases include daily counts of counter actions grouped by ACTION_TYPE, identification of rows with populated PROCESSING_TEXT for error analysis, and user-level auditing by CREATED_BY or LAST_UPDATED_BY.

Related Objects

The most significant objects related to CS_CTR_AUDIT are:

• CS_CTR_AUDIT_LINES — The primary dependent table; joined on CS_CTR_AUDIT_LINES.AUDIT_ID = CS_CTR_AUDIT.AUDIT_ID. Holds the line-level detail of each audit event.
• CS_CTR_AUDIT_PK — The primary key constraint on AUDIT_ID that enforces uniqueness of each audit record.
• Counter definition and control objects in the CS schema — Referenced indirectly through SOURCE_CODE and SOURCE_ID, which identify the counter source being audited.
• Standard EBS audit/security views — Reporting on CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN draws on FND_USER for user-name resolution.
• Service request and task tables in the CS schema — Consumers of counter values whose numbering is explained by the audit rows recorded here.

Because CS_CTR_AUDIT functions as the recognized parent in the documented FK relationship, direct writes should be avoided; audit rows are generated by the Service counter engine, and any reporting should be read-only.