Search Results original_system_source_code




Overview
Explore in AI Chat

Overview

AS_DOSSIER_HEADERS_DETAIL_V is a reporting view in the Oracle E-Business Suite Sales Foundation (AS) module. It exposes order history header-level detail, consolidating data that would otherwise require joining the order header table OE_ORDER_HEADERS_ALL with customer, order type, agreement, salesperson, contact, and lookup reference tables. In EBS 12.1.1 and 12.2.2 the view falls under the Order Management/Sales Foundation functional area and is intended primarily for read-only reporting and integration extracts rather than transactional processing.

The naming convention ("DOSSIER") reflects Oracle's dossier-style history reporting, where a complete snapshot of an order's header attributes is made available for downstream inquiry screens and BI Publisher reports. Importantly, the ETRM metadata notes that the view is not implemented in this database, meaning it may not be deployed in every environment; its presence depends on whether the corresponding Order Management history/purge functionality has been enabled. Users searching for the column-like token "warehouse_svrid" should note that no such column exists in this view — the closest attribute is WAREHOUSE_ID, the ship-from warehouse identifier. warehouse_svrid is a separate seed/identifier used in warehouse-related configuration tables (e.g., WSH parameters) and is not exposed here.

Underlying Base Objects

Although the ETRM extraction did not enumerate the referenced base objects, the view text reveals the joins involved. The driving table is OE_ORDER_HEADERS_ALL (aliased HEAD), which supplies header identifiers, order number, currency, dates, flags, and the ATTRIBUTE1–15/DDL context flexfields. Supporting objects include:

The view is therefore logically a denormalized projection over these tables, keyed by HEADER_ID with ROW_ID exposed from OE_ORDER_HEADERS_ALL.ROWID for update-tracking purposes.

Key Columns

The principal identifiers are HEADER_ID, ORDER_NUMBER, ORDER_TYPE_ID/ORDER_TYPE, and ORIGINAL_SYSTEM_REFERENCE (useful when orders are imported from external sources). Customer context is captured through CUSTOMER_ID, CUSTOMER_NAME, and CUSTOMER_NUMBER. Date fields include BOOKED_DATE (S1_DATE), DATE_ORDERED, DATE_REQUESTED_CURRENT, and CREATION_DATE/LAST_UPDATE_DATE for audit purposes.

Shipping and fulfillment attributes include WAREHOUSE_ID, SHIP_TO_SITE_USE_ID, SHIP_TO_CONTACT_ID, SHIP_METHOD_CODE, SHIPMENT_PRIORITY_CODE, FREIGHT_TERMS_CODE, FOB_CODE, and SHIP_PARTIAL_FLAG. Financial attributes include CURRENCY_CODE, PRICE_LIST_ID, CONVERSION_TYPE_CODE, CONVERSION_RATE, CONVERSION_DATE, TERMS_ID, INVOICING_RULE_ID, and ACCOUNTING_RULE_ID. Status flags (OPEN_FLAG, CANCELLED_FLAG), SALES_CHANNEL_CODE, salesrep/agreement references, and the full flexfield set (ATTRIBUTE1–15 plus CONTEXT) round out the projection.

Common Use Cases and Queries

Typical uses include order history inquiry reports, customer order trend analysis, and extract programs feeding data warehouses. A representative query:

  • SELECT ORDER_NUMBER, CUSTOMER_NAME, CURRENCY_CODE, BOOKED_DATE, WAREHOUSE_ID, SALESREP FROM AS_DOSSIER_HEADERS_DETAIL_V WHERE BOOKED_DATE >= :from_date; — retrieves header history within a date range.
  • SELECT ORDER_TYPE, COUNT(*) FROM AS_DOSSIER_HEADERS_DETAIL_V GROUP BY ORDER_TYPE; — summarizes orders by type.
  • SELECT HEADER_ID, ORIGINAL_SYSTEM_SOURCE_CODE, ORIGINAL_SYSTEM_REFERENCE FROM AS_DOSSIER_HEADERS_DETAIL_V WHERE ORIGINAL_SYSTEM_SOURCE_CODE IS NOT NULL; — isolates externally sourced orders.

Because warehouse_svrid is not part of this view, queries requiring that attribute must join to the appropriate warehouse configuration table rather than relying on AS_DOSSIER_HEADERS_DETAIL_V alone. In 12.1.1 and 12.2.2 the view retains the same column signature; differences arise only from underlying table changes in OE_ORDER_HEADERS_ALL.