Search Results charges_total




Overview
Explore in AI Chat

Overview

OE_PRN_ORDER_HEADERS_V is an APPS-owned database view in the Oracle E-Business Suite Order Management (ONT) module. It is a denormalized, print-oriented projection of order header data, intended to supply the reporting and document-printing layers with a single, ready-to-consume row per sales order header. Unlike the transactional base table OE_ORDER_HEADERS_ALL, which stores identifiers and foreign keys, this view resolves many of those keys into descriptive names and computes monetary totals at query time. It carries a VALID status in both 12.1.1 and 12.2.2, and its structure is identical across the two releases, so reports and integrations built against it remain portable during an upgrade.

Because the view joins transaction type, agreement, blanket, invoicing rule, payment terms and currency descriptions, it is frequently used as the header source for order acknowledgements, pick/pack documents and custom operational reports where a flat, printable result set is preferred over multi-table joins. It is a read-only object; no DML should be issued against it.

Underlying Base Objects

The view is defined primarily over OE_ORDER_HEADERS_ALL (aliased H), which supplies all header identifiers, dates, contact references, shipping attributes and the transactional currency code. Three outer joins enrich the header with descriptive text: OE_AGREEMENTS_TL supplies the agreement name and revision, OE_BLANKET_HEADERS_ALL supplies the blanket version number, RA_TERMS_TL supplies the payment terms name, and RA_RULES supplies the invoicing rule name. FND_CURRENCIES_TL provides the transactional currency name.

Two additional objects perform computation rather than description. The OE_TOTALS_GRP package exposes GET_ORDER_TOTAL, which is called four times to produce the order, line, charges and tax totals, and FND_CURRENCY.SAFE_GET_FORMAT_MASK supplies the currency-specific format mask used by TO_CHAR. An inner join to OE_TRANSACTION_TYPES_ALL restricts the result set to order types whose TRANSACTION_TYPE_CODE is 'ORDER', excluding returns and other non-order flows. The TL tables are joined with LANGUAGE = USERENV('LANG'), so descriptions are returned in the session language.

Key Columns

Common Use Cases and Queries

The view is typically queried by ORDER_NUMBER, by ORG_ID for an operating unit, or by a date range on ORDERED_DATE. A representative query listing orders with their tax and overall totals is:

  • SELECT order_number, transactional_curr_name, lines_total, charges_total, taxes_total, order_total, payment_terms FROM oe_prn_order_headers_v WHERE org_id = :p_org_id AND ordered_date >= :p_from_date ORDER BY order_number;
  • SELECT order_number, taxes_total FROM oe_prn_order_headers_v WHERE header_id = :p_header_id; — retrieves the formatted tax total for a specific order.
  • SELECT agreement_name, blanket_number, order_number, order_total FROM oe_prn_order_headers_v WHERE agreement_name IS NOT NULL; — lists orders governed by agreements or blankets.

Note that the four total columns are stored as formatted character strings, not numbers, so arithmetic or aggregation in SQL requires TO_NUMBER conversion and is generally discouraged. Because totals are computed by a package function at fetch time, performance on large result sets depends on filtering aggressively by org and date rather than on the view definition itself.