Results for “oe_blanket_lines_all”

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

Overview

OE_BLANKET_LINES_ALL is the Oracle Order Management (ONT) transactional table that stores line-level detail for sales agreements, commonly referred to as blanket sales orders in Oracle E-Business Suite 12.1.1 and 12.2.2. The table is owned by the ONT schema and holds the attributes common between standard sales order lines and sales agreement lines, making it the single source of truth for the negotiated item, quantity, pricing, shipping, and fulfillment terms that a customer agreement authorizes. In the EBS data model, blanket lines represent the commitments a customer has made against a specific agreement, and downstream releases (actual sales orders) reference these lines through the BLANKET_NUMBER, BLANKET_LINE_NUMBER, and BLANKET_VERSION_NUMBER columns.

The documented relationship profile classifies this object heuristically as a link in a Data Vault model. Its foreign keys interconnect several reference entities — HZ_CUST_ACCOUNT_ROLES for the four contact roles, PO_LINE_TYPES_B for the line type, PN_PAYMENT_TERMS_ALL for payment terms, and PON_OFFER_COMMITMENTS for commitment references — which makes it a natural associative table between the sales agreement header and those dimensions.

Key Information Stored

The unique index OE_BLANKET_LINES_U1 defines LINE_ID as the surrogate primary key and the business-key candidate. The header that owns each line is identified by HEADER_ID and AGREEMENT_ID, while ORG_ID scopes the row to a specific operating unit. The most operationally significant columns include:

• LINE_ID — the unique surrogate identifier for the blanket line.
• HEADER_ID / AGREEMENT_ID — parent sales agreement references.
• ORDERED_ITEM / INVENTORY_ITEM_ID — the item being negotiated, in user-facing and internal forms.
• ORDERED_QUANTITY / ORDERED_QUANTITY_UOM — the agreed quantity and its unit of measure.
• PRICING_QUANTITY / PRICING_QUANTITY_UOM — the quantity basis for price calculations.
• UNIT_LIST_PRICE / UNIT_SELLING_PRICE — list and negotiated selling prices.
• PRICE_LIST_ID / PRICING_DATE — pricing source and effective date.
• SHIP_TO_ORG_ID / SHIP_TO_CONTACT_ID and their DELIVER_TO, INVOICE_TO, INTMED_SHIP_TO counterparts — the full address and contact role set.
• PAYMENT_TERM_ID — agreed payment terms for the line.
• SHIP_TOLERANCE_ABOVE / SHIP_TOLERANCE_BELOW — quantity tolerance thresholds.
• SHIPPING_METHOD_CODE / FREIGHT_CARRIER_CODE / FOB_POINT_CODE — logistics and delivery terms.
• LINE_NUMBER / SHIPMENT_NUMBER — human-readable sequence identifiers.
• BLANKET_NUMBER / BLANKET_LINE_NUMBER / BLANKET_VERSION_NUMBER — legacy compatibility references to the blanket agreement.
• FLOW_STATUS_CODE — the workflow/processing status of the line.

Common Use Cases and Queries

Typical reporting scenarios include listing all active lines for a customer agreement, auditing negotiated pricing versus list price, and tracing which sales orders consumed a specific blanket line. A representative query joining the line to its header and item master appears as:

SELECT l.line_id, l.line_number, l.ordered_item,
       l.ordered_quantity, l.unit_selling_price,
       l.flow_status_code
FROM   oe_blanket_lines_all l
WHERE  l.header_id = :p_header_id
AND    l.org_id    = :p_org_id
ORDER BY l.line_number;

For tolerance and pricing analysis, analysts frequently aggregate ORDERED_QUANTITY against FULFILLED_QUANTITY or SHIPPED_QUANTITY and compare UNIT_SELLING_PRICE to UNIT_LIST_PRICE. Because the table is partitioned conceptually by ORG_ID, all production queries should filter on the operating unit to avoid cross-organization leakage. Integration flows also read this table to validate that a release order does not exceed SHIP_TOLERANCE_ABOVE or fall below SHIP_TOLERANCE_BELOW.

Related Objects

The FK profile in the ETRM metadata identifies the following principal dependencies, all of which should be joined on the listed columns:

• HZ_CUST_ACCOUNT_ROLES — joined via SHIP_TO_CONTACT_ID, DELIVER_TO_CONTACT_ID, INVOICE_TO_CONTACT_ID, and INTMED_SHIP_TO_CONTACT_ID for contact role resolution.
• PO_LINE_TYPES_B — joined via LINE_TYPE_ID to classify the agreement line.
• PN_PAYMENT_TERMS_ALL — joined via PAYMENT_TERM_ID for term descriptions.
• PON_OFFER_COMMITMENTS — joined via COMMITMENT_ID for procurement commitment linkage.
• OE_BLANKET_HEADERS_ALL — the parent header table, joined via HEADER_ID.
• OE_ORDER_LINES_ALL — releases and resulting sales order lines reference the blanket through BLANKET_NUMBER, BLANKET_LINE_NUMBER, and BLANKET_VERSION_NUMBER.

These joins, combined with the OE_ORDER_PUB and OE_BLANKET_PUB PL/SQL APIs, constitute the standard programmatic and reporting access path to sales agreement line data.