Results for “ahl_route_operations_v”

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

Overview

AHL_ROUTE_OPERATIONS_V is a valid, APPS-owned view within the AHL (Complex Maintenance Repair and Overhaul) product family of Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. Its purpose is to present the operational steps that make up a maintenance route, augmented with descriptive attributes drawn from the operations definition itself. A route in AHL represents an ordered sequence of maintenance or repair operations performed against a maintainable asset, and this view exposes the intersection of the route structure with the operation master data.

Rather than forcing report and interface developers to join AHL_ROUTE_OPERATIONS to AHL_OPERATIONS_VL and to the lookup tables manually, the view performs those joins internally and decodes two flag columns into their user-facing meanings. This makes it a convenient single-row-per-route-step source for operational reporting, concurrent program data extraction, and integration payloads. The search term ahl_yes_no_type is directly relevant, because the view relies on that lookup type to decode both the check point flag and the standard operation flag.

Underlying Base Objects

The view is defined over the following documented objects:

• AHL_ROUTE_OPERATIONS (referenced through a synonym) — the primary transactional table holding each route step, keyed by ROUTE_OPERATION_ID and linked to its parent route through ROUTE_ID.
• AHL_OPERATIONS_VL (view) — supplies the operation's description, date range, concatenated segments, and the standard operation flag. The join is on AO.OPERATION_ID = ARO.OPERATION_ID.
• FND_LOOKUP_VALUES_VL (view) — referenced twice, aliased CHKPT and STD, to translate the yes/no flags into readable descriptions.

Both lookup joins filter on LOOKUP_TYPE = 'AHL_YES_NO_TYPE'. The CHKPT join (for CHECK_POINT_FLAG) is an outer join ((+)), while the STD join (for STANDARD_OPERATION_FLAG) is also outer-joined. This design ensures route steps are returned even when no lookup value is found.

Key Columns

• ROUTE_OPERATION_ID — primary surrogate key for each route step.
• ROUTE_ID — foreign key to the parent route header.
• OPERATION_ID — link to the underlying operation definition.
• STEP — the ordinal position of the operation within the route sequence.
• REVISION_NUMBER — revision of the route operation.
• STANDARD_OPERATION_FLAG / STANDARD_OPERATION_FLAG_DESC — the raw flag and its decoded meaning from AHL_YES_NO_TYPE.
• CHECK_POINT_FLAG / CHECK_POINT_FLAG_DESC — indicates whether the step is a quality check point, with its decoded description.
• OPERATION_DESCRIPTION, CONCATENATED_SEGMENTS, START_DATE_ACTIVE, END_DATE_ACTIVE — descriptive and validity attributes from the operation.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER) and fifteen flexfield ATTRIBUTE columns.

Common Use Cases and Queries

Typical uses include route step listings, check point analysis, and extract interfaces feeding shop-floor or MES systems. Because the flags are pre-decoded, reporting tools can display them directly.

• List all steps of a route in sequence:

SELECT step, operation_id, operation_description,
       check_point_flag_desc
FROM   apps.ahl_route_operations_v
WHERE  route_id = :p_route_id
ORDER  BY step;

• Identify quality check points across routes:

SELECT route_id, step, operation_description
FROM   apps.ahl_route_operations_v
WHERE  check_point_flag = 'Y';

• Find routes containing non-standard operations:

SELECT route_id, step, standard_operation_flag_desc
FROM   apps.ahl_route_operations_v
WHERE  NVL(standard_operation_flag,'N') = 'N';

Consult the ETRM 12.2.2 metadata and AHL product documentation for authoritative column behavior.