Context Aware Data Action Scoping

[ScottGodfree]

Overview

Data actions are a critical component of end-to-end planning workflows in SAP Analytics Cloud, supporting everything from seeding, to allocations, to complex calculations. Despite their importance, one lingering question has persisted: how can we optimize the data action to process only the minimum data required based on user actions?

Until now, users have not had a straightforward mechanism for discrete change tracking at the planning record level - no built-in way to identify which specific dimension members or data was actually changed in a version during a planning session. Progress has been made in related areas: the Planning Area concept significantly improved the ability to limit the scope of data brought into a Public Edit session (and thus processed by a data action), and scripted approaches using the onAfterDataEntryProcess table event have allowed developers to capture changed members and pass them to data actions via parameters (see The onAfterDataEntryProcess event in SAC).  While certainly helpful, these either do not address this core issue of data action processing, or do so in a way that requires custom development effort, carries some risk, and are not always transparent.

Without a native way to know exactly what changed, the result has been that data actions are often scoped more broadly than necessary, which can lead to longer run times and consumption of unnecessary resources. That changes with our Q3/2026 QRC release.

Introducing Change-Context Data Action Scoping

Change-context data action scoping builds on the new Data Filter parameter capability, also introduced in our Q3/2026 QRC release (see Improved Data Action scoping with the new Data Filter Parameter type for a full overview).  It allows the data action author to use a data filter to define specific dimension(s) along which to track user updates (such as Cost Center, Product, or Time). During runtime, the system automatically identifies which members within the designated filter dimensions have changed data in the target version (or another designated version), and those members then become the filter scope.  No custom scripting, no workarounds - just a simple configuration option which tells SAC to automatically scope data action processing to the dimension elements where data that was actually changed by the user.

Using Change-Context Scoping

Change tracking is easily enabled within the data action during definition of the data filter parameter. When adding a new parameter, the data action author selects two inputs within the configuration: the dimensions to track changed members on (for example, Cost Center, Time, or Product), and the version to inspect for changes (either a fixed version such as Budget 2026, or a reference to a version parameter such as the target version). These are configured within the Input section of the parameter definition by changing the Visibility setting to Private, after which the data action author can add the specific dimension filter(s) and the relevant version for change tracking. At runtime, SAP Analytics Cloud identifies which members of the dimension(s) have modified records in the reference version and uses those as the filter scope.

If multiple dimensions are selected within the filters, then the data action will run on the cartesian product of impacted members across the applicable dimensions.

Note: The change-context filter should be configured as a dedicated data filter, distinct from any filters and input controls used to filter the story data. Setting the data filter parameter type to Private, and then selecting the ”Auto-Determined by version changes” ensures it operates as the change-tracking filter. Once configured, as with other parameters, the change-context data filter needs to be applied to the filter section for the relevant data action steps where filtering is required.

The change context members accumulate across runs — subsequent executions will include members changed in earlier runs within the same version, and resets on version publish.

Figure 1: Parameter Definition

Figure 2: Parameter Assignment

The included screenshots illustrate a scenario with a data action that performs a currency conversion and has configured change-context tracking enabled on the EB_OPEX_CC (cost center) dimension.  When the user enters data changes on the Information Technology cost center (see below), the data action runtime parses the user updates and detects Information Technology as the only cost center dimension element that has modified records, and scopes the execution accordingly (as can be seen in the Job Monitor for the specific execution).

Figure 3: Data Action Execution

 

Figure 4: Job Monitor

Summary

Change-context data action scoping is a meaningful step forward in making planning workflows in SAP Analytics Cloud more intelligent and efficient. By equipping data actions with native awareness of user changes, calculations automatically target only what’s been modified—streamlining processing and boosting responsiveness.   Easily configured in the data action designer with just a dimension selection and reference version, it eliminates the need for custom scripting or other complex workarounds.

We’d love to hear how it works for you—please share your experiences and feedback in the comments below.