Results for “transactional_curr_code”

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

Overview

The OE_PRN_CHG_PERIODICITY_V view is an Oracle Order Management (ONT) reporting object owned by the APPS schema. It is documented as a VALID view in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its stated purpose is to obtain recurring charge information while printing a Sales Order. The view returns the periodic (recurring) charge codes associated with sales order lines, resolved to the transaction currency carried on the parent order header.

Because periodicity codes determine whether a charge recurs weekly, monthly, quarterly, annually, or is charged only once, this view supplies the print and reporting layer with a compact, de-duplicated result set of header, charge periodicity, and transaction currency. It sits in the reporting/integration tier — it is not a transactional entry point and carries no DML — and is typically consumed by order-print programs, custom concurrent requests, BI Publisher layouts, and inbound/outbound interfaces that must reproduce the periodicity and currency context of a sales order.

The user search term transactional_curr_code maps directly to the exposed column TRANSACTIONAL_CURR_CODE, which is the currency of the transaction as recorded on the order header. This makes the view useful wherever recurring charge amounts must be formatted or converted in the order's transactional currency rather than in functional currency.

Underlying Base Objects

The view is defined over two synonym-referenced base tables in the APPS schema:

• OE_ORDER_HEADERS_ALL — aliased H; the source of TRANSACTIONAL_CURR_CODE and the header identity used for the join.
• OE_ORDER_LINES_ALL — aliased L; the source of HEADER_ID and CHARGE_PERIODICITY_CODE.

The documented view text is a correlated join:

SELECT DISTINCT L.HEADER_ID, NVL(L.CHARGE_PERIODICITY_CODE,'ONE'), H.TRANSACTIONAL_CURR_CODE FROM OE_ORDER_HEADERS_ALL H, OE_ORDER_LINES_ALL L WHERE L.HEADER_ID = H.HEADER_ID

The join is a simple equijoin on HEADER_ID. The DISTINCT operator collapses the many order lines that share a header into a single row per distinct header/periodicity/currency combination. The NVL wrapper substitutes the literal value 'ONE' when a line's periodicity code is null, ensuring the print layer always receives a non-null periodicity token. Note that because the join is on header alone, the result is not scoped to a specific line; it reports the set of periodicity codes present across all lines of each order.

Key Columns

• HEADER_ID — Surrogate primary key of the order header in OE_ORDER_HEADERS_ALL. Used to group and to link the view back to the order for printing or further joins.
• CHARGE_PERIODICITY_CODE — The periodicity of the recurring charge, sourced from OE_ORDER_LINES_ALL.CHARGE_PERIODICITY_CODE. Nulls are returned as the literal 'ONE' by the NVL expression, indicating a single (non-recurring) charge.
• TRANSACTIONAL_CURR_CODE — The transactional currency code of the order, taken from OE_ORDER_HEADERS_ALL.TRANSACTIONAL_CURR_CODE. This is the column matched by the search term transactional_curr_code.

Common Use Cases and Queries

Typical scenarios include reproducing recurring charge periodicity on printed sales orders, validating which orders carry more than one periodicity code, and extracting transactional currency alongside periodicity for downstream formatting or interface staging.

Retrieve periodicity and transaction currency for a specific order:

SELECT header_id, charge_periodicity_code, transactional_curr_code FROM oe_prn_chg_periodicity_v WHERE header_id = :header_id;

Identify orders carrying recurring (non-'ONE') charges in a given currency:

SELECT header_id, charge_periodicity_code FROM oe_prn_chg_periodicity_v WHERE transactional_curr_code = 'USD' AND charge_periodicity_code <> 'ONE';

Join back to the header for printing context:

SELECT v.header_id, v.charge_periodicity_code, v.transactional_curr_code, h.order_number FROM oe_prn_chg_periodicity_v v, oe_order_headers_all h WHERE v.header_id = h.header_id AND h.org_id = :org_id;

Because the view is DISTINCT and header-scoped, queries should treat it as a periodicity/currency summary per order rather than as a line-level detail source; line-level periodicity must be read from OE_ORDER_LINES_ALL directly.