Search Results oe_order_lines_history




Overview

The OE_ORDER_LINES_HISTORY table is a critical audit and tracking entity within the Oracle E-Business Suite (EBS) Order Management (ONT) module. Its primary function is to serve as a historical log, capturing all modifications made to the attributes of sales order lines over time. This table is fundamental for maintaining a complete audit trail, enabling users to reconstruct the state of an order line at any point in its lifecycle. It supports compliance, troubleshooting, and analytical reporting by providing a persistent record of changes that complements the current, active data stored in the OE_ORDER_LINES_ALL table.

Key Information Stored

While the provided metadata does not list specific columns, the table's structure is designed to store both the changed data and contextual metadata for each modification. Typically, such history tables contain a set of columns mirroring the tracked attributes from the source table (OE_ORDER_LINES_ALL), along with standard audit columns. Key data points stored include the LINE_ID (foreign key to the original order line), the old and new values for the altered field, the date and time of the change (CREATION_DATE), and the identifier of the user or process that initiated the modification (CREATED_BY). The foreign key relationships documented, such as END_CUSTOMER_CONTACT_ID and SHIP_TO_CONTACT_ID, indicate that changes to critical customer and site assignment attributes are meticulously logged.

Common Use Cases and Queries

The primary use case is auditing order line modifications for compliance or root-cause analysis. A common query involves retrieving the change history for a specific order line to understand when and how its pricing, schedule, or customer details were altered. For reporting, the table is often joined with OE_ORDER_LINES_ALL and OE_ORDER_HEADERS_ALL to provide a comprehensive view of order evolution. A typical SQL pattern selects historical records where the LINE_ID matches the target order line, ordered by creation date to show the sequence of changes. This data is essential for generating reports on order volatility, change frequency, and user modification patterns.

Related Objects

As defined by its foreign key constraints, OE_ORDER_LINES_HISTORY has a direct and fundamental relationship with the OE_ORDER_LINES_ALL table via the LINE_ID column. It is heavily dependent on customer and trading community entities, linking to HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES (for various contact points), and HZ_CUST_SITE_USES_ALL. A relationship with IBE_MSITES_B indicates tracking of changes related to iStore mini-sites. From an application perspective, data is populated into this table by the Order Management application logic and APIs, such as the Order Import process and the Order Management forms, whenever a line attribute is updated. It is commonly queried alongside the OE_ORDER_HEADERS_HISTORY table for a complete order audit.