Results for “oe_charge_lines_v”

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

Overview

OE_CHARGE_LINES_V is a reporting and integration view owned by the APPS schema within the Oracle E-Business Suite Order Management (ONT) module. It is defined over the pricing adjustment, order line, and order header tables, and exposes freight and special charge information associated with sales orders. In the ETRM repository for release 12.2.2 (and consistent with 12.1.1), the object carries a VALID status and is documented as being used for Freight and Special Charges.

The view does not store data itself. Instead, it presents a pre-joined, pre-derived result set that simplifies consumption of charge data by reports, extensions, and integration interfaces. Because Oracle Order Management records freight and special charges as price adjustments rather than as ordinary order lines, consumers of the base tables must apply several filters and derivations. OE_CHARGE_LINES_V encapsulates that logic, presenting each qualifying freight charge as a charge line with a resolved name, a signed amount, and the associated currency and conversion context.

Underlying Base Objects

The view is defined over the following documented base objects:

• OE_PRICE_ADJUSTMENTS (synonym in APPS) — the driving table, aliased P. It holds the charge records, including charge type and subtype codes, the arithmetic operator, operand, adjusted amount, credit/charge indicator, and the invoiced and intercompany invoiced flags.
• OE_ORDER_HEADERS_ALL (synonym in APPS) — aliased H. It supplies header-level context such as the order number, ordered date, transactional currency code, conversion rate, conversion rate date, conversion type, FOB point, and ORG_ID.
• OE_ORDER_LINES_ALL (synonym in APPS) — aliased L. It is joined with an outer join (LINE_ID(+)), providing line-level quantity used to compute line-related charge amounts where the adjustment applies to a specific line.
• ONT_CHARGE_UTIL (package) — invoked through GET_MEANING to resolve the charge meaning from the charge type and subtype codes.

The join condition requires P.HEADER_ID = H.HEADER_ID and P.LINE_ID = L.LINE_ID(+). The view restricts output to records where LIST_LINE_TYPE_CODE = 'FREIGHT_CHARGE' and APPLIED_FLAG = 'Y', meaning only applied freight charges are surfaced.

Key Columns

• HEADER_ID, LINE_ID, CHARGE_ID — Identifiers linking the charge to its order header and, where applicable, to a specific order line. PRICE_ADJUSTMENT_ID in the view text is exposed as CHARGE_ID.
• CHARGE_NAME — Derived via ONT_CHARGE_UTIL.GET_MEANING, returning a readable description of the charge type and subtype.
• CHARGE_AMOUNT — A computed, sign-adjusted amount. Debits and credits are normalized using CREDIT_OR_CHARGE_FLAG; credits are multiplied by -1. For line-level charges with a non-lumpsum operator, the amount is derived from ordered quantity multiplied by the adjusted amount; otherwise the operand value is used directly.
• CURRENCY_CODE, CONVERSION_RATE, CONVERSION_DATE, CONVERSION_TYPE_CODE — Sourced from the header, giving the transactional currency and conversion context for the charge.
• FIXED_FLAG, INVOICED_FLAG — Status indicators describing whether the charge is fixed and whether it has been invoiced.
• CONTEXT, ATTRIBUTE1–15, AC_CONTEXT, AC_ATTRIBUTE1–15 — Descriptive flexfield and additional (global) descriptive flexfield columns supporting attribute capture.

Common Use Cases and Queries

Typical scenarios include reconciling freight charges on sales orders, extracting charge detail for external freight or tax systems, and building order-level cost reports. A simple listing for a given order is:

• SELECT header_id, line_id, charge_id, charge_name, charge_amount FROM oe_charge_lines_v WHERE header_id = :p_header_id;
• SELECT charge_name, SUM(charge_amount) FROM oe_charge_lines_v WHERE org_id = :p_org_id GROUP BY charge_name;
• SELECT h.order_number, c.charge_name, c.charge_amount, c.currency_code FROM oe_charge_lines_v c, oe_order_headers_all h WHERE c.header_id = h.header_id AND c.invoiced_flag = 'N';

Because the view already applies the FREIGHT_CHARGE and APPLIED_FLAG filters, queries need not restate those predicates. Users should note that only applied freight charges are returned; special charges recorded under other list line types are not included by this definition.