Results for “as_exchanges_vl”

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

Overview

AS_EXCHANGES_VL is a Multi-Lingual Support (MLS) compliant view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AS - Sales Foundation product family, itself part of the broader Oracle Advanced Pricing and Order Management footprint. The view presents exchange rate information that is used to convert between currencies within sales and pricing transactions, and its MLS-compliant design means that translated descriptive text is resolved automatically according to the runtime language session of the querying user.

The "VL" suffix follows the standard Oracle EBS naming convention denoting a view that joins a base ("_B") table to its translation ("_TL") table. Consumers of AS_EXCHANGES_VL therefore see the language-independent business columns from AS_EXCHANGES_B alongside the translated NAME value pulled from AS_EXCHANGES_TL. Because it is a view rather than a table, it exposes no independent storage and remains valid only for read access; all inserts, updates, and deletes must target the underlying base tables. ETRM lists the object with STATUS = VALID, confirming it is compiled and usable in the documented release.

Underlying Base Objects

ETRM documentation records two referenced base objects, both exposed through synonyms in the APPS schema:

• AS_EXCHANGES_B — the base table holding the exchange definition, including its identifier, the country and currency codes it relates to, WHO columns, and the 15 descriptive flexfield attribute columns.
• AS_EXCHANGES_TL — the translation table holding the multilingual NAME column, keyed by EXCHANGE_ID and LANGUAGE.

The view text confirms the join is performed on EXCHANGE_ID (B.EXCHANGE_ID = TL.EXCHANGE_ID) and is filtered with TL.LANGUAGE = USERENV('LANG'). This filter is the mechanism that makes the view MLS compliant: a user running with a French language setting sees the French NAME, while an English session sees the English NAME, without any change to the calling SQL.

Key Columns

The view exposes the following documented columns:

• EXCHANGE_ID — primary identifier joining the base and translation records.
• NAME — translated descriptive name of the exchange, sourced from AS_EXCHANGES_TL and language-filtered.
• COUNTRY_CODE — country associated with the exchange definition.
• CURRENCY_CODE — currency associated with the exchange definition.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns maintained by EBS.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield (DFF) segments, available for customer-specific extension data.

Common Use Cases and Queries

Because the view is language-aware, it is the preferred access path for any report, concurrent program, or integration that must display the exchange NAME in the user's own language. Typical scenarios include currency-conversion lookups during order entry, pricing validation reports, and data extracts feeding downstream warehouses.

A representative query is:

• SELECT exchange_id, name, country_code, currency_code FROM apps.as_exchanges_vl WHERE currency_code = :p_currency;
• SELECT e.exchange_id, e.name, e.country_code FROM apps.as_exchanges_vl e WHERE e.exchange_id = :p_id;
• SELECT e.name, e.currency_code FROM apps.as_exchanges_vl e, apps.as_exchanges_tl t WHERE e.exchange_id = t.exchange_id AND t.language = 'US' AND e.currency_code = 'USD';

Note that the third example deliberately queries the translation table directly rather than relying on the view's USERENV('LANG') filter, which is useful when a fixed language must be enforced regardless of session settings. Developers integrating with AS_EXCHANGES_VL should treat it as read-only and route any maintenance through AS_EXCHANGES_B and AS_EXCHANGES_TL respectively.