Search Results currency_flag




Overview
Explore in AI Chat

Overview

APPS.BEN_CWB_CURRENCY_LOV_V is a lightweight Oracle EBS database view whose sole purpose is to supply a filtered list of currencies for a List of Values (LOV). It is delivered in the APPS schema and is documented as part of the Compensation Workbench (CWB) functional area, a component of the Advanced Benefits (BEN) product family. The view does not store data; it derives a two-column result set from the currencies master and exposes it in the "ID / Value" shape that Oracle Forms and OAF-based LOV components expect. Because the view is a simple projection, it imposes almost no parsing or execution overhead and can be safely queried from reports, concurrent programs, and integrations that need a validated currency pick list.

Underlying Base Objects

The view is defined over a single documented base object: FND_CURRENCIES_VL, itself a view in the FND (Application Object Library) schema. FND_CURRENCIES_VL is the translation-enabled ("_VL") view that joins the base currency table FND_CURRENCIES with its translation table FND_CURRENCIES_TL, returning the language-appropriate currency name. BEN_CWB_CURRENCY_LOV_V therefore does not reference the translation tables directly; it inherits multilingual behavior from the _VL layer. The ETRM metadata identifies only FND_CURRENCIES_VL as a referenced base object, so any dependency analysis for the LOV view should treat FND_CURRENCIES and FND_CURRENCIES_TL as transitive dependencies.

Key Columns

  • ID — The CURRENCY_CODE value (for example, "USD" or "EUR"). It is the returned identifier used by the LOV and is the value typically written into a foreign key column by the calling form.
  • VALUE — A concatenation of the currency code, a hyphen separator, and the translated currency name (for example, "USD - US Dollar"). This is the display string presented to the user in the LOV poplist.

The view exposes no other columns. Filtering is applied internally against four FND_CURRENCIES_VL attributes: ENABLED_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE, and CURRENCY_FLAG. Because the filters live inside the view definition, consumers cannot widen or narrow the returned set without creating a wrapper query.

Common Use Cases and Queries

The view is most often used to populate a currency LOV in a Compensation Workbench setup or eligibility screen, and to validate a currency value supplied by an external interface before it is committed. The CURRENCY_FLAG = 'Y' predicate is significant: it restricts the list to currencies that are permitted to be used in a given context, and it is this predicate that distinguishes the view from a simple "all enabled currencies" query. The date predicates limit results to the currency's active window, defaulting to the current date when the start or end date is null. A typical query is:

SELECT id, value FROM apps.ben_cwb_currency_lov_v ORDER BY value;

A validation-friendly variant that confirms a specific code is selectable:

SELECT id FROM apps.ben_cwb_currency_lov_v WHERE id = :p_currency_code;

Because the view returns the same shape regardless of caller, it is suitable for reuse in BI Publisher data templates, Oracle Reports, and custom PL/SQL validation packages that must enforce the same currency eligibility rules applied by the standard forms.