Results for “start_from”

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

Overview

AHL_SPACE_ASSIGNMENTS is a transactional table in the AHL schema (Complex Maintenance Repair and Overhaul) within Oracle E-Business Suite 12.1.1 and 12.2.2. It records the association of a physical space—such as a hangar bay, dock, shop floor location, or maintenance slot—with a specific visit. In the ETRM documentation this object is described simply as storing "information about space assignments," and its structure confirms that it functions as the intersection of the visit and space entities. In practical terms, this table is the mechanism by which EBS tracks who or what occupies a given maintainable location, and for what period, supporting capacity planning and scheduling within complex MRO operations.

The mined Data Vault classification is link, which is consistent with the documented foreign keys to AHL_VISITS_B and AHL_SPACES_B. The table resolves a many-to-many-style relationship between visits and spaces, with START_FROM and END_TO supplying the temporal validity of each assignment.

Key Information Stored

The table contains 28 documented columns. The most significant are:

• SPACE_ASSIGNMENT_ID — the surrogate primary key, enforced by AHL_SPACE_ASSIGNMENTS_PK and also unique through AHL_SPACE_ASSIGNMENTS_U1.
• VISIT_ID — foreign key to AHL_VISITS_B, identifying the visit occupying the space.
• SPACE_ID — foreign key to AHL_SPACES_B, identifying the assigned space.
• START_FROM and END_TO — the effective window of the assignment, enabling date-bounded reporting of occupancy.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security access control.
• OBJECT_VERSION_NUMBER — used for optimistic locking in the EBS framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns for customer-specific extensions.

No column is documented as a business-key unique index beyond SPACE_ASSIGNMENT_ID; referential integrity is delegated to the parent tables.

Common Use Cases and Queries

Typical reporting scenarios include occupancy tracking, space utilization analysis, and visit scheduling conflicts. A representative query joining the link to its parent entities is:

• SELECT sa.space_assignment_id, sa.visit_id, sa.space_id, sa.start_from, sa.end_to FROM ahl.ahl_space_assignments sa WHERE sa.space_id = :space_id AND sysdate BETWEEN sa.start_from AND sa.end_to;
• Join to AHL_VISITS_B to obtain visit context: ... FROM ahl_space_assignments sa, ahl_visits_b v WHERE sa.visit_id = v.visit_id.
• Join to AHL_SPACES_B for the location description: ... WHERE sa.space_id = s.space_id.

Because SECURITY_GROUP_ID is present, queries issued outside a secured session should filter or be run through an ORG-secured view. Analysts frequently use this table to detect overlapping assignments for the same SPACE_ID within a START_FROM/END_TO range.

Related Objects

• AHL_VISITS_B — parent visit entity; joined via VISIT_ID.
• AHL_SPACES_B — parent space entity; joined via SPACE_ID.
• AHL_SPACE_ASSIGNMENTS_PK / AHL_SPACE_ASSIGNMENTS_U1 — the primary and unique indexes on SPACE_ASSIGNMENT_ID.
• FND_SECURITY_GROUPS — security grouping referenced via SECURITY_GROUP_ID.
• Standard EBS WHO/DFF framework tables that consume the ATTRIBUTE and audit columns through the AHL business layer.

Together these relationships confirm AHL_SPACE_ASSIGNMENTS as the connective link between visits and spaces in the AHL module.