Results for “ahl_rt_oper_labor_h”

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

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, AHL.AHL_RT_OPER_LABOR_H is the date-tracked history (audit/version) table for AHL_RT_OPER_LABOR, within the AHL – Complex Maintenance Repair and Overhaul product. It records the labor, skill, and headcount requirements associated with a route operation, capturing each historical revision of those requirements so that changes to manning and skill definitions over time are preserved rather than overwritten.

Its role is twofold: it supports routing/operation labor planning in the maintenance execution flow and it serves as the archival counterpart of the base table. In heuristic Data Vault terms, the table would be modeled as a link, reflecting the intersection of labor records, route operations, and the underlying object (route or operation) referenced through OBJECT_ID. The single-column unique index AHL_RT_OPER_LABOR_H_U1 on RT_OPER_LABOR_H_ID reinforces the row-per-version identity of each historical record.

Key Information Stored

The table exposes 36 documented columns. The most significant are:

• RT_OPER_LABOR_H_ID — surrogate primary key (AHL_RT_OPER_LABOR_H_PK), also carried by the unique index AHL_RT_OPER_LABOR_H_U1 as the business-key candidate.
• RT_OPER_LABOR_ID — the versioned business key linking each history row back to its parent labor record in AHL_RT_OPER_LABOR.
• OBJECT_ID — the route or operation the labor line is attached to; FK to AHL_ROUTES_B and AHL_OPERATIONS_B.
• SKILL_TYPE_CODE, SKILL_COMPETENCE_ID, SKILL_LEVEL_CODE, SKILL_RATING_LEVEL_ID — skill requirements, competence, level, and rating.
• ASSOCIATION_TYPE_CODE — how the labor/skill is associated with the route operation.
• REVISION_NUMBER — the revision context of the labor definition.
• HEADCOUNT, DURATION, TIME_SPAN — planned labor quantities and timing.
• SIGN_OFF_FLAG — whether the labor requirement has been formally approved.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, controlling multi-org/style access.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard concurrent-program-aware WHO columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF flexfield segments for client extension.

Common Use Cases and Queries

Typical use cases include auditing changes to operation labor requirements, reconstructing the labor plan as of a past revision, and reporting on skill demand across routes. A common join returns the current and historical views together:

• SELECT h.RT_OPER_LABOR_ID, h.REVISION_NUMBER, h.HEADCOUNT, h.DURATION, h.LAST_UPDATE_DATE FROM AHL_RT_OPER_LABOR_H h WHERE h.OBJECT_ID = :p_object_id ORDER BY h.LAST_UPDATE_DATE DESC;
• SELECT l.RT_OPER_LABOR_ID, h.HEADCOUNT, h.SKILL_TYPE_CODE FROM AHL_RT_OPER_LABOR l JOIN AHL_RT_OPER_LABOR_H h ON l.RT_OPER_LABOR_ID = h.RT_OPER_LABOR_ID WHERE l.SIGN_OFF_FLAG = 'Y' ORDER BY h.CREATION_DATE;
• Filtering by SECURITY_GROUP_ID is essential in multi-org queries, and combining SKILL_LEVEL_CODE with HEADCOUNT supports skill-gap and capacity reporting.

Related Objects

• AHL_RT_OPER_LABOR — the base table whose versions are archived here; join on RT_OPER_LABOR_ID.
• AHL_ROUTES_B — the route definition referenced by OBJECT_ID.
• AHL_OPERATIONS_B — the operation definition also referenced by OBJECT_ID.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for access control.
• Standard concurrent/audit views and the AHL routing setup APIs that read the current table complement these relationships.