Audit History Incorrect/missing Data (Doc ID 1982145.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

On : 12.1.3 version, Transaction Control

ACTUAL BEHAVIOR
---------------
You enabled Require Reason, History and Raise event on update operation for
few attributes at line level.
1) warehouse
2) schedule ship date
3) promise date
4) order qty

You are finding the below issues with audit trail

For warehouse changes
1) You could see data is captured in OE_ORDER_LINES_HISTORY table but could
not find data in OE_AUDIT_ATTR_HISTORY or OE_AUDIT_ATTR_DESC_V even after
running Audit history consolidator program.
2) Order qty was changed with a specific reason code, saved the record by
user A. User B updated warehouse and gave a separate reason code for
warehouse change. Ran the audit history consolidator. Here audit trail was
captured. Order qty change has the correct audit trail, but warehouse audit
trail is showing the order qty 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

EXPECTED BEHAVIOR
-----------------------
Expect correct audit history data

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1) You could see data is captured in OE_ORDER_LINES_HISTORY table but could
not find data in OE_AUDIT_ATTR_HISTORY or OE_AUDIT_ATTR_DESC_V even after
running Audit history consolidator program.
2) Order qty was changed with a specific reason code, saved the record by
user A. User B updated warehouse and gave a separate reason code for
warehouse change. Ran the audit history consolidator. Here audit trail was
captured. Order qty change has the correct audit trail, but warehouse audit
trail is showing the order qty change reason code and comments and showing
User A as the user name who made the change.


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see correct audit history data.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms