Search Results ahl_unit_accomplishmnts




Overview
Explore in AI Chat

Overview

AHL_UNIT_ACCOMPLISHMNTS is a table within the AHL schema, owned by the Complex Maintenance Repair and Overhaul (AHL) product of Oracle E-Business Suite. As stated in the ETRM documentation, the table contains all instances of counter values captured at the time of accomplishment. In the context of AHL, a unit represents a maintainable asset or configuration item tracked against a maintenance program, and an accomplishment records that a maintenance task, requirement, or visit has been executed against that unit. The counter values persisted here therefore represent a point-in-time snapshot of an asset's usage drivers — such as flight hours, cycles, or operating hours — at the moment a maintenance accomplishment was recorded. This makes the table the authoritative historical record linking usage data to the maintenance events that consumed that usage.

From a data modeling perspective, the metadata's heuristic Data Vault classification suggests a satellite-leaning role. The table carries a surrogate primary key on UNIT_ACCOMPLISHMNT_ID and a foreign key to AHL_UNIT_EFFECTIVITIES_B, which is consistent with a satellite attached to a parent effectivity or accomplishment hub, holding descriptive and measured counter values rather than defining new business entities on its own.

Key Information Stored

The documented physical schema for release 12.2.2 comprises 27 columns. The most significant for functional and reporting purposes are:

The unique index AHL_UNIT_ACCOMPLISHMNTS_U2 on (UNIT_EFFECTIVITY_ID, COUNTER_ID) constitutes the business-key candidate, ensuring that for a given unit effectivity only one accomplishment snapshot exists per counter.

Common Use Cases and Queries

The primary reporting use case is extracting usage snapshots for a specific unit effectivity to compare against maintenance thresholds. A typical query joins this table to the unit effectivity parent and filters by counter:

SELECT a.UNIT_ACCOMPLISHMNT_ID, a.UNIT_EFFECTIVITY_ID,
       a.COUNTER_ID, a.COUNTER_VALUE, a.CREATION_DATE
FROM   AHL_UNIT_ACCOMPLISHMNTS a
WHERE  a.UNIT_EFFECTIVITY_ID = :p_unit_effectivity_id
AND    a.SECURITY_GROUP_ID  = :p_security_group_id;

Because the table stores the counter value at the time of accomplishment, it supports trending analysis: plotting COUNTER_VALUE over time per COUNTER_ID reveals utilization rates and can be used to project when the next maintenance interval becomes due. Maintenance planners and reliability engineers use these queries in custom reports and OBIEE extracts where AHL's standard counter monitoring functions need historical rather than current data. The DFF columns enable organization-specific classification, so filters on ATTRIBUTE_CATEGORY and an ATTRIBUTE column are a common way to drive attribute-based reporting.

Related Objects

  • AHL_UNIT_EFFECTIVITIES_B — referenced via UNIT_EFFECTIVITY_ID; the parent business entity to which each accomplishment counter record belongs.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces security partitioning of rows.
  • AHL_UNIT_ACCOMPLISHMNTS_PK — the primary-key constraint on UNIT_ACCOMPLISHMNT_ID.
  • AHL_UNIT_ACCOMPLISHMNTS_U1 and _U2 — the unique indexes enforcing the surrogate and business keys respectively.
  • AHL counter and counter value tables — referenced through COUNTER_ID to resolve the identity and properties of each usage counter.
  • AHL accomplishment and maintenance-program tables — related through UNIT_EFFECTIVITY_ID to obtain task, requirement, and effectivity context for the recorded snapshot.
  • Public AHL APIs and concurrent programs that persist program accomplishments write into this table on task completion.