Results for “wsh_itm_parameter_setups_tl”

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

Overview

WSH_ITM_PARAMETER_SETUPS_TL is a translation table within the Oracle E-Business Suite Shipping Execution (WSH) module. It stores the translatable descriptive information for item parameter setups used by the Shipping Execution application. In an Oracle EBS multilingual implementation, Oracle separates base data from translatable text to avoid duplicating non-linguistic attributes across languages. This table holds only the language-dependent attributes — specifically the description and user-facing parameter name — while the non-translatable attributes reside in the companion base table, WSH_ITM_PARAMETER_SETUPS_B. The suffix "_TL" is the standard Oracle naming convention for such translation entities.

Under the Data Vault classification heuristic mined from the foreign-key structure, this object is characterized as satellite-leaning. As a modeling suggestion, this means it functions as a dependent, context-bearing entity that hangs off a parent (business-key) record rather than serving as a hub or a link. Each row enriches a base record with language-specific descriptive text, consistent with a satellite role. The table is owned by the WSH schema and is marked VALID in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table is documented with eleven columns, but the core identity and descriptive attributes are the most significant:

• PARAMETER_ID — The identifier of the parent parameter setup. This is the foreign key column that links to WSH_ITM_PARAMETER_SETUPS_B and is part of the composite primary key. It is the business-meaningful join key between the translation row and its base record.
• LANGUAGE — The language code of the translated text in this row. It is the second component of the composite primary key and determines which linguistic value the row supplies.
• SOURCE_LANG — The source language from which the translated description originated, used to track translation lineage.
• DESCRIPTION — The translated description of the parameter setup, the principal human-readable text stored in this table.
• USER_PARAMETER_NAME — The translated, user-facing name of the parameter, enabling the parameter to be displayed and understood in the session language.
• ZD_EDITION_NAME — The edition name column supporting Oracle's Edition-Based Redefinition (EBR) capability. It participates in the unique index WSH_ITM_PARAMETER_SETUPS_TL_U1.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture standard Oracle WHO column audit information.

The surrogate/composite primary key is defined by WSH_ITM_PARAMETER_SETUPS_TL_PK over (LANGUAGE, PARAMETER_ID). A documented unique index, WSH_ITM_PARAMETER_SETUPS_TL_U1 over (PARAMETER_ID, LANGUAGE, ZD_EDITION_NAME), serves as the business-key candidate and enforces that a parameter has at most one translation row per language per edition.

Common Use Cases and Queries

Translation tables are typically queried in conjunction with their base table to resolve descriptive text for reporting, validation, and user interface display. A representative join retrieves the translated parameter name and description for a given parameter identifier:

• Multilingual reporting — Retrieve parameter descriptions filtered by LANGUAGE to produce reports in a specific locale.
• Data validation — Confirm that every parameter in WSH_ITM_PARAMETER_SETUPS_B has a corresponding translation row for each installed language.
• Setup auditing — Compare DESCRIPTION and USER_PARAMETER_NAME values across languages to verify translation completeness.

A sample SQL pattern joining on the foreign key column is:

SELECT b.parameter_id, tl.language, tl.user_parameter_name, tl.description
FROM wsh_itm_parameter_setups_b b, wsh_itm_parameter_setups_tl tl
WHERE b.parameter_id = tl.parameter_id
AND tl.language = USERENV('LANG');

Related Objects

The table's relationships in the documented metadata are centered on its parent base table, supplemented by the standard Oracle translation infrastructure:

• WSH_ITM_PARAMETER_SETUPS_B — The base table joined via PARAMETER_ID → WSH_ITM_PARAMETER_SETUPS_B.PARAMETER_ID. This is the primary and only foreign-key relationship documented for this translation table.
• WSH_ITM_PARAMETER_SETUPS_TL_PK — The primary key constraint over (LANGUAGE, PARAMETER_ID).
• WSH_ITM_PARAMETER_SETUPS_TL_U1 — The unique index over (PARAMETER_ID, LANGUAGE, ZD_EDITION_NAME), serving as the business-key candidate.

Because the metadata documents only one explicit foreign key, additional dependent objects such as language-aware views and Shipping Execution parameter APIs should be verified against the specific 12.1.1 or 12.2.2 instance, as their definitions are not captured in the provided ETRM record.