Results for “so_results_tl”

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

Overview

SO_RESULTS_TL is the translation table for the base table SO_RESULTS_B within the Oracle Order Entry (OE) module. It is owned by the OE schema and holds the language-dependent (translatable) attributes of order result definitions recorded in the corresponding base table. In Oracle E-Business Suite 12.1.1 and 12.2.2, this follows the standard Oracle Applications multilingual design pattern, in which a "_B" table stores language-independent columns and a companion "_TL" table stores descriptive text for each installed language.

Each row in SO_RESULTS_TL represents one result record translated into one specific language. The object is classified heuristically as a standalone entity under the Data Vault modeling convention. This classification is offered as a modeling suggestion only: the table does not participate in any documented foreign-key relationship to other OE tables, so it would typically be modeled as an independent satellite (a descriptive structure keyed by the parent business key plus LANGUAGE) rather than as a hub or link. Its purpose is confined to serving as the translated-attribute satellite of SO_RESULTS_B.

Key Information Stored

The table contains ten documented columns. The most important of these are described below.

• RESULT_ID — Surrogate identifier for the result record. It forms the first component of the composite primary key and is the join column back to SO_RESULTS_B (and to any entity that references the base result).
• LANGUAGE — The language code of the translated row (for example, US for American English). It forms the second component of the composite primary key, uniquely identifying which language version of the result is stored.
• SOURCE_LANG — The language in which the source text was originally authored; used by the translation and NLS utilities to determine whether a translated value is current.
• NAME — The translated short name of the result. This is the primary user-visible business attribute.
• DESCRIPTION — The translated long description of the result, providing the fuller descriptive text displayed in order-processing inquiries and reports.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the translated row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Audit columns recording the most recent change to the row and the responsible user.
• LAST_UPDATE_LOGIN — The login identifier associated with the last update, used for audit and concurrency tracing.

The surrogate primary key is SO_RESULTS_TL_PK, defined on the composite of (RESULT_ID, LANGUAGE). No separate unique business-key index is documented beyond this primary key; the natural business identity of a row is effectively the combination of the result it describes and the language in which it is expressed.

Common Use Cases and Queries

Because SO_RESULTS_TL stores only descriptive text, the primary use cases are multilingual reporting and joined retrievals of result information. A typical query joins the translation table to the base table to return the language-appropriate name and description, for example selecting RESULT_ID, NAME, and DESCRIPTION from SO_RESULTS_TL where LANGUAGE equals the session language and RESULT_ID matches a supplied value. A parameterized join between SO_RESULTS_B and SO_RESULTS_TL on RESULT_ID, filtered by LANGUAGE, is the standard pattern for extracting the current-language description of a result.

Other practical patterns include verifying translation completeness (identifying results in the base table that lack a row for a given LANGUAGE), listing all language versions of a single result by selecting rows sharing a RESULT_ID, and auditing recent translation changes using LAST_UPDATE_DATE and LAST_UPDATED_BY. Because the table is small and read-mostly, it is commonly extracted into reporting or data-warehouse layers as a language dimension attached to the result entity.

Related Objects

The following objects are the most significant in relation to SO_RESULTS_TL:

• SO_RESULTS_B — the base table holding language-independent results; joined on RESULT_ID.
• SO_RESULTS_TL_PK — the composite primary key constraint on (RESULT_ID, LANGUAGE) that enforces one row per result per language.
• FND_LANGUAGES — the registered-language reference used to interpret the LANGUAGE and SOURCE_LANG codes.
• FND_USER — referenced for resolving CREATED_BY and LAST_UPDATED_BY values.
• OE Order Entry result-related views and concurrent programs — consumer objects that retrieve result names and descriptions through the base-and-translation join.

Within the OE module, SO_RESULTS_TL is thus a supporting translation satellite: it carries no transactional weight of its own and exists to supply localized text to any process or report that presents order result information.