Results for “route_number”

50+ results




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

Overview

AHL_MR_ROUTES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the AHL (Complex Maintenance Repair and Overhaul) product family. It is a denormalized, code-to-description view whose purpose is to present maintenance route assignments in a business-readable form. The view joins route assignment records to route master data and resolves several coded columns—product type and operator—into their corresponding descriptive values using Oracle lookup and party tables.

In Oracle EBS 12.1.1 and 12.2.2, this view is used as a reporting and integration surface rather than as a transactional entity. Because it carries the OBJECT_VERSION_NUMBER and the full ATTRIBUTE1 through ATTRIBUTE15 flexfield set from the underlying assignment entity, it exposes both the descriptive joins needed for ad hoc queries and the DFF context required by integration extracts, interfaces, and extensions. No DML should be issued against it; it is read-only.

The view is documented in ETRM with status VALID, confirming that it compiles cleanly against the referenced base objects in the supported releases.

Underlying Base Objects

The documented view text joins four primary sources:

FND_PROFILE is also listed among referenced base objects, reflecting the standard profile-dependent behavior (for example, language or org context) inherited through the joined AHL views and the lookup view. The correlation between assignment and master is established with A.ROUTE_ID = B.ROUTE_ID, making the view a flat, one-row-per-route-assignment result set.

Key Columns

  • MR_ROUTE_ID — Primary key of the maintenance route assignment record.
  • OBJECT_VERSION_NUMBER — Optimistic locking / concurrency token from the base entity.
  • MR_HEADER_ID — Foreign key to the maintenance (work order) header, tying the route to its execution context.
  • ROUTE_ID — Foreign key to the route master.
  • ROUTE_NUMBER, ROUTE_REVISION_NUMBER, ROUTE_DESCRIPTION — Descriptive route identity; note the column names differ from the underlying view's ROUTE_NO, REVISION_NUMBER, and TITLE.
  • PRODUCT_TYPE — Decoded MEANING from lookup type 'ITEM_TYPE'.
  • OPERATOR — PARTY_NAME of the operator, null when no operator party is assigned.
  • START_DATE_ACTIVE, END_DATE_ACTIVE — Effective dating for the route.
  • ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and segments carried from the assignment.
  • APPLICATION_USG_CODE — Application usage classification from the assignment.

Common Use Cases and Queries

Typical uses include listing routes assigned to a maintenance header with decoded product type, building extracts for interfaces that require flexfield attributes, and reporting route assignments by effective period. A basic query to list decoded routes for a given MR header is:

SELECT mr_route_id, mr_header_id, route_number, route_revision_number,
       route_description, product_type, operator,
       start_date_active, end_date_active, application_usg_code
 FROM apps.ahl_mr_routes_v
 WHERE mr_header_id = :p_mr_header_id
 ORDER BY route_number, route_revision_number;

To find active routes as of the current date:

SELECT mr_route_id, route_number, route_description, product_type, operator
 FROM apps.ahl_mr_routes_v
 WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                  AND NVL(end_date_active, SYSDATE);

Because OPERATOR and PRODUCT_TYPE rely on outer joins, queries filtering on those columns should account for null values. For integration extracts requiring DFF data, select attribute_category and the relevant attribute columns alongside mr_route_id to maintain the context-segment pairing. All queries should be schema-qualified with APPS and run with an appropriate MO or reporting responsibility, observing the standard multi-org security expectations of the AHL module.