Search Results oe_blanket_lines_hist_v




Overview
Explore in AI Chat

Overview

OE_BLANKET_LINES_HIST_V is a valid APPS-owned view in the Oracle E-Business Suite Order Management (ONT) module. It exposes blanket sales agreement (BSA) line history information and is documented as being used by the BSA version comparison user interface. In Oracle EBS 12.1.1 and 12.2.2, blanket sales agreements support versioning, whereby each approved revision of an agreement is retained so that changes to line attributes can be audited and compared. This view provides the line-level historical snapshot consumed by that comparison mechanism.

Because the object is a view rather than a table, no data is physically stored in it. It is a reporting and integration access point that projects columns from the underlying blanket line history entity, OE_BLANKET_LINES_HIST. The view presents row identifiers together with the identifying, pricing, shipping, tax, and reference attributes of a historical agreement line, allowing consumers to retrieve prior-version line detail without directly querying the base history table.

Underlying Base Objects

The documented referenced base objects for this view include:

The presence of these joins indicates that the view resolves foreign-key identifiers on the history line into meaningful business context, which is why it is suitable for a version comparison screen that must display customer, pricing, and terms detail across revisions.

Key Columns

The view text exposes a broad set of line attributes. The most significant columns include:

Common Use Cases and Queries

The principal use case is the BSA version comparison UI, which reconciles line attributes across successive agreement versions. Beyond that, the view supports historical analysis of agreement lines, audit reporting on prior pricing and shipping terms, and integration extracts that need revision-level line detail.

A typical query retrieving line history for a given agreement header:

  • SELECT line_id, line_number, ordered_item, ordered_quantity, pricing_quantity, unit_selling_price, agreement_id FROM oe_blanket_lines_hist_v WHERE header_id = :p_header_id AND org_id = :p_org_id ORDER BY line_number;

A comparison-oriented query selecting key attributes for a line across revisions:

  • SELECT line_id, line_number, ordered_item, ordered_quantity, unit_selling_price, price_list_id, payment_term_id FROM oe_blanket_lines_hist_v WHERE header_id = :p_header_id AND line_number = :p_line_number;

A reporting query joining to pricing and terms context:

  • SELECT h.line_number, h.ordered_item, h.unit_selling_price, p.name AS price_list, t.name AS payment_terms FROM oe_blanket_lines_hist_v h, qp_list_headers_tl p, ra_terms_tl t WHERE h.header_id = :p_header_id AND h.price_list_id = p.list_header_id AND h.payment_term_id = t.term_id;

Because the view already resolves many foreign keys through its referenced base objects, queries should rely on the exposed columns rather than re-joining to the same master tables unless additional attributes are required. Access is granted through the APPS schema, and reporting should filter by ORG_ID to respect operating unit security.