Results for “ams_iba_pl_parameters_tl”

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

Overview

The AMS_IBA_PL_PARAMETERS_TL table resides in the AMS (Marketing) schema and stores language-specific, translatable text for parameter definitions associated with Interactive Branding (IBA) personalization and site configuration in Oracle E-Business Suite. The "_TL" suffix designates this as a translation table, holding multilingual versions of attribute names and descriptions that are presented to end users based on their session language. In Oracle EBS 12.1.1 and 12.2.2, this table supports the One-to-Many multilingual architecture used throughout the applications, where base transactional or definitional data sits in a "_B" table and translatable attributes reside in the corresponding "_TL" table keyed by language.

In Data Vault modeling terms, the mined foreign-key structure suggests a satellite-leaning classification. The table behaves as a dependent satellite attached to the base definitions table AMS_IBA_PL_PARAMETERS_B, carrying descriptive, language-dependent attributes rather than acting as an independent hub or linking entity.

Key Information Stored

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

• PARAMETER_ID — The surrogate identifier linking each translated row back to the base definition in AMS_IBA_PL_PARAMETERS_B. It forms part of the composite primary key and is the primary foreign-key join column.
• LANGUAGE — The language code identifying the locale of the translated text. Together with PARAMETER_ID, it constitutes the AMS_IBA_PL_PARAMETERS_TL_PK primary key.
• NAME — The language-specific display name of the parameter definition.
• DESCRIPTION — The translated descriptive text explaining the parameter's purpose.
• SOURCE_LANG — Indicates the source language from which translations were derived, supporting the multilingual translation workflow.
• ZD_EDITION_NAME — The editioning column introduced under the Edition-Based Redefinition (EBR) model in 12.2.x, supporting online patching.
• SECURITY_GROUP_ID — Restricts visibility of rows under Oracle's Multi-Org/security group access control.
• Audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN track the who/when of each row's lifecycle.
• OBJECT_VERSION_NUMBER — Supports optimistic locking during concurrent updates.

The business-key candidate is defined by the unique index AMS_IBA_PL_PARAMETERS_TL_U1 (PARAMETER_ID, LANGUAGE, ZD_EDITION_NAME), ensuring one translation row per parameter, per language, per edition.

Common Use Cases and Queries

Typical usage involves joining the translation table to its base to resolve localized parameter labels for reporting, personalization setup, or interface rendering. A representative query:

• SELECT b.parameter_id, t.name, t.description FROM ams.ams_iba_pl_parameters_b b, ams.ams_iba_pl_parameters_tl t WHERE b.parameter_id = t.parameter_id AND t.language = USERENV('LANG') AND t.zd_edition_name = 'SET1';

Common scenarios include verifying translation completeness across installed languages, auditing parameter definitions for a given site, and troubleshooting display issues where a parameter name appears in the base language only. Reporting extracts frequently key on LANGUAGE to measure translation coverage, while the SECURITY_GROUP_ID column supports segregated querying in multi-org deployments.

Related Objects

• AMS_IBA_PL_PARAMETERS_B — The base table holding language-independent parameter definitions; joined via PARAMETER_ID.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID to enforce access control.
• FND_LANGUAGES — Not formally referenced but functionally related, supplying the valid LANGUAGE codes used in the translation rows.
• AMS_IBA_PL_PARAMETERS_TL_PK / _U1 — The primary key constraint and unique index enforcing translation uniqueness.

Because translation tables are tightly bound to their base counterparts, any application logic, concurrent program, or view that surfaces parameter definitions should reference both tables to deliver correctly localized output.