ONT Audit History – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™. Oracle EBS module: Order Management · all Order Management reports

Overview

Order Management audit history report showing changes to order headers, lines, sales credits, and price adjustments with old/new values, change reasons, and the user who made the change. Based on Oracle standard report OEXAUDHR_XML (Audit History Report).

Run this report in Excel in seconds: download Blitz Report™ free (your first 30 reports are free) or try it in the online demo.

Report Parameters

Operating Unit, History Date From, History Date To, Entity, Attribute, Order Number From, Order Number To, User Name, Responsibility

Oracle EBS Tables Used

oe_order_lines_all, oe_sales_credits, oe_price_adjustments, hr_all_organization_units_vl, oe_audit_attr_desc_v, mo_glob_org_access_tmp, dual

Report Categories

Enginatics

QP Customer Pricing Engine Request, AR Customers and Sites, ONT Orders and Lines 11i, ONT Orders and Lines, ONT Price Adjustments and Charges, ONT Blanket Sales Agreements, AR Autoinvoice Interface, AR Customer Credit Limits, INV Intercompany Invoice Reconciliation

Running This SQL Without Blitz Report

The SQL source can be run in any SQL client. Some Oracle EBS SQL reports in this library use functions from the utility package xxen_util – install it first. Blitz Report™ adds parameters, Excel output with pivots, scheduling and security on top.

Download & Import Options

Resource Link
Excel Example Output Example
Blitz Report™ XML Import ONT_Audit_History.xml
SQL Source ONT Audit History.sql
Full Report on Enginatics www.enginatics.com/reports/ont-audit-history/

Case Study & Technical Analysis: ONT Audit History

Executive Summary

This report is the Order Management audit history. It lists every recorded change to order lines, sales credits and price adjustments, with the entity and attribute that changed, the old and new values, the change reason and comments, and the user and responsibility that made the change. It is based on Oracle’s standard Audit History Report (OEXAUDHRXML). Order management supervisors, revenue assurance teams and auditors use it to answer questions such as who changed a price, when a requested date was moved, or why a line was cancelled. It can be run for an operating unit and a date range, or narrowed to a range of order numbers.

Business Challenge

The Solution

Technical Architecture (High Level)

Primary Tables

Logical Relationships

  1. OE_AUDIT_ATTR_DESC_V is joined to the operating unit on the organization identifier.
  2. The operating unit is restricted to those the user can access through MO_GLOB_ORG_ACCESS_TMP.
  3. For an audit row whose entity is an order line, the line is the entity number itself.
  4. For a sales credit, the order line is found from the sales credit record, and for a price adjustment from the price adjustment record.
  5. The order line’s line, shipment, option, component and service numbers are combined into one dotted line number.

Parameters & Filtering

Performance & Optimization

FAQ

Q: How do I see who changed the price of an order line? A: Run the report with the Entity set to the order line or price adjustment and the Attribute set to the price field, for the order number and date range in question. The User Name and Responsibility columns show who made the change.

Q: What does a dotted line number such as 1.1.2 mean? A: It is the line number, followed by the shipment, option and component or service numbers of the order line. Each part is shown only when it is present on the line.

Q: Can I see the reason for a change? A: Yes. The Reason and Comments columns show the reason and comments that were recorded with the change.

© Enginatics GmbH