Search Results ahl_simulation_plans_b_pk

Overview

In Oracle E-Business Suite, the table AHL.AHL_SIMULATION_PLANS_B is a base (non-translated) table within the AHL — Complex Maintenance Repair and Overhaul product family. It stores the master records for simulation plans, which are used to model and evaluate maintenance, repair, and overhaul scenarios before committing them to live execution. Each row represents a single simulation plan header, identified by the surrogate primary key SIMULATION_PLAN_ID, and is referenced by dependent translation and visit tables.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. This suggests that the table functions primarily as a hub of business keys and stable identifiers, with descriptive and state attributes distributed to satellites. This classification is a modeling suggestion only; in native EBS form, the table is a conventional transactional base table with standard WHO columns and a multi-lingual companion table.

Key Information Stored

The documented physical schema for release 12.2.2 contains 29 columns. The most significant are:

• SIMULATION_PLAN_ID — the surrogate primary key and the table's central identifier. It is also the join key to every related object.
• ZD_EDITION_NAME — the editioning column. Together with SIMULATION_PLAN_ID, it forms the unique index AHL_SIMULATION_PLANS_U1, making this pair the documented business-key candidate.
• OBJECT_VERSION_NUMBER — supports optimistic locking for concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns.
• PRIMARY_PLAN_FLAG — indicates whether the simulation plan is the primary plan for its context.
• SECURITY_GROUP_ID — the operating unit / security context, referencing FND_SECURITY_GROUPS.
• STATUS_CODE — the lifecycle status of the simulation plan.
• SIMULATION_TYPE — classifies the nature of the simulation.
• LAST_BUE_RUN — records the last Business Unit Engine run associated with the plan.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension columns.

Common Use Cases and Queries

Typical uses include reporting on active simulation plans, listing plans by status or simulation type, and joining plan headers to their translated names and associated visits.

• Retrieve plans for a given operating unit:

  SELECT simulation_plan_id, status_code, simulation_type
  FROM   ahl.ahl_simulation_plans_b
  WHERE  security_group_id = :p_security_group_id;

• Join to the translation table for display names:

  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');

• Identify the primary plan:

  SELECT simulation_plan_id
  FROM   ahl.ahl_simulation_plans_b
  WHERE  primary_plan_flag = 'Y';

These patterns support dashboards, planning reconciliation, and audit of status transitions.

Related Objects

• AHL.AHL_SIMULATION_PLANS_TL — translation table; join on SIMULATION_PLAN_ID. Holds language-specific plan text.
• AHL.AHL_VISITS_B — visit base table; join on SIMULATION_PLAN_ID. Links simulation plans to visits.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID to enforce security context.
• AHL.AHL_SIMULATION_PLANS_B_PK — the primary key constraint on SIMULATION_PLAN_ID.
• AHL.AHL_SIMULATION_PLANS_U1 — unique index on (SIMULATION_PLAN_ID, ZD_EDITION_NAME).

Together, these objects form the core simulation planning data model within AHL, with AHL_SIMULATION_PLANS_B acting as the central hub referenced by translations and visits.