Search Results ibc_audit_logs_u1




Overview
Explore in AI Chat

Overview

IBC.IBC_AUDIT_LOGS is a transactional audit table in the Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 environment, owned by the IBC schema. The table stores a record of every action performed on an OCM (Object Configuration Manager / Object Component Manager) object. Each row captures the activity name, the user who performed the activity, the timestamp of the event, the OCM object type, and up to five identifying object values that pinpoint the object against which the activity was executed. The record therefore functions as a central activity ledger for OCM object lifecycle events, providing a traceable history of who did what, when, and against which object.

The table resides in the APPS_TS_TX_DATA tablespace. From a Data Vault modeling heuristic, the metadata classifies IBC_AUDIT_LOGS as standalone, which suggests it is best modeled as a satellite-style, standalone event table rather than as a hub or link. It carries its own surrogate key, business attributes, and standard WHO columns, but does not participate in a hub/link relationship structure within the data vault heuristic.

Key Information Stored

The primary surrogate key is AUDIT_LOG_ID (NUMBER), which uniquely identifies each audit entry. The unique index IBC_AUDIT_LOGS_U1 — the object referenced in the user query — enforces uniqueness on AUDIT_LOG_ID and is the canonical business-key candidate documented for this table. A secondary non-unique index, IBC_AUDIT_LOGS_N01, covers OBJECT_VALUE1 and OBJECT_VALUE2 to support lookup by object identifiers.

The most significant columns include:

The documented schema lists 39 columns in total for release 12.2.2; the additional EXTRA_INFO1–5, OBJECT_STATUS, MESSAGE_NAME, MESSAGE_APPLICATION, and INTERNAL_FLAG columns extend the audit payload for message and reference-type metadata.

Common Use Cases and Queries

Typical usage centers on auditing, troubleshooting OCM object changes, and compliance reporting. A frequent query pattern joins audit entries to users and filters by activity or time window:

SELECT a.AUDIT_LOG_ID, a.ACTIVITY, a.USER_ID, a.TIME_STAMP, a.OBJECT_TYPE, a.OBJECT_VALUE1, a.OBJECT_VALUE2 FROM IBC.IBC_AUDIT_LOGS a WHERE a.OBJECT_TYPE = :p_object_type AND a.TIME_STAMP >= :p_from_date ORDER BY a.TIME_STAMP DESC;

Because IBC_AUDIT_LOGS_U1 uniquely indexes AUDIT_LOG_ID, single-row retrieval by that key is efficient. Lookups by object identity benefit from IBC_AUDIT_LOGS_N01 on OBJECT_VALUE1 and OBJECT_VALUE2. Reporting scenarios include reconstructing the change history of a specific OCM object, identifying which user performed a given activity, and producing audit trails for regulatory review. Joins to FND_USER on USER_ID = CREATED_BY/USER_ID, and to FND_SECURITY_GROUPS on SECURITY_GROUP_ID, are common.

Related Objects

The following objects are most significant in relation to IBC_AUDIT_LOGS:

  • IBC.IBC_AUDIT_LOGS_U1 — unique index on AUDIT_LOG_ID; the business-key candidate referenced by the user query.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for data segregation.
  • FND_USER — implied user reference for USER_ID, CREATED_BY, and LAST_UPDATED_BY.
  • FND_LOGINS — implied login reference for LAST_UPDATE_LOGIN.
  • IEU_UWQM_AUDIT_LOG — a downstream table whose AUDIT_LOG_ID foreign key references IBC_AUDIT_LOGS, linking quality-management audit data back to these entries.

Together these relationships establish IBC_AUDIT_LOGS as a referenced audit hub for OCM activity within the EBS IBC schema.