Results for “ahl_simulation_plans_vl”

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

Overview

The AHL_SIMULATION_PLANS_VL view is a public, language-aware database object owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is delivered as part of the AHL product family — Complex Maintenance, Repair and Overhaul (CMRO) — which supports the definition and simulation of maintenance and overhaul plans for complex assets. The _VL suffix identifies this as a "view with language," a standard Oracle EBS construct in which a multilingual (MLS) translation table is joined to the base entity table so that users automatically see descriptive text in their session language rather than in all installed languages.

The view's declared purpose is to present the denormalized, language-resolved representation of simulation plans by combining the base entity attributes stored in AHL_SIMULATION_PLANS_B with the translatable name and description columns held in AHL_SIMULATION_PLANS_TL. In Oracle EBS reporting and integration, such views are the recommended access layer: they hide the underlying multi-table storage model, enforce the session-language filter, and expose a flat row per simulation plan that can be queried directly by BI Publisher reports, OAF pages, concurrent programs, PL/SQL APIs, and external integration interfaces via the APPS schema.

Underlying Base Objects

Documented ETRM metadata for Release 12.2.2 confirms that the view is defined over two synonym-referenced base objects: AHL_SIMULATION_PLANS_B and AHL_SIMULATION_PLANS_TL. The _B table stores the non-translatable "base" or entity-level columns of a simulation plan — the primary key, WHO audit columns, the primary plan indicator, the security group, and the DFF attribute columns. The _TL table stores the translatable columns, namely SIMULATION_PLAN_NAME and DESCRIPTION, keyed by SIMULATION_PLAN_ID and LANGUAGE.

The view joins the two tables on SIMULATION_PLAN_ID and restricts the translation row with the predicate T.LANGUAGE = USERENV('LANG'). Consequently, exactly one row is returned per simulation plan for the language of the current session. This is the canonical Oracle EBS MLS join pattern, and the view is therefore read-only for practical purposes.

Key Columns

• ROW_ID — the ROWID of the base-table row, used by EBS framework tools (e.g., OAF and Forms) for optimistic locking and row identification.
• SIMULATION_PLAN_ID — the primary key of the simulation plan; the join key between the base and translation tables.
• OBJECT_VERSION_NUMBER — the standard EBS concurrency control token.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the WHO audit columns populated automatically by EBS.
• PRIMARY_PLAN_FLAG — indicates whether the record is the primary simulation plan for its context.
• SECURITY_GROUP_ID — supports multi-organization / security group data segregation.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the extensible Descriptive Flexfield (DFF) columns available for customer-specific attributes.
• SIMULATION_PLAN_NAME — the translatable plan name, resolved for the session language from AHL_SIMULATION_PLANS_TL.
• DESCRIPTION — the translatable long description of the plan, also resolved from the translation table.

Common Use Cases and Queries

The view is typically queried to list simulation plans with their user-visible names for reporting, LOV population, or integration extracts. A representative query is:

• SELECT simulation_plan_id, simulation_plan_name, description, primary_plan_flag FROM apps.ahl_simulation_plans_vl WHERE primary_plan_flag = 'Y' ORDER BY simulation_plan_name;
• SELECT simulation_plan_id, simulation_plan_name FROM apps.ahl_simulation_plans_vl WHERE UPPER(simulation_plan_name) LIKE UPPER(:p_name)||'%'; — used to drive a name-based LOV or search page.
• SELECT v.simulation_plan_name, v.description, v.creation_date, v.created_by FROM apps.ahl_simulation_plans_vl v WHERE v.last_update_date >= :p_since; — used by delta-extract interfaces to synchronize plan definitions with external systems.

Because the view applies USERENV('LANG'), callers should set the session language (e.g., via NLS_LANG or FND_GLOBAL initialization) before querying so that names and descriptions return in the expected locale. Where the DFF attributes are required, extend the SELECT with the relevant ATTRIBUTEn columns.