Search Results object_status

Overview

IBC_AUDIT_LOGS_V is a reporting view owned by the APPS schema within the IBC - Content Manager product in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the audit trail that the Content Manager maintains for content and repository activity, presenting each audited event as a single row enriched with readable descriptions and supplementary contextual data. Because the view is defined over a base audit table and a PL/SQL package rather than being materialized, it always reflects the current state of the underlying audit log and requires no refresh or concurrent program to stay synchronized.

The view plays a dual role in Oracle EBS. For reporting and integration, it provides a stable, denormalized interface that external tools can query without joining to package functions directly. Internally, the descriptive columns are populated by calling functions in the IBC_AUDIT_LOG_GRP package at query time, so a SELECT against the view effectively triggers PL/SQL execution per row. This design keeps the base table lean while still returning human-readable audit information to consumers.

Underlying Base Objects

The view is defined over two documented base objects:

• IBC_AUDIT_LOGS (SYNONYM) — the synonym resolving to the audit log table that stores one row per audited event, supplying every physical column in the view.
• IBC_AUDIT_LOG_GRP (PACKAGE) — the package whose functions generate the derived columns AUDIT_MESSAGE, EXTRA_INFO1 through EXTRA_INFO5.

The physical columns are taken directly from the base audit table with a simple column list from IBC_AUDIT_LOGS. The last six columns are computed expressions: GET_AUDIT_MESSAGE(AUDIT_LOG_ID) returns a formatted narrative for the event, while GET_EXTRA_INFO(AUDIT_LOG_ID, n) returns up to five supplemental detail strings. Referencing the view therefore mixes a set-based table scan with row-by-row function evaluation, which is the principal performance consideration when querying large audit ranges.

Key Columns

• AUDIT_LOG_ID — primary identifier for the audit row; also the argument passed to the package functions to derive message and extra info.
• ACTIVITY — the audited action, such as a create, update, delete, or content operation.
• USER_ID — the user who performed the activity; resolve to a name via FND_USER.
• TIME_STAMP — the date and time the event was recorded.
• OBJECT_TYPE — the category of object affected, used to filter audit records by entity.
• PARENT_VALUE — the identifier of the parent or owning object, useful for correlating related audit entries.
• OBJECT_VALUE1 through OBJECT_VALUE5 — up to five object-specific values captured at audit time.
• DESCRIPTION — stored descriptive text for the record.
• INTERNAL_FLAG — the column the user searched for; a flag distinguishing internal system-generated entries from user-facing activity, allowing reports to suppress internal noise.
• APPLICATION_ID — the Oracle EBS application owning the event; join to FND_APPLICATION for the application name.
• CREATION_DATE — row creation date, typically aligned with TIME_STAMP.
• OBJECT_STATUS — status of the audited object at the time of the event.
• AUDIT_MESSAGE — derived narrative produced by GET_AUDIT_MESSAGE.
• EXTRA_INFO1 through EXTRA_INFO5 — derived supplemental details produced by GET_EXTRA_INFO.

Common Use Cases and Queries

Typical uses include content audit reporting, troubleshooting who changed an object and when, and extracting audit extracts for external compliance systems. Because INTERNAL_FLAG separates internal from user activity, it appears in most production filters.

Recent user activity for review:

• SELECT AUDIT_LOG_ID, ACTIVITY, USER_ID, TIME_STAMP, OBJECT_TYPE, AUDIT_MESSAGE FROM APPS.IBC_AUDIT_LOGS_V WHERE INTERNAL_FLAG = 'N' AND TIME_STAMP >= SYSDATE - 7 ORDER BY TIME_STAMP DESC;

History for a specific object, resolved to user names:

• SELECT a.TIME_STAMP, f.USER_NAME, a.ACTIVITY, a.AUDIT_MESSAGE, a.EXTRA_INFO1 FROM APPS.IBC_AUDIT_LOGS_V a, APPS.FND_USER f WHERE a.USER_ID = f.USER_ID AND a.OBJECT_TYPE = :object_type AND a.PARENT_VALUE = :parent_value ORDER BY a.TIME_STAMP;

Count internal versus user events by application:

• SELECT a.APPLICATION_ID, fa.APPLICATION_SHORT_NAME, a.INTERNAL_FLAG, COUNT(*) FROM APPS.IBC_AUDIT_LOGS_V a, APPS.FND_APPLICATION fa WHERE a.APPLICATION_ID = fa.APPLICATION_ID GROUP BY a.APPLICATION_ID, fa.APPLICATION_SHORT_NAME, a.INTERNAL_FLAG;

Restrict earliest binding and avoid unbounded full scans, since each returned row invokes the IBC_AUDIT_LOG_GRP functions.