Search Results ahl_simulation_plans_u1

Overview

The AHL.AHL_SIMULATION_PLANS_B table is a core transactional data object within the Oracle E-Business Suite (EBS) Asset Lifecycle Management (AHL) schema, which underpins the Advanced Product Catalog and Complex Maintenance, Repair, and Overhaul (CMRO) functionality. Specifically, this table stores information about simulation plans — modeling constructs used by maintenance and reliability engineers to evaluate alternative maintenance strategies, resource loading, and turnaround scenarios against a primary plan without affecting production data. It is a base table (the _B suffix indicates the base, non-translated entity), and its descriptive fields are exposed through the corresponding translated table AHL_SIMULATION_PLANS_TL.

From a Data Vault modeling perspective, the metadata classifies this object as hub-leaning. This is a modeling suggestion: SIMULATION_PLAN_ID behaves as a durable business key (hub), while descriptive and audit attributes such as PRIMARY_PLAN_FLAG, STATUS_CODE, and SIMULATION_TYPE would typically be separated into satellite structures in a dimensional warehouse design. In the native EBS schema the table is resident in the APPS_TS_TX_DATA tablespace with a PCT Free of 10.

Key Information Stored

The table contains 29 documented columns. The principal identifiers and control columns are:

• SIMULATION_PLAN_ID — NUMBER, the surrogate primary key and unique identifier for each simulation plan. This is also the leading column of the unique index AHL_SIMULATION_PLANS_U1.
• OBJECT_VERSION_NUMBER — NUMBER, an optimistic locking sequence used by the framework to detect concurrent updates.
• PRIMARY_PLAN_FLAG — VARCHAR2, distinguishes whether the record represents a simulation plan or a primary plan.
• SIMULATION_TYPE — VARCHAR2, classifies the nature of the simulation plan (e.g., predictive or what-if scenario).
• STATUS_CODE — VARCHAR2, the lifecycle status of the plan.
• LAST_BUE_RUN — timestamp/identifier for the last Business Event or batch execution associated with the plan.
• SECURITY_GROUP_ID — NUMBER, used in application hosting and multi-tenant deployments; foreign-keyed to FND_SECURITY_GROUPS.
• ZD_EDITION_NAME — the editioning column supporting Oracle EBS Online Patching (Edition-Based Redefinition) in 12.2.x.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — a descriptive flexfield (DFF) structure defined by ATTRIBUTE_CATEGORY, with fifteen 150-character segment columns for customer extensions.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN, providing full auditability.

The unique index AHL_SIMULATION_PLANS_U1 is defined on (SIMULATION_PLAN_ID, ZD_EDITION_NAME), reflecting the 12.2 editioning-aware business key. In 12.1.1 the same index resolves to the surrogate key alone, since editioning is not present.

Common Use Cases and Queries

Simulation plans are queried when maintenance planners compare projected resource utilization, cost, or scheduling outcomes across alternative strategies before committing changes to the live plan. Typical reporting includes plan inventory, status dashboards, and DFF-driven user-defined attributes.

• Retrieve all active simulation plans for a given status: SELECT simulation_plan_id, simulation_type, status_code FROM ahl.ahl_simulation_plans_b WHERE status_code = 'ACTIVE';
• List only simulation (non-primary) plans: SELECT simulation_plan_id FROM ahl.ahl_simulation_plans_b WHERE primary_plan_flag = 'N';
• Join to the translated table for user-facing names, restricting by language: SELECT b.simulation_plan_id, t.simulation_plan_name FROM ahl.ahl_simulation_plans_b b, ahl.ahl_simulation_plans_tl t WHERE b.simulation_plan_id = t.simulation_plan_id AND t.language = USERENV('LANG');
• Audit recently modified plans using the Who columns: SELECT * FROM ahl.ahl_simulation_plans_b WHERE last_update_date > SYSDATE - 7;
• Report on DFF extensions where populated: SELECT simulation_plan_id, attribute_category, attribute1, attribute2 FROM ahl.ahl_simulation_plans_b WHERE attribute_category IS NOT NULL;

Related Objects

The following objects are the most significant dependents and references based on the documented FK relationships:

• AHL.AHL_SIMULATION_PLANS_TL — the translated (language) table; joined on SIMULATION_PLAN_ID. It carries the descriptive, translatable name and description columns.
• AHL.AHL_VISITS_B — visit base records reference a simulation plan via SIMULATION_PLAN_ID. This links planned maintenance visits to the scenario that generated them.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs hosting and security-group partitioning.
• AHL_SIMULATION_PLANS_B_PK — the primary-key constraint enforcing uniqueness on SIMULATION_PLAN_ID.
• AHL_SIMULATION_PLANS_U1 — the unique index (SIMULATION_PLAN_ID, ZD_EDITION_NAME) supporting edition-aware lookups in 12.2.2.

Application-level access is typically performed through the CMRO and Asset Maintenance UI or via the AHL public APIs that manage simulation plan creation, update, and deletion, rather than through direct DML on the base table.