Search Results oe_blanket_headers_all




The OE_BLANKET_HEADERS_ALL table is a fundamental component of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically within the Order Management (OM) module. It serves as the primary repository for blanket sales agreement headers, which are long-term contractual agreements between buyers and sellers outlining terms, pricing, and other commercial conditions for future transactions. This table is part of the multi-org architecture in Oracle EBS, meaning it stores data for all operating units, distinguished by the ORG_ID column.

Table Structure and Key Columns

The OE_BLANKET_HEADERS_ALL table contains critical columns that define blanket agreement attributes:
  • HEADER_ID: Primary key, uniquely identifying each blanket agreement.
  • ORG_ID: Operating unit identifier, enabling multi-org functionality.
  • ORDER_NUMBER: User-facing identifier for the agreement.
  • ORDER_TYPE_ID: Links to OE_TRANSACTION_TYPES_ALL, defining agreement type (e.g., "Blanket Sales Agreement").
  • ORDERED_DATE: Date when the agreement was created.
  • STATUS_CODE: Current lifecycle state (e.g., "Entered", "Approved", "Closed").
  • CUSTOMER_ID: References HZ_CUST_ACCOUNTS for the buyer.
  • SHIP_TO_ORG_ID/BILL_TO_ORG_ID: Ship-to and bill-to locations from HZ_CUST_SITE_USES_ALL.
  • PRICING_DATE: Baseline date for price calculations.
  • CURRENCY_CODE: Agreement currency from FND_CURRENCIES.
  • AGREEMENT_START_DATE/AGREEMENT_END_DATE: Validity period of the contract.

Functional Significance

Blanket agreements streamline procurement processes by:
  • Establishing pre-negotiated terms for repetitive purchases
  • Reducing administrative overhead for order creation
  • Enforcing pricing consistency across transactions
The table integrates with:
  • OE_BLANKET_LINES_ALL: Stores line items for agreements
  • OE_ORDER_HOLDS_ALL: Manages contractual holds
  • QP_* tables: For pricing calculations
  • AR_PAYMENT_SCHEDULES: For billing integration

Technical Implementation

In Oracle EBS 12.x:
  • The table is populated via Order Management forms or API calls (ONT_ORDER_PUB_PKG)
  • Workflow processes (OE_BLANKET_WF) manage approval routing
  • Key views like OE_BLANKET_HEADERS_V provide application-layer access
  • Indexes on HEADER_ID, ORDER_NUMBER, and CUSTOMER_ID optimize performance

Customization Considerations

Common extensions include:
  • Adding descriptive flexfields for industry-specific attributes
  • Creating custom workflows for agreement approval
  • Developing triggers to enforce business rules
  • Building custom reports using the OE_BLANKET_HEADERS_ALL as the primary data source

Upgrade Implications

Between 12.1.1 and 12.2.2:
  • Table structure remains largely consistent
  • New columns may be added for enhanced functionality
  • Web ADI integrations improve in later versions
  • Oracle recommends using public APIs rather than direct table updates
The OE_BLANKET_HEADERS_ALL table remains a critical component for organizations leveraging blanket agreements in Oracle Order Management, providing the structural foundation for long-term customer contracts while maintaining integration with core EBS functionality.