SAP Analytics Cloud – Structured Allocations Migration to Data Actions (UPDATE)

[Alecsandra]

With QRC1 2024, we restricted the usage of the legacy Allocation Designer for designing new allocation processes and offered a manual migration path to data actions (more details can be found here). Continuing our product journey of gradually discontinuing the legacy Allocation Designer and running structured allocation processes as an integral part of data actions, we reached the next milestone of automatically migrating all legacy allocations to data actions.  

QRC3 - Important Updates Coming

With the SAP Analytics Cloud upgrade to QRC3, the legacy allocation processes and steps will be automatically copied and migrated to data actions, facilitating an easy transition from the legacy allocation functionality. Using the data actions going forward for defining and executing the structured allocation processes brings additional benefits, such as parameterizable data action triggers, multi-action execution, and automated planning processes (visit SAP help for more details).

The migration will ensure a smooth transition by maintaining the following:

• The data action representations of the legacy allocations will retain all existing relations between allocation steps, processes and data actions embedded legacy allocations.
• Each allocation process is copied and migrated to a dedicated data action. Its properties, like name and description, are transferred to this data action for easy retrieval. The process's legacy allocation steps are migrated as data action steps.
• The legacy allocation steps used multiple times in different allocation processes and/or data actions will be created as nested data actions.
• The privileges transfer is part of the migration. This means the corresponding created data actions will be governed by the same user- and team- privileges as the original legacy allocations. Privileges of existing teams and users with access to legacy allocations are adapted to access the newly created data actions. Besides, new teams with the name prefix "StructuredAllocationRole" will be created during the migration to cover specific user, team and role configurations. A Planning Professional license is required to access, edit, and execute data actions. 

The automatically created data actions will be accessible from the newly created Files > My Files > Public > Structured Allocations folder.

Image 1 Migrated legacy allocations

 Note: You will retain view-only access to legacy allocations through the Allocation Legacy Designer. However, editing legacy allocation processes or steps will no longer be possible.

Image 2 Using the Legacy Designer does not allow creating new allocations

Although the execution of legacy allocations is still supported, we strongly advise updating your legacy structured allocation execution workflows. As a reminder, users triggering legacy allocations from stories will receive a notification advising them to transition to data actions.

Image 3 Message displayed upon legacy allocation execution

The final phase of discontinuing legacy allocations is expected with the QRC4 update. Then, we will no longer support the execution of legacy allocations. Please use the automatically migrated data action representations or manually migrate your allocations in the oncoming release period (QRC3 until QRC4) and update your planning workflows accordingly. We plan to retire the legacy designer completely with QRC1 in 2025.

Please use the Commenting section if you have any questions or require assistance with the structure allocations transition to data actions!