Full questions with full answers — no sign-in required.
easyDatasphere Spaces, Data Builder and Business Builder
1. What is a Data Action in SAP Analytics Cloud and when would you use one instead of a simple input template?
A Data Action is a scripted, server-side procedure in SAC that performs multi-step calculations across a planning model, such as copy, allocation, distribution, or conversion logic using advanced formulas and steps. You use it instead of manual input when business logic needs to run consistently across many records, requires looping/conditional logic, or must be triggered on demand (e.g., copy actuals to plan) rather than relying on manual cell entry.
mediumDatasphere Spaces, Data Builder and Business Builder
2. Your team needs to replicate delta changes from an S/4HANA source table into Datasphere on an ongoing basis using the BW Bridge space, and later expose this data through an analytic model. How would you approach this using Replication Flows?
Create a Replication Flow in the Data Builder that sources the S/4HANA table using an appropriate connection supporting delta capture, selecting the target as either a standard Datasphere space or the BW Bridge space depending on where downstream BW-style modeling is needed. Configure the load type as initial plus delta if supported by the source. Once the replicated table lands in the target space, build a view exposing needed fields, then create an analytic model on that view for consumption in SAP Analytics Cloud.
mediumDatasphere Spaces, Data Builder and Business Builder
3. When configuring a Multi Action that chains several Data Actions together, what execution behavior and dependency settings must you configure to ensure correct sequencing and rollback?
In a Multi Action you sequence Data Actions in the order they must execute, and each step runs against the outputs of the prior step since Multi Actions execute serially, not in parallel. You configure prompts once for shared parameters, and if any step fails the entire Multi Action stops and no partial commit occurs for that run, so you must test each contained Data Action independently before chaining, and document dependencies since there is no native conditional branching between steps.
hardDatasphere Spaces, Data Builder and Business Builder
4. You are designing the connection and flow architecture for a multi-source Datasphere landscape combining SAP ECC, a third-party cloud application, and HANA Cloud native tables, feeding a harmonized reporting layer. What architectural decisions would you make regarding connection types and flow orchestration?
I'd use SLT or a Replication Flow with CDC for the ECC source to capture deltas efficiently, an API-based or OData connection for the third-party cloud app given likely lack of CDC support, and direct modeling on native HANA Cloud tables without replication since they're already local. I'd orchestrate Transformation Flows downstream of the replicated/staged data to harmonize schemas into a common reporting layer, sequencing flow triggers so transformations only run after successful replication completion, and isolate staging objects in a dedicated integration Space before exposing curated models to consuming Spaces.
mediumDatasphere Spaces, Data Builder and Business Builder
5. A story built on an S/4HANA live model is timing out for business users during month-end close reporting. What steps would you take to diagnose and resolve the performance issue?
First check story design for excessive widgets, unoptimized charts, or too many concurrent live queries hitting S/4HANA. Review filter usage, default variables, and whether users are pulling wide date ranges. Consider adding input controls to force filtering before query execution, reduce visible data via default views, and check S/4HANA-side load during month-end. If persistent, evaluate switching high-use tables to an acquired model with scheduled refresh.
mediumDatasphere Spaces, Data Builder and Business Builder
6. A regional planner reports that the calendar task for their forecast submission shows as complete even though they never opened the task, while a colleague in another region with the same role assignment must manually mark theirs complete. Both work in a BW-sourced planning model. What calendar and security configuration areas would you check to explain this inconsistency?
I would check whether the task's completion is tied to an automated trigger, such as a Data Action or approval workflow step, versus manual user confirmation, since calendar tasks can be configured either way. I'd verify the task template and assignment settings for both regions weren't configured differently, check if the affected planner's task was linked to a step that auto-completes on data save, and review team/role assignments in case the planner inherited a task through a group rather than direct assignment, causing different completion behavior.
