Results for “jai_cmn_base_currency_v”

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

Overview

JAI_CMN_BASE_CURRENCY_V is a database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2, shipped as part of the JA (Asia/Pacific Localizations) product family. The view exposes a consolidated list of currency codes together with an optional order identifier, allowing callers to resolve the base or functional currency associated with an organization alongside the billing currency recorded on sales orders. Its primary role is as a lightweight lookup source for localization logic, concurrent programs, reports, and integration interfaces that must determine which currency governs a given operating unit or order. Because it is a view rather than a table, it carries no storage of its own and always reflects the current state of the underlying policy and order data.

Underlying Base Objects

The view text documented in the ETRM metadata is a UNION ALL of two distinct query branches, each drawing on separate physical sources via APPS synonyms:

• GL_PLCY_MST (synonym) — the localization currency policy master table, joined to SY_ORGN_MST (synonym), the organization master, on the common column CO_CODE. This branch yields the functional or base currency configured for an organization and returns TO_NUMBER(NULL) in place of an order identifier.
• OP_ORDR_HDR (synonym) — the order header table in the Asia/Pacific order entry schema, which contributes the BILLING_CURRENCY value along with the actual ORDER_ID for each order record.

Both branches project the same two columns, BASE_CURRENCY_CODE and ORDER_ID, which is what permits the UNION ALL to produce a single, uniform result set. The join to SY_ORGN_MST ensures that only organizations with a valid currency policy are returned in the first branch, while the second branch is unconstrained by organization and reflects order-level currency data directly.

Key Columns

• BASE_CURRENCY_CODE — The currency code surfaced by the view. In the first branch it is the policy-level base currency for an organization; in the second branch it is the billing currency of the order. This is the column most commonly searched for as "base_currency_code".
• ORDER_ID — The order identifier associated with the row. For policy-derived rows this is deliberately set to NULL, since the currency is not tied to any specific order. For order-derived rows it carries the actual order header identifier, allowing consumers to correlate the currency back to a transaction.

The NULL ORDER_ID convention is significant: it signals to the calling application that the row represents a setup-level currency definition rather than a transactional one.

Common Use Cases and Queries

Typical scenarios include validating that an order's billing currency matches the operating unit's base currency, driving currency-sensitive pricing or tax localization routines, and populating LOVs or validation sets in Asia/Pacific localization forms. A representative query to retrieve the base currency for organizations is:

• SELECT base_currency_code FROM apps.jai_cmn_base_currency_v WHERE order_id IS NULL;
• SELECT base_currency_code, order_id FROM apps.jai_cmn_base_currency_v WHERE order_id = :p_order_id;
• SELECT DISTINCT base_currency_code FROM apps.jai_cmn_base_currency_v ORDER BY base_currency_code;

Because the view performs a UNION ALL without an ORDER BY or aggregation, callers requiring distinct currency values should apply DISTINCT explicitly, and joins back to OP_ORDR_HDR or the organization master should be performed on the appropriate key depending on which branch the row originates from.