Search Results ahl_visit_types_vl




Overview
Explore in AI Chat

Overview

Within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases, APPS.AHL_VISIT_TYPES_VL is a validated database view belonging to the AHL product family, Complex Maintenance Repair and Overhaul (also referred to as Enterprise Asset Management for complex assets). The view presents visit type definitions — the configurable categories that describe and classify the nature of a service or maintenance visit — in a fully translated, display-ready form. Its suffix _VL identifies it as a "view with language" variant, meaning it joins the base entity to its translation table and resolves a user-facing name through the language environment, in addition to the descriptive text stored in the translation table. This makes the view the standard, multi-lingual source for consuming visit type reference data rather than the underlying tables directly.

From a reporting and integration standpoint, AHL_VISIT_TYPES_VL functions as a read-only reference (lookup) source. It is not a transactional object: it does not record individual visits, only the visit type definitions against which visits are later planned and executed. Because it exposes the security group identifier and the standard WHO audit columns, the view is also suitable for security-scoped and audit-aware extracts. In pre-12.2.2 contexts the object already existed under the same name; the ETRM-documented 12.2.2 metadata (owner APPS, view type, valid status) reflects its continued availability in the later multitenant-capable release.

Underlying Base Objects

The ETRM metadata documents the view as being defined over three referenced objects:

  • AHL_VISIT_TYPES_B (SYNONYM) — the base entity table holding the visit type identifier, code, service category, status, estimated duration, flags, security group, and the fifteen ATTRIBUTE columns.
  • AHL_VISIT_TYPES_TL (SYNONYM) — the translated layer holding language-specific descriptive text keyed by VISIT_TYPE_ID and LANGUAGE.
  • FND_LOOKUP_VALUES_VL (VIEW) — the application lookup view used to resolve the visit type code into a display meaning.

The view connects these through an inner join: the base table B is matched to the translation table TL on VISIT_TYPE_ID, restricted to TL.LANGUAGE = USERENV('LANG') so that only the current session's language row is returned. A second join links the base code to the lookup view FND on FND.LOOKUP_CODE = B.VISIT_TYPE_CODE with FND.LOOKUP_TYPE = 'AHL_PLANNING_VISIT_TYPE', yielding the resolved meaning. The view exposes the ROWID of the base table as ROW_ID, along with all B columns, TL.DESCRIPTION, and FND.MEANING aliased as VISIT_TYPE_NAME.

Key Columns

Common Use Cases and Queries

Typical scenarios include populating a lookup LOV with visit types, building extracts of active planning visit types, and joining visit transactions to their human-readable classification.

SELECT VISIT_TYPE_ID, VISIT_TYPE_CODE, VISIT_TYPE_NAME, DESCRIPTION,
       SERVICE_CATEGORY_CODE, STATUS_CODE, ESTIMATED_DURATION
FROM   APPS.AHL_VISIT_TYPES_VL
WHERE  STATUS_CODE = 'ACTIVE';
SELECT vt.VISIT_TYPE_NAME, vt.SERVICE_CATEGORY_CODE, vt.ESTIMATED_DURATION
FROM   APPS.AHL_VISIT_TYPES_VL vt
WHERE  vt.SECURITY_GROUP_ID = :p_security_group_id
ORDER BY vt.VISIT_TYPE_NAME;

Because the joins are inner joins and the language filter uses USERENV('LANG'), queries run under a language with no translation row return fewer results; reports requiring all languages should query AHL_VISIT_TYPES_TL directly.