SAP analytics topics by subject

When people ask me where to start with SAP analytics, my honest answer is that it depends entirely on the question you are trying to answer. A finance lead shaping a rolling forecast, a data engineer wiring Salesforce into a governed model, and an architect deciding whether to keep BW/4HANA alive to 2040 are all working in the same platform — but they are not reading the same page. Browsing by topic respects that. Instead of a single linear narrative, each hub below treats one concern as the protagonist and pulls the rest of the stack in only where it earns its place.

The hubs are not isolated, though. They map onto a fairly stable mental model that I find holds up across engagements. At the top sit the surfaces business users actually touch: SAP Analytics Cloud for stories, dashboards, and planning. Beneath that is the semantic and modeling engine — SAP Datasphere — where a "customer" or a "margin" gets a single governed definition that everything upstream can trust. Business Data Cloud wraps those two as a commercial bundle and adds the enterprise data foundation: SAP HANA Cloud, master data, the partner engines SAP Databricks and SAP Snowflake, and BDC Connect for sharing data products with external clouds without copying data. Around that core, three cross-cutting concerns run the full height of the stack — AI (Joule and the agent and prediction layer), BTP (the runtime that everything actually executes on), and integrations (how non-SAP systems and external data platforms join the picture). Governance, security, and administration is the discipline that keeps all of it trustworthy and operable. And BW/4HANA modernization is the question of how decades of existing investment coexist with, and eventually transition into, this newer shape.

A practical way to pick a starting hub is to name where your problem currently hurts. If users are complaining about dashboards or a forecast cycle, start at the consumption layer in SAP Analytics Cloud. If two reports disagree on the same number, the issue is almost always semantic, and SAP Datasphere is where it gets resolved. If the pain is commercial or you are trying to reconcile SAP data with a lake or warehouse, Business Data Cloud is the layer to study. If the conversation has turned to copilots, agents, or "can it just answer in natural language," the AI hub separates the durable patterns from the theater. And if you are wrestling with custom logic, third-party feeds, access control, or what to do with a long-standing BW estate, the BTP, integrations, governance, and modernization hubs each take one of those head-on. You rarely need all eight at once; you usually need one deeply and two nearby.

Read the topic map below as a quick orientation to those relationships, then drop into whichever hub matches the decision in front of you. None of these are dead-end reference pages — each one connects out to the deeper architecture playbooks, comparisons, and the 2026 landscape overview where the threads converge.

Each card opens a hub dedicated to a single layer of the stack. Pick the one that matches the problem on your desk today.

If you are not sure which hub fits, that usually means the question is an architecture question rather than a product one — and that is worth naming. A few starting points I point people to most often:

• You want the whole picture first. Read the SAP analytics landscape in 2026 for a layer-by-layer tour before you commit to a single topic.
• You are facing a real design decision. The architectures hub frames the five decisions — semantic ownership, planning, integration boundaries, governance, and modernization — that actually shape your stack.
• You are choosing between two options. The comparisons hub works through the side-by-side calls, like SAC versus Datasphere or whether to modernize BW at all.
• You are learning the platform from the ground up. The 15-week learning path sequences the whole stack, and the glossary keeps the vocabulary straight as you go.
• You work in one line of business. Three deep dives apply the stack to a single domain: SAP SuccessFactors people analytics, SAP Signavio process intelligence, and SAP Green Ledger and sustainability analytics.

However you navigate it, the principle behind these hubs is the same one I bring to every engagement: understand each layer on its own terms before you try to wire them together. The integration is always easier once the responsibilities are clear.