Results for “oe_blanket_headers_u1”

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

Overview

ONT.OE_BLANKET_HEADERS_ALL is the core transactional header table for sales agreements (blanket sales orders) in Oracle Order Management. Within Oracle EBS 12.1.1 and 12.2.2, it stores the header-level attributes of blanket agreements — long-term purchasing commitments negotiated with a customer that serve as templates for releasing standard sales orders. The object resides in the ONT schema, is marked VALID, and is physically stored in the APPS_TS_TX_DATA tablespace with a PCT Free of 10. The table comprises 167 documented columns and carries the FND Design Data reference ONT.OE_BLANKET_HEADERS_ALL, making it a recognized dictionary object for concurrent programs, forms, and report generation.

From a data-modeling perspective, the mined foreign-key structure suggests a Data Vault classification of link: the table sits at the intersection of customer (sold-to, ship-to, and invoice-to parties), order type, payment terms, price list, and sales document context. It therefore behaves less like an isolated hub and more like a relationship record that binds several business entities into a single negotiated agreement.

Key Information Stored

The surrogate primary key is HEADER_ID, enforced by the unique index OE_BLANKET_HEADERS_U1. The business-key candidate is the composite (ORDER_NUMBER, ORDER_TYPE_ID), enforced by OE_BLANKET_HEADERS_U2 — the index the user searched for. ORDER_NUMBER holds the user-visible agreement number, while ORDER_TYPE_ID identifies the transaction type that governs processing, pricing, and fulfillment defaults.

• HEADER_ID – surrogate primary key and the join anchor to all agreement lines and detail tables.
• ORDER_NUMBER / VERSION_NUMBER – user-visible agreement number and revision, supporting renegotiation history.
• ORDER_TYPE_ID – transaction type linking to SO_ORDER_TYPES_115_ALL; part of the U2 unique key.
• ORG_ID – operating unit that owns the agreement, critical for multi-org security (MOAC).
• SOLD_TO_ORG_ID, SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID – party and site context, each backed by a nonunique index.
• SOLD_TO_SITE_USE_ID – FK to HZ_CUST_SITE_USES_ALL, identifying the site use for billing or shipping.
• PRICE_LIST_ID, PAYMENT_TERM_ID, INVOICING_RULE_ID, ACCOUNTING_RULE_ID – commercial terms driving pricing and invoicing on release.
• CUST_PO_NUMBER – customer purchase-order reference; separately indexed for lookup.
• OPEN_FLAG, BOOKED_FLAG, CANCELLED_FLAG, FLOW_STATUS_CODE – lifecycle and status indicators.
• EXPIRATION_DATE, ORDERED_DATE, BOOKED_DATE – validity and date tracking for agreement aging.
• SALES_DOCUMENT_NAME, SALES_DOCUMENT_TYPE_CODE – document naming and classification; SALES_DOCUMENT_NAME is indexed via OE_BLANKET_HEADERS_N8.
• BATCH_ID, ORIG_SYS_DOCUMENT_REF, ORDER_SOURCE_ID – import, batch, and source-system traceability.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY – standard WHO audit columns.

Common Use Cases and Queries

Typical reporting retrieves active agreements by customer or operating unit, checks expiration, or traces releases back to the parent agreement. Because OE_BLANKET_HEADERS_N1 through N8 support filtered access, the following patterns run efficiently:

• List open agreements for a customer: SELECT order_number, expiration_date, flow_status_code FROM oe_blanket_headers_all WHERE sold_to_org_id = :p AND open_flag = 'Y';
• Find an agreement by the U2 business key: SELECT header_id FROM oe_blanket_headers_all WHERE order_number = :num AND order_type_id = :type;
• Batch or interface reconciliation using the N7 index: SELECT header_id, order_number FROM oe_blanket_headers_all WHERE batch_id = :batch;
• External-system traceability via N5: SELECT header_id FROM oe_blanket_headers_all WHERE orig_sys_document_ref = :ref AND order_source_id = :src;

Common reporting scenarios include blanket-usage analysis (released versus remaining quantity, joining lines), expiration dashboards, and customer PO cross-referencing via OE_BLANKET_HEADERS_N4.

Related Objects

FK metadata identifies the following significant dependencies:

• HZ_CUST_ACCOUNT_ROLES – referenced by SOLD_TO_CONTACT_ID, SHIP_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, and DELIVER_TO_CONTACT_ID.
• HZ_CUST_SITE_USES_ALL – referenced by SOLD_TO_SITE_USE_ID; supplies site-use context for the sold-to party.
• SO_ORDER_TYPES_115_ALL – referenced by ORDER_TYPE_ID; defines the transaction type and its processing rules.
• PN_PAYMENT_TERMS_ALL – referenced by PAYMENT_TERM_ID; supplies payment-term definitions.
• OE_BLANKET_LINES_ALL – child table joined on HEADER_ID; holds agreement line items.
• OE_ORDER_HEADERS_ALL – released sales orders linked through SOURCE_DOCUMENT_ID and the agreement reference.
• OE_BLANKET_HEADERS_ALL – self-reference via SOURCE_DOCUMENT_ID for versioning and source tracking.
• ONT Order Management APIs – OE_ORDER_PUB and related PL/SQL interfaces create and maintain blanket headers programmatically.