Search Results sales_document_type_code




Overview
Explore in AI Chat

Overview

APPS.OE_ORDER_VERSIONS_V is a reporting and integration view in Oracle E-Business Suite (documented for 12.1.1 and 12.2.2) that consolidates order header version information from both the live order table and the order header history table. It presents, for each header, the version number, a derived sales document type code, a flag indicating whether the version carries a customer signature, and an archival indicator. Its principal role is to give downstream reports, concurrent programs, and interfaces a single, stable read interface for enumerating the version lineage of a sales order without requiring callers to understand the split between OE_ORDER_HEADERS_ALL and OE_ORDER_HEADER_HISTORY.

The view is commonly consulted when implementers search on sales_document_type_code, because that column is projected as the second element of the SELECT list and is central to distinguishing quotation-style, order-style, and return-style documents during version analysis.

Underlying Base Objects

The view is owned by APPS and is defined over two referenced base objects:

  • OE_ORDER_HEADERS_ALL (SYNONYM) — the current or "live" order header records. Rows from this table are always tagged with ARCHIVED_YN = 'N'.
  • OE_ORDER_HEADER_HISTORY (SYNONYM) — the historical/archived header records. Rows are included only where VERSION_FLAG = 'Y', and are tagged with ARCHIVED_YN = 'Y'.

The two sources are combined with UNION, so a header can appear more than once across the live and archived sets. The union output is ordered by VERSION_NUMBER in descending sequence, so the most recent version appears first. No joins to customer, line, or lookup tables are performed inside the view; it is a pure projection and union of the two header sources.

Key Columns

  • HEADER_ID — the order header identifier, provided by both source tables and used to correlate versions back to a specific order.
  • SALES_DOCUMENT_TYPE_CODE — the sales document type. It is not exposed directly but through NVL(SALES_DOCUMENT_TYPE_CODE,'O'), so a null source value is returned as 'O' (order).
  • VERSION_NUMBER — the version sequence number for the header; the ordering key of the result set (descending).
  • SIGNED_YN — derived as DECODE(NVL(TO_CHAR(CUSTOMER_SIGNATURE_DATE),'N'),'N','N','Y'). Returns 'Y' when a customer signature date exists for that version, otherwise 'N'.
  • ARCHIVED_YN — a literal discriminator: 'N' for rows sourced from OE_ORDER_HEADERS_ALL, 'Y' for rows from OE_ORDER_HEADER_HISTORY.

Common Use Cases and Queries

Typical uses include auditing version history for a specific order, filtering by document type, and identifying signed or archived versions for compliance or approval reporting.

  • Retrieve all versions of a given order, newest first:
SELECT header_id, sales_document_type_code, version_number,
       signed_yn, archived_yn
FROM   apps.oe_order_versions_v
WHERE  header_id = :p_header_id;
  • Filter by document type (the column most often searched):
SELECT header_id, version_number
FROM   apps.oe_order_versions_v
WHERE  sales_document_type_code = 'O';
  • Identify signed, non-archived versions:
SELECT header_id, version_number
FROM   apps.oe_order_versions_v
WHERE  signed_yn = 'Y' AND archived_yn = 'N';

Because the view depends only on the two header sources, it is efficient for header-level reporting and is well suited to views, LOVs, and interfaces that must not read base tables directly.