Search Results new_display_value

Overview

APPS.OE_AUDIT_ATTR_DESC_V is a seed data view registered in Oracle E-Business Suite under the FND Design Data identifier ONT.OE_AUDIT_ATTR_DESC_V. It belongs to the Order Management (ONT) product family and is owned by the APPS schema. The view exposes the audit trail of order and transaction entities in a decoded, presentation-ready form, pairing the raw internal identifiers of audit records with human-readable display names for entities, attributes, old values, and new values. Its purpose is to support the audit-history user interface and related reporting, where users must see the prior and revised values of an attribute rather than opaque internal codes. The presence of OLD_DISPLAY_VALUE and NEW_DISPLAY_VALUE, together with OLD_CONTEXT_VALUE and NEW_CONTEXT_VALUE, indicates the view renders both the attribute value change and its associated context value change. Oracle classifies this object as internal use only; it is not supported for direct customer access except through standard Oracle Applications programs, and it should be treated as a read-only reporting surface in 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over the following documented base objects and dependencies:

• OE_AUDIT_ATTR_HISTORY — the audit attribute history table that stores the raw audit rows, including previous and current values.
• OE_AUDIT_HISTORY_PVT — the audit history private package supplying decoding logic, such as translating stored values into display values.
• OE_PC_ENTITIES_V — a view supplying entity identifiers and their display names.
• OE_LOOKUPS — the order management lookup view used to resolve codes into their displayed meanings.
• FND_USER — supplies the user identifier and user name associated with each audit record.
• FND_RESPONSIBILITY_TL — supplies the translated responsibility name for the responsibility under which the change was made.

Because the view joins translated responsibility data and lookup-based decoding, it returns a fully attributed audit record without requiring the calling application to perform additional joins. The ETRM metadata records that OE_AUDIT_ATTR_DESC_V is not referenced by any other database object, so it functions as a terminal reporting view rather than as a component of a larger dependency chain.

Key Columns

• ENTITY_ID / ENTITY_DISPLAY_NAME — the transaction entity identifier and its decoded display name.
• ATTRIBUTE_ID / ATTRIBUTE_DISPLAY_NAME — the audited attribute and its descriptive name.
• OLD_DISPLAY_VALUE / NEW_DISPLAY_VALUE — the prior and revised attribute values as displayed to the user; these are the columns most commonly targeted by users searching on "old_display_value".
• OLD_CONTEXT_VALUE / NEW_CONTEXT_VALUE — the prior and revised context values associated with the attribute.
• HIST_CREATION_DATE — the timestamp when the audit record was created.
• ORDER_NUMBER / ENTITY_NUMBER / ORG_ID — order and entity identifiers plus the operating unit.
• REASON / HIST_COMMENTS — the reason code and free-text comments captured with the change.
• USER_ID / USER_NAME — the application user who performed the change.
• RESPONSIBILITY_ID / RESPONSIBILITY_NAME — the responsibility under which the change was made.

Common Use Cases and Queries

The view is typically queried to reconstruct who changed what, when, and under which responsibility. A common pattern is to retrieve all historical value changes for a given order:

• Change history for an order: SELECT ORDER_NUMBER, ATTRIBUTE_DISPLAY_NAME, OLD_DISPLAY_VALUE, NEW_DISPLAY_VALUE, HIST_CREATION_DATE, USER_NAME FROM APPS.OE_AUDIT_ATTR_DESC_V WHERE ORDER_NUMBER = :order_number ORDER BY HIST_CREATION_DATE;
• Filtering by user or date range: add predicates on USER_NAME, RESPONSIBILITY_NAME, or HIST_CREATION_DATE to isolate activity for audit reviews.
• Locating a specific attribute change: SELECT * FROM APPS.OE_AUDIT_ATTR_DESC_V WHERE ATTRIBUTE_DISPLAY_NAME = :attribute AND OLD_DISPLAY_VALUE IS NOT NULL;
• Entity-level reporting: group by ENTITY_DISPLAY_NAME and ATTRIBUTE_DISPLAY_NAME to summarize the volume of changes per entity.

All queries should be read-only and executed with the understanding that the object is an Oracle-internal view; direct modification is neither possible nor supported.