Introduction
Planning Area introduced in 2021 is intended to reduce the scope of public edit version and private version. The performance of planning actions in story and data actions/multi actions highly depends on the size of planning area. The smaller that Planning Area size is, the better the performance of planning action is.
To understand the concept of planning area and its influence on performance, please refer to help doc.
With Table Context for planning area definition released in QRC4.2023, planning area is created as small as possible.
Now we are pleased to release a further optimization of planning area as part of SAP Analytics Cloud QRC2.2024. Planning area is extended seamlessly and dynamically without user interference. Planner doesn't need to be bother with planning area and if planning area is setup in a right way. System creates and maintains planning area sophistically to optimize the performance and resource consumption.
Workflows
For this blog post, we will review the configurations required and how the planning area is fully optimized.
Firstly, in model preference, "Recommended Planning Area" is moved to "Planning" tab.
Secondly, the two options to enable planning area based on Data Access Control or Data Lock remain.
Thirdly, a new option to set "auto-generated based on table context" as default is introduced , making the "public edit version based on the table context" default for all newly created tables. We will focus more on this new option in this blog post.
Now, let's move to Story table. The toggle “Auto-generated based on the table context” in the builder panel of the table should be enabled. If "auto-generated based on table context" is enabled for model, all newly created tables have this toggle enabled by default. Or else story designer can easily enable it in build panel of the table.
All configurations are done! These are fairy simple and straightforward.
Now, let's switch to the view of end user. The end user opens the story and the table is restricted to "2023.Q2" by page filter. He starts to edit a cell and a public edit version is created. Planning Area Scope for this public edit version is "2023.Q2".
Planning Area Scope can be found with Version Management and "Details" of a version.
He changes page filter to another date member "2023.Q3", and edits the cell for "2023.Q3". Behind the scenes, public edit version is extended to "2023.Q3" dynamically. As an end user, he doesn't need to take care planning area, which is created and extended sophistically to optimize the performance and resource consumption.
Note: if "Based on Data Access Control and Model Privacy" and "Based on Data Locking" are enabled, the extension of planning area is also limited based on data locking, data access control and model privacy, or both.
Planning area is a critical performance factor for planning actions. Maintaining planning area as small as possible really makes a big difference from a performance perspective.
Others
One more change and an important safety belt that is the limit to a 100 million for a planning area that we create in interactive workflows. Interactive workflows mean the workflows with table, incl. data entry, copy&paste, and distribute values. Model admin can customize the most suitable planning area size.
The one limitation that we still have is that data actions are not yet able to dynamically extend the planning area in case I run data action that needs to write data or create data outside of my existing planning area. This right now will end up running into an error message.
- SAP Managed Tags:
