My Oracle Support Banner

Audit History Not Getting Consolidated for Require Reason, History and Raise Integration Event Processing Constraint (Doc ID 1519881.1)

Last updated on APRIL 29, 2018

Applies to:

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


On : 12.1.3 version, Transaction Control


Audit history was not getting consolidated for the require reason, history and raise Integration Event Processing Constraint. Requirement is to capture reason as well as the history and raise integration event.

Steps to reproduce:

  1. Log into OM Responsibility.
  2. Navigate to Setup> rules> Security> Processing constraints.
  3. Create a “Require Reason, History and Raise Integration Event” processing constraint on update of Promise Date & Schedule Ship Date attributes on order line, with only one validation template for the order line is Booked.
  4. Set the System Parameter for all OU’s: Audit Trail = Enable when Order is Booked
  5. Update an order line which is Booked. Update Schedule Ship Date or Promise Date, on saving, the system will prompt you to enter the reason for change, as required by the processing constraint. After entering the reason the transaction is saved.
  6. Run ‘Audit History Consolidator’ concurrent request with the order number as parameter.
  7. Open the View Audit History form and query the order in question. Go to the lines tab and you can view the history in detail for changes on Schedule Ship Date or Promise Date. Find no data populated in the Audit History form.



To view full details, 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 a vibrant support community of peers and Oracle experts.