Search Results quote_date




Overview
Explore in AI Chat

Overview

OE_BLANKET_HEADERS_ALL is the header-level table within Oracle Order Management (ONT) that stores sales agreement (blanket sales agreement) information. In Oracle E-Business Suite 12.1.1 and 12.2.2, this table captures the customer-facing commercial terms defined at the agreement level before individual releases or orders are created against it. Each row represents a distinct blanket agreement header, identified by a combination of order number and order type, and is editioned through a version number so that amendments can be tracked without losing historical context.

The table resides in the ONT schema and is classified as VALID in the ETRM repository. Under a heuristic Data Vault classification, the object most closely resembles a link entity: its foreign keys reference customer contact roles and customer site uses in the Trading Community Architecture (HZ) model as well as order types and payment terms, meaning it primarily records relationships between parties, sites, and commercial attributes rather than serving as a standalone reference hub or a pure descriptive satellite. This classification should be treated as a modeling suggestion rather than an authoritative designation.

Key Information Stored

The table contains 167 columns. The most operationally significant are:

Common Use Cases and Queries

Typical reporting queries join this table to customer and site entities, filter by operating unit, and constrain on expiration to surface active agreements:

  • Listing active blanket agreements for a sold-to customer within an operating unit.
  • Identifying agreements approaching expiration for renewal campaigns.
  • Auditing agreement versions for a given order number to trace amendments.
  • Reconciling agreements against downstream releases and orders using AGREEMENT_ID.

A representative pattern:

SELECT bh.order_number, bh.version_number, bh.expiration_date, bh.flow_status_code
FROM   oe_blanket_headers_all bh
WHERE  bh.org_id = :p_org_id
AND    bh.sold_to_org_id = :p_customer_id
AND    bh.expiration_date > SYSDATE
ORDER BY bh.order_number;

Because ORDER_NUMBER alone is not unique, joins to child tables should always include ORDER_TYPE_ID or HEADER_ID to avoid row multiplication. Currency and pricing columns should be restricted by TRANSACTIONAL_CURR_CODE when converting amounts across operating units.

Related Objects

  • HZ_CUST_ACCOUNT_ROLES — referenced via SOLD_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID.
  • HZ_CUST_SITE_USES_ALL — referenced via SOLD_TO_SITE_USE_ID.
  • SO_ORDER_TYPES_115_ALL — referenced via ORDER_TYPE_ID.
  • PN_PAYMENT_TERMS_ALL — referenced via PAYMENT_TERM_ID.
  • OE_BLANKET_LINES_ALL — child table holding line-level agreement detail keyed by HEADER_ID.
  • OE_ORDER_HEADERS_ALL — downstream order headers created from the agreement.
  • OE_BLANKET_HEADERS_115 — historical versioned snapshot used in 12.1.1 upgrade scenarios.