My Oracle Support Banner

The Behavior When Processing Constraints Setup Are Changed Before Submitting Audit History Consolidator (Doc ID 2461295.1)

Last updated on MARCH 17, 2023

Applies to:

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


Audit History behaves like below:

  1. Enable the two Flexfields as per the following steps:
    Application: Order Management
    Title: Additional Line Attribute Information
    Description: Global Data Elements
    Segments: enable ATTRIBUTE16 and ATTRIBUTE18
    Enable Displayed enabled/Enabled flag.

  2. Then go to setup->Rules->Security->Processing Constraints
    Entity: Order Line
    Operation: Update
    Attribute: Attribute16
    User Action: Require History
    Enabled flag checked.

    Attribute: Attribute18
    User Action: Generate Version
    Enabled flag checked.

  3. Create a sales order, make sure it booked.
    Set Attribute 16 as value '1', then set Attribute 18 value as 'a'

  4. Login by using User A to Change Attribute 16 value of the sales order from '1' to '2'
  5. Login by using User B to change Attribute 18 value of the sales order from 'a' to 'b'.
  6. Again go to setup->Rules->Security->Processing Constraints, do the change as below(due to business requirement):
    Attribute: Attribute18
    User Action: Require History
    Enabled flag checked.

  7. Run Audit History Consolidator against this sales order.
  8. Go to view Audit History form
  9. Enter the order number, then do a search, the following information displayed:

    Old Value  New Value  User
    1          2          User A
    A          B          User A



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

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