Search Results ahl_visit_types_b_u1




Overview
Explore in AI Chat

Overview

AHL.AHL_VISIT_TYPES_B is the base (transaction) table that defines the visit type master data used by Oracle Enterprise Asset Management (eAM) and the Complex Maintenance, Repair and Overhaul (CMRO) / Fleet Maintenance modules in Oracle E-Business Suite Release 12.1.1 and 12.2.2. A visit type describes a reusable template for a maintenance visit — an inspection, service call, or scheduled maintenance activity that can be attached to an asset, a work order, or a maintenance program. The _B suffix indicates this is the base table in the standard Oracle EBS MLS (Multi-Lingual Support) table pair; it holds language-independent attributes and is normally joined to AHL_VISIT_TYPES_TL for translated name and description columns.

The record belongs to the AHL schema (the eAM/AHL product schema) and is stored in the APPS_TS_TX_DATA tablespace, indicating it is treated as transaction-level configuration data rather than reference (seed) data. Based on the foreign key and index structure mined from the ETRM metadata, the table is best modelled as a standalone (hub-like) entity: it has no inbound foreign keys and no foreign key columns pointing to other AHL business entities, so it forms an independent reference/master dimension rather than a link or satellite of another hub.

Key Information Stored

The table contains 32 documented columns. The most significant are:

  • VISIT_TYPE_ID (NUMBER) — the surrogate primary key and unique identifier for each visit type. It is enforced by the unique index AHL_VISIT_TYPES_B_U1, which the metadata identifies as the sole unique key and the principal surrogate candidate.
  • VISIT_TYPE_CODE (VARCHAR2(30)) — the human-readable business code (for example, an inspection or service code) used to identify the visit type in user interfaces and integrations.
  • SERVICE_CATEGORY_CODE (VARCHAR2(30)) — the service category to which the visit type is assigned, allowing visits to be grouped by service discipline.
  • ESTIMATED_DURATION (NUMBER) — the planned duration for the visit type, used for capacity and scheduling calculations.
  • LINKED_VISIT_TYPE_ID (NUMBER) — self-referencing identifier that ties a draft visit type back to the visit type from which it was created.
  • TRANSIT_TYPE_FLAG (VARCHAR2) — flag indicating whether the visit type represents transit-related activity.
  • COMPONENT_VISIT_FLAG (VARCHAR2) — flag indicating whether the visit applies at component level.
  • SECURITY_GROUP_ID (NUMBER) — foreign key to FND_SECURITY_GROUPS, enforcing Oracle EBS security grouping on the record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 (VARCHAR2(150)) — the descriptive flexfield (DFF) structure and segment columns, available for client-specific extension of visit type records.
  • LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE#1 — the standard WHO audit columns.
  • OBJECT_VERSION_NUMBER#1 and MC_ID#1 — concurrency and multi-currency/organization control columns applied by the EBS runtime.

The user search term ahl_visit_types_b_u1 refers directly to the unique index on VISIT_TYPE_ID documented above, which is the primary lookup path into this table.

Common Use Cases and Queries

Typical usage includes validating visit type configuration during eAM implementation, reporting on visit types by service category, and reconciling estimated durations against scheduled maintenance plans.

  • Look up a visit type by code: SELECT visit_type_id, visit_type_code, service_category_code, estimated_duration FROM ahl_visit_types_b WHERE visit_type_code = :code;
  • List visit types with translated names: join AHL_VISIT_TYPES_TL on VISIT_TYPE_ID and filter on LANGUAGE to retrieve the display name.
  • Report by service category: SELECT service_category_code, COUNT(*), AVG(estimated_duration) FROM ahl_visit_types_b GROUP BY service_category_code;
  • Identify draft/derived visit types: query rows where LINKED_VISIT_TYPE_ID IS NOT NULL.
  • Security-scoped extraction: filter on SECURITY_GROUP_ID to honour EBS security group assignments in custom reports.

Related Objects

The documented foreign key from SECURITY_GROUP_ID to FND_SECURITY_GROUPS is the primary outward dependency. The most significant related objects are:

  • AHL.AHL_VISIT_TYPES_TL — the translated (MLS) table joined on VISIT_TYPE_ID; carries name/description per language.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to resolve security group membership.
  • AHL.AHL_VISIT_TYPES_B itself via LINKED_VISIT_TYPE_ID — a self-join used to trace draft-to-source visit type lineage.
  • AHL visit/work order definition tables that consume VISIT_TYPE_ID as a lookup when building maintenance visit schedules.
  • Descriptive flexfield metadata in FND_DESCR_FLEX_COL_USAGE / FND_DESCR_FLEX_DEFN_TL, resolved through ATTRIBUTE_CATEGORY.

Because no inbound foreign keys were documented, dependent objects derive their relationship through application logic rather than database constraints, so joins should be validated against the specific AHL visit tables used in the implementation.