Results for “fnd_stage_fn_parameters_tl”

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

Overview

FND_STAGE_FN_PARAMETERS_TL is the translation table for FND_STAGE_FN_PARAMETERS in the Oracle E-Business Suite environment, owned by the APPLSYS schema and belonging to the FND — Application Object Library product. It stores language-dependent, translatable attributes for staged function parameter definitions, allowing the same functional parameter (identified by application, function, and parameter) to carry distinct names and descriptions in each installed language. In Oracle EBS 12.1.1 and 12.2.2 this table supports the multilingual presentation layer of the staged functions framework, which underpins features such as function parameter configuration for forms-based and self-service functions.

From a Data Vault modeling perspective, and consistent with the heuristic classification mined from the foreign-key structure, this object behaves as a link rather than a pure hub or satellite: its primary key and uniqueness constraints span the business keys of the parent staged-function parameter entity together with the language dimension, so it associates a parameter with its translated text.

Key Information Stored

The table contains 13 documented columns. The most significant are the key and descriptive attributes:

• APPLICATION_ID — application owning the staged function; part of the surrogate primary key and a foreign key to FND_EXECUTABLES.
• FUNCTION_ID — the staged function to which the parameter belongs; jointly identifies the parent record.
• PARAMETER_ID — the internal identifier of the parameter being translated.
• PARAMETER_NAME — the translatable display name of the parameter, exposed in the business-key unique index.
• USER_PARAMETER_NAME — an alternate, user-facing translatable parameter label.
• DESCRIPTION — the language-specific descriptive text explaining the parameter's purpose.
• LANGUAGE — the language in which the translated values are held; part of both unique keys.
• SOURCE_LANG — the language from which the translation was derived, referenced against FND_LANGUAGES.
• CREATION_DATE / CREATED_BY and LAST_UPDATE_DATE / LAST_UPDATED_BY / LAST_UPDATE_LOGIN — standard WHO audit columns, with the user columns referencing FND_USER and the login column referencing FND_LOGINS.

The surrogate primary key is FND_STAGE_FN_PARAMETERS_TL_PK on (APPLICATION_ID, FUNCTION_ID, PARAMETER_ID, LANGUAGE). Three unique indexes act as business-key candidates: U1 on (APPLICATION_ID, FUNCTION_ID, PARAMETER_ID, LANGUAGE), U2 on (APPLICATION_ID, FUNCTION_ID, PARAMETER_NAME, LANGUAGE), and U3 on (APPLICATION_ID, FUNCTION_ID, USER_PARAMETER_NAME, LANGUAGE). The latter two enforce uniqueness of the translatable names within a function and language.

Common Use Cases and Queries

Typical usage includes retrieving localized parameter names and descriptions for a given staged function, verifying translation coverage across installed languages, and auditing translation metadata. A representative query joining the translation table to its language reference is:

• SELECT t.application_id, t.function_id, t.parameter_id, t.parameter_name, t.user_parameter_name, t.description, t.language FROM fnd_stage_fn_parameters_tl t WHERE t.application_id = :app_id AND t.function_id = :func_id AND t.language = USERENV('LANG');
• Reporting translation gaps: compare base rows in FND_STAGE_FN_PARAMETERS against FND_STAGE_FN_PARAMETERS_TL where no matching LANGUAGE row exists.
• Audit queries joining CREATED_BY or LAST_UPDATED_BY to FND_USER to establish who maintained a given translation.

Related Objects

• FND_STAGE_FN_PARAMETERS — the base (untranslated) table for which this object holds translations; joined on APPLICATION_ID, FUNCTION_ID, and PARAMETER_ID.
• FND_EXECUTABLES — referenced by APPLICATION_ID and FUNCTION_ID; defines the executable associated with the staged function.
• FND_LANGUAGES — referenced twice, via LANGUAGE and SOURCE_LANG, supplying the installed and source language definitions.
• FND_USER — referenced through CREATED_BY and LAST_UPDATED_BY for WHO audit attribution.
• FND_LOGINS — referenced through LAST_UPDATE_LOGIN, linking the update to a user session.
• FND_FUNCTIONS / FND_FORM_FUNCTIONS — the broader function registration framework that consumes staged function parameter metadata.