Search Results ahl_simulation_plans_tl




Overview
Explore in AI Chat

Overview

AHL_SIMULATION_PLANS_TL is the translation table for simulation plans in the Oracle E-Business Suite Complex Maintenance Repair and Overhaul (AHL) module. In Oracle EBS, a "_TL" table stores the language-dependent, translatable descriptive attributes for a base ("_B") entity, while the base table holds the language-independent transactional and key data. Simulation plans define planned maintenance or overhaul scenarios that allow maintenance organizations to model "what-if" execution strategies before committing to actual work orders.

This object resides in the AHL schema and carries a VALID status in the ETRM 12.2.2 documentation. Its role is narrowly scoped: it holds the translated values of user-facing text columns — namely the simulation plan name and description — for each supported language. The heuristic Data Vault classification derived from the FK structure is satellite-leaning, which reflects its position as a dependent, attribute-bearing child of the base entity rather than an independent hub or a linking table. Under a Data Vault model, this table would naturally map to a satellite hanging off the AHL_SIMULATION_PLANS_B hub.

Key Information Stored

The physical schema documents twelve columns. The most significant are:

  • SIMULATION_PLAN_ID — Foreign key to AHL_SIMULATION_PLANS_B; the surrogate identifier of the parent simulation plan. This column participates in both the primary key and the unique business-key index.
  • LANGUAGE — The language code identifying the translation. Together with SIMULATION_PLAN_ID it forms the composite primary key AHL_SIMULATION_PLANS_TL_PK.
  • SIMULATION_PLAN_NAME — The translated name of the simulation plan, presented to users in the corresponding language.
  • DESCRIPTION — The translated long description of the simulation plan.
  • SOURCE_LANG — The source language from which the translation originated, used by the translation framework to track the base-language row.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org / security-group data partitioning.
  • ZD_EDITION_NAME — Editioning column supporting Oracle EBS Online Patching (adop) in Release 12.2, allowing edition-specific visibility of rows.

The surrogate/business key distinction is noteworthy: the primary key AHL_SIMULATION_PLANS_TL_PK covers (SIMULATION_PLAN_ID, LANGUAGE), while the unique index AHL_SIMULATION_PLANS_TL_U1 covers (SIMULATION_PLAN_ID, LANGUAGE, ZD_EDITION_NAME), making the latter the true business-key candidate for the editioning model. Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — follow the standard EBS WHO column convention.

Common Use Cases and Queries

The primary use case is retrieving simulation plan descriptive text in a specific language for display in OAF pages or reports. A typical join retrieves the translated name and description alongside the base entity:

  • SELECTING translated plan names: SELECT b.simulation_plan_id, tl.simulation_plan_name, tl.description FROM ahl_simulation_plans_b b, ahl_simulation_plans_tl tl WHERE b.simulation_plan_id = tl.simulation_plan_id AND tl.language = USERENV('LANG');
  • Identifying which plans have translations in a given language for localization completeness reporting.
  • Joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to enforce security-group filtering when building custom concurrent programs.
  • Filtering by ZD_EDITION_NAME in patching-aware queries for Release 12.2 environments.

Because this is a _TL table, direct DML is discouraged; translations should be maintained through the AHL simulation plan maintenance forms or the standard translation APIs to preserve integrity with the base entity.

Related Objects

The most significant objects related to this table are:

  • AHL_SIMULATION_PLANS_B — The base table holding language-independent simulation plan data; joined via SIMULATION_PLAN_ID.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID to support security partitioning.
  • AHL_SIMULATION_PLANS_TL_PK and AHL_SIMULATION_PLANS_TL_U1 — The primary and unique indexes enforcing row identity and business-key integrity.
  • AHL_SIMULATION_PLANS_* dependent entities — Downstream entities such as plan operations, resource assignments, and templates that ultimately resolve their descriptive text through this translation layer.
  • AHL simulation plan maintenance forms and translation APIs — The application-layer interfaces through which rows in this table are created and updated.

Consumers should always resolve translated attributes by joining to this table on SIMULATION_PLAN_ID and LANGUAGE rather than querying it in isolation, since it carries no independent business meaning.