Search Results oe_blanket_headers_hist




Overview
Explore in AI Chat

Overview

The OE_BLANKET_HEADERS_HIST 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 a historical repository for revisions made to sales agreement headers, commonly known as blanket sales agreements. Unlike the active transactional table (OE_BLANKET_HEADERS_ALL), this table captures a complete audit trail of changes. Whenever a user modifies and saves a blanket sales agreement, a historical record is typically created, preserving the prior state of the header information. This design is critical for compliance, auditing, and understanding the evolution of contractual terms with customers over time.

Key Information Stored

The table stores a snapshot of all significant header-level attributes from a blanket sales agreement at a point in time prior to a revision. While the specific column list is extensive, the provided metadata highlights its strong relationship with customer and site data. Crucially, it maintains foreign keys to critical customer tables, including:

Other typical columns would include agreement number, revision number, effective dates, customer PO number, currency, price list, agreement status, and various header-level descriptive flexfield attributes. Each historical record is uniquely identifiable, often through a combination of HEADER_ID and a REVISION_NUMBER or a system-generated HISTORY_ID.

Common Use Cases and Queries

The primary use case is auditing and reporting on changes to blanket sales agreements. Analysts can trace how terms, pricing, or customer details have changed throughout the agreement's lifecycle. A common query retrieves the full revision history for a specific agreement, ordered chronologically. For example:

SELECT header_id, revision_number, last_update_date, sold_to_contact_id
FROM ont.oe_blanket_headers_hist
WHERE header_id = :p_header_id
ORDER BY revision_number DESC, last_update_date DESC;

Another key scenario is comparing a specific historical revision against the current active version in OE_BLANKET_HEADERS_ALL to identify exact field-level differences. This table is also essential for generating compliance reports that demonstrate when and how a contractual agreement was modified, which is vital for regulated industries.

Related Objects

OE_BLANKET_HEADERS_HIST is part of a closely related set of objects in Order Management. Its structure and purpose are directly tied to the main transactional table, OE_BLANKET_HEADERS_ALL. The history for corresponding agreement lines is stored in OE_BLANKET_LINES_HIST. As indicated by its foreign keys, it has a direct dependency on the Trading Community Architecture (TCA) customer base tables, principally HZ_CUST_ACCOUNT_ROLES (for contacts) and HZ_CUST_SITE_USES_ALL (for sites). Data is typically populated into this history table by the application's business logic, often within PL/SQL APIs or triggers in the Order Management schema, rather than via direct user DML operations.