Results for “ahl_spaces_b”

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

Overview

AHL_SPACES_B is the base (non-translated) master table within the AHL — Complex Maintenance Repair and Overhaul product family in Oracle EBS 12.1.1 and 12.2.2. It stores the definition of spaces, meaning the physical or logical maintainable locations (bays, docks, cells, hangars, workshops, or slots) that are scheduled, assigned, and maintained as part of a complex MRO facility. The table holds the language-independent attributes of each space, while descriptive/translatable text is externalized to the companion AHL_SPACES_TL table. Ownership resides in the AHL schema, and the object is reported as VALID.

From a dimensional modeling perspective, the documented FK topology suggests this object behaves as a hub entity (hub-leaning classification). Its surrogate primary key, SPACE_ID, is referenced by multiple dependent tables, which is characteristic of a durable business entity acting as a central anchor in a Data Vault-style design. This classification is a modeling suggestion derived from relationship metadata rather than a functional statement of the table's purpose.

Key Information Stored

Although 28 columns are documented, the following are the most significant for understanding and querying the table:

• SPACE_ID — Surrogate primary key, enforced by AHL_SPACES_B_PK and additionally protected by unique index AHL_SPACES_B_U1, making it the primary business-key candidate for joins.
• BOM_DEPARTMENT_ID — Department associated with the space, linking it to the maintenance/bill-of-material organizational structure.
• SPACE_CATEGORY — User-defined or seeded classification that groups spaces by type (for example, hangar versus wash bay).
• ORGANIZATION_ID — Owning inventory/maintenance organization, enabling multi-org filtering.
• INACTIVE_FLAG — Indicates whether the space is currently active and available for assignment.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling data-level access in a multi-tenant or secured environment.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the AHL application layer during concurrent updates.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns for change tracking and compliance reporting.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1 … ATTRIBUTE15 — Descriptive flexfield (DFF) storage for customer-specific space attributes.

Common Use Cases and Queries

Typical usages include listing all active spaces for a given organization, resolving the descriptive name of a space via the TL table, and identifying spaces with no current assignment or capability. Reporting on space utilization frequently combines AHL_SPACES_B with assignment and capability data.

• Joining to the translated table: SELECT b.space_id, t.description FROM ahl_spaces_b b, ahl_spaces_tl t WHERE b.space_id = t.space_id AND t.language = USERENV('LANG');
• Filtering by organization and status: WHERE organization_id = :org AND NVL(inactive_flag,'N') = 'N'.
• Finding unassigned spaces by outer-joining to AHL_SPACE_ASSIGNMENTS.
• Auditing changes using LAST_UPDATE_DATE and LAST_UPDATED_BY, or extracting DFF values from ATTRIBUTE1–ATTRIBUTE15.

Related Objects

• AHL_SPACES_TL — Translation table joined on SPACE_ID; supplies language-specific name and description values.
• AHL_SPACE_ASSIGNMENTS — Records assignment of spaces to work, joined on SPACE_ID.
• AHL_SPACE_CAPABILITIES — Defines what a space can support, joined on SPACE_ID.
• AHL_SPACE_UNAVAILABLE_B — Captures periods for which a space is unavailable, joined on SPACE_ID.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID to enforce access control.
• BOM departments / organization references — Resolved through BOM_DEPARTMENT_ID and ORGANIZATION_ID for facility and organizational context.