Results for “ahl_visits_vl”

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

Overview

APPS.AHL_VISITS_VL is a valid, published view in the Oracle E-Business Suite environment, owned by the APPS schema and delivered as part of the AHL product family, Oracle Complex Maintenance, Repair and Overhaul. As its name implies, the _VL suffix denotes a "view with translation" — a hybrid construct that exposes both the operational columns stored on a base entity table and the language-dependent descriptive columns held on the corresponding translation table. In this instance, the view fulfills the documentation's stated purpose: "This view stores the query to retrieve Visit information."

A Visit in the AHL model represents a discrete maintenance or service engagement, typically tied to an item instance, a service request, or a simulation plan. AHL_VISITS_VL therefore serves as the primary read interface through which Visit records are surfaced to Oracle Forms, OA Framework pages, concurrent programs, and integration endpoints. Because it abstracts the join between the base table and its translations, callers are insulated from language-handling logic and can rely on a consistent column set regardless of the runtime language.

Underlying Base Objects

The view is defined over two APPS-owned synonyms:

• AHL_VISITS_B — the base transactional table storing Visit identifiers, status, dates, flags, key flexfield and descriptive flexfield attributes, and pricing information. The view's DBA record lists this alias as AVTB.
• AHL_VISITS_TL — the translation table storing language-specific content, aliased as AVTT, which carries the visit name and description.

The join condition is AVTB.VISIT_ID = AVTT.VISIT_ID AND AVTT.LANGUAGE = USERENV('LANG'). The USERENV('LANG') predicate restricts results to the session's active language, so a session configured for a supported language returns exactly one translated row per visit. This is the standard EBS multi-language pattern (TL/L) and explains the "VL" designation in the object name.

Key Columns

The view exposes the full column set of the base table plus the two translated columns. Principal columns include:

• VISIT_ID — the primary key, used as the foreign key in downstream visit-related tables.
• VISIT_NUMBER — the user-facing identifier for the visit.
• VISIT_NAME, DESCRIPTION — sourced from AHL_VISITS_TL; the language-sensitive descriptive attributes.
• STATUS_CODE, VISIT_TYPE_CODE, SPACE_CATEGORY_CODE, SCHEDULE_DESIGNATOR — classification and state columns governing visit behavior.
• START_DATE_TIME, CLOSE_DATE_TIME — the operative scheduling and closure timestamps.
• ORGANIZATION_ID, DEPARTMENT_ID, ITEM_INSTANCE_ID, ITEM_ORGANIZATION_ID, INVENTORY_ITEM_ID — organizational and asset context for the visit.
• PROJECT_FLAG, PROJECT_ID — the specific columns the user searched for. PROJECT_FLAG indicates whether the visit is associated with an Oracle Projects project, and PROJECT_ID carries the corresponding project reference. Both are essential when visits must be costed, billed, or reported against project structures.
• SIMULATION_PLAN_ID, SIMULATION_DELETE_FLAG, TEMPLATE_FLAG, OUT_OF_SYNC_FLAG, ASSO_PRIMARY_VISIT_ID — flags governing simulation-derived and templated visits.
• PRICE_LIST_ID, ESTIMATED_PRICE, ACTUAL_PRICE — commercial attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the descriptive flexfield segment values defined for the visit entity.

Common Use Cases and Queries

Reporting on Open Visits filtered by project association is a typical requirement:

• SELECT v.VISIT_NUMBER, v.VISIT_NAME, v.STATUS_CODE, v.START_DATE_TIME FROM APPS.AHL_VISITS_VL v WHERE v.PROJECT_FLAG = 'Y' AND v.STATUS_CODE NOT IN ('CLOSED','CANCELLED');
• SELECT v.VISIT_ID, v.PROJECT_ID, v.ESTIMATED_PRICE, v.ACTUAL_PRICE FROM APPS.AHL_VISITS_VL v WHERE v.ORGANIZATION_ID = :org_id AND v.PROJECT_ID IS NOT NULL;
• Integration extracts commonly select the full descriptive flexfield column list along with OBJECT_VERSION_NUMBER to support optimistic locking during inbound updates.

Because translation is resolved through USERENV('LANG'), queries executed in different language sessions may return differently titled visits for the same VISIT_ID; reports intended for cross-language consolidation should join AHL_VISITS_TL directly or pin the language explicitly. All access should be granted through the APPS synonyms rather than attempting to query the base tables by their own schema names.