Search Results ahl_mr_routes

Overview

The AHL_MR_ROUTES table is a core data entity within the Oracle E-Business Suite (EBS) module for Complex Maintenance, Repair, and Overhaul (CMRO). It serves as the fundamental junction table that establishes and stores the associations between Maintenance Requirements (MRs) and Routes. In the CMRO business process, a maintenance requirement defines a specific task or inspection, while a route defines a sequence of operations or steps. This table enables the linkage of a defined maintenance task to a procedural workflow, which is essential for planning, executing, and tracking complex maintenance activities on assets.

Key Information Stored

The table's primary purpose is to manage the relationship between a maintenance requirement and a route. Its key columns, as defined by its primary and unique keys, are MR_ROUTE_ID, ROUTE_ID, and MR_HEADER_ID. The MR_ROUTE_ID is the system-generated unique identifier for each association record. The MR_HEADER_ID is a foreign key to AHL_MR_HEADERS_B, linking to the specific maintenance requirement header. The ROUTE_ID is a foreign key to AHL_ROUTES_B, linking to the associated procedural route. The unique key constraint (AHL_MR_ROUTES_UK1) on ROUTE_ID and MR_HEADER_ID ensures that a given route is not duplicated for the same maintenance requirement.

Common Use Cases and Queries

A primary use case is retrieving all routes defined for a specific maintenance requirement to understand the procedural steps involved. Conversely, identifying which maintenance requirements utilize a particular standard route is another common query. This data is critical when generating work orders or visit tasks, as the route sequences linked via this table dictate the task flow. A typical reporting query would join AHL_MR_ROUTES to AHL_MR_HEADERS_B and AHL_ROUTES_B to list MR details with their associated route names. For instance, to find all routes for a given MR Header ID:

• SELECT mr_route.mr_route_id, mr_route.route_id, route.route_name FROM ahl_mr_routes mr_route, ahl_routes_b route WHERE mr_route.route_id = route.route_id AND mr_route.mr_header_id = <MR_HEADER_ID>;

This association is also foundational for APIs and processes that generate visit tasks, as the AHL_VISIT_TASKS_B table directly references the MR_ROUTE_ID.

Related Objects

The AHL_MR_ROUTES table is centrally connected to several key CMRO objects, as detailed in its foreign key relationships. It is a child table of AHL_MR_HEADERS_B (for the maintenance requirement) and AHL_ROUTES_B (for the route definition). It is a parent table to AHL_MR_ROUTE_SEQUENCES, which stores the detailed steps within the route for the MR, and can also be self-referencing via the RELATED_MR_ROUTE_ID column in that child table for complex route dependencies. Most operationally, it is the parent to AHL_VISIT_TASKS_B, meaning that when a maintenance visit is created, the tasks are instantiated based on the specific MR-route association stored in this table.