Search Results ahl_fleet_headers_b_u1

Overview

AHL.AHL_FLEET_HEADERS_B is the base table in the Oracle E-Business Suite Fleet Management (AHL) module that stores fleet header definitions — the top-level master records representing a fleet of maintainable assets. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the AHL schema, is registered as FND Design Data AHL.AHL_FLEET_HEADERS_B, and carries a VALID status. Fleet headers act as the grouping construct under which individual fleet instances, operating organizations, and departmental ownership are organized for maintenance planning and execution.

Physically the table is stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and exposes 30 documented columns. The metadata includes the "_B" suffix convention typical of EBS translated (base) entities; the corresponding "_TL" table normally holds language-dependent descriptive text, while this base table holds the language-independent fleet attributes. The metadata relationship data classifies this object heuristically as a standalone entity, so a Data Vault modeling suggestion would treat it as a hub candidate keyed on the fleet identifier rather than as a link or satellite.

Key Information Stored

• FLEET_HEADER_ID — surrogate primary key for the fleet header record; also the target of unique index AHL_FLEET_HEADERS_B_U2.
• NAME — the business name of the fleet; the target of unique index AHL_FLEET_HEADERS_B_U1, making it the primary business-key candidate.
• OPERATING_ORG_ID — the operating organization (inventory organization) context in which the fleet is maintained.
• DEPARTMENT_ID — owning department; foreign key to BOM_DEPARTMENTS.
• OPERATIONS_TYPE_CODE — classifies the operational nature of the fleet for maintenance processing rules.
• STATUS_CODE — lifecycle/status indicator governing whether the fleet header is active and usable.
• COMPLETION_DATE — date the fleet header record reached its terminal or completed state.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework during concurrent DML.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; supports multiple-organization / data-security partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS DFF (Descriptive Flexfield) column set providing user-extensible attributes; each ATTRIBUTE n is VARCHAR2(150).
• Who-columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN capture audit lineage.

Common Use Cases and Queries

Typical usage covers fleet roster reporting, organisation-based fleet counts, maintenance work-order scoping, and retrospective audit of fleet status changes. The most common access path is the NAME unique index, which supports exact lookup of a fleet by its business name.

-- Look up a fleet by its unique business name
SELECT fleet_header_id, name, operating_org_id, department_id,
       operations_type_code, status_code, completion_date
FROM   ahl.ahl_fleet_headers_b
WHERE  name = :p_fleet_name;

-- Fleet roster for an operating organization
SELECT f.fleet_header_id, f.name, d.department_code, f.status_code
FROM   ahl.ahl_fleet_headers_b f,
       bom.bom_departments d
WHERE  f.department_id       = d.department_id
AND    f.operating_org_id    = :p_org_id
AND    f.status_code         = 'ACTIVE';

Because the table exposes 15 descriptive flexfield attributes, reporting queries frequently project ATTRIBUTE_CATEGORY with the relevant ATTRIBUTEn columns to surface client-specific fleet classifications. Note the "_B" suffix: many reports join to AHL.FLEET_HEADERS_TL to retrieve language-dependent descriptions, filtering by the current session language.

Related Objects

• FND_SECURITY_GROUPS — joined via AHL_FLEET_HEADERS_B.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID; drives org-level data security.
• BOM_DEPARTMENTS — joined via AHL_FLEET_HEADERS_B.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID; identifies the owning department.
• AHL_FLEET_HEADERS_TL — the language-dependent translation table keyed on FLEET_HEADER_ID; supplies fleet display names/descriptions.
• AHL_FLEET_INSTANCES / AHL_FLEET_ child tables — the metadata indicates AHL_FLEET_* objects reference this header, so fleet instance and composition children are joined on FLEET_HEADER_ID.
• AHL maintenance and work-order objects — fleet maintenance activities (visit, work order, and procedure associations in the AHL module) resolve their fleet context through FLEET_HEADER_ID.
• Generic EBS concurrency/audit framework — OBJECT_VERSION_NUMBER and the who-columns are consumed by the standard Forms/ADF-based maintenance screens servicing this table.