Asymmetric Reporting Layout

[GregBotticchio]

What is Asymmetric Reporting?

It is our pleasure to announce the introduction of a new innovation in SAP Analytics Cloud, delivered as part of the 2026 Q2 QRC release.

Asymmetric Reporting introduces a new way to design tables in SAP Analytics Cloud, enabling greater flexibility in how data is structured and presented within a single table.

Instead of relying on a strictly uniform layout, where all rows and columns follow the same dimensions, hierarchies, and granularity, Asymmetric Reporting enables selected aspects of a table layout such as measures, time ranges, and visible hierarchy levels, to vary across different sections of the same table.

In practice, this means that a single table can combine multiple perspectives. For example, one part of the table may focus on actuals at a detailed monthly level, while another section presents forecasts or budgets at a higher level of aggregation. These views coexist within the same table, without requiring separate reporting objects or duplicated structures.

This capability helps users design more expressive and context-aware tables directly in SAP Analytics Cloud, better reflecting the way business questions are actually asked and answered.

Why it matters: Real-world reporting is not symmetric

Traditional table structures in BI and planning tools are typically symmetric by design. This means that the same dimensions, hierarchies, and filters are applied consistently across all rows and columns of a report.

While this approach ensures simplicity and consistency, it often does not reflect the reality of business reporting, especially in financial planning and analysis scenarios.

In practice, different parts of the same report frequently require different levels of detail or different analytical perspectives. For example:

• Actuals are often analyzed at a monthly or even daily level of granularity
• Forecasts may start from a specific cut-off date
• Budgets are frequently reviewed at a quarterly or yearly level

Bringing all of these perspectives into a single symmetric table often leads to compromises: duplicated reports, complex workarounds, or loss of clarity in how data is presented.

From a planning perspective, this limitation becomes even more visible. An additional challenge comes from “unbooked” combinations that must remain visible for data entry and forecast collection, even when no transactional data exists yet. Business users want to compare actuals, forecasts, and budgets side by side, but each of these elements naturally follows a different logic and time structure. Forcing them into a single rigid model can reduce both usability and analytical accuracy.

Asymmetric Reporting in SAP Analytics Cloud addresses this challenge by allowing different parts of a table to reflect different structures and levels of detail, while still being part of a single, coherent model. This makes it possible to align table design more closely with real business processes, rather than adapting business logic to technical constraints.

Example and typical use cases

A typical example is a rolling forecast table.

In this scenario:

• Accounts are displayed in the rows
• Actuals are shown from January up to a selected cut-off date
• Rest of Year Forecast starts after the cut-off date through the end of the period
• Full Year Actuals plus Forecast provides a consolidated yearly view
• Full Year Budget is displayed at a quarterly level
• A Delta highlights the difference between Budget and Actuals plus Forecast

Each column represents a different perspective, with its own logic and level of detail. This is what makes the table asymmetric.

This approach is especially useful for:

• Rolling forecasts
• Budget vs Actual vs Forecast analysis
• Financial statements such as P&L or Balance Sheet
• Management reporting dashboards

See it in action

To see how this comes together in practice, watch the following demo:

In this example, notice how:

• Time ranges adjust dynamically
• Different measures display different levels of granularity
• The table adapts based on user input

How it works: The building blocks behind Asymmetric Reporting

Asymmetric Reporting is enabled by a combination of three key innovations that work together.

First, Measure Input Control in Restricted Measures and Cross Calculations allows input controls, such as date, version, or measure selection, to dynamically drive calculations within the table.

Second, Dynamic Time Filters for “Rest of Period” automatically adjust time ranges based on the current context, enabling scenarios like “Actuals up to a selected date” and “Forecast for the remaining period.”

Third, Visibility Filters for Table Widgets control which dimension members or hierarchy levels are displayed for each measure, allowing different parts of the table to present different views.

Combined, these capabilities enable each column or row to behave independently while remaining part of a single, consistent table.

With these building blocks, you can:

• Combine multiple reporting perspectives in a single table
• Mix different levels of granularity (monthly, quarterly, yearly)
• Dynamically adapt time ranges and calculations
• Reduce the need for multiple tables or manual workarounds
• Create reports that better reflect real business logic

Share your feedback

Asymmetric Reporting introduces a more flexible way to design tables in SAP Analytics Cloud.

By combining dynamic calculations, adaptive time filtering, and flexible display control, it enables reporting structures that better align with real-world business needs. This results in more intuitive reports, improved analysis, and a more efficient BI and Planning experience.

That being said, we now want to hear from you. Your feedback directly helps us improve both the product and its documentation.

Please let us know your thoughts. Your input is highly appreciated and will actively influence future enhancements to SAP Analytics Cloud.