Results for “ahl_space_capabilities”

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

Overview

The AHL_SPACE_CAPABILITIES table resides in the AHL schema and belongs to the Oracle Complex Maintenance, Repair and Overhaul (CMRO) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store information about space capabilities — that is, the qualifying attributes that describe what a given maintainable space (such as a hangar bay, dock position, or shop floor area) is equipped and authorized to accommodate. In the CMRO model, spaces represent physical maintenance locations, and this table records the capability attributes that constrain or enable work to be scheduled or performed within those locations.

From a heuristic Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning. It carries a surrogate primary key and several descriptive attributes tied to a parent space record, with no downstream tables depending on it through foreign keys. This suggests it functions as a descriptive satellite attached to the AHL_SPACES_B hub rather than as an independent hub or a connecting link table.

Key Information Stored

The table contains 28 documented columns, of which the most significant are:

• SPACE_CAPABILITY_ID — the surrogate primary key, defined by the unique index AHL_SPACE_CAPABILITIES_U1 and constraint AHL_SPACE_CAPABILITIES_PK. This is the only documented business-key candidate; it is a system-generated identifier rather than a natural key.
• SPACE_ID — a foreign key to AHL_SPACES_B that establishes the owning space. This is the primary relationship column and the anchor for any join to the physical space definition.
• VISIT_TYPE — the visit or work-visit classification associated with the capability, used to determine which visit categories the space can support.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — reference the inventory item and inventory organization context, linking the capability to a specific item and operating organization.
• SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enforcing multi-org / data-security partitioning across the capability records.
• OBJECT_VERSION_NUMBER — the optimistic locking control used by the OA Framework to detect concurrent updates.
• Standard WHO audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — capture the creation and modification history of each row.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns, providing an extension area for client-specific capability attributes without schema modification.

Common Use Cases and Queries

The most frequent operational need is listing all capabilities defined for a given space, typically as part of space configuration review or maintenance planning:

• Retrieving capabilities by space: SELECT * FROM AHL.AHL_SPACE_CAPABILITIES WHERE SPACE_ID = :p_space_id;
• Joining to the parent space to present a readable result: SELECT c.SPACE_CAPABILITY_ID, c.VISIT_TYPE, c.INVENTORY_ITEM_ID FROM AHL.AHL_SPACE_CAPABILITIES c, AHL.AHL_SPACES_B s WHERE c.SPACE_ID = s.SPACE_ID;
• Filtering by visit type and organization to validate whether a space supports a planned visit category.
• Reporting on capabilities by inventory item to determine which spaces are qualified to handle a specific item or component.
• Security-scoped extracts restricted by SECURITY_GROUP_ID for multi-org reporting.
• Flexfield-based analytics using ATTRIBUTE_CATEGORY and the ATTRIBUTE1–ATTRIBUTE15 columns for customer-defined capability classifications.

Because the table is satellite-leaning and carries audit and version columns, queries used for integration or reconciliation should filter or expose LAST_UPDATE_DATE and OBJECT_VERSION_NUMBER to detect stale or concurrently modified records.

Related Objects

• AHL_SPACES_B — the base space table; joined on AHL_SPACE_CAPABILITIES.SPACE_ID = AHL_SPACES_B.SPACE_ID. This is the principal parent relationship.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs data-security partitioning.
• AHL_SPACES_TL — the translated space table providing the language-specific names and descriptions of the owning space.
• AHL_VISITS / AHL_VISIT_TYPES — related through the VISIT_TYPE column, supporting capability-to-visit-category analysis.
• MTL_SYSTEM_ITEMS_B — referenced through INVENTORY_ITEM_ID for item master validation and reporting.
• HR_ALL_ORGANIZATION_UNITS / ORG_ORGANIZATION_DEFINITIONS — referenced through ORGANIZATION_ID for organization context.
• AHL_SPACE_CAPABILITIES_PK / AHL_SPACE_CAPABILITIES_U1 — the primary key constraint and unique index that enforce row identity on SPACE_CAPABILITY_ID.

These relationships make AHL_SPACE_CAPABILITIES a supporting descriptive object within the CMRO space model, consumed primarily for capability validation and reporting rather than as a transactional driver.