
Organizational structures are constantly evolving. Cost centers change departments, corporate hierarchies are restructured at the turn of the year, and product categories are renamed. For reporting that not only reflects the current status but also remains accurate retrospectively, a simple, static hierarchy is insufficient. This is precisely where one of SAP Datasphere's most interesting—and still underappreciated—capabilities comes into play: Hierarchy with Directory.
Since 2023, SAP DataSphere has offered its own semantic usage for parent-child hierarchies called Hierarchy with Directory. It's important to understand that this is not simply an extension of the classic hierarchy within a dimension, but rather an independent entity type – designed for the structured integration of hierarchies from SAP S/4HANA and SAP BW, such as general ledger, cost center, or profit center hierarchies, which already have their own versioning and time logic in the source system.
The really interesting aspect arises when one adds time dependency – on three independent levels:
The whole thing is controlled via a Reference Date Variable In the Analytic Model: The user selects a cut-off date, and Datasphere automatically considers only the hierarchy, the assignments, and the texts valid at that time – all three levels combined.
In practice, this affects every reorganization: If cost centers, sales territories, or product structures change, historical analyses must not retroactively become "incorrect." A report for Q4 2025 must reflect the structure valid at that time—even if the system is already using the structure for 2026. This is precisely what the combination of time-dependent hierarchy, time-dependent assignments, and time-dependent texts enables: analyses based on a specific date remain possible, regardless of how often the business reality has changed since then.
This is particularly valuable for scenarios where hierarchies are adopted from SAP S/4HANA or SAP BW – time dependency is often already inherent in the source system, and Hierarchy with Directory maps it structurally in Datasphere instead of simplifying it.

Hierarchy with Directory is more than just a technical feature for modelers. It forms the basis for ensuring that reporting and planning remain reliable even as organizational or business realities constantly evolve.