Hierarchies with Linked Nodes (Specifics for SAP BW)

SAP BW hierarchies with linked nodes are supported in SAP Analytics Cloud, with some restrictions.

Restriction

You can use SAP BW hierarchies that have linked nodes, but only in the optimized view mode and the optimized story experience.

For more information on the optimized story experience, see Optimized Story Experience.

You may need to apply a support package for this feature to work. For information on which support package to apply, refer to the following SAP Note:

SAP Note 3283848 desc: InA: Persisted InA Support Part X

SAP BW Linked Nodes - Story Restrictions

The following restrictions need to be considered when using the linked nodes in SAP Analytics Cloud stories.

Context	Description
A multi-tenant scenario Save/Open story Bookmarks	For SAP BW link nodes that exist in the query, the SIDs change when the tenant changes. If the SID was saved with the story and the story is then opened on another tenant, the SID can no longer be found. Instead of using the SID, the KEY is sent to the backend. However, the node that is selected from the backend may not be the one that you expect, but a different linked (or original) node.
Classic to optimized story conversion	If you have a classic design experience story that is using optimized view mode, when you open the View mode, the SAP BW linked nodes may not work for persisted InA. Workaround: Convert the story to optimized design mode and then save it before opening view mode.
Input control / Story filter	To be able to see the linked nodes inside the input control, you need to resave the optimized story. De-selecting a linked node will not trigger a query to fetch the whole hierarchy. After expanding or drilling, there might be some mismatch in the UI: one linked node appears selected, but the other one is not selected. This mismatch will automatically be fixed in the UI when you change the selection in the input control.

Context

Description

A multi-tenant scenario

Save/Open story
Bookmarks

For SAP BW link nodes that exist in the query, the SIDs change when the tenant changes.

If the SID was saved with the story and the story is then opened on another tenant, the SID can no longer be found.

Instead of using the SID, the KEY is sent to the backend. However, the node that is selected from the backend may not be the one that you expect, but a different linked (or original) node.

Classic to optimized story conversion

If you have a classic design experience story that is using optimized view mode, when you open the View mode, the SAP BW linked nodes may not work for persisted InA.

Workaround: Convert the story to optimized design mode and then save it before opening view mode.

Input control / Story filter

To be able to see the linked nodes inside the input control, you need to resave the optimized story.
De-selecting a linked node will not trigger a query to fetch the whole hierarchy.

After expanding or drilling, there might be some mismatch in the UI: one linked node appears selected, but the other one is not selected.

This mismatch will automatically be fixed in the UI when you change the selection in the input control.

SAP BW Linked Nodes - Table Restrictions

Context	Description
UDH	SIDs from the backend are also used for the Universal Display Hierarchy (UDH). However, for both linked nodes and duplicate nodes, the generated SIDs are not stable or unique. There is the added technical issue that these SIDs are assigned later than the drill operation.
Threshold	Currently, thresholds don't work properly in tables.
Frontend calculation (FEC)	Frontend calculation in table with linked nodes in hierarchical data is not supported.
CSV Export	CSV export with a hierarchy containing linked nodes and scope Point of view is not supported. Workaround: You can either select the Flatten the Hierarchy option or set the scope to All to get an export without the parent nodes.

SAP BW Linked Nodes - Chart Restrictions

Context	Description
Waterfall charts	Currently, SAP BW linked nodes are not supported in waterfall charts.
Expand	Currently, linked nodes don't work with the expand feature.