Search Results ahl_rt_oper_labor_h_n1

Overview

The AHL_RT_OPER_LABOR_H table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Oracle Complex Maintenance, Repair, and Overhaul (CMRO) application. This table, owned by the AHL (Advanced Service Online) schema, functions as a history table. Its primary role is to maintain a historical record of changes made to labor requirements associated with operations defined in a routing or a standalone operation. It captures revisions of labor skill, headcount, and duration assignments, enabling audit trails, compliance reporting, and analysis of how labor plans evolve over time for maintenance and repair processes.

Key Information Stored

The table stores historical snapshots of labor operation details. The primary unique identifier is the RT_OPER_LABOR_H_ID column. Key transactional columns include RT_OPER_LABOR_ID, which links to the current record in the master AHL_RT_OPER_LABOR table, and OBJECT_ID, which references either a routing (AHL_ROUTES_B) or an operation (AHL_OPERATIONS_B). Labor skill details are captured through SKILL_TYPE_CODE, SKILL_COMPETENCE_ID, SKILL_LEVEL_CODE, and SKILL_RATING_LEVEL_ID. Operational planning data is stored in HEADCOUNT, DURATION, and TIME_SPAN. The REVISION_NUMBER tracks the sequence of changes for a given record. Standard EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER) and descriptive flexfield columns (ATTRIBUTE1-15) are also present for extensibility and compliance.

Common Use Cases and Queries

A primary use case is auditing changes to labor plans for a specific routing or operation. Analysts can query the history to understand when skill requirements or estimated durations were modified. This is critical for root cause analysis in production delays or for validating procedural compliance. Another common scenario is generating reports that show the evolution of a maintenance task's labor cost estimates over multiple revisions.

A sample query to retrieve the full revision history for labor assignments on a specific routing (OBJECT_ID) would be:

• SELECT rt_oper_labor_h_id, revision_number, skill_type_code, headcount, duration, last_update_date, last_updated_by FROM ahl.ahl_rt_oper_labor_h WHERE object_id = <route_id> ORDER BY rt_oper_labor_id, revision_number;

To compare the current labor data with its last historical entry for a given RT_OPER_LABOR_ID, a query would join this history table with the master AHL_RT_OPER_LABOR table on RT_OPER_LABOR_ID.

Related Objects

The table maintains defined foreign key relationships with several core CMRO tables, as documented in the ETRM metadata:

• Master Table Reference: RT_OPER_LABOR_ID → AHL_RT_OPER_LABOR. This links each historical record to its corresponding current record in the master labor operations table.
• Routing Reference: OBJECT_ID → AHL_ROUTES_B. When the labor is associated with a routing, this foreign key points to the master routes table.
• Operation Reference: OBJECT_ID → AHL_OPERATIONS_B. When the labor is associated with a standalone operation, this foreign key points to the master operations table.

The table's primary key constraint, AHL_RT_OPER_LABOR_H_PK, is on the RT_OPER_LABOR_H_ID column. It is indexed for performance by the unique index AHL_RT_OPER_LABOR_H_U1. Non-unique indexes (AHL_RT_OPER_LABOR_H_N1, AHL_RT_OPER_LABOR_H_N2) exist on foreign key and commonly queried combination columns to optimize joins and queries.