Search Results oe_blanket_lines_all




Overview
Explore in AI Chat

Overview

The OE_BLANKET_LINES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically for versions 12.1.1 and 12.2.2. It serves as the primary repository for storing line-level details of sales agreements, also known as blanket sales orders. These agreements establish long-term contractual terms between a business and its customer, defining items, pricing, and other conditions under which future standard sales orders (releases) will be created. The table's description explicitly notes it holds attributes common between sales orders and sales agreements, indicating its role in the shared data architecture of the Order Management system. It is a multi-org table, as denoted by the "_ALL" suffix, meaning it stores data for all operating units and requires a security condition, such as `ORG_ID`, to be applied in queries for meaningful results.

Key Information Stored

The table captures comprehensive line details essential for governing the fulfillment of sales agreements. While the provided metadata does not list specific columns, based on its function and foreign key relationships, it typically stores critical attributes such as: agreement header identifier (`HEADER_ID`), line identifier (`LINE_ID`), ordered item details (`INVENTORY_ITEM_ID`, `ORDERED_QUANTITY`), pricing information (`UNIT_SELLING_PRICE`), and schedule details. Crucially, the documented foreign keys reveal the table stores several contact role identifiers, linking each line to specific individuals or roles at the customer's site for delivery (`DELIVER_TO_CONTACT_ID`), intermediate shipping (`INTMED_SHIP_TO_CONTACT_ID`), invoicing (`INVOICE_TO_CONTACT_ID`), and shipping (`SHIP_TO_CONTACT_ID`). These links are established through the `HZ_CUST_ACCOUNT_ROLES` table, part of the Trading Community Architecture (TCA).

Common Use Cases and Queries

This table is central to operations and reporting related to contractual sales. Common use cases include generating reports on agreement line performance, such as quantities ordered versus released, and validating pricing compliance for standard orders created against a blanket agreement. For technical consultants and report developers, a typical query involves joining to the agreement header table (`OE_BLANKET_HEADERS_ALL`) and item master (`MTL_SYSTEM_ITEMS_B`) to analyze line data. A fundamental pattern for retrieving released lines against an agreement would join `OE_BLANKET_LINES_ALL` to the standard order lines table (`OE_ORDER_LINES_ALL`) via the `SOURCE_DOCUMENT_LINE_ID` column. All queries must include an `ORG_ID` filter or use a multi-org view (e.g., `OE_BLANKET_LINES`) for correct data isolation.

Related Objects

The OE_BLANKET_LINES_ALL table exists within a tightly integrated schema. Its primary parent is `OE_BLANKET_HEADERS_ALL`, which stores the agreement header information. As per the metadata, it has four distinct foreign key relationships to `HZ_CUST_ACCOUNT_ROLES` for contact management. It is also intrinsically linked to the standard sales order entities; lines from this table are sourced by `OE_ORDER_LINES_ALL` when releases are created. Key related APIs include the Order Management transactional APIs (e.g., `OE_ORDER_PUB`) for processing agreements and the `OE_BLANKET_LINES` multi-org view, which provides a secure access layer. For item information, it relates to `MTL_SYSTEM_ITEMS_B`.