Introduction to SAP Embedded Analytics in the ICM Ecosystem

SAP SuccessFactors Incentive Management (IM) is a platform for managing compensation plans, quotas, and incentives at scale. But data is only valuable if you can see it. That is where Embedded Analytics enters—it is the built-in reporting capability that lets business users explore compensation data without waiting for an IT report or digging into a data warehouse. Yet many teams approach it incorrectly, either by trying to build everything in Embedded Analytics or by trying to use Crystal Reports for interactive dashboards. Understanding the three-tool ecosystem—Embedded Analytics, Crystal Reports, and SAP Datasphere—is the first step to picking the right tool for the job.

What is SAP Embedded Analytics?

SAP Embedded Analytics is the native reporting layer built into SAP SuccessFactors Incentive Management. It is not an external tool you bolt on. It is part of the product itself—accessed from within the IM user interface, connected directly to the SAP HANA Database that powers IM, and designed for business users to self-serve without IT involvement.

The key distinction from external BI tools: Embedded Analytics is embedded inside the IM product. You do not export data to a separate data warehouse or run a nightly ETL job. The instant the calculation engine completes a period run and writes results to the CSC_RESULTS table in SAP HANA Database, Embedded Analytics can read those results and display them in a dashboard. There is no delay, no separate data source, no copy of the data. It is live data from the system of record.

Embedded Analytics is technically a flavour of SAP Analytics Cloud (SAC)—the same cloud BI platform that SAP sells as a standalone product. But in the context of IM, SAC is pre-configured and embedded. You access it from the IM interface. The underlying technology is the same, but you do not need to be a SAC expert to use it.

The Three Reporting Tools and Their Jobs

This is the most important concept to understand early, because confusion about the three tools is where implementations derail. Each has a distinct job:

Embedded Analytics = interactive exploration. You click a filter, the dashboard updates. You drill down from region to territory to individual. You compare this period to last period. The user is in control and exploring in real time.

Crystal Reports = formatted document output. You need a compensation statement that looks exactly like the one from last year—same fonts, margins, logo placement, signature line, page break. You need a formal audit trail document that can be printed, signed, and filed. Crystal Reports does that. Embedded Analytics cannot.

SAP Datasphere = cross-system integration. You need to combine IM data (incentive cost) with S/4HANA Finance data (revenue) and Salesforce data (pipeline) to answer "what was incentive cost as a percent of revenue in each territory?" That requires pulling data from three systems, harmonizing it, and making it queryable. Datasphere is the engine that does that. Neither Embedded Analytics nor Crystal Reports can join data across systems.

Why Embedded Analytics Matters to Business Users

Before Embedded Analytics, the answer to "what was the quota attainment for the EMEA region last month?" required a ticket to the IT team. Someone writes a query, the query runs on a weekend (or doesn't), and the answer comes back three days later. By then, the question has usually changed.

With Embedded Analytics, a sales operations analyst logs into IM, clicks Embedded Analytics, selects a period and a region, and has the answer in three seconds. No IT ticket. No waiting. No intermediary. The analyst can then drill into the data, compare to the previous period, export a list of underperformers, and take action.

This is why Embedded Analytics is embedded inside IM—not a separate tool, but part of the day-to-day interface. The system of record and the reporting layer are one and the same. You make a change to a participant record, and the next time someone refreshes Embedded Analytics, they see the updated data.

Who Uses Embedded Analytics?

Embedded Analytics is designed for business users in three main roles:

• Compensation analysts — operational monitoring. They run period calculations, validate results in Embedded Analytics (quota attainment distribution, pipeline run logs, earnings distribution), and sign off when numbers are correct. They check the data quality dashboards: plan coverage, participant hierarchy, and active assignment status.
• Sales leadership — quota attainment and performance dashboards. A director can see which reps hit quota, which are below target, what the regional spread looks like. They can drill down to individual participants and compare across periods. This is their source of truth for performance conversations.
• HR and finance teams — incentive cost reporting. Finance needs to know total incentive spend by period, by plan, by cost centre. HR needs to validate that all active employees have plan assignments. Both can access Embedded Analytics reports without waiting for IT.

The Relationship to SAP HANA Database

Embedded Analytics reads from SAP HANA Database—specifically, from the CSC_ table layer that IM uses to store compensation data. The CSC_ tables include:

• CSC_RESULTS — the core table, holding incentive calculation results by participant, period, and plan. The result amount, incentive amount, quota attainment percentage, and other computed fields.
• CSC_PARTICIPANT — master data: participant name, manager, territory, cost centre, effective dates, and status.
• CSC_COMP_PLAN — plan definitions and metadata.
• CSC_QUOTA — quota amounts by participant, period, and plan.
• CSC_PERIOD — period definitions (fiscal year, quarter, month, start/end dates).
• CSC_PLAN_PARTICIPANT — the join table mapping which participants are on which plans and when those assignments are active.

Embedded Analytics does not query these tables directly. Instead, it queries Calculation Views—pre-built HANA objects that sit on top of the CSC_ tables. A Calculation View is like a saved query: it joins the raw tables, defines the reporting data model (which fields are dimensions, which are measures), and sets aggregation behaviour. The calculation view layer exists so Embedded Analytics has a clean, pre-optimized data model to read from. You, as a report builder, do not need to know the join logic—you select fields from a Calculation View and build a story (dashboard).

What You Can Do in Embedded Analytics

Embedded Analytics is designed for interactive reporting. The standard use cases are:

• Filter a dashboard by period, plan, region, manager, or participant status and see results update in real time.
• Create a KPI tile showing total participants, average incentive, percentage above target.
• Build a bar chart of quota attainment by territory or a trend line showing attainment over multiple periods.
• Export a table of participants below target to Excel for follow-up conversations.
• Drill down from region to territory to individual participant and see details.
• Use SAC's no-code story builder (drag-and-drop interface) to create a custom dashboard without touching code.

All of this happens in-browser, live against HANA data. There is no data delay, no ETL job to schedule, no separate warehouse to load.

What You Cannot Do in Embedded Analytics

Equally important: understand the boundaries. Embedded Analytics is not suitable for:

• Cross-system reports combining IM with S/4HANA Finance or CRM — you cannot join IM incentive results with revenue or pipeline data in Embedded Analytics. That is SAP Datasphere territory.
• Pixel-perfect formatted documents — compensation statements, formal audit reports, dispute resolutions. Crystal Reports handles that. Embedded Analytics is a browser-based BI tool, not a document formatter.
• Batch report generation for distribution — if you need to email 500 participants their individual statements each month, Crystal Reports is the right tool. Embedded Analytics is self-service exploration, not batch distribution.
• Complex row-level security policies — Embedded Analytics supports filtering and basic security, but if you need fine-grained row-level access control (e.g., each manager sees only their team), that is a consideration for architecture.

The Three-Tool Ecosystem in Context

Here is the practical breakdown: Your IM implementation has three reporting layers.

Layer 1: Embedded Analytics. Your first stop for operational dashboards and ad-hoc analysis. Pre-built stories are ready out of the box. Custom stories take hours to build. Live data, self-service, embedded in the UI.

Layer 2: Crystal Reports. Your second stop when you need formatted document output. Participant compensation statements, formal audit reports, executive summary decks that are printed and signed. Crystal Reports connects to the same HANA Database, reads the same CSC_ tables, but renders output as a formatted PDF or Excel file.

Layer 3: SAP Datasphere. Your third layer, used only when you need to integrate data from multiple systems. If your question requires IM data + S/4HANA Finance + Salesforce CRM, Datasphere is where you build that integration. This is a big scope item—do not underestimate it.

Most IM implementations use Layers 1 and 2 heavily. Layer 3 is an add-on that only large enterprises need early. The mistake teams make is trying to force Layer 1 (Embedded Analytics) to do the job of Layer 2 (Crystal Reports) or Layer 3 (Datasphere). Pick the right tool for the job, and implementation becomes straightforward.

The CSC_ Table Layer and Calculation Views

The technical foundation of Embedded Analytics is simple: CSC_ tables + Calculation Views = reporting data model.

SAP IM writes all data to CSC_ tables on the SAP HANA Database. These are normalized relational tables—participant here, plan there, results in another table. A calculation view joins them into a denormalized reporting layer. For example, a "Quota Attainment" calculation view might join CSC_RESULTS + CSC_PARTICIPANT + CSC_QUOTA + CSC_PERIOD to produce a single row per participant/period/plan with all the context needed for reporting.

Embedded Analytics reads from these calculation views. You do not write SQL (unless you are building a custom query story, which we cover in Lesson 04). You drag fields into a story designer and build a dashboard. Behind the scenes, SAC translates that into a query against the calculation view and returns the results.

This matters because it means Embedded Analytics performance depends on how well the calculation views are defined. If a calculation view does unnecessary joins or aggregates poorly, your Embedded Analytics dashboard will be slow. But SAP ships these calculation views pre-optimized, so in most cases, you do not need to worry about it.

Key Takeaways

As you move through this learning path, keep these points in mind:

• Embedded Analytics is embedded inside IM, not a separate tool. Business users access it from the IM interface.
• It reads directly from SAP HANA Database CSC_ tables via Calculation Views—no separate ETL, no data delay.
• It is one of three reporting tools. Use it for interactive dashboards. Use Crystal Reports for formatted documents. Use SAP Datasphere for cross-system integration.
• Embedded Analytics is for business users, not just IT. The goal is self-service reporting.
• Pre-built content ships with IM and covers the most common reporting needs. Customization is possible but often unnecessary.
• SAP Analytics Cloud (SAC) is the underlying technology—Embedded Analytics is SAC configured for IM.