Search Results oe_blanket_headers_all




Overview
Explore in AI Chat

Overview

The OE_BLANKET_HEADERS_ALL table is a core transactional table within the Oracle E-Business Suite (EBS) Order Management (ONT) module. It serves as the primary repository for header-level information pertaining to sales agreements, commonly known as blanket sales orders or blanket purchase agreements. These agreements establish long-term contractual terms between an organization and its customer, defining pricing, products, and conditions under which future standard sales orders (releases) will be created. The table's role is critical for managing the master contract, from which individual order releases are generated, ensuring consistency and adherence to negotiated terms. Its '_ALL' suffix indicates it is a multi-organization table, storing data partitioned by the ORG_ID column to support multiple operating units within a single installation.

Key Information Stored

The table captures the essential administrative and business attributes of a blanket sales agreement. While the provided metadata does not list specific columns, based on its function and foreign key relationships, the table typically stores the agreement's header identifier (HEADER_ID), document number (ORDER_NUMBER), and type (ORDER_TYPE_ID). It holds critical dates such as the agreement start and end dates, and key status attributes (FLOW_STATUS_CODE, BOOKED_FLAG). Crucially, it stores foreign key references to the trading community architecture (TCA) for customer and site information. This includes identifiers for the sold-to customer (SOLD_TO_ORG_ID), and specific site use IDs for sold-to (SOLD_TO_SITE_USE_ID), ship-to, bill-to, and deliver-to locations. The ORG_ID column is fundamental for multi-org access control.

Common Use Cases and Queries

This table is central to reporting on and processing blanket agreements. Common operational use cases include generating a list of active agreements for a customer, validating agreement dates before creating a release, and auditing agreement terms. A typical reporting query would join to related TCA tables to retrieve customer names and addresses. For instance, to find active blanket agreements for a specific customer number, a developer might use a SQL pattern such as: SELECT obha.header_id, obha.order_number, hca.account_number, obha.agreement_start_date, obha.agreement_end_date FROM oe_blanket_headers_all obha, hz_cust_accounts hca WHERE obha.sold_to_org_id = hca.cust_account_id AND hca.account_number = '&CUST_ACCT_NUM' AND obha.flow_status_code = 'ACTIVE' AND SYSDATE BETWEEN obha.agreement_start_date AND NVL(obha.agreement_end_date, SYSDATE); This table is also a primary source for data extracts into business intelligence systems for sales performance and contract compliance analysis.

Related Objects

OE_BLANKET_HEADERS_ALL maintains integral relationships with several key EBS objects, primarily within the Trading Community Architecture (TCA) and Order Management. As documented in the provided metadata, it has foreign key relationships to the following tables:

Furthermore, it is the parent table to OE_BLANKET_LINES_ALL, which stores the detailed line items of the agreement. The header's HEADER_ID is the primary foreign key in the lines table. The table is also referenced by key Order Management APIs and views such as OE_ORDER_HEADERS_ALL (for released orders sourced from the blanket) and OE_BLANKET_HEADERS_V.