Search Results visit_type_name

Overview

APPS.AHL_VISIT_TYPES_VL is a translated (VL) view within the Oracle E-Business Suite Enterprise Asset Management and Complex Maintenance, Repair and Overhaul (cMRO) product family. It exposes the definition of visit types used in visit planning and scheduling, presenting the user-facing name of each visit type alongside its descriptive and control attributes. The view is defined over the base table AHL_VISIT_TYPES_B, its translation table AHL_VISIT_TYPES_TL, and the lookup view FND_LOOKUP_VALUES_VL. Its principal role is to provide a language-aware, display-ready representation of visit type definitions that can be consumed by forms, concurrent programs, reports, and integration interfaces without requiring callers to join the underlying tables themselves.

Underlying Base Objects

The view is documented as referencing three objects: AHL_VISIT_TYPES_B (SYNONYM), AHL_VISIT_TYPES_TL (SYNONYM), and FND_LOOKUP_VALUES_VL (VIEW). The driver table AHL_VISIT_TYPES_B holds the untranslated definition of each visit type, including its primary key VISIT_TYPE_ID. It is joined to AHL_VISIT_TYPES_TL on VISIT_TYPE_ID, restricted to the session language through TL.LANGUAGE = USERENV('LANG'), which supplies the translated DESCRIPTION. A further join is made to FND_LOOKUP_VALUES_VL on LOOKUP_CODE = B.VISIT_TYPE_CODE, constrained by LOOKUP_TYPE = 'AHL_PLANNING_VISIT_TYPE', and the lookup MEANING is aliased as VISIT_TYPE_NAME. Because the synonyms are owned by APPS, the view is queried with the APPS schema prefix in client SQL.

Key Columns

• ROW_ID — the ROWID of the base row, retained for row-level addressing.
• VISIT_TYPE_ID — primary identifier of the visit type and the join key across the base and translation tables.
• VISIT_TYPE_CODE — internal code, matched against the lookup code of the AHL_PLANNING_VISIT_TYPE lookup type.
• VISIT_TYPE_NAME — the lookup MEANING, providing the display name for the visit type in the user's language; this is the column returned when users search for "visit_type_name".
• DESCRIPTION — the translated long description sourced from AHL_VISIT_TYPES_TL.
• SERVICE_CATEGORY_CODE, STATUS_CODE, ESTIMATED_DURATION — classification, lifecycle status, and expected duration of the visit type.
• TRANSIT_TYPE_FLAG, COMPONENT_VISIT_FLAG — control flags indicating whether the type represents transit activity or a component-level visit.
• LINKED_VISIT_TYPE_ID, MC_ID — reference to a related visit type and the master configuration identifier.
• SECURITY_GROUP_ID — the security grouping used for multi-organization access control.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield columns available for customer-defined data.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER, supporting auditing and optimistic locking.

Common Use Cases and Queries

The view is typically used to populate LOVs, validate visit type references during visit creation, and drive reports that must present visit type names in the operating language. A common usage filters by status to retrieve only active definitions:

• SELECT visit_type_id, visit_type_name, description, estimated_duration FROM apps.ahl_visit_types_vl WHERE status_code = 'ACTIVE' ORDER BY visit_type_name;
• SELECT visit_type_id, visit_type_name, service_category_code FROM apps.ahl_visit_types_vl WHERE visit_type_code = :p_visit_type_code;
• SELECT vt.visit_type_name, COUNT(v.visit_id) FROM apps.ahl_visit_types_vl vt, apps.ahl_visits v WHERE v.visit_type_id = vt.visit_type_id GROUP BY vt.visit_type_name;

Because VISIT_TYPE_NAME is derived from a lookup rather than the base table, any change to the AHL_PLANNING_VISIT_TYPE lookup meaning is reflected automatically in query results. Callers should note that the row set is restricted to the current session language and that the lookup join is mandatory, so visit type codes without a corresponding lookup entry are excluded from the view.