ID

How to Audit Changes to Orders Using Audit History [ID 209473.1]

goal: How to Audit Changes to Orders using Audit History

fact: Oracle Order Management 11.5.8

fact: OEXAUDHR - Audit History Report

fact: OEXAUGEN - Audit History Consolidator

fact: OEXPCFWK - Processing Constraints

fact: OEXPCFWK - Organization Parameters

fix:
The following example illustrates how to audit when a change is made
to the Payment Terms of an order that is booked with a reason as to
why it was changed.
The steps to initiate Audit History are
1.
2.

3.
4.

5.
6.
7.

8.

To turn audit history on at the site level, navigate to Order Management> Setup > Parameters
Change Audit Trail from Disable. There are two choices:
Enable When Order is Entered:This will initiate auditing when a change
is made to a specified field after the order has been saved
Enable When Order is Booked: This will initiate auditing when a change
is made to a specified field after the order has been booked
In this example, select "Enable When Order is Booked.
To identify a specified field when changed that will be audited,
navigate to Order Management > Setup > Rules > Security >
Processing Constraints and query up one of the following entities:
Order Header
Order Line
Order Sales Credit
Order Price Adjustment
Line Sales Credit
Line Price Adjustment
In this example, select entity type of "Order Header"
Position your cursor on the field to be audited in the constraints
block and click the plus icon in the toolbar. This will add a new
row where information can be entered.
In this example, enter the following:
Operation: Update
Attribute: Payment Term
User Action: Requires Reason and history
There are two choices. If "Requires Reason and history is selected

when the field is changed, a reason window will always appear and
a reason with optional comments must be entered. History will be
captured. If "Requires History" is selected, a reason window will
not appear when making a change and history will be captured.
There is always the flexibility of entering a reason by navigating
to Tools > Change Reason.
9. Now change to the Conditions tab in the form and enter the
following:
Scope: All
Validation entity: Order Header
Record set: Order
Validation template: Booked
10. Navigate to the applicable to tab. The audit can be associated with a
specific responsibility.
11. In this example, select "All Responsibilities"
12. Launch the program to create the necessary source for the new
constraint by navigating to Order Management > Setup > Rules >
Security > Processing Constraints and selecting "Generate Constraint
Validation Packages". This will launch a concurrent program with
a request id.
13. It is now time to create and book the order to test this functionality.
Navigate to Order Management > Orders,Returns > Sales Orders.
Enter a customer number and fields will default in based upon
the defined defaulting rules and transaction type.
14. Change to Line tab and enter an item.
15. Save the order. It will be in an Entered state.
16. Change to the Other tab and make a change to the payment terms.
There will be no prompt for a reason and no history will be
captured because our Order Management > Setup > Parameters >
Audit Trail is set for Auditing when Booking.
17. Book the Order.
18. Change to the Other tab and make a change to the payment terms.
A reason window will appear. Select a reason and enter optional
comments.
19. In order to obtain data in the Audit History Report it is necessary
to run on a regularly scheduled basis a consolidation program
that will extract the audit information and add it to a history
file.
20. Navigate to Order Management > Reports,Request > Run Requests and
select Audit History Consolidator. Data can be extracted based on
History Date From and To, Order Number From and To, or
Changes in last N days.
21. Enter 1 in the Changes in last N days.
22. To view the data either an audit report can be run or online query can be
performed.
Navig.
ate to
Order Management > Reports,Requests > Reports and select Audit
History.
23. Report can be created based upon History Date From and To, Order Number
From and To, Entity Name (in this example we set up the processing
constraint using entity type of Order Header), Attribute (in this
example auditing is being performed on payment terms), User, and
Responsibility.
24. To view history online,
navigate to Order Management > Orders, Returns > View Audit History
and select the data you want to view..