My Oracle Support Banner

Incorrect and/or Missing Data in the OE_AUDIT_ATTR_HISTORY Table (Doc ID 1982145.1)

Last updated on SEPTEMBER 30, 2024

Applies to:

Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Have enabled Require Reason, History and Raise event on update operation for  the following attributes at line level:

1) warehouse
2) schedule ship date
3) promise date
4) order quantity

Finding the below issues with audit history.
For warehouse changes:

1) The data is captured in OE_ORDER_LINES_HISTORY table, but could not find data in the OE_AUDIT_ATTR_HISTORY or OE_AUDIT_ATTR_DESC_V  tables even after
running Audit history consolidator program.

2) Order quantity was changed with a specific reason code and was saved by user A. User B updated the warehouse and gave a separate reason code for the
warehouse change.  The Audit history consolidator program was ran and audit trail was captured.  The order quantity change has the correct audit trail, but the
warehouse audit trail is showing the order quantity change reason code and comments and showing User A as the user name who made the change.

Audit trail system parameter: Enable when Order is Entered

The expectation is the audit history data reflect correctly.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.