Results for “default_currency_code”

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

Overview

JTF_MSITES_VL is a translated (VL) view owned by the APPS schema within the JTF – CRM Foundation product of Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a language-resolved, read-only projection of the mobile site (MSITE) definition tables that underpin Oracle's mobile and self-service CRM applications, including the framework used by iStore mobile storefronts and field service mobile interfaces.

The view joins the base entity table JTF_MSITES_B with its translation table JTF_MSITES_TL, resolving the language-specific attributes (site name and description) against the session language returned by USERENV('LANG'). Because of this filtering, the view returns exactly one translated row per MSITE_ID corresponding to the current session's language context, rather than all translations. This makes it suitable for runtime reporting, concurrent programs, PL/SQL validation logic, and integration extracts where a single localized description is required. The status is documented as VALID in the ETRM 12.2.2 repository.

Underlying Base Objects

The view is defined over two documented base objects, both referenced as synonyms:

• JTF_MSITES_B — the base (non-translated) table holding physical, language-independent columns of a mobile site, aliased as B in the view text.
• JTF_MSITES_TL — the translation table holding language-dependent columns (MSITE_NAME, MSITE_DESCRIPTION, SOURCE_LANG, LANGUAGE), aliased as L.

The join condition is L.MSITE_ID = B.MSITE_ID AND L.LANGUAGE = USERENV('LANG'), which enforces the translated view semantics. The ROW_ID column is derived from B.ROWID, allowing the view to participate in certain DML and row-identification contexts. The _B/_TL pair is the standard Oracle EBS multilingual schema pattern, and JTF_MSITES_VL is the canonical consumer-facing definition of that pattern for mobile sites.

Key Columns

The view exposes the full B column set plus the translation columns. Columns most relevant to the user's search term and general use include:

• DEFAULT_LANGUAGE_CODE — the default language assigned to the mobile site, sourced from JTF_MSITES_B. This is a site-level configuration value and is distinct from the LANGUAGE column, which reflects the session/translation language applied by the join.
• DEFAULT_CURRENCY_CODE and DEFAULT_DATE_FORMAT — regionalization defaults applied when the mobile site is served.
• MSITE_ID — primary key of the mobile site; the join key to both base and translation tables.
• MSITE_NAME and MSITE_DESCRIPTION — translated display attributes returned for USERENV('LANG').
• SOURCE_LANG and LANGUAGE — the source language of the translation record and the active translation language.
• STORE_ID, URL, THEME_ID, PROFILE_ID — store association, access URL, presentation theme, and profile linkage.
• ATP_CHECK_FLAG, WALKIN_ALLOWED_FLAG, PARTY_ACCESS_CODE, RESP_ACCESS_FLAG, ACCESS_NAME — functional and access-control flags governing site behavior.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating of the site.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard Oracle descriptive flexfield columns.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns for audit and optimistic locking.

Common Use Cases and Queries

Typical reporting and validation scenarios involve listing active mobile sites, checking language defaults, and extracting translated names for a given session language.

• Listing active sites: SELECT msite_id, msite_name, default_language_code FROM jtf_msites_vl WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);
• Finding sites by default language: SELECT msite_id, msite_name, default_language_code, default_currency_code FROM jtf_msites_vl WHERE default_language_code = 'US';
• Comparing site default language against the translation language: SELECT msite_id, msite_name, language, source_lang, default_language_code FROM jtf_msites_vl WHERE language <> default_language_code;
• Locating the master site or store-linked sites: SELECT msite_id, access_name, store_id, url FROM jtf_msites_vl WHERE master_msite_flag = 'Y';

Because the LANGUAGE predicate is fixed to USERENV('LANG'), queries executed under a different session language may return no rows for a site that lacks a translation in that language. Reports requiring all translations should query JTF_MSITES_TL directly rather than this view.