Results for “simulation_plan_id”

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

Overview

Within Oracle E-Business Suite, the view APPS.AHL_PLAN_VISITS_V belongs to the AHL product family, Complex Maintenance Repair and Overhaul (CMRO). It exposes a consolidated, read-only projection that links simulation plans to the visits generated against them. The ETRM documentation describes it concisely as a view that "stores the query relates to simulation plans and visit detail information." In practice it functions as a reporting and integration bridge: planners and external systems can retrieve plan-level attributes together with a count of the planning-stage visits belonging to each plan, without navigating the underlying normalized tables directly.

Because it is a view and not a table, no data is persisted within it; every access re-executes the defining query against the base objects. This makes it safe for ad-hoc reporting but means its output reflects the current transactional state of the underlying CMRO entities at query time. The view resides in the APPS schema and is documented as VALID in both 12.1.1 and 12.2.2.

Underlying Base Objects

The documented 12.2.2 metadata lists the objects referenced by the view definition:

• AHL_SIMULATION_PLANS_VL — the multilingual view over simulation plans, supplying the plan identity, name, version, and primary flag.
• AHL_VISITS_B — the base table holding visit records, joined to the plan by SIMULATION_PLAN_ID.
• AHL_VISITS_VL — a multilingual view over visits, referenced in the scalar sub-query that computes the visit count.
• AHL_UNIT_CONFIG_HEADERS — configuration header synonyms referenced by the CMRO data model.
• ORG_ORGANIZATION_DEFINITIONS — the organization flexfield view used for operating-unit context.
• HR_GENERAL, HR_SECURITY, MO_GLOBAL — standard Oracle packages that provide security and multi-org filtering semantics inherited by secured views.

Structurally, the view is driven by a join between AHL_SIMULATION_PLANS_VL and AHL_VISITS_B with an outer-join condition (ASP L.SIMULATION_PLAN_ID = AVTB.SIMULATION_PLAN_ID(+)), ensuring plans with no associated visits are still returned. The correlated scalar sub-query against AHL_VISITS_VL counts visits where the plan matches, TEMPLATE_FLAG = 'N', and STATUS_CODE = 'PLANNING'.

Key Columns

• SIMULATION_PLAN_ID — primary identifier of the simulation plan; the join key across all CMRO plan-related objects.
• SIMULATION_PLAN_NAME — the user-facing name of the plan.
• OBJECT_VERSION_NUMBER — optimistic locking version; useful for detecting whether a plan record has been modified.
• PRIMARY_PLAN_FLAG — indicates whether the plan is the primary plan for its context.
• NUMBER_OF_VISITS — a computed count of non-template visits in PLANNING status, produced by the scalar sub-query.

Common Use Cases and Queries

Typical uses include simulation plan reporting, workload estimation, and integration feeds that require a roll-up of visits per plan. A representative query is:

• SELECT SIMULATION_PLAN_ID, SIMULATION_PLAN_NAME, PRIMARY_PLAN_FLAG, NUMBER_OF_VISITS FROM APPS.AHL_PLAN_VISITS_V WHERE NUMBER_OF_VISITS > 0 ORDER BY SIMULATION_PLAN_NAME;
• SELECT SIMULATION_PLAN_ID, OBJECT_VERSION_NUMBER FROM APPS.AHL_PLAN_VISITS_V WHERE PRIMARY_PLAN_FLAG = 'Y';

Note that the view already contains DISTINCT semantics on SIMULATION_PLAN_ID and applies the 'PLANNING' status filter inside the sub-query, so NUMBER_OF_VISITS reflects only planned (not executed or template) visits. Supplements to this metadata should be validated against the live view text in the target instance.