In SAP Analytics Cloud (SAC), planning versions allow teams to test ideas, forecast outcomes, and collaborate on plans without impacting original data. Versions make it easy to compare different scenarios—like budgets, forecasts, or “what-if” simulations—within a single model.
What Is a Planning Version?
A version is a slice of your planning data. Instead of copying an entire model, SAC lets you work with different versions of the same dataset. This means all your scenarios—Actuals, Forecast, Budget, Best Case, Worst Case—can live in the same planning model, keeping everything connected and organized.
Types of Planning Versions
Public Versions
- Shared across your team
- Visible in the core planning model
- Controlled by permissions
- Often used for actuals, budgets, and final forecasts
Example
- Everyone in the finance team sees and works with the “Q3 Forecast” public version.
Private Versions:
- Your own working copy of a public version
- Used for testing or personal simulations
- Not visible to others until you choose to publish
- Great for experimenting with changes before sharing
Example
- You create a private version of “Q3 Forecast” to try a new revenue projection without affecting the team’s work.
When to Use Each Version Type
| Use Case | Version Type |
|---|---|
|
Share a finalized forecast |
Public Version |
|
Run a “what-if” simulation |
Private Version |
|
Prepare team-wide targets |
Public Version |
|
Try different assumptions before sharing |
Private Version |
Best Practices
- Always create a private version before testing major changes
- Don’t publish unless you’re sure—publishing updates the shared public version
- Use clear naming conventions like “2025 Budget Draft” or “Worst Case Forecast”
- Limit who can publish to public versions using permissions
- Check your change history in the Version Management Panel if you need to revert
