Search Results oe_ak_blanket_lines_v




Overview
Explore in AI Chat

Overview

The OE_AK_BLANKET_LINES_V view is an Oracle Application Object Library (AK) style reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Order Management (ONT) product family and exposes blanket sales agreement line information in a denormalized, query-friendly format. Its principal role is to support Oracle Order Management's descriptive flexfield and object-attribute (AK) infrastructure, where a single flat view is required to present blanket line data to flexfield definition, reporting, and integration layers without the caller having to join the two base tables directly.

The view is defined strictly as a join between the transactional blanket header/lines table and the corresponding extension table holding the flexfield and additional attribute columns. Because the AK framework requires stable, non-null column definitions and consistent data types, the view text includes several literal expressions — for example, constant values of 1 and an RPAD-derived placeholder value — that satisfy these structural requirements. This makes the view safe for consumption by the flexfield database and by external reporting tools that register database views as data sources.

Underlying Base Objects

According to the documented ETRM metadata for 12.2.2, OE_AK_BLANKET_LINES_V is defined over two referenced base objects, both accessed through private APPS synonyms:

  • OE_BLANKET_LINES — the primary blanket sales agreement line table, aliased as BL in the view definition.
  • OE_BLANKET_LINES_EXT — the blanket line extension table, aliased as BLE, which carries the descriptive flexfield context and attribute columns plus additional control flags.

The two objects are joined on LINE_ID, meaning the view returns exactly one row per blanket line that also has a matching extension row. The WHERE clause further restricts output to rows where BL.SALES_DOCUMENT_TYPE_CODE equals 'B', ensuring only blanket-type documents are returned and excluding other sales document categories stored in the same tables. Header-level descriptive flexfield columns (CONTEXT through ATTRIBUTE20) are sourced from BL, while line-level activity and control columns are sourced from BLE.

Key Columns

The view exposes a broad set of columns across document identity, organization defaults, pricing, controls, and flexfields:

Common Use Cases and Queries

Typical scenarios include reporting on active blanket agreements, validating enforcement settings before release creation, and extracting blanket data into external systems or Oracle BI Publisher reports.

A simple listing of blanket lines with validity windows:

  • SELECT order_number, line_number, inventory_item_id, start_date_active, end_date_active FROM oe_ak_blanket_lines_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • SELECT order_number, line_number, blanket_line_max_amount, blanket_max_quantity, enforce_price_list_flag FROM oe_ak_blanket_lines_v WHERE enforce_price_list_flag = 'Y';
  • SELECT v.order_number, v.line_number, v.cust_po_number, v.attribute1, v.attribute2 FROM oe_ak_blanket_lines_v v WHERE v.context IS NOT NULL;

Because the view already resolves the join to OE_BLANKET_LINES_EXT and filters to document type 'B', these queries avoid re-implementing that logic and remain consistent with the AK flexfield registration used by Order Management.