Results for “model_code”

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

Overview

AHL_ROUTES_B_KFV is a Key Flexfield (KFV) automatically generated view owned by the APPS schema in Oracle E-Business Suite. It belongs to the AHL product family, Complex Maintenance Repair and Overhaul, and is registered as VALID in both Oracle EBS 12.1.1 and 12.2.2. The view presents routing definition data maintained against the AHL_ROUTES_B base table, adding the concatenated and padded concatenated key flexfield segment representations that Oracle's Flexfield infrastructure derives from the individual SEGMENT1 through SEGMENT15 columns. As a KFV view, it exists so that reports, concurrent programs, forms, and integration interfaces can retrieve a human-readable, formatted flexfield combination alongside the underlying descriptive and transactional attributes of a route, without reimplementing the concatenation logic in application code.

Because the view is a thin projection over AHL_ROUTES_B rather than a denormalized reporting structure, it retains the complete column set of the base table, including audit columns, route identification attributes, accounting classification attributes, and the descriptive flexfield (DFF) attribute columns ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15. This makes it suitable both as a substitute for the base table in queries that require the formatted flexfield value, and as the canonical source for reporting on route configuration in the AHL module.

Underlying Base Objects

The documented base object referenced by the view is AHL_ROUTES_B, accessed through the APPS synonym. The view text confirms a direct, single-table SELECT against AHL_ROUTES_B, exposing ROWID and all key business columns. Two literal values, each the character 'X', are projected in the segment-adjacent positions that the Flexfield generator uses for the compiled and compiled-attribute markers in the concatenated segment display. The view therefore inherits the base table's primary key semantics (ROUTE_ID) and its object versioning through OBJECT_VERSION_NUMBER.

No additional joins to AHL_ROUTES_TL or other dependent tables are present in the documented view text. Consequently, the view returns one row per route row in AHL_ROUTES_B and does not itself resolve translated or referenced entity descriptions such as the operator party, service item, or accounting class names; those must be joined separately by the consuming query.

Key Columns

• ROUTE_ID — Primary identifier of the route record, carried directly from AHL_ROUTES_B.
• ROUTE_NO, REVISION_NUMBER, REVISION_STATUS_CODE — Route number, revision, and revision status, forming the user-facing identity of the route.
• START_DATE_ACTIVE, END_DATE_ACTIVE, ENABLED_FLAG, SUMMARY_FLAG — Effective dating and record-state controls that determine which routes are active at a point in time.
• TIME_SPAN — A route-level attribute capturing the expected or standard duration associated with the routing definition. This column was the specific term matched in the user search, and it is exposed unchanged from the base table.
• ROUTE_TYPE_CODE, PRODUCT_TYPE_CODE, ZONE_CODE, SUB_ZONE_CODE, PROCESS_CODE, APPLICATION_USG_CODE — Classification codes that categorize the route by type, product context, geographic zone, sub-zone, process, and application usage.
• OPERATOR_PARTY_ID, SERVICE_ITEM_ID, SERVICE_ITEM_ORG_ID, TASK_TEMPLATE_GROUP_ID — Foreign-key references to the operating party, service item, its organization, and the associated task template group.
• ACCOUNTING_CLASS_CODE, ACCOUNTING_CLASS_ORG_ID — Accounting classification and its owning organization.
• QA_INSPECTION_TYPE — Quality assurance inspection category associated with the route.
• SEGMENT1–SEGMENT15, CONCATENATED_SEGMENTS, PADDED_CONCATENATED_SEGMENTS — The key flexfield segments, their concatenated rendering, and the padded concatenated rendering used for fixed-width display and alignment.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE15 — Descriptive flexfield context and attribute values.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER.

Common Use Cases and Queries

The view is typically queried when route data must be reported with a readable flexfield combination, when routes must be filtered by TIME_SPAN, or when integration extracts require the concatenated segment representation. A representative query retrieving active routes and their formatted flexfield value is:

SELECT route_id, route_no, revision_number,
       revision_status_code, time_span,
       concatenated_segments
FROM   apps.ahl_routes_b_kfv
WHERE  enabled_flag = 'Y'
AND    NVL(start_date_active, SYSDATE) <= SYSDATE
AND    NVL(end_date_active, SYSDATE) >= SYSDATE;

A focused query on the searched attribute, ORDER BY time_span DESC, isolates the longest-duration routes. Analysts also use the view as a join target when they need the flexfield display for a route referenced elsewhere, joining on ROUTE_ID. Because the view mirrors the base table one-to-one, it can be substituted for AHL_ROUTES_B in any existing report, and the CONCATENATED_SEGMENTS and PADDED_CONCATENATED_SEGMENTS columns removed where the base table's plain segment columns are sufficient.