Results for “skill_level_code”

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

Overview

The AHL_RT_OPER_LABOR table resides in the AHL schema and belongs to the Complex Maintenance Repair and Overhaul (AHL) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the labor requirements associated with either a Route or an Operation, acting as the authoritative record for which skills and rating levels are required to perform a given maintenance task. Each row links a parent object—identified through OBJECT_ID—to a specific skill competency and skill rating level, together with association, headcount, duration, and sign-off attributes.

From a dimensional modeling perspective, the metadata's heuristic Data Vault classification is satellite-leaning. This reflects the table's structure: it carries descriptive and qualifying attributes (skill, rating, headcount, duration) attached to a business key defined by OBJECT_ID and its skill dimensions, rather than acting as an independent hub or an associative link. Practically, RT_OPER_LABOR_ID functions as the row-level identifier, while the composite of OBJECT_ID, SKILL_COMPETENCE_ID, SKILL_RATING_LEVEL_ID, and ASSOCIATION_TYPE_CODE forms the business-key candidate.

Key Information Stored

The table contains 35 documented columns. The most operationally significant are:

• RT_OPER_LABOR_ID — Surrogate primary key (AHL_RT_OPER_LABOR_PK), uniquely identifying each labor requirement row.
• OBJECT_ID — Foreign key pointing either to AHL_ROUTES_B or AHL_OPERATIONS_B, depending on whether the labor requirement is attached to a Route or an Operation.
• SKILL_COMPETENCE_ID — The specific skill or competency required, forming part of the unique business key.
• SKILL_RATING_LEVEL_ID — The proficiency rating level demanded for that skill.
• ASSOCIATION_TYPE_CODE — Distinguishes the nature of the association and completes the business-key set.
• SKILL_TYPE_CODE and SKILL_LEVEL_CODE — Classification attributes for the skill requirement.
• REVISION_NUMBER — Supports versioning of the labor requirement definition.
• HEADCOUNT — Number of personnel required.
• DURATION and TIME_SPAN — Effort and scheduling parameters.
• SIGN_OFF_FLAG — Indicates whether completion requires sign-off.
• SECURITY_GROUP_ID — References FND_SECURITY_GROUPS for access control.
• Audit columns such as OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY, and the fifteen ATTRIBUTE flex columns for extensibility.

The unique indexes AHL_RT_OPER_LABOR_U1 (RT_OPER_LABOR_ID) and AHL_RT_OPER_LABOR_U2 (OBJECT_ID, SKILL_COMPETENCE_ID, SKILL_RATING_LEVEL_ID, ASSOCIATION_TYPE_CODE) enforce identity and prevent duplicate skill definitions per object.

Common Use Cases and Queries

Typical scenarios include resource planning, certification gap analysis, and maintenance cost estimation. A common query joins labor requirements to their parent operation:

• Identify all required skills for a given route or operation by filtering on OBJECT_ID.
• Aggregate HEADCOUNT and DURATION to compute total labor effort per operation.
• Compare SKILL_RATING_LEVEL_ID against employee certification records to detect qualification gaps.
• Report all rows requiring sign-off using SIGN_OFF_FLAG = 'Y'.

A representative SQL pattern is: SELECT l.RT_OPER_LABOR_ID, l.SKILL_COMPETENCE_ID, l.SKILL_RATING_LEVEL_ID, l.HEADCOUNT, l.DURATION FROM AHL_RT_OPER_LABOR l WHERE l.OBJECT_ID = :object_id ORDER BY l.SKILL_COMPETENCE_ID; Analysts frequently join to AHL_OPERATIONS_B or AHL_ROUTES_B to resolve object names, and to FND_SECURITY_GROUPS for security-scoped reporting.

Related Objects

• AHL_ROUTES_B — Parent route definition; joined via AHL_RT_OPER_LABOR.OBJECT_ID.
• AHL_OPERATIONS_B — Parent operation definition; joined via AHL_RT_OPER_LABOR.OBJECT_ID.
• AHL_RT_OPER_LABOR_H — History table capturing prior versions; joined via RT_OPER_LABOR_ID.
• FND_SECURITY_GROUPS — Security grouping referenced by SECURITY_GROUP_ID.
• AHL_ROUTES_B / AHL_OPERATIONS_B child dependencies that resolve labor requirements into workable maintenance procedures.

Together these relationships make AHL_RT_OPER_LABOR the central bridge between maintenance objects and the skill requirements needed to execute them.