Search Results version_flag




Overview
Explore in AI Chat

Overview

OE_BLANKET_VERSIONS_V is an Oracle E-Business Suite (EBS) view owned by the APPS schema and defined within the Order Management (ONT) product module. It presents a consolidated, version-oriented representation of blanket sales agreements, exposing both the currently active header records and their archived historical counterparts through a single query interface. In Release 12.1.1 and 12.2.2 this view serves as a lightweight reporting and integration surface, allowing concurrent programs, custom reports, and external interfaces to enumerate blanket agreement versions without needing to query the two underlying header tables separately. Because the view is documented as VALID and supplied as an Oracle-proprietary seeded object, it should be treated as read-only; direct DML against it is neither supported nor advisable.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

The view text is a UNION of these two sources. For each, SIGNED_YN is derived via DECODE(NVL(TO_CHAR(CUSTOMER_SIGNATURE_DATE),'N'),'N','N','Y'), returning 'Y' when a customer signature date exists. The ARCHIVED_YN column is a literal 'N' for rows drawn from OE_BLANKET_HEADERS_ALL and a literal 'Y' for rows drawn from OE_BLANKET_HEADERS_HIST, making the origin of each row explicit. The combined result set is ordered by VERSION_NUMBER DESC.

Key Columns

The view exposes the following columns:

  • DOCUMENT_ID — maps to HEADER_ID; the unique identifier of the blanket agreement header.
  • DOCUMENT_TYPE — maps to SALES_DOCUMENT_TYPE_CODE; identifies the sales document type of the agreement.
  • DOCUMENT_VERSION — maps to VERSION_NUMBER; the sequential version of the blanket agreement.
  • SIGNED_YN — indicates whether the agreement has been signed by the customer.
  • ARCHIVED_YN — 'N' for current versions, 'Y' for archived historical versions.

Common Use Cases and Queries

Typical scenarios include auditing which versions of a blanket agreement exist, distinguishing live from archived records, and identifying unsigned agreements pending customer action. A representative query against a specific document is:

  • SELECT document_id, document_type, document_version, signed_yn, archived_yn FROM oe_blanket_versions_v WHERE document_id = :header_id ORDER BY document_version DESC;
  • SELECT document_id, document_version FROM oe_blanket_versions_v WHERE archived_yn = 'Y' AND signed_yn = 'N';

The first returns the full version history for one agreement, newest first. The second isolates archived, unsigned versions. Because the view performs no joins to lines or parties, it is efficient for header-level listings and is well suited to embedded LOVs, concurrent extracts, and validation logic in custom ONT extensions.