Configuring and Using a Planning Area

Planning on large versions can affect performance. Queries and planning actions largely impact on the performance of planning models can be optimized to reduce processing time when working with large public versions. In this lesson, we explore the planning area and how creating a custom planning area can improve the performance of your planning model.

What is a planning area? From a planner’s perspective, the planning area represents the editable data slice, or plannable data, in a working session. This data slice is much smaller than the complete version. So, by optimizing the planning area, you keep the data size manageable and can work on data that’s the most relevant to you. It is especially useful if you’re trying to limit the data size of a model with a large public version that’s not limited.

How does it work? Working on large versions can impact performance and configuring your initial planning area with only the data that is needed can improve performance. Once the planning area is configured, you complete your data entry directly in your planning table. The planning area automatically generates based on the planning context. This allows you to change table filters and plan across many tables without having to actively manage your planning areas.

You configure the Performance Parameter and the Recommended Planning Area settings in the Planning tab of the Model Preferences.

Planning Parameter: The initial planning area has a default parameter of 5 million database records. If you create a data snapshot that exceeds the configured parameter, for example, while creating a private version or starting to edit a public version, then you are notified. You can choose to either proceed or create a private version with more filters.

The planning parameter can be adjusted, as planning performance depends on multiple factors, some of which include, the number of dimensions, the complexity of the dimensions, calculations, or the number of concurrent users.

Although this limit can be overridden, if you have large datasets, then it is best to first rethink the model design and ask yourself if these large datasets are really necessary. Using the Private Versions Statistics and Analysis Tool will allow you to review and keep version sizes managed.

To check if the data size and the limits for acquiring data are within the SAP Analytics Cloud limitation, see the SAP Help Portal: System Sizing, Tuning, and Limits

Recommended Planning Area: Use the options in this section to restrict the recommended planning area. You can limit the size of the recommended planning area by selecting either Based on Data Access Control and Model Privacy or Based on Data Locking, or both (they must, however, be enabled and configured). When you edit a public version, the application stores a reduced data snapshot but still shows locked data outside of that snapshot.

You can select Set 'Auto-generate based on table context' as Default to reduce the size of your planning area based on the table you are working in. If you choose to set this feature as the default, you can disable it from the builder panel when working with individual tables if required. When it is enabled, the editable slice of data you can plan on takes into account data access control and data locking (as selected and configured), as well as the current table context that covers story, page, and table filters.

A planning area is automatically created when you start manual planning or executing data actions for planning.

In the following example, you can see a table widget and the planning settings available to you in the builder panel.

In the following example, you can see a data action starter and the planning settings available to you in the builder panel.

Select Recommended Planning Area from the list of options available in the Default strategy if target version isn’t in edit mode dropdown. If the target version in the starter is a public version, then the data action (as well as multi action and data upload actions) will only run on data within the planning area.

Now that you understand how to customize the planning area and how it can impact on the performance of your model, let's explore how you can use the planning area when you select Set 'Auto-generate based on table context' as Default in the Model Preferences.

When the Auto-generate based on table context option is selected, the system creates or extends planning areas as plan values change. When you make a change, you go to Version Management, and if the public version forecast is in Edit Mode (Limited), then you know that the planning area was generated. In the Details panel, you can see the entities that were included and the number of records that were updated with the change.

Planning areas can significantly improve performance, especially in large planning versions by reducing the size of your planning area based on the table you are working in. The Edit Mode (Limited) is an editable slice of data that you plan on which takes into account data access control and data locking (as selected and configured), as well as the current table context that covers story, page, and table filters.