Results for “location_type_description”

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

Overview

JTF_LOC_TYPES_TL is the translation (language) table for location types within the JTF – CRM Foundation product of Oracle E-Business Suite. It stores the translated columns for each location type defined in the base table JTF_LOC_TYPES_B, enabling multi-language display of location type names and descriptions across CRM applications. In Oracle EBS 12.1.1 and 12.2.2, this table follows the standard "_TL" translation pattern: the base table holds language-independent attributes keyed by LOCATION_TYPE_ID, while the _TL table holds the language-dependent text keyed by LOCATION_TYPE_ID and LANGUAGE.

From a Data Vault modeling perspective, the FK-derived heuristic classifies JTF_LOC_TYPES_TL as satellite-leaning. It is a dependent, descriptive child of the base entity JTF_LOC_TYPES_B, capturing attribute history per language. Note that this classification is a modeling suggestion only; the object is a standard EBS translation table, not a native Data Vault construct.

Key Information Stored

The table contains 12 documented columns. The most significant are:

• LOCATION_TYPE_ID – Surrogate/foreign key linking to the base table JTF_LOC_TYPES_B; identifies which location type this translation applies to.
• LANGUAGE – The language code for this translated row (e.g., US, AR, FR). Part of the composite primary key.
• LOCATION_TYPE_NAME – The translated, user-facing name of the location type.
• LOCATION_TYPE_DESCRIPTION – The translated long description of the location type.
• SOURCE_LANG – Indicates the source language of the row, used in EBS multilanguage installations.
• SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, supporting multi-org/security-group data partitioning.
• ZD_EDITION_NAME – Editioning column used in 12.2 online patching, included in both unique indexes.
• Audit columns – LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

The primary key JTF_LOC_TYPES_TL_PK is defined on (LOCATION_TYPE_ID, LANGUAGE). Business-key candidates include unique indexes JTF_LOC_TYPES_TL_U1 on (LOCATION_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), which is the edition-aware version of the PK, and JTF_LOC_TYPES_TL_U2 on (LOCATION_TYPE_NAME, LANGUAGE, ZD_EDITION_NAME), which enforces uniqueness of the translated name per language.

Common Use Cases and Queries

The primary use case is retrieving translated location type labels for CRM UI, reporting, and integration. A typical join retrieves the localized name for a given language:

• SELECT tl.location_type_name FROM jtf.jtf_loc_types_tl tl WHERE tl.location_type_id = :id AND tl.language = USERENV('LANG');
• Joining base and translation: SELECT b.location_type_id, tl.location_type_name FROM jtf_loc_types_b b, jtf_loc_types_tl tl WHERE b.location_type_id = tl.location_type_id AND tl.language = 'US';
• Listing all translations for a location type for localization audits.

Reporting scenarios include validating completeness of translations across all installed languages, and extracting reference data for downstream CRM, TCA, or external systems.

Related Objects

• JTF_LOC_TYPES_B – Base table; joined via LOCATION_TYPE_ID. Parent of the FK relationship.
• JTF_LOC_TYPES_VL – Typical EBS VL view combining base and _TL columns for translations.
• FND_SECURITY_GROUPS – Referenced via SECURITY_GROUP_ID for secured access.
• JTF_LOC_TYPES_TL_PK / _U1 / _U2 – Primary key and unique indexes enforcing integrity.
• FND_LANGUAGES – Reference for the LANGUAGE column values.