Results for “order_total”

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

Overview

AST_ORDER_HEADERS_V is a TeleSales (AST) reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a denormalized, user-friendly projection of sales order header information sourced primarily from the Oracle Order Management tables, enriched with customer, contact, salesperson, and lookup descriptive attributes. The view is designed to support the TeleSales application, where agents and reporting users require order header data in a readable form without navigating the numerous foreign-key joins intrinsic to the Order Management data model.

Because the view resolves display-friendly values such as flow status meaning, order type name, sales channel meaning, and a formatted order total, it serves both interactive TeleSales screens and downstream reporting or integration queries. Note that the view is defined in APPS and is documented as VALID, meaning it is a supported, queryable object at the time the ETRM metadata was captured.

Underlying Base Objects

The view is defined over a collection of base tables, synonyms, and views. The principal driving table is OE_ORDER_HEADERS_ALL, aliased H, which supplies the core order header identifiers and attributes. This is joined to OE_TRANSACTION_TYPES_TL (OT) for the order type name, restricted by the session language through USERENV('LANG'), and to OE_ORDER_SOURCES (OS) for the order source name via an outer join.

Customer and contact information is assembled through a chain of Trading Community Architecture objects: HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_RELATIONSHIPS, HZ_ORG_CONTACTS, and HZ_PARTIES. Additional descriptive values are resolved through AR_LOOKUPS (contact title via SOLD_ARL) and OE_LOOKUPS, the latter used twice—once for flow status meaning and once for sales channel meaning. Salesperson data is obtained from JTF_RS_SALESREPS, and the operating unit name from HR_OPERATING_UNITS. The formatted order total is derived by invoking the PL/SQL function OE_OE_TOTALS_SUMMARY.PRT_ORDER_TOTAL, with a currency format mask supplied by FND_CURRENCY.SAFE_GET_FORMAT_MASK.

Key Columns

• HEADER_ID – Primary key of the order header; the join key back to OE_ORDER_HEADERS_ALL.
• ORG_ID / ORG_NAME – Operating unit identifier and its descriptive name from HR_OPERATING_UNITS.
• ORDER_NUMBER – The user-visible sales order number.
• FLOW_STATUS_CODE / FLOW_STATUS – Internal status code and its translated lookup meaning.
• ORDER_TYPE / ORDER_SOURCE – Descriptive names for the transaction type and order source.
• TRANSACTIONAL_CURR_CODE – Currency of the order, also used to format the total.
• SOLD_TO_CONTACT – Concatenation of the contact's last name, first name, and title meaning.
• ACCOUNT_NUMBER / PARTY_ID – Customer account number and party identifier.
• SALESREP_NAME / SALES_CHANNEL – Assigned salesperson and the translated sales channel meaning.
• ORDER_TOTAL – The formatted, currency-masked order total produced by the totals summary function.

Common Use Cases and Queries

The most frequent use is retrieving order headers for a given customer or operating unit, with the order total formatted for display. A representative query follows:

SELECT order_number, order_type, flow_status, sold_to_contact, account_number, order_total FROM apps.ast_order_headers_v WHERE org_id = :p_org_id AND sold_to_org_id = :p_cust_id ORDER BY creation_date DESC;

Because the ORDER_TOTAL column is computed through a packaged function, filtering or sorting on it directly can be costly; it is preferable to filter on indexed identifiers such as HEADER_ID, ORG_ID, or SOLD_TO_ORG_ID and restrict the row set before referencing the total. Applications commonly join this view back to OE_ORDER_LINES_ALL using HEADER_ID when line-level detail is required alongside header attributes, and reporting layers frequently use it as the source for TeleSales order dashboards where salesperson and channel attribution are needed.