Search Results user_item_description




Overview
Explore in AI Chat

Overview

The OE_ORDER_LINES_AUDIT_V view is a reporting and integration construct in the Oracle E-Business Suite Order Management (ONT) module, owned by the APPS schema. It exposes the auditable history of order lines by combining header context, line-level history records, and reason-code descriptions into a single denormalized result set. In Oracle EBS 12.1.1 and 12.2.2 the object is registered as a VALID view, meaning it is a supported component of the data dictionary rather than an ad hoc user object.

Its primary role is to support audit trails, historical change analysis, and downstream reporting. Because order lines are frequently modified after entry—pricing corrections, quantity adjustments, schedule changes, and cancellations—the base transaction tables retain only the current state. OE_ORDER_LINES_AUDIT_V surfaces the versioned history so that users and integrators can reconstruct what changed, when, by whom, and under which responsibility. It is commonly consumed by Order Management inquiry screens, custom reports, and extract programs that feed data warehouses.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies three referenced base objects, all accessed through APPS synonyms:

Aliases in the view text (OLH for the history/lines source, OH for headers) confirm the join strategy: header rows are joined to their line history rows, and reason codes are resolved to user-facing descriptions. Additional referenced tables appear in the full view SQL, but the three objects above are the documented dependencies.

Key Columns

The view exposes a broad set of columns, of which the following are most significant for audit and reporting work:

Common Use Cases and Queries

Typical scenarios include tracing the change history of a single order line, reporting all price or quantity revisions within a date range, and feeding audit extracts to external systems. A representative query follows:

  • SELECT order_number, line_number, hist_type_code, hist_comments, hist_created_by, hist_creation_date FROM oe_order_lines_audit_v WHERE order_number = :p_order_number ORDER BY hist_creation_date;
  • SELECT h.order_number, h.line_number, h.inventory_item_id, msi.description, h.unit_selling_price, h.hist_creation_date FROM oe_order_lines_audit_v h, mtl_system_items_vl msi WHERE h.inventory_item_id = msi.inventory_item_id AND h.hist_creation_date >= :p_from_date;
  • SELECT hist_type_code, COUNT(*) FROM oe_order_lines_audit_v WHERE hist_creation_date BETWEEN :p_start AND :p_end GROUP BY hist_type_code;

Bind variables should be used for all predicates, and queries against history tables should be filtered by date or key to avoid full scans. Because the view is not a table, no DML is permitted; any corrective action must target the underlying history and line tables through supported APIs.