Search Results oe_blkt_lines_hist_v




Overview
Explore in AI Chat

Overview

OE_BLKT_LINES_HIST_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the ONT (Order Management) product family. It is available in both 12.1.1 and 12.2.2 and carries a VALID status in the ETRM data dictionary. The view exposes historical blanket sales agreement (BSA) line information and is documented as the data source consumed by the BSA Organizer, the Order Management workbench used to review blanket agreement activity.

Blanket sales agreements capture long-term customer purchase commitments, typically expressed as a header with one or more lines defining items, pricing, and quantities. The transactional tables store current line state, while the history table preserves superseded versions of each line. OE_BLKT_LINES_HIST_V projects that historical content through the standard APPS synonym layer so concurrent programs, Oracle Forms, and ad hoc reports can retrieve prior versions of BSA lines without querying the underlying table directly.

Because the view returns the ROWID of the underlying history row as its first projected column along with LINE_ID and HEADER_ID, it supports both row-level addressing (for updateable, Forms-based blocks) and relational joins back to the active blanket tables.

Underlying Base Objects

The documented metadata lists the following referenced objects: OE_BLANKET_LINES_HIST, OE_BLANKET_LINES_ALL, OE_BLANKET_HEADERS, OE_BLANKET_LINES_EXT, OE_BLANKET_FORM_CONTROL (package), OE_AGREEMENTS_TL, OE_LOOKUPS, MTL_PARAMETERS, MTL_GRADES, QP_LIST_HEADERS_TL, QP_LIST_LINES, QP_PRICING_ATTRIBUTES, RA_RULES, and RA_TERMS_TL.

The primary projection source is OE_BLANKET_LINES_HIST, the archive table holding previous versions of blanket lines; the view text selects from this object, aliased OBL. Joins to OE_BLANKET_LINES_ALL and OE_BLANKET_HEADERS return the current header context and identify the parent agreement, while OE_BLANKET_LINES_EXT supplies descriptive flexfield context and attribute columns. OE_AGREEMENTS_TL provides the translated agreement name. QP_LIST_HEADERS_TL, QP_LIST_LINES, and QP_PRICING_ATTRIBUTES resolve the price list, pricing attributes, and list line associated with historic pricing. RA_RULES and RA_TERMS_TL supply invoicing and accounting rule and payment term descriptions, and OE_LOOKUPS decodes lookup codes such as DEMAND_CLASS_CODE and SHIPMENT_PRIORITY_CODE. MTL_PARAMETERS and MTL_GRADES resolve inventory organization and grade information. OE_BLANKET_FORM_CONTROL is a database package referenced for form-level control behavior rather than row data. All base objects appear through APPS synonyms, so the view remains name-stable across the 12.1.1 and 12.2.2 code lines.

Key Columns

Common Use Cases and Queries

The principal consumer is the BSA Organizer, which uses the view to render prior line states so planners can compare historic versus current quantities, dates, and prices. Additional uses include audit reporting on blanket agreement revision history, reconciliation of changed dates or prices against the current line, and extraction of historic lines into custom OBIEE or BI Publisher reports.

Retrieve all historic versions of a blanket line:

  • SELECT line_id, header_id, line_number, ordered_item, ordered_quantity, unit_selling_price FROM oe_blkt_lines_hist_v WHERE header_id = :p_header_id ORDER BY line_number, line_id;

Report historic lines for a customer purchase order reference:

  • SELECT h.header_id, h.line_number, h.ordered_item, h.cust_po_number, h.promise_date, h.shipping_quantity FROM oe_blkt_lines_hist_v h WHERE h.cust_po_number = :p_cust_po ORDER BY h.promise_date;

Join history to the current line to detect changes in quantity or price:

  • SELECT hl.line_id, cl.line_number, hl.ordered_quantity hist_qty, cl.ordered_quantity curr_qty, hl.unit_selling_price hist_price, cl.unit_selling_price curr_price FROM oe_blkt_lines_hist_v hl, oe_blanket_lines_all cl WHERE hl.line_id = cl.line_id AND hl.ordered_quantity <> cl.ordered_quantity;

When writing custom queries, qualify columns with the view alias to avoid ambiguity with joined blanket tables, and filter on ORG_ID to restrict output to the correct operating unit.