AUDIT TRAIL CONTAINS DUPLICATE ENTRIES (Doc ID 1553198.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
---------------
System Split of Order Line not Honoring Processing Constraint

We have a user defined processing constraint set to capture the ordered quantity history. When a user splits a line, we get the history record of the quantity change as expected. When the system splits the line, we get no history records. This is imperative for our business metrics to have a clear history of when records change.

EXPECTED BEHAVIOR
-----------------------
Expect that any change to the QTY will trigger the processing constraint.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Processing Constraint.
2. Enter sales order with lines.
3. Split line 2 manually - processing constraint records the change.
4. System split does not record the change.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot verify all history changes to order lines.

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