Search Results ahl_unit_deferrals_b_u2

Overview

The table AHL.AHL_UNIT_DEFERRALS_B is a core transactional base table within the Oracle E-Business Suite (EBS) Complex Maintenance, Repair, and Overhaul (CMRO) / Advanced Service functionality, owned by the AHL schema. It stores deferral and Maintenance Requirement (MR) initialization information associated with a unit effectivity record. In operational terms, this table records decisions to defer, skip, or reset the due dates of maintenance requirements for a specific configuration of a serialized unit — for example, deferring an inspection requirement on a particular aircraft tail number for a defined period.

From a Data Vault modeling perspective, the heuristic classification for this object is satellite-leaning. The table carries descriptive, time-stamped attributes about a deferral event — status codes, effective dates, flags, reason codes, and standard Who columns — rather than functioning as a pure hub or a many-to-many link. It does, however, hold foreign keys to AHL_UNIT_EFFECTIVITIES_B, AHL_MEL_CDL_ATA_SEQUENCES, and FND_SECURITY_GROUPS, which gives it a modest link-like quality. The metadata records the table status as VALID with FND Design Data registered as AHL.AHL_UNIT_DEFERRALS_B, and it is stored in the APPS_TS_TX_DATA tablespace.

Key Information Stored

The table contains 35 documented columns. The most significant are summarized below, distinguishing the surrogate primary key from the documented business-key candidates.

• UNIT_DEFERRAL_ID (NUMBER) — Surrogate primary key (AHL_UNIT_DEFERRALS_B_PK) and the unique identifier for a unit effectivity deferral detail. It is also the sole column of unique index AHL_UNIT_DEFERRALS_B_U1.
• UNIT_EFFECTIVITY_ID (NUMBER) — Foreign key to AHL_UNIT_EFFECTIVITIES_B; identifies the unit effectivity to which the deferral applies. Together with UNIT_DEFERRAL_TYPE it forms the composite business-key candidate enforced by unique index AHL_UNIT_DEFERRALS_B_U2.
• UNIT_DEFERRAL_TYPE (VARCHAR2(30)) — System deferral type; documented as for internal use only.
• SET_DUE_DATE (DATE) — Manually set due date applied at initialization or at the time a maintenance requirement is deferred.
• APPROVAL_STATUS_CODE (VARCHAR2(30)) — Approval status of the deferral, driving workflow and release decisions.
• SKIP_MR_FLAG (VARCHAR2) — Indicates whether the maintenance requirement has been skipped ('Y'/'N').
• AFFECT_DUE_CALC_FLAG (VARCHAR2) — Indicates whether the deferral due date cascades into future due dates for the maintenance requirement ('Y'/'N').
• DEFER_REASON_CODE (VARCHAR2(240)) and USER_DEFERRAL_TYPE — Reason and user-facing classification of the deferral.
• DEFERRAL_EFFECTIVE_ON (DATE) — Effective date from which the deferral applies.
• CANCEL_FLAG — Denotes cancellation of a deferral record.
• ATA_SEQUENCE_ID (NUMBER) — Foreign key to AHL_MEL_CDL_ATA_SEQUENCES, linking the deferral to ATA chapter sequencing data.
• SECURITY_GROUP_ID (NUMBER) — Foreign key to FND_SECURITY_GROUPS; used in application hosting.
• OBJECT_VERSION_NUMBER (NUMBER) — Locking sequence number supporting optimistic concurrency control.
• Standard Who columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
• Descriptive flexfield columns ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 provide extensibility.

Common Use Cases and Queries

Typical reporting scenarios include listing all active deferrals for a unit, identifying deferrals pending approval, and auditing deferrals that alter future due-date calculations.

To retrieve deferrals for a given unit effectivity, resolving the composite business key:

• SELECT d.unit_deferral_id, d.unit_deferral_type, d.set_due_date, d.approval_status_code, d.defer_reason_code FROM ahl.ahl_unit_deferrals_b d WHERE d.unit_effectivity_id = :p_unit_effectivity_id ORDER BY d.deferral_effective_on DESC;
• SELECT * FROM ahl.ahl_unit_deferrals_b WHERE approval_status_code = 'PENDING' AND cancel_flag IS NULL;
• SELECT unit_effectivity_id, unit_deferral_type, COUNT(*) FROM ahl.ahl_unit_deferrals_b GROUP BY unit_effectivity_id, unit_deferral_type;

Because the table stores approval status and effective dates, it is commonly joined to AHL_UNIT_DEFERRALS_TL to obtain translatable/display text and to AHL_UNIT_THRESHOLDS to correlate deferrals with threshold monitoring. Care should be taken to filter on CANCEL_FLAG and to respect SECURITY_GROUP_ID when multi-org/security-group partitioning applies.

Related Objects

• AHL_UNIT_EFFECTIVITIES_B — Parent object; joined via AHL_UNIT_DEFERRALS_B.UNIT_EFFECTIVITY_ID = AHL_UNIT_EFFECTIVITIES_B.UNIT_EFFECTIVITY_ID. Defines the unit configuration to which the deferral applies.
• AHL_UNIT_DEFERRALS_TL — Holds translation/description rows referencing UNIT_DEFERRAL_ID; joined on AHL_UNIT_DEFERRALS_TL.UNIT_DEFERRAL_ID = AHL_UNIT_DEFERRALS_B.UNIT_DEFERRAL_ID.
• AHL_UNIT_THRESHOLDS — References UNIT_DEFERRAL_ID; used to associate deferrals with threshold tracking.
• AHL_MEL_CDL_ATA_SEQUENCES — Referenced via ATA_SEQUENCE_ID; supplies ATA chapter/sequence context for MEL/CDL deferrals.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; supports hosted/partitioned deployments.

These relationships make AHL_UNIT_DEFERRALS_B a central detail table for maintenance deferral tracking, complemented by its translation and threshold companion tables.