3339163 - Single hierarchy load for a public dimension with multiple hierarchies not working correctly

The solution in KBA 3027725  does not work for for “Generic” type public dimensions .

• SAP Analytics Cloud 2023.8.8

1. Create a new public dimension, making sure the dimension type is set to Generic.
2. Locate the hierarchies drop down in Dimension Details. There should be no pre-existing parent-child Hierarchy. Click on the plus icon next to Hierarchies heading, then select Parent-Child hierarchy.
3. Once the 2 Hierarchies have been created, save the Dimension. Then go to Workspace in the top left and click on the drop down to open up Data Management.
4. The source of the data we will be working with will be a file. Click on file and set the desired file as your source.
5. Once you’ve selected the source file, click on set up import. This will take you to the following page. Here you can see what mappings SAC has carried out and how it has treated each cell, specifically the empty ones. The whole of hierarchy 2 has been populated with <root> as expected.
6. Map Hierarchy1 with Hierarchy and Dimension ID with Member ID. Once that’s been done, click on the X next to Hierarchy 2 under Dimension Mapping to remove the mapping of the Hierachy2 column and Hierachy2 attribute, this is because we have no data within that hierarchy and we are only trying to import Hierarchy1.
7. Back in the Dimension view, we can see that Hierarchy1 has been imported as expected with the Region of countries being assigned the <root> attribute as expected. However we can see that Hierarchy2 has been brought along too in the import which was not a desired outcome as we specifically only had Hierarchy1 mapped.
8. The resolution suggests to do multiple import sessions however this was proven in the above scenario with Generic dimension to not work.

This is a current product limitation.

A new feature will be introduced, which allows users to set a mandatory/optional flag for each property (including hierarchy) of a dimension.  When a hierarchy is set to mandatory, any new member must be in the hierarchy and thus will get a <root> by default (such as when the hierarchy is not mapped during data import). Whereas when the hierarchy is set to optional, new member will then be not belonging to this hierarchy when the hierarchy is not mapped in the import process. 

The new feature is planed to release for 2024.

3027725 - When the hierarchy is imported, <root> is automatically created as member if the there is no data for the row in SAP Analytics Cloud (SAC)

<root> , account , model  , KBA , LOD-ANA-AQU , Import Data Connections (Acquiring Data) , Problem