TL;DR
The core distinction: Embedded Analytics is for interactive exploration (user drills down, filters, changes period in the browser). Crystal Reports is for formatted document output (exact pixel placement, PDF quality, compensation statements). Neither does the other's job well.
Embedded Analytics: live HANA data, self-service, no-code story builder, mobile-friendly, KPI tiles and charts. Weaknesses: no pixel-perfect formatting, not suitable for legal documents, not designed for print. Crystal Reports: pixel-perfect output, PDF quality, long-established for comp statements, connects to HANA via ODBC/JDBC. Weaknesses: not interactive, requires Designer software, static output, separate from the IM UI.
For migrations from Callidus Commissions on Oracle: Crystal Reports queries carry over (SQL rewrite from CS_ Oracle tables to CSC_ HANA tables, but layout and formatting survive). Use this decision table for 10 common IM reporting needs to pick the right tool every time.
One of the most common mistakes IM teams make is picking the wrong reporting tool. They try to build a pixel-perfect compensation statement in Embedded Analytics (it does not work—there is no formatting engine). Or they try to make a Crystal Report interactive (it does not work—the output is static). Or they build both and maintain two versions of the same report. This lesson defines the two tools clearly, shows you their strengths and weaknesses, and gives you a decision framework so you never waste time building the wrong thing.
The Core Distinction
Embedded Analytics is for exploration. Crystal Reports is for documents. That is the entire decision framework. Everything else flows from this one idea.
- Exploration: I want to explore data in my browser. I want to filter by period, then by manager, then drill down to see individual participants. I want to change the chart type. I want to export to Excel. I want to see results update as I click. That is Embedded Analytics.
- Documents: I want to produce a PDF or printed report that looks exactly like the one from last year. Same margins. Same fonts. Same signature line. Same layout. Users will sign this document and file it away. That is Crystal Reports.
Once you internalise that distinction, tool selection becomes simple.
SAP Embedded Analytics: Strengths and Weaknesses
Strengths
- Live HANA data. No export, no batch job, no data copy. What is in HANA right now is what you see in the dashboard. Query runs in real time (milliseconds to seconds).
- Self-service for business users. Analysts can create stories (dashboards) using a no-code drag-and-drop interface. No SQL knowledge required. No IT ticket needed.
- Interactive filtering and drilldown. User clicks a filter, the dashboard updates. User clicks a bar in a chart, drills down to the detail. User can re-order a table, export to Excel.
- Mobile-friendly. SAC stories render well on tablets and phones. Compensation analysts can pull up attainment data on their phone in a meeting.
- KPI tiles and visualisations. Show a big red/green KPI tile. Show a trend line. Show a distribution histogram. SAC has rich visualisation options.
- Embedded in IM UI. Users do not need to open a separate tool. They log into IM, click Embedded Analytics, and they are there. Lower friction than a separate reporting tool.
Weaknesses
- No pixel-perfect formatting control. You cannot set exact margins, font sizes, logo placement, signature lines. The output is a browser dashboard, not a formatted document.
- Not suitable for legal documents. If this report will be signed and filed as evidence (audit trail, formal dispute resolution), Crystal Reports is the right tool. Embedded Analytics is a BI tool, not a document formatter.
- Not designed for print. If you need to print 500 copies of a report and mail them, Embedded Analytics is not the answer. Crystal Reports is built for this exact use case.
- Complex multi-page formatted documents are painful. If you need a 10-page report with detailed formatting, section breaks, sub-tables, and conditional formatting based on data, Crystal Reports is the right tool. Embedded Analytics is not a report designer.
- User must interact with the tool. Embedded Analytics is self-service. If you want to email a participant their compensation statement once a month without them needing to log in and pull the report, Crystal Reports is the right tool (it can batch-generate and email).
SAP Crystal Reports: Strengths and Weaknesses
Strengths
- Pixel-perfect formatted output. You design the report once in Crystal Reports Designer, and every time it runs, the output looks exactly the same. Same margins, fonts, logo placement, signature lines, conditional formatting.
- PDF and printable quality. Crystal Reports has been the standard for formatted document output for decades. It is built for PDF and print.
- Compensation statements. For participant comp statements—the formal document reps see showing their earnings, broken down by component, with grand total, signature line—Crystal Reports is the standard. The IM product itself provides Crystal Report templates for this exact use case.
- Batch and scheduled output. Crystal Reports can generate 500 participant statements overnight, convert them to PDF, and email them. Embedded Analytics cannot.
- Formal audit and compliance documents. If the report is an audit trail, a dispute resolution decision, or a formal document that will be archived and possibly referenced in legal proceedings, Crystal Reports is the right choice.
- Connects to SAP HANA Database directly. Via ODBC or JDBC driver. Same data source as Embedded Analytics, but Crystal Reports executes the query at report run time and flows the results into a designed template.
Weaknesses
- Not interactive. The user cannot filter a Crystal Report in the browser or drill down. The report is static output—PDF or Excel file. If they want to see different data, they need to run the report again with different parameters.
- Requires Crystal Reports Designer software to create/modify. Not a no-code tool. Requires technical skills (SQL knowledge, understanding of Crystal's formula language, report design skills). It is not something a business analyst can learn in an afternoon.
- Separate from the IM UI. Users need to log into Crystal or navigate to a separate reporting portal. Higher friction than Embedded Analytics.
- Requires HANA ODBC/JDBC driver setup and configuration. Not as seamlessly integrated as Embedded Analytics. More infrastructure required.
- Performance depends on the query. If the SQL query is slow, the report takes a long time to generate. Crystal Reports does not have the same optimisation and caching layer as SAC.
Full Tool Comparison
| Dimension | SAP Embedded Analytics | SAP Crystal Reports |
|---|---|---|
| Primary use case | Interactive dashboards and ad-hoc exploration | Formatted document output and batch distribution |
| Output format | In-browser visualisations (charts, tables, KPIs) | PDF, Excel, printable documents |
| Data freshness | Live (query runs in real time against HANA) | On-demand or scheduled (query runs at report generation time) |
| Interactivity | Full interactivity (filter, drill down, export) | Static output (no filtering or drilling in the output) |
| Formatting control | Limited (browser-based styling) | Pixel-perfect (margins, fonts, logo placement, signature lines) |
| Learning curve | Low (no-code story builder) | Moderate-to-high (requires Crystal Designer and SQL skills) |
| Deployment | Embedded in IM UI | Separate reporting tool (or Crystal Enterprise server) |
| Mobile support | Good (SAC stories responsive) | Poor (designed for desktop/print) |
| Batch processing | Not designed for it | Built for batch generation and distribution |
| Cost | Included with IM | Included with IM (but requires designer licence if creating custom reports) |
| Suitable for compensation statements | No (too interactive, not formal enough) | Yes (pixel-perfect, formal document quality) |
| Suitable for audit trails | No (BI tool, not document archive) | Yes (formal, archivable, PDF-based) |
| Suitable for data exploration | Yes (the primary use case) | No (not interactive) |
Decision Guide: 10 Common IM Reporting Requirements
| Reporting Requirement | Right Tool | Why |
|---|---|---|
| Sales leadership quota attainment dashboard | Embedded Analytics | Interactive, self-service, live data, no IT needed. Leadership wants to drill down and explore. |
| Monthly compensation statements for participants | Crystal Reports | Formal legal document, pixel-perfect, PDF quality, participants sign and file it away. |
| Operational pipeline run monitoring | Embedded Analytics | Real-time operational dashboard, tabular data, self-service for ops team. |
| Formal audit trail of calculation changes | Crystal Reports | Archive-worthy document, signatures, exact formatting, signed off by finance. |
| Incentive earnings distribution validation | Embedded Analytics | Histogram, self-service analysis, compensation analyst checks before approving results. |
| Dispute resolution decision document | Crystal Reports | Formal output, signatures, legal trail, archived per company policy. |
| Participant self-service earnings history | Embedded Analytics | Interactive portal, participants can filter by period, drill into details. IM participant portal uses Embedded Analytics for this. |
| Commission cost vs revenue analysis (cross-system) | SAP Datasphere + Embedded Analytics | Requires joining IM data with Finance data. Neither Crystal nor Embedded Analytics alone can do this. Use Datasphere to integrate, then Embedded Analytics to explore. |
| Plan assignment coverage report (pre-period) | Embedded Analytics | Quick validation dashboard, helps ops team spot gaps before calculation run. Self-service, no IT needed. |
| Executive summary with formatting and branding | Crystal Reports | Pixel-perfect, company logo, signature lines, footer, printed and distributed. Crystal Reports is built for this. |
The Callidus Commissions Migration Question
Teams migrating from Callidus Commissions on Oracle Database often ask: "Can we keep our Crystal Reports?" The answer is mostly yes, with caveats.
What Carries Over
The Crystal Reports design and formatting carries over—margins, fonts, logo placement, conditional formatting, subreports, all of it survives migration. The report layout itself does not change.
What Requires Rewriting
The SQL driving the reports needs rewriting. Callidus Commissions stored data in Oracle Database with CS_ table prefix. SAP SuccessFactors IM stores data in SAP HANA Database with CSC_ table prefix. The query logic translates, but the syntax changes:
| Change Category | Callidus Commissions (Oracle) | SAP SuccessFactors IM (HANA) |
|---|---|---|
| Table prefix | CS_ | CSC_ |
| Date data type | Oracle DATE | TIMESTAMP |
| String data type | VARCHAR2 | NVARCHAR |
| NULL substitution | NVL(col, default) | COALESCE(col, default) |
| Row numbering | ROWNUM, ROW_NUMBER() | ROW_NUMBER() OVER (PARTITION BY ... ORDER BY ...) |
| Date arithmetic | TRUNC(SYSDATE), ADD_MONTHS() | TRUNC(CURRENT_DATE), ADD_MONTHS() or ADD_DAYS() |
| String functions | SUBSTR(), INSTR() | SUBSTRING(), LOCATE() (or SUBSTR() also works in HANA) |
| Aggregation | GROUP BY, HAVING | GROUP BY, HAVING (same) |
A Crystal Reports query that looked like this on Oracle:
-- Oracle SQL for Callidus Commissions Crystal Report SELECT p.PARTICIPANT_NAME, cp.PLAN_NAME, NVL(r.QUOTA_AMOUNT, 0) AS QUOTA, NVL(r.RESULT_AMOUNT, 0) AS RESULT, ROUND(r.RESULT_AMOUNT / NVL(r.QUOTA_AMOUNT, 1) * 100, 1) AS ATTAINMENT_PCT FROM CS_RESULTS r JOIN CS_PARTICIPANT p ON p.ID = r.PARTICIPANT_ID JOIN CS_COMP_PLAN cp ON cp.ID = r.PLAN_ID WHERE TRUNC(r.CALC_DATE) = TRUNC(SYSDATE);
Becomes this on HANA:
-- SAP HANA SQL for SuccessFactors IM Crystal Report (same layout, new SQL) SELECT p.NAME AS PARTICIPANT_NAME, cp.PLAN_NAME, COALESCE(r.QUOTA_AMOUNT, 0) AS QUOTA, COALESCE(r.RESULT_AMOUNT, 0) AS RESULT, ROUND(r.RESULT_AMOUNT / COALESCE(r.QUOTA_AMOUNT, 1) * 100, 1) AS ATTAINMENT_PCT FROM CSC_RESULTS r JOIN CSC_PARTICIPANT p ON p.ID = r.PARTICIPANT_ID JOIN CSC_COMP_PLAN cp ON cp.ID = r.PLAN_ID WHERE CAST(r.CREATED_AT AS DATE) = CURRENT_DATE;
The query logic is the same, the SQL syntax changes. This is straightforward to rewrite, and the Crystal Reports design (the part that took effort to build) stays exactly the same.
Migration Checklist
- Inventory all Callidus Commissions Crystal Reports currently in use.
- For each report, identify the primary table (CS_RESULTS, CS_QUOTA, etc.) and the key join columns.
- Rewrite the SQL from Oracle to HANA syntax (see table above for common changes).
- Test each Crystal Report against SAP HANA Database to verify query results match the old reports (spot-check 5-10 rows).
- The formatting (layout, fonts, signature lines) does not need to change. Update the title if needed (from "Callidus" to "SAP SuccessFactors").
- Deploy the updated Crystal Reports in the IM environment.
When You Need SAP Datasphere
Neither Embedded Analytics nor Crystal Reports can join data from multiple systems. If your reporting question requires combining IM data with data from S/4HANA Finance, Salesforce CRM, or HCM, you need SAP Datasphere—the data integration layer. This is the third tool in the ecosystem and is a significant scope item. Do not underestimate it.
⚠️SAP Datasphere is not a quick add-on. Teams that scope Datasphere late in a project ("we'll add cross-system analytics for Phase 2") consistently underestimate the effort. Data integration, connection setup, data quality resolution, and performance tuning across multiple source systems is a workstream in its own right. If you need cross-system analytics, scope Datasphere separately and early, or defer it to a later phase. Do not try to squeeze it into the initial IM go-live.
Key Takeaways
- Embedded Analytics is for interactive exploration. Crystal Reports is for formatted documents. Neither does the other's job well.
- Use this decision: If the user will interact with the report (filter, drill, explore), use Embedded Analytics. If the output is a formal document (signature required, archived, printed), use Crystal Reports.
- Embedded Analytics is live data, self-service, no-code, embedded in IM. Crystal Reports is pixel-perfect, formal, requires Designer, separate from IM.
- Use the decision guide (10 common requirements) to pick the right tool every time.
- For Callidus Commissions migrations: Crystal Reports design carries over, but SQL requires rewriting from Oracle to HANA syntax.
- For cross-system analytics, neither Embedded Analytics nor Crystal Reports is the answer. Use SAP Datasphere + Embedded Analytics.