Search Results get_extra_info

Overview

IBC_AUDIT_LOG_GRP is the private PL/SQL API that implements the Oracle Content Manager (OCM) Audit Log, or History, functionality within Oracle E-Business Suite. The package is owned by APPS and classified as a GRP (grouped) API, reflecting its role as a container of related audit logging routines rather than a single-purpose interface. Its header identifies it as the private API for OCM Audit Log handling, with selected methods exposed externally as Java APIs through the AuditLog class.

The package maintains a historical record of actions performed against OCM business entities. It defines constants identifying the auditable object types — content types (CTYPE), content items (CITEM), content item versions (CIVERSION), attribute bundles (ABUNDLE), associations (ASSOC), components (COMP), labels (LABEL), and directory nodes (DIRNODE) — as well as constants for the extra information segment types CONSTANT, LOOKUP, MESSAGE, and CS_LOOKUP (comma-separated lookups). These constants underpin the audit entries the package writes and reads. The default API version constant is defined as 1.0.

Key Procedures and Functions

• LOG_ACTION — Stores an audit log entry. Its documented parameters include an activity code, an object type, up to five object value columns carrying the primary key of the audited object, a parent value, the message application and message name referencing FND_MESSAGES, and extra information segments described by type and reference type. The procedure is the principal write path into the audit history.
• GET_AUDIT_MESSAGE — Retrieves the audit message associated with a logged action, resolving the stored message application and message name into usable message text for display. This function supports rendering of history entries.
• GET_EXTRA_INFO — Returns the extra information segments attached to an audit log entry. Because the segment type governs interpretation (constant text, a lookup value, a message, or a comma-separated list of lookups), this routine resolves the stored type and reference type into the appropriate descriptive value. It is the routine most directly associated with the search term "get_extra_info" and is used when the audit display must present contextual detail beyond the base message.

Tables Accessed

• IBC_AUDIT_LOGS — The primary audit history table. LOG_ACTION inserts records here, and the retrieval routines read from it.
• FND_MESSAGES — Source of the audit message text identified by application and message name; GET_AUDIT_MESSAGE resolves entries against it.
• FND_LOOKUP_VALUES — Used to translate LOOKUP and CS_LOOKUP extra information references into displayable lookup meanings.
• FND_USER — Provides the user identity associated with an audited action in history displays.
• IBC_CONTENT_ITEMS and IBC_CITEM_VERSIONS_B — Referenced to resolve content item and content item version identifiers recorded against audited actions, allowing history entries to be tied back to the affected OCM objects.

Usage Notes

As a private API, IBC_AUDIT_LOG_GRP is not intended for direct invocation by external custom code. It is called by the OCM application itself whenever an auditable action occurs, and its methods are surfaced to the middle tier through the AuditLog Java class. The package is referenced by two other packages within the OCM schema, which drive logging on behalf of their own operations.

In EBS 12.1.1 and 12.2.2, audit history is typically surfaced through the Oracle Content Manager administrative and content management user interfaces, where the Java layer invokes these PL/SQL routines to record actions and to render history. Custom integrations needing audit retrieval should prefer the supported Java APIs or query IBC_AUDIT_LOGS read-only, rather than calling package internals whose signatures are private and version-bound.