Search Results ibc_audit_logs




Overview
Explore in AI Chat

Overview

IBC_AUDIT_LOGS is a core auditing table within the IBC (Content Manager) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to store all actions performed on any OCM (Oracle Content Manager) object. As the central repository for content-management activity, it provides the forensic and troubleshooting substrate for tracking who changed what content item, when, and through which activity, application, or workflow message.

The table is owned by the IBC schema and is classified as VALID. Mined from its foreign key structure, the heuristic Data Vault classification is standalone, suggesting it functions neither as a pure hub, link, nor satellite but as a self-contained transactional log. Modelers should treat it as an audit fact table centered on a single surrogate primary key rather than as a normalized hub-and-satellite construct.

Key Information Stored

The table contains 39 documented columns. The most significant include:

Common Use Cases and Queries

Typical uses include auditing content changes for compliance, investigating unauthorized modifications, and reporting on OCM activity volumes by user or object type. A common query retrieves recent activity for a specific object:

  • SELECT audit_log_id, activity, user_id, time_stamp, object_type, description FROM ibc.ibc_audit_logs WHERE object_value1 = :p_object_id ORDER BY time_stamp DESC;
  • SELECT user_id, COUNT(*) FROM ibc.ibc_audit_logs WHERE time_stamp >= :p_from_date GROUP BY user_id;
  • SELECT a.audit_log_id, a.activity, f.security_group_name FROM ibc.ibc_audit_logs a, fnd_security_groups f WHERE a.security_group_id = f.security_group_id;

Reporting responsibilities frequently join USER_ID to FND_USER to resolve user names, and TIME_STAMP ranges are the standard predicate for date-bounded extracts. Because per-object values reside in OBJECT_VALUE1 through OBJECT_VALUE5, queries are usually written against a specific slot once the object convention for the relevant OCM object type is known.

Related Objects

  • FND_SECURITY_GROUPS — referenced by IBC_AUDIT_LOGS.SECURITY_GROUP_ID; joins resolve the security group owning each audit row.
  • IEU_UWQM_AUDIT_LOG — contains AUDIT_LOG_ID referencing IBC_AUDIT_LOGS, linking interaction/quality-management audit records back to the OCM audit trail.
  • FND_USER — commonly joined on USER_ID to resolve the acting user identity.
  • FND_APPLICATION — typically joined on APPLICATION_ID or MESSAGE_APPLICATION to attribute the audit event to a source application.
  • OCM content objects — the various IBC content tables identified dynamically by OBJECT_TYPE and OBJECT_VALUE1 through OBJECT_VALUE5, which the audit rows describe.

Together these relationships allow administrators to trace any OCM content action from triggering message through affected object to the user, date, and security context in which it occurred.