Results for “oe_blanket_headers_hist”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ONT.OE_BLANKET_HEADERS_HIST is the sales agreement header history table in Oracle Order Management (ONT). In Oracle EBS, a "blanket" is the internal name for a sales agreement — a long-term contractual arrangement with a customer that defines pricing, terms, and conditions against which release orders are later created. While OE_BLANKET_HEADERS_ALL holds the current, active definition of each agreement, OE_BLANKET_HEADERS_HIST preserves prior versions of that header information each time a revision is committed. Its documented purpose is to capture sales agreement header history, primarily for storing revisions.

Each row represents a snapshot of the agreement header at a specific version. As columns such as BLANKET_MAX_AMOUNT, PAYMENT_TERM_ID, or pricing-effective dates are revised, the pre-change values are written to this table together with a version identifier and audit attributes, enabling full lifecycle traceability without altering the live record.

From a Data Vault modeling perspective, the FK relationships suggest a link classification: the table connects agreement header instances to customer contact roles, site uses, order types, and payment terms, functioning as a transactional relationship record between these business entities rather than a standalone hub of unique business keys.

Key Information Stored

The table contains 198 columns. The most significant include:

• HEADER_ID — surrogate identifier carried over from the live blanket header; not globally unique across history rows on its own.
• VERSION_NUMBER — the revision sequence for the agreement; combined with HEADER_ID, this is the practical business key for a historical snapshot.
• HIST_TYPE_CODE, HIST_COMMENTS, HIST_CREATION_DATE, HIST_CREATED_BY — history-specific metadata describing why and when the revision was captured.
• BLANKET_NUMBER — the user-facing agreement number, constant across versions.
• BLANKET_MAX_AMOUNT, BLANKET_MIN_AMOUNT, RELEASED_AMOUNT, RETURNED_AMOUNT, FULFILLED_AMOUNT — financial ceilings and accumulated release activity at that version.
• START_DATE_ACTIVE, END_DATE_ACTIVE, EXPIRATION_DATE — agreement validity windows.
• SOLD_TO_ORG_ID, SOLD_TO_CONTACT_ID, SOLD_TO_SITE_USE_ID — the customer and contact context of the agreement.
• REVISION_CHANGE_REASON_CODE, REVISION_CHANGE_COMMENTS, REVISION_CHANGE_DATE — the documented rationale for each revision.
• ORDER_TYPE_ID, PAYMENT_TERM_ID, PRICE_LIST_ID — the terms and defaults governing release orders.
• CONVERSION_RATE, TRANSACTIONAL_CURR_CODE — currency and rate context.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE) plus descriptive flexfield attributes (ATTRIBUTE1–ATTRIBUTE20 and GLOBAL_ATTRIBUTE*).

Common Use Cases and Queries

Typical scenarios include auditing agreement revision history, comparing amounts before and after a change, and reconstructing what terms were in effect on a given date. A representative query listing revisions for an agreement:

• SELECT header_id, version_number, revision_change_date, revision_change_reason_code, blanket_max_amount, released_amount FROM ont.oe_blanket_headers_hist WHERE header_id = :p_header_id ORDER BY version_number;
• Audit view: join to SO_ORDER_TYPES_115_ALL on ORDER_TYPE_ID to display the agreement type, and to PN_PAYMENT_TERMS_ALL on PAYMENT_TERM_ID for term descriptions.
• Amount trend reporting: aggregate released_amount by version_number to track consumption against blanket_max_amount over time.

Related Objects

• HZ_CUST_ACCOUNT_ROLES — joined via SOLD_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID.
• HZ_CUST_SITE_USES_ALL — joined via SOLD_TO_SITE_USE_ID.
• SO_ORDER_TYPES_115_ALL — joined via ORDER_TYPE_ID.
• PN_PAYMENT_TERMS_ALL — joined via PAYMENT_TERM_ID.
• OE_BLANKET_HEADERS_ALL — the live header source that this history table shadows.
• OE_BLANKET_LINES_ALL / line history equivalents — the detail-level agreements revised alongside each header version.