Results for “space_category_mean”

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

Overview

AHL_VISIT_DETAILS_V is a denormalized reporting view owned by the APPS schema within the AHL (Complex Maintenance Repair and Overhaul) product family in Oracle EBS 12.1.1 and 12.2.2. Its purpose is to present a consolidated, human-readable projection of visit records maintained in the AHL visit model, joining the core visit entity to instance, organization, department, item, simulation plan, and lookup metadata so that reporting and integration consumers do not need to reconstruct these relationships themselves.

The view is documented in ETRM as VALID at 12.2.2 and is defined over the visit header table plus a wide set of referential lookups. It exposes descriptive attributes such as visit number, visit name, organization name, department description, item description (via the concatenated segments key flexfield view), serial number, unit name, visit type meaning, status meaning, and space category meaning, together with the primary visit linkage column ASSO_PRIMARY_VISIT_ID, which is the attribute most commonly searched by users of this object.

Underlying Base Objects

The view text joins the following documented objects:

• AHL_VISITS_VL (VIEW) — the primary visit header source, aliased AVTS; also sub-queried to resolve the associated primary visit number.
• CSI_ITEM_INSTANCES (SYNONYM) — supplies the serial number for the instance referenced by ITEM_INSTANCE_ID.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — supplies the organization name; joined outer (ORGANIZATION_ID(+)).
• BOM_DEPARTMENTS (SYNONYM) — supplies the department description; also outer-joined.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — supplies the concatenated item segments used as item description.
• AHL_SIMULATION_PLANS_VL (VIEW) — supplies the simulation plan name.
• FND_LOOKUP_VALUES_VL (VIEW) — referenced four times to translate visit type, simulation-delete flag, space category, and status codes into meanings.
• AHL_UNIT_EFFECTIVITIES_B and AHL_VISIT_TASKS_B (SYNONYMS) — combined in a scalar subquery to derive the maximum DUE_DATE (exposed as DUE_BY).
• AHL_UTILITY_PVT (PACKAGE) — invoked via GET_UNIT_NAME to resolve the unit name from the instance.

The metadata also records dependencies on HR_GENERAL, HR_SECURITY, MO_GLOBAL, MTL_PARAMETERS, and ORG_ORGANIZATION_DEFINITIONS, which are typical of multi-org and security-aware AHL views.

Key Columns

• VISIT_ID, VISIT_NUMBER, VISIT_NAME — the visit identity and descriptive labels.
• ASSO_PRIMARY_VISIT_ID — the identifier of the associated primary visit; combined with the subquery it yields PRIMARY_VISIT_NUMBER.
• ORG_ID, ORG_NAME, DEPT_ID, DEPT_DESCRIPTION — organizational and departmental context.
• ITEM_INSTANCE_ID, SERIAL_NUMBER, INVENTORY_ITEM_ID, ITEM_ORGANIZATION_ID, ITEM_DESCRIPTION — item and instance identification.
• VISIT_TYPE_CODE, VISIT_TYPE_MEAN, STATUS_CODE, STATUS_MEANING, SPACE_CATEGORY_CODE, SPACE_CATEGORY_MEAN — code/meaning pairs for classification and lifecycle state.
• START_DATE_TIME, CLOSE_DATE_TIME, END_DATE (returned as NULL), DUE_BY — scheduling and completion attributes.
• SIMULATION_PLAN_ID, SIMULATION_PLAN_NAME, SIMULATION_DELETE_FLAG, SIMULATION_DELETE_MEAN, OBJECT_VERSION_NUMBER — simulation and concurrency control.
• Unit name — returned by the AHL_UTILITY_PVT.GET_UNIT_NAME call and typically aliased in consuming queries.

Common Use Cases and Queries

The view is typically consumed for visit status dashboards, work-order and unit readiness reporting, and downstream integration extracts that require resolved descriptions rather than raw IDs. The search term asso_primary_visit_id corresponds to the most frequent access pattern: tracing a visit back to its associated primary visit.

SELECT visit_id, visit_number, visit_name,
       asso_primary_visit_id, primary_visit_number,
       org_name, dept_description,
       serial_number, item_description,
       visit_type_meaning, status_meaning
  FROM apps.ahl_visit_details_v
 WHERE asso_primary_visit_id = :p_visit_id;

Reporting over organization scope and open visits commonly filters on ORG_ID and CLOSE_DATE_TIME IS NULL, while item-centric reporting joins on SERIAL_NUMBER or ITEM_INSTANCE_ID. Because the view embeds lookup and package logic, consumers should treat it as a read-only reporting object and expect the associated multi-org and security predicates to apply.