Search Results oe_order_header_history




Overview
Explore in AI Chat

Overview

The OE_ORDER_HEADER_HISTORY table is a core data object within the Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically for versions 12.1.1 and 12.2.2. Its primary function is to serve as an audit trail, systematically storing a historical record of changes made to critical attributes of sales order headers. This table is fundamental for maintaining data integrity and providing a traceable log of modifications, which is essential for compliance, troubleshooting, and understanding the evolution of an order throughout its lifecycle. Unlike the main transaction table (OE_ORDER_HEADERS_ALL), which holds the current state of an order header, this history table captures discrete snapshots of changed data, enabling users to reconstruct the state of an order at any point in the past.

Key Information Stored

The table's structure is designed to capture the before-and-after state of modified attributes. While the provided metadata does not list all columns, the foreign key relationships indicate the types of critical data tracked. Key columns typically include a reference to the parent order header (HEADER_ID), the specific column or attribute that was changed (COLUMN_NAME), the original value (OLD_VALUE), the new value (NEW_VALUE), and metadata about the change such as the creation date (CREATION_DATE) and who made the change (CREATED_BY). Crucially, the foreign keys reveal that the table tracks historical changes to customer and contact assignments, including the Sold-To, Ship-To, Invoice-To, and Deliver-To contacts and sites, as well as end-customer and minisite information.

Common Use Cases and Queries

The primary use case is auditing and reporting on order header modifications. This is vital for customer service to explain changes to an order, for finance to audit pricing or customer terms updates, and for system administrators to diagnose data issues. A common query pattern involves joining to OE_ORDER_HEADERS_ALL to retrieve current order details alongside their change history. For example, to find all historical changes to the Sold-To customer for a specific order, one might use a query such as: SELECT oh.order_number, hh.column_name, hh.old_value, hh.new_value, hh.creation_date FROM oe_order_header_history hh, oe_order_headers_all oh WHERE hh.header_id = oh.header_id AND oh.order_number = '&order_num' AND hh.column_name LIKE '%SOLD_TO%' ORDER BY hh.creation_date;. Another frequent scenario is generating a comprehensive audit report for all changes within a specific date range.

Related Objects

The OE_ORDER_HEADER_HISTORY table maintains direct foreign key relationships with several foundational Trading Community Architecture (TCA) and Order Management tables, as documented in the metadata. These relationships are central to understanding the data it audits:

The table's primary parent is the OE_ORDER_HEADERS_ALL table, linked via the HEADER_ID column, from which the historical snapshots are derived.