- SAP Managed Tags
Introduction
Welcome fellow SAC planning technical analysts! Over time, I have explored numerous blogs and resources about enhancing SAC planning templates and optimizing performance. It is crucial to understand the reasoning behind these performance metrics to grasp why they are integrated. A seamless budgeting cycle in SAC is vital for users to keep leveraging SAC Planning for Enterprise Performance Management (EPM). This blog addresses the limitations of cross tables in SAC planning templates and how to mitigate associated performance issues.
Creating an Effective Planning Template
To initiate an efficient planning cycle, the foremost task is creating a planning template that simplifies the process for each user to enter their budgeted or forecasted values. In this blog, we will delve into the technical aspects of using tables, specifically:
- Cross tables which are commonly used for budgeting.
- Forecast layout
Prerequisites
Before diving into the specifics, ensure you have:
- A planning model with required public/private dimensions.
- Mandatory dimensions including Date, Version, and Measure.
- Imported master and transaction data.
Handling Complex Hierarchies in Planning
When managing any complex hierarchy for planning, keep the following points in mind:
1. Effect of Unbooked Data
Unbooked data refers to combinations of dimensions that lack actual transactional values, meaning these combinations are "not booked." Displaying unbooked data increases the number of transactions in the planning template, resulting in null values in the Measure column. This can negatively impact the performance of the planning template due to certain limitations of cross tables in SAC.
Technical Constraints:
- Total Cells Displayed: 1 million.
- Total Cells Rendered During Scroll: 100,000.
When selecting dimensions, ensure that unbooked data is disabled unless necessary. If the data load approaches its maximum value, applying filters or manipulating the template could lead to long load times (1-2 minutes) or even page unresponsiveness errors.
Best Practice Tips:-
- Disable unbooked data to enhance performance unless it is explicitly required for analysis.
- Usage of Story / Page filters allowing the users to minimise the Amount of data being loaded by filtering improves the efficiency of Planning template.
2. Editing Drill Limitation for Cross Tables
Cross tables have a predefined drill limitation: 500 rows and 60 columns. However, best practice suggests using the unlimited option, which dynamically allocates the number of rows to the columns. If data volume is excessively high, consider the following to reduce it: -
- Reduce the number of dimensions on the axes.
- Decrease the number of exception aggregation dimensions.
- Limit the number of measures/accounts requested.
- Apply more restrictive filters for dimensions on an axis or for dimensions indirectly used as exception aggregation dimensions.
3. Usage of Audit Log: -
By enabling the Audit Log in the Model preferences, you will be able to retrieve the log of each Planning template/report.
This can be done in Security-> Data Changes from which we will be able to take the Log.
The information from Audit log can be used to verify the changes done by any User under any specific version required with respect to the Date.
Please note: For each Object, this log has a capability to store 500,000-line items. Once the limit is reached, the oldest line items automatically get deleted permanently.
For more info: https://userapps.support.sap.com/sap/support/knowledge/en/2781343
4. Utilisation of Data / Multi actions: -
Planning processes can be simplified by using Data actions. These actions automate routine tasks, such as copying data between versions or performing complex calculations like depreciation, thereby enhancing efficiency and accuracy in planning cycles.
- Copying Data Between Versions
- Automate the transfer of data from one planning version to another.
- Use Cases: Updating the existing asset depreciation in Actuals from Planning model and copying it to the Budget version to start planning.
- Backend Configuration: Define mappings and schedule automated executions to maintain data consistency and reduce manual effort.
2)Advanced Formula: -
In SAP (SAC planning) Analytics Cloud (SAC) Planning, Advanced Formulas can be used to perform custom scenarios, such as calculating depreciations, to meet specific business requirements:
- Custom Scenario Support: Enables organizations to define and execute custom depreciation calculations tailored to unique business needs, beyond standard methods like straight-line or declining balance.
- Precision: Ensures accurate calculations by incorporating detailed parameters such as salvage values, useful life adjustments, and partial periods.
- Flexibility: Facilitates integration with user input through parameters, allowing users to enter depreciation percentages or other variables during budgeting or forecasting. This flexibility supports dynamic adjustments based on changing business conditions or asset specifics.
Advanced Formulas in SAC empower organizations to perform precise and customizable depreciation calculations, enhancing financial planning capabilities and supporting compliance with accounting standards effectively.
To understand about Advanced formulas in Data action for Planning: https://help.sap.com/docs/SAP_ANALYTICS_CLOUD/00f68c2e08b941f081002fd3691d86a7/afe93e3cf1414a7b8419b...
Conclusion
Creating an efficient and user-friendly planning cycle in SAC involves a blend of thoughtful template design, effective data management, and continuous performance optimization. By addressing key factors like unbooked data and adhering to best practices, you can ensure a smoother budgeting and forecasting process, enhancing user experience and the overall effectiveness of SAC Planning.
Stay tuned for more technical insights and best practices in SAC planning. Feel free to share your experiences and questions in the comments below!
| User | Count |
|---|---|
| 10 | |
| 9 | |
| 8 | |
| 8 | |
| 7 | |
| 7 | |
| 5 | |
| 5 | |
| 5 | |
| 5 |
