Search Results ahl_simulation_plans_tl_u1




Overview

The table AHL.AHL_SIMULATION_PLANS_TL is a translation table within the Oracle E-Business Suite (EBS) Applications product family, owned by the AHL schema (Oracle Enterprise Asset Management / eAM and related applications). Its purpose is to store translated or language-specific column values for simulation plan records, thereby enabling multi-language presentation of simulation plan names and descriptions to end users operating in different language contexts. The object resides in the APPS_TS_TX_DATA tablespace and is classified as VALID in the ETRM 12.2.2 documentation. The companion base table, AHL.AHL_SIMULATION_PLANS_B, holds the language-independent attributes, while this "_TL" suffix table holds the denormalized, language-dependent textual attributes.

From a Data Vault modeling perspective, ETRM's heuristic classification places this object as satellite-leaning. This reflects its role as a descriptive extension of the core simulation plan entity: it carries the translated descriptive context (name, description, source language) keyed by the business identifier plus language, rather than introducing new business entities or relationships of its own.

Key Information Stored

The table's most significant columns are as follows:

  • SIMULATION_PLAN_ID (NUMBER) — Foreign key to AHL_SIMULATION_PLANS_B, identifying the parent simulation plan. Combined with LANGUAGE, it forms the business-key candidate.
  • LANGUAGE (VARCHAR2) — The defined language code for the row's translated columns; the discriminator that distinguishes one translation of a simulation plan from another.
  • SIMULATION_PLAN_NAME (VARCHAR2, 80) — The unique identifier / display name for the simulation plan in the given language.
  • DESCRIPTION (VARCHAR2, 4000) — The translated descriptive text for the simulation plan.
  • SOURCE_LANG (VARCHAR2) — Indicates the actual source (base) language of the translated columns.
  • SECURITY_GROUP_ID (NUMBER) — Used in application hosting and multi-tenant security isolation; foreign key to FND_SECURITY_GROUPS.
  • Standard Who columnsLAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, which capture audit and concurrency information for each row.

The surrogate primary key is defined by the constraint AHL_SIMULATION_PLANS_TL_PK on (SIMULATION_PLAN_ID, LANGUAGE). ETRM additionally documents the unique index AHL_SIMULATION_PLANS_TL_U1 on (SIMULATION_PLAN_ID, LANGUAGE, ZD_EDITION_NAME), which serves as the business-key candidate and supports the editioning scheme introduced in Release 12.2. Note that ZD_EDITION_NAME is present in the documented physical schema (12 columns) though not shown in the original index excerpt.

Common Use Cases and Queries

Because this table is a translation table, the prevailing access pattern is a language-filtered join to the base table to retrieve the plan name and description appropriate to the logged-in session language. Typical reporting and integration scenarios include:

  • Extracting the translated simulation plan name for multilingual UI rendering or document generation.
  • Auditing which languages have translations available for a given plan (completeness checks).
  • Populating downstream data warehouse or reporting layers with localized labels.

A representative query pattern joins the translation row to its base record, honoring the session language or a fallback to SOURCE_LANG:

SELECT b.simulation_plan_id,
       tl.language,
       tl.simulation_plan_name,
       tl.description
FROM   ahl.ahl_simulation_plans_b  b,
       ahl.ahl_simulation_plans_tl tl
WHERE  b.simulation_plan_id = tl.simulation_plan_id
AND    tl.language = &session_language;

For a complete listing independent of language, the documented SELECT statement from ETRM can be used directly against all columns of the table.

Related Objects

  • AHL.AHL_SIMULATION_PLANS_B — The base (language-independent) simulation plans table; joined via SIMULATION_PLAN_ID. This is the principal parent.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for application hosting / security partitioning.
  • APPS.AHL_SIMULATION_PLANS_TL — The synonym / view layer exposed to the APPS schema that references this object; the primary consumption path for application SQL and concurrent programs.
  • AHL_SIMULATION_PLANS_TL_PK — Primary key constraint on (SIMULATION_PLAN_ID, LANGUAGE).
  • AHL_SIMULATION_PLANS_TL_U1 — Unique index (business-key candidate) on (SIMULATION_PLAN_ID, LANGUAGE, ZD_EDITION_NAME).

Additional reference relationships flow from the parent AHL_SIMULATION_PLANS_B entity toward simulation, scheduling, and work management objects within the AHL module, but the translation table itself does not introduce further foreign-key dependencies beyond those documented above.