Search Results ahl_workorders_v




Overview
Explore in AI Chat

Overview

AHL_WORKORDERS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the AHL (Complex Maintenance Repair and Overhaul) product family. Its primary purpose is to expose work order data for the Production module while enforcing two important restrictions: results are limited by the current operating unit identifier, and the view deliberately excludes master work orders and work orders created specifically for costing. This makes the view a streamlined, operational read model rather than a complete transactional listing of all work orders.

Because the underlying data is filtered through operating unit security (largely driven by MO_GLOBAL, FND_PROFILE, and FND_GLOBAL), the view automatically returns only the work orders visible to the session's active organization. It joins work order headers to production discrete job data, visit and visit-task context, item instance (unit) details, routing information, and quality plans, producing a wide, denormalized row suitable for operational dashboards, reports, and integration extracts without requiring the caller to reconstruct these relationships manually.

Underlying Base Objects

The view is built over a large set of AHL and shared EBS base objects. Core work order data originates from AHL_WORKORDERS (synonym) and WIP_DISCRETE_JOBS, which supply job identifiers, status, and scheduling information. Production job descriptions and department context come from BOM_DEPARTMENTS and HR_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS.

Visit and route context is drawn from AHL_VISITS_VL, AHL_VISIT_TASKS_VL, AHL_ROUTES_VL, and AHL_VISIT_INST_ROUTINGS. Unit and item instance information is supplied by CSI_ITEM_INSTANCES and MTL_SYSTEM_ITEMS_KFV. Maintenance route headers and routes are referenced via AHL_MR_HEADERS_B and AHL_MR_ROUTES_APP_V. Quality data flows through QA_PLANS_VAL_V, QA_PLAN_COLLECTION_TRIGGERS, and QA_PLAN_TRANSACTIONS, while warranty context (where used) references AHL_WARRANTY_CLAIMS_B, AHL_WARRANTY_CONTRACTS_B, and AHL_WARRANTY_ENTITLEMENTS.

Operationally significant is the use of PL/SQL packages embedded in the view definition: AHL_UTILITY_PVT.GET_UNIT_NAME, AHL_COMPLETIONS_PVT.GET_MR_STATUS, and helper logic from AHL_UTIL_UC_PKG, AHL_PRD_PRINT_PVT, and AHL_PRD_SERN_CHANGE_PVT. These packages enrich rows at query time. Security and lookups are handled by MO_GLOBAL, FND_GLOBAL, FND_PROFILE, HR_SECURITY, and lookup views such as MFG_LOOKUPS, FND_LOOKUP_VALUES_VL, and PA_LOOKUPS.

Key Columns

Common Use Cases and Queries

The view is typically queried for production work order reporting, shop-floor status tracking, and unit-level maintenance history. A representative query lists open work orders for the current operating unit:

  • SELECT workorder_id, job_number, status_code, meaning, scheduled_start_date FROM ahl_workorders_v WHERE status_code = 'RELEASED';
  • SELECT job_number, serial_number, visit_number, actual_start_date FROM ahl_workorders_v ORDER BY actual_start_date DESC;
  • SELECT job_number, route_no, revision_number, title FROM ahl_workorders_v WHERE project_id IS NOT NULL;

Because the view applies operating-unit and costing restrictions internally, no additional MO security predicate is required. Reporting tools and interfaces that consume AHL_WORKORDERS_V therefore inherit consistent, secured results aligned with the session's active organization context.