Results for “repair_category_id”

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

Overview

AHL_REPAIR_CATEGORIES is a table owned by the AHL schema, the database foundation of Oracle Complex Maintenance Repair and Overhaul (CMRO). It functions as a reference and configuration object that defines the repair categories used in maintenance execution and stores the associated repair time limits, expressed in hours. The record set is derived from CS_INCIDENT_URGENCIES_B, the Service (CS) module table that holds incident urgency definitions, and the AHL table effectively extends each urgency into a maintenance-specific category carrying a service-level repair window.

In Oracle EBS 12.1.1 and 12.2.2 the table appears with 26 documented columns and is flagged as VALID. Two unique indexes are documented: AHL_REPAIR_CATEGORIES_U1 on REPAIR_CATEGORY_ID and AHL_REPAIR_CATEGORIES_U2 on SR_URGENCY_ID. The primary key is AHL_REPAIR_CATEGORIES_PK, defined on REPAIR_CATEGORY_ID. Based on the foreign key topology mined from the ETRM metadata, the table is heuristically classified as satellite-leaning. In a Data Vault model this suggests treating AHL_REPAIR_CATEGORIES as a satellite whose descriptive attributes (notably REPAIR_TIME) attach to a business key sourced from the CS urgency hub, rather than as an independent hub or an associative link.

Key Information Stored

The most operationally significant columns are the identifiers, the descriptive business attributes, and the standard EBS audit and extensibility fields.

• REPAIR_CATEGORY_ID — the surrogate primary key, generated for each repair category and enforced by AHL_REPAIR_CATEGORIES_PK and the unique index AHL_REPAIR_CATEGORIES_U1.
• SR_URGENCY_ID — the foreign key to CS_INCIDENT_URGENCIES_B and the second documented business-key candidate, enforced by AHL_REPAIR_CATEGORIES_U2. It ties the repair category to its source incident urgency.
• REPAIR_TIME — the repair time limit in hours; this is the principal business attribute distinguishing one category from another.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, supporting multi-organization and data-security partitioning.
• OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework to detect concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard who-column audit trail populated by the EBS runtime.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF/descriptive flexfield columns reserved for customer-specific extensions.

Because REPAIR_CATEGORY_ID is a system-generated surrogate, integrations should resolve categories by joining on SR_URGENCY_ID rather than assuming a meaningful identifier value.

Common Use Cases and Queries

Typical usage centers on reporting repair turn-around commitments by category, validating configuration consistency with Service incident urgencies, and feeding scheduling logic where a repair time limit influences prioritization.

A frequent pattern resolves the urgency description for a given category:

• SELECT rc.repair_category_id, rc.repair_time, u.urgency_code, u.urgency FROM ahl.ahl_repair_categories rc JOIN cs.cs_incident_urgencies_b u ON u.urgency_id = rc.sr_urgency_id;

Configuration health checks look for repair categories without a numeric limit or with an orphaned urgency, while scheduling and SLA reporting aggregates REPAIR_TIME to compare committed versus actual repair durations. Security-filtered extracts should constrain on SECURITY_GROUP_ID. When querying in a multi-org or 12.2.2 online-patching environment, the ACL-validated table name should be used.

Related Objects

The documented relationships and dependencies around this table are limited but tightly coupled, reflecting its role as an extension of Service incident urgencies.

• CS_INCIDENT_URGENCIES_B — referenced by AHL_REPAIR_CATEGORIES.SR_URGENCY_ID; the primary parent in the FK model.
• FND_SECURITY_GROUPS — referenced by AHL_REPAIR_CATEGORIES.SECURITY_GROUP_ID for multi-org data security.
• AHL_MEL_CDL_ATA_SEQUENCES — references AHL_REPAIR_CATEGORIES.REPAIR_CATEGORY_ID, making this table its parent for MEL/CDL ATA sequence configuration.
• CS_INCIDENT_TYPES_B — the sibling Service setup table commonly joined alongside CS_INCIDENT_URGENCIES_B when classifying incidents and their urgency-driven repair categories.

Table access is ordinarily performed directly rather than through a dedicated CMRO API, although forms in the AHL module maintain the records and respect the unique-index and primary-key constraints documented here.