SAP Analytics Cloud Planning Licensing: Embedded vs Standalone Models Explained

SAC Licensing Model Overview: Story Points vs Named Users

SAP Analytics Cloud licensing is confusing because it uses two entirely different metrics depending on which version and which feature set you are using.

Story Points Model (Embedded Planning)

Embedded planning within S/4HANA or BTP is licensed using "story points." A story point is SAP's abstraction of computational load. It does not directly measure users, data volume, or transactions. Instead, SAP calculates story points based on the complexity of planning models you deploy.

SAP's story point calculation includes:

• Number of planning dimensions (each dimension = points)
• Data volume (larger datasets = more points)
• Calculation complexity (advanced analytics = more points)
• Number of planning versions (multiple what-if scenarios = more points)
• Collaborative features (multiple users planning simultaneously = more points)

The problem: SAP calculates story points after deployment. Most customers discover their actual story point consumption only after they've built and deployed planning models. By that time, they're often over-allocated and facing "true-up" fees.

Named User Model (Standalone SAC)

Standalone SAP Analytics Cloud (where you license the full SAC product rather than embedded planning) uses a Named User licensing model. You purchase a specific number of user seats. Each named user can access all SAC modules (planning, analytics, dashboards) without additional user-specific charges.

Named User licensing is simpler to understand but more expensive per user. A typical SAC Named User license costs $3,000-$4,500 per user per year for a 500-user organization.

Embedded Planning vs Standalone SAC: What's the Difference?

This distinction is critical because it determines pricing, feature access, and scalability.

Embedded Planning (Included with S/4HANA or BTP)

If you have S/4HANA Public Cloud or S/4HANA Private Cloud, you have access to SAP Analytics Cloud planning functionality at no additional charge (beyond the story point costs built into your S/4HANA subscription). The planning capability is "embedded" — it is part of the broader platform.

What embedded planning includes:

• Basic planning models (revenue, cost, headcount, etc.)
• Multiple planning dimensions and versions
• Collaborative planning for multiple users
• Integration with S/4HANA transactional data
• Simple dashboards and reporting

What embedded planning typically does NOT include:

• Advanced SAC analytics features (free-form visualizations, AI-driven insights)
• Standalone SAC dashboards (embedded dashboards are basic)
• Multi-dimensional analysis outside of planning modules
• Advanced data integration (SAP Data Intelligence connectors)
• Custom ML/AI model deployment

Standalone SAP Analytics Cloud

Standalone SAC is a separate product with full features: advanced analytics, dashboarding, planning, and data integration. You license it independently, not as part of S/4HANA.

Standalone SAC is used when:

• You need advanced analytics and visualization beyond basic planning.
• You are integrating data from multiple systems (SAP and non-SAP).
• You have complex, multi-dimensional analysis requirements.
• You want a cloud-native analytics platform separate from your ERP.

The critical difference: Embedded planning is constrained to the S/4HANA context. Standalone SAC is a complete analytics platform.

What's Actually Included in S/4HANA Planning (Public vs Private Cloud)

SAP's documentation is deliberately vague about what "planning" is included in S/4HANA subscriptions. Different deployment models (Public Cloud vs Private Cloud) include different entitlements.

S/4HANA Public Cloud

S/4HANA Public Cloud licensing is subscription-based and includes embedded SAC planning at no additional charge. However, story points are metered. Your subscription tier determines your included story point allocation:

• S/4HANA Cloud Essentials: Limited story points (typically 500-1,000), suitable for basic planning.
• S/4HANA Cloud Professional: More story points (2,000-5,000), for multi-dimensional planning.
• S/4HANA Cloud Enterprise: Highest allocation (10,000+), for complex analytics.

If you exceed your included story point allocation, you pay for overages. SAP charges $2-$3 per story point for overage usage.

S/4HANA Private Cloud

Private Cloud licensing works differently. Planning is included, but the story point allocation depends on your support contract. The contract must explicitly state story point entitlements.

Key trap: Many Private Cloud customers do not have explicit story point allocations in their contracts. When they deploy planning, SAP claims they are "exceeding" unspecified limits and demands true-up payments.

Solution: If you have S/4HANA Private Cloud, ensure your support contract explicitly specifies story point allocations. If it does not, negotiate one.

BTP Entitlements and SAC Credits: What Counts, What Doesn't

Many enterprises are adopting SAP Business Technology Platform (BTP) to run SAC, extension applications, and integration services. BTP licensing is model-based: You purchase "commercial units" or "compute hours," and those units entitle you to use various SAP cloud services, including SAC.

How BTP Entitlements Map to SAC

BTP does not directly license users. Instead, it licenses computational capacity. SAP's mapping is:

• Each BTP commercial unit includes a certain amount of SAC "capacity credits."
• SAC planning consumption is measured in credits (similar to story points but named differently).
• If your planning models consume more credits than your BTP entitlement provides, you are out of compliance.

The Credit Carryover Trap

BTP credits are typically monthly allocations. A critical question: Can unused credits roll over to the next month?

SAP's answer: It depends on your contract. Some BTP contracts allow carryover; most do not. If credits do not carryover, you face an incentive to "use it or lose it," which can lead to over-provisioning or waste.

Negotiation point: Negotiate credit carryover language into your BTP contract. This gives you flexibility to manage peaks and valleys in planning workload.

Double-Licensing Risk with BTP

A dangerous scenario: You have both S/4HANA (with embedded planning story points) and BTP (with SAC credits). Are they separate entitlements or does one cover both?

Answer: They are typically separate. If you deploy planning models in both S/4HANA and standalone SAC on BTP, you are consuming story points in one environment and credits in another. SAP will count both against your licensing position.

Story Points: What They Measure and Why Customers Run Out

Story points are SAP's opacity in licensing. They are intentionally opaque because opacity benefits SAP (it allows them to claim compliance violations and demand true-ups).

What Consumes Story Points?

1. Planning dimensions: Each dimension you add to a planning model costs points. More dimensions = higher costs.
2. Data volume: Larger datasets consume more points. A planning model with 1M rows costs more than a model with 100K rows.
3. Version variants: Each version (actual, forecast, scenario) is a separate planning instance and consumes points.
4. User concurrency: If multiple users plan simultaneously, concurrent access consumes additional points.
5. Data refresh frequency: Planning models that refresh data frequently (from S/4HANA or external systems) consume points per refresh.
6. Calculation complexity: Models with advanced formulas, macros, or custom scripts consume more points.

The problem: SAP does not provide transparent pre-deployment story point estimators. You build a planning model, deploy it, and then SAP tells you how many story points it consumed.

Why Customers Run Out of Story Points

Typical scenario: A 500-user enterprise deploys 10 planning models covering budget, forecast, and headcount planning. They estimate 5,000 story points are sufficient. After deployment:

• Planning model 1 (budget): 1,200 points (larger than expected due to 5 dimensions, 2M rows)
• Planning model 2 (headcount): 800 points
• Planning model 3 (project planning): 950 points
• And so on... Total deployed: 7,500 points

They are now over their 5,000 point allocation by 2,500 points. SAP demands payment for the overage, typically $2-$3 per point per month = $5,000-$7,500 in unexpected monthly costs.

Planning-Specific User Types: BI Professional, BI Platform Professional

In standalone SAC, user licensing is based on user types, and planning has specific user type designations.

BI Platform Professional (Planning Focus)

This user type can create, edit, and execute planning models. They have full authoring rights. Cost: ~$3,500/year per user.

BI Professional (Read-Only / Consumer Focus)

This user type can view and execute planning models but cannot edit the underlying models. They can submit plans or enter budget data, but cannot change formulas or structure. Cost: ~$1,800/year per user.

The Reclassification Opportunity

Many enterprises over-license by assigning BI Platform Professional licenses to users who only need consumer rights. If your 500-user planning community has only 50 power users who build models and 450 users who enter data, you could:

• License 50 users as BI Platform Professional (~$175K/year)
• License 450 users as BI Professional (~$810K/year)
• Total: ~$985K/year

Instead of licensing all 500 as BI Platform Professional at ~$1.75M/year, you save $765K annually.

Negotiation point: Ensure your SAC licensing agreement allows users to be reclassified based on actual usage. Do not accept language that requires all users to be the same type.

The Trap: SAP Sells "Embedded" Planning But Useful Features Require Paid Add-Ons

This is where SAP's commercial model becomes predatory. Embedded planning in S/4HANA includes basic functionality. However, most real-world planning scenarios require features that are NOT included in embedded planning—they require paid upgrades or standalone SAC.

Feature Categories in Embedded Planning

Included in Embedded Planning:

• Basic budget planning (rows and columns)
• Simple variance analysis
• Standard aggregation and rollup

Requires Standalone SAC or Paid Upgrade:

• Advanced visualizations and dashboarding (heat maps, geospatial, custom charts)
• Predictive planning (forecasting, what-if scenarios with AI)
• Multi-currency planning with exchange rate management
• Collaboration features beyond basic commenting (version control, approval workflows)
• Integration with external data sources (beyond S/4HANA)
• Custom ML models and advanced analytics

SAP's playbook: Position embedded planning as "sufficient" for standard use cases. When customers ask for advanced features, push them toward standalone SAC, which is ~10x more expensive per user.

Cost Benchmarks and Typical Pricing for a 500-User Enterprise

What should a 500-user enterprise expect to pay for planning?

Scenario 1: Embedded Planning (S/4HANA Public Cloud)

Annual cost structure:

• S/4HANA subscription (500 users): ~$2.5M-$3.5M/year (includes planning story points)
• Planning story point overage (5,000 points allocated, 7,500 actual): $2/point × 2,500 × 12 months = ~$60K/year additional
• Total: ~$2.5M-$3.56M/year

Scenario 2: Standalone SAC for 500 Planning Users

Annual cost structure:

• 50 BI Platform Professional users: 50 × $3,500 = $175K
• 450 BI Professional users: 450 × $1,800 = $810K
• Infrastructure/BTP licensing: ~$150K-$250K
• Total: ~$1.135M-$1.235M/year

Standalone SAC appears cheaper, but it includes only analytics/planning—not ERP transaction processing. Most enterprises choose embedded planning because they already have S/4HANA.

Scenario 3: Hybrid (S/4HANA + Limited Standalone SAC)

Many enterprises use both: embedded planning in S/4HANA for operational planning (budget, forecast) and standalone SAC for strategic analytics and advanced dashboarding.

• S/4HANA with embedded planning: ~$2.5M-$3.5M/year
• Standalone SAC for 50 power users (BI Platform Professional): 50 × $3,500 = $175K
• Total: ~$2.675M-$3.675M/year

Negotiation Tactics: Story Point Bundles, User Type Reclassification, Credit Carryover

If you are licensing SAC or planning, these negotiation moves protect you from overpaying:

Tactic 1: Pre-Committed Story Point Bundles

Instead of paying for story points on a monthly overage basis, negotiate a pre-committed bundle. For example:

"Customer shall be entitled to 10,000 monthly story points for planning at a fixed cost of $X/month. Overage beyond 10,000 points in any month shall be true-up billed at $Y per point, provided that Customer receives 10 days' notice before incurring overages and opportunity to optimize usage."

This locks in costs and prevents surprise bills.

Tactic 2: User Type Flexibility

Negotiate language allowing unlimited reclassification of users between BI Platform Professional and BI Professional based on actual usage patterns:

"Customer may adjust user type classifications monthly based on actual usage without additional fees or penalties. Reclassification requests shall be processed within 5 business days."

Tactic 3: BTP Credit Carryover

If using BTP, negotiate credit carryover to handle seasonal planning peaks:

"Unused commercial units/credits may be carried forward to the following month, provided that total carried-forward credits do not exceed [X% of monthly allocation]. Credits not used within 12 months of issuance shall be forfeited."

Tactic 4: Story Point Transparency

Push SAP for pre-deployment story point estimation:

"SAP shall provide a preliminary story point estimation (±10%) within 5 business days of Customer providing planning model specifications. Actual consumption shall not exceed the estimate by more than 15% without written notification and opportunity to optimize."

Integration with BW/4HANA and Datasphere Licensing Implications

Many planning deployments rely on BW/4HANA (SAP's data warehouse) or Datasphere (SAP's modern data fabric) for data integration. These integrations create additional licensing considerations.

BW/4HANA Integration

If your SAC planning pulls data from BW/4HANA, you are licensing two products. SAC licenses are separate from BW/4HANA licenses. Some key interactions:

• Dual-use data models: If a data model is accessed by both BW/4HANA and SAC planning, ensure your contract clarifies licensing attribution.
• Real-time data sync: If planning pulls data in real-time from BW/4HANA, confirm that data refresh counts toward SAC story points or separate BW licensing metrics.
• User overlap: If the same user accesses both BW and SAC, confirm that a single SAC license covers both tools (it typically does).

Datasphere Integration

Datasphere is SAP's newer integration platform. Planning models that source data from Datasphere introduce another licensing layer.

• Data volume metrics: Datasphere is licensed based on data volume and integration complexity, not users. Ensure planning model data flows are included in your Datasphere quota.
• External connectors: If Datasphere integrates non-SAP systems (e.g., Salesforce, Workday) to feed planning, confirm these external data connectors are within your Datasphere entitlements.
• Storage and compute: Large planning datasets may exceed Datasphere storage allocations, creating overage charges. Track this separately.

What This Means For You

If you are deploying SAC planning, follow this roadmap:

• Clarify your deployment model: Are you using embedded planning (S/4HANA), standalone SAC, or both? Costs vary dramatically.
• Get pre-deployment story point estimation: Do not deploy planning models without understanding expected story point consumption. Request SAP's pre-estimation service.
• Negotiate story point bundles: Lock in fixed monthly allocations instead of paying overage rates.
• Classify users strategically: Assign BI Platform Professional rights only to power users; use BI Professional for data entry and consumption.
• Document planning requirements upfront: Get explicit clarity on which features are included in your license tier. Advanced features may require paid upgrades.
• Integrate data carefully: Ensure BW/4HANA or Datasphere licenses are coordinated with your SAC planning deployment.

Summary: Key Takeaways

SAP Analytics Cloud planning is available in two licensing models: embedded planning (included with S/4HANA) and standalone SAC (full analytics platform). Embedded planning uses story points as a consumption metric, which is intentionally opaque—SAP calculates story points after deployment, creating surprise billing. Standalone SAC uses Named User licensing, which is simpler but more expensive.

The most dangerous trap is SAP's positioning of embedded planning as "sufficient" when it is actually limited. Advanced planning features are not included; they require paid upgrades or migration to standalone SAC. For a 500-user enterprise, embedded planning costs $2.5M-$3.5M/year (as part of S/4HANA), while standalone SAC costs $1.1M-$1.2M/year but provides analytics only, not ERP.

Negotiation is critical. Lock in pre-committed story point bundles, allow flexible user type reclassification, and ensure integration with BW/4HANA or Datasphere is clear in your contract. Most enterprises overpay because they do not negotiate these terms upfront.