Search Results oe_audit_attr_desc_v




Overview
Explore in AI Chat

Overview

The OE_AUDIT_ATTR_DESC_V view is a reporting and integration object in the Oracle E-Business Suite Order Management (ONT) module. It is owned by the APPS schema and is validated in both 12.1.1 and 12.2.2 environments. The view presents decoded, human-readable audit history for order management entities by joining the raw audit attribute history table to descriptive lookups and to the private package OE_AUDIT_HISTORY_PVT. Rather than exposing internal attribute IDs, coded values, and context values directly, the view resolves these into display names and translated meanings for each audit record.

This view is significant because it forms the reporting layer over the audit trail generated by Order Management. Each row represents a single audited attribute change on an entity such as an order or a return, capturing the old and new values, the responsible user, responsibility, organization, timestamp, and any change comments. The presence of the CANCEL_CODE lookup join is directly relevant to users searching on "cancel_code": the view decodes the reason code associated with an audited change by joining OE_LOOKUPS on lookup type 'CANCEL_CODE'. This allows cancellation reasons recorded during audit to appear as descriptive meanings rather than raw codes.

Underlying Base Objects

The view is defined over several documented base objects. The primary source is OE_AUDIT_ATTR_HISTORY (referenced through a synonym), which supplies the entity, attribute, old and new attribute values, context values, history creation date, order and entity numbers, organization, reason code, change comments, and the user and responsibility identifiers. Two decode functions from the OE_AUDIT_HISTORY_PVT package are invoked: GET_DISPLAY_NAME resolves the attribute display name from the attribute ID and context values, while ID_TO_VALUE translates stored old and new attribute values into their display equivalents using the attribute ID, value, context, and organization.

Three descriptive objects enrich the output. FND_USER supplies the user name for USER_ID, and FND_RESPONSIBILITY_TL supplies the responsibility name for RESPONSIBILITY_ID, restricted by the session language via USERENV('LANG'). OE_PC_ENTITIES_V provides the entity display name. OE_LOOKUPS is outer-joined on lookup type 'CANCEL_CODE' with the lookup code equal to the audit reason code; the outer join ensures audit rows are retained even when no matching cancel code exists. The result is a fully decoded, presentation-ready audit trail.

Key Columns

Common Use Cases and Queries

Typical uses include audit reporting on order and return modifications, tracking cancellation reasons via the CANCEL_CODE lookup, and feeding audit data into downstream reporting or integration layers.

SELECT ORDER_NUMBER, ENTITY_NUMBER, ATTRIBUTE_DISPLAY_NAME,
       OLD_DISPLAY_VALUE, NEW_DISPLAY_VALUE, REASON,
       USER_NAME, HIST_CREATION_DATE
FROM   APPS.OE_AUDIT_ATTR_DESC_V
WHERE  ORDER_NUMBER = :order_number
ORDER  BY HIST_CREATION_DATE;

To isolate cancellation events, filter on rows where a CANCEL_CODE meaning is present:

SELECT ORDER_NUMBER, REASON, USER_NAME, HIST_CREATION_DATE
FROM   APPS.OE_AUDIT_ATTR_DESC_V
WHERE  REASON IS NOT NULL
AND    TRUNC(HIST_CREATION_DATE) BETWEEN :start_date AND :end_date;

Because the view already resolves names, values, and lookup meanings, it removes the need to replicate the decode logic in custom reporting SQL.