Results for “as_dossier_headers_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view AS_DOSSIER_HEADERS_V belongs to the Oracle EBS AS – Sales Foundation product family and is documented as an Order history header summary view. Its purpose is to expose a denormalized, reporting-friendly projection of sales order header information, combining the order header record with selected descriptive attributes sourced from customer, order type, order line, sales channel, agreement, sales representative, contact, and address entities. In Oracle EBS 12.1.1 and 12.2.2 this object supports order history inquiries, dossier-style reporting, and downstream integrations that require a flattened header-level view rather than joining the underlying transactional tables directly. Because the view already resolves foreign-key descriptions such as customer name, order type name, and ship-to/bill-to address attributes, it is well suited for operational reporting, data extracts, and custom concurrent programs.

Underlying Base Objects

The ETRM metadata for this object does not document explicit base tables under a "Referenced base objects" heading; no owner is recorded and the view is noted as not implemented in this database. The view text, however, reveals an alias-based join structure. The primary driving alias is HEAD, which supplies the header-level columns and supplies ROWID as ROW_ID. Joined aliases include CUST (customer name and number), OT (order type id and name), LN (which supplies ORDER_AMOUNT, indicating a line-level aggregation or line join), S1_DATE (booked date), SOL (sales channel meaning), A (agreement name), SALE (sales representative), CONT (contact), RS (comments), and ADDR1/ADDR2 for ship-to and bill-to addresses. Although the exact base tables are not enumerated in the supplied metadata, these aliases correspond to standard Sales Foundation entities such as order headers, customers, order types, order lines, agreements, and address tables.

Key Columns

The most significant column relative to the user's search for order_amount is LN.ORDER_AMOUNT, exposed in the view as ORDER_AMOUNT. It represents the monetary value derived from the order line source and is essential for order value reporting against the header. Other notable columns include:

• ROW_ID, HEADER_ID, ORDER_NUMBER – identifiers for the order header record.
• CUSTOMER_ID, CUSTOMER_NAME, CUSTOMER_NUMBER – customer identification attributes.
• ORDER_TYPE_ID, ORDER_TYPE – order classification.
• CURRENCY_CODE – currency of the order amount.
• BOOKED_DATE, PO_NUMBER, SALES_CHANNEL, AGREEMENT, SALESREP – order context and history descriptors.
• CONTACT_FIRST_NAME, CONTACT_LAST_NAME, COMMENTS – contact and remark text.
• Ship-to and bill-to address columns (address id, address lines, city, state, province, postal code, county, country).
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT – descriptive flexfield segments.
• Audit and concurrency columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE.

Common Use Cases and Queries

Typical uses include order value reporting, customer order history listings, and extracts feeding data warehouses. A representative query filtering on the searched column is:

• SELECT HEADER_ID, ORDER_NUMBER, CUSTOMER_NAME, ORDER_AMOUNT, CURRENCY_CODE FROM AS_DOSSIER_HEADERS_V WHERE ORDER_AMOUNT > 10000 AND BOOKED_DATE >= :from_date;
• Aggregation by customer: SELECT CUSTOMER_NUMBER, CUSTOMER_NAME, SUM(ORDER_AMOUNT) FROM AS_DOSSIER_HEADERS_V GROUP BY CUSTOMER_NUMBER, CUSTOMER_NAME;
• Sales channel analysis: SELECT SALES_CHANNEL, COUNT(*), SUM(ORDER_AMOUNT) FROM AS_DOSSIER_HEADERS_V GROUP BY SALES_CHANNEL;

Because the view flattens descriptive attributes, these queries avoid complex multi-table joins, making it convenient for ad hoc and published reports. Users should confirm the actual base tables in their instance, since the view is documented as not implemented in the reference database.