Results for “jtf_stores_tl”

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

Overview

JTF_STORES_TL is the translation (language-specific) table for JTF_STORES_B, the base table that stores store and location definitions used throughout Oracle E-Business Suite CRM Foundation (JTF). In Oracle EBS 12.1.1 and 12.2.2, the "_TL" suffix identifies a table that holds the translated, user-facing text attributes for a corresponding "_B" base entity. Every row in JTF_STORES_TL corresponds to one base store record combined with one installed language, supplying the translated STORE_NAME and STORE_DESCRIPTION values that end users see in the UI, reports, and printed documents.

The table resides in the JTF schema and is documented as VALID in ETRM. Heuristically, the Data Vault classification for JTF_STORES_TL is satellite-leaning: the pattern of a composite key of STORE_ID plus LANGUAGE referencing a base entity, together with descriptive attributes, is characteristic of a satellite table attached to a hub (JTF_STORES_B, whose unique business key is STORE_ID). This classification is a modeling suggestion derived from the foreign-key structure rather than a documented data-warehouse design.

Key Information Stored

The table carries 13 documented columns. The most significant are:

• STORE_ID — the surrogate primary key component and foreign key to JTF_STORES_B.STORE_ID; each row belongs to one base store record.
• LANGUAGE — the language code of the translated content; combined with STORE_ID it forms the primary key JTF_STORES_TL_PK.
• STORE_NAME — the translated display name of the store, the primary business-visible attribute used in lists and lookups.
• STORE_DESCRIPTION — the translated descriptive text for the store.
• SOURCE_LANG — the language of the source (base) record from which the translation was derived, enabling correct fallback behavior.
• SECURITY_GROUP_ID — the security group that scopes visibility of the row; it carries a foreign key to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the edition identifier used for edition-based redefinition (EBR) in 12.2.x; it participates in the unique index JTF_STORES_TL_U1 (STORE_ID, LANGUAGE, ZD_EDITION_NAME).
• OBJECT_VERSION_NUMBER — optimistic locking counter maintained by the ORM/ADF layer.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS audit who-columns tracking row creation and modification.

The documented surrogate primary key is (STORE_ID, LANGUAGE). The unique index JTF_STORES_TL_U1 (STORE_ID, LANGUAGE, ZD_EDITION_NAME) is the business-key candidate that guarantees at most one translation row per store per language per edition.

Common Use Cases and Queries

JTF_STORES_TL is queried whenever a list of stores must be displayed in the user's language. A typical lookup joins the base and translation tables, filtering on the session language and security group:

SELECT b.store_id, t.store_name, t.store_description
FROM jtf_stores_b b, jtf_stores_tl t
WHERE b.store_id = t.store_id
AND t.language = USERENV('LANG')
AND b.security_group_id = :security_group_id;

Common scenarios include populating store LOVs in CRM and Field Service screens, generating multilingual reports, and verifying translation coverage. A data-quality query counts languages per store to detect missing translations:

SELECT store_id, COUNT(*) lang_cnt
FROM jtf_stores_tl GROUP BY store_id HAVING COUNT(*) < :expected_languages;

Because of EBR, 12.2.x production queries should honor the edition context; the ZD_EDITION_NAME predicate from the unique index is applied when editioning is enabled.

Related Objects

• JTF_STORES_B — the base table; joined on JTF_STORES_TL.STORE_ID = JTF_STORES_B.STORE_ID. This is the mandatory parent via foreign key.
• FND_SECURITY_GROUPS — referenced by JTF_STORES_TL.SECURITY_GROUP_ID for row-level security scoping.
• FND_LANGUAGES — supplies valid LANGUAGE and SOURCE_LANG codes used in the translation key.
• JTF_STORES_VL / related views — the language-joined views that applications typically query instead of the tables directly.
• JTF_LOCATIONS_B / _TL — companion CRM Foundation address tables frequently joined to stores for geo-reporting.
• FND_TERRITORIES — territory reference used alongside store location data.

Together these objects form the CRM Foundation reference-data layer through which Oracle EBS resolves localized store names for transactional and reporting applications.