In the world of consolidation with SAP Group Reporting, there are regular innovations that make everyday work easier – if you understand them properly. One of these innovations concerns the extended configuration option for aggregation conditions for reclassifications in the On Premise Release 2023. What sounds technical at first glance actually provides more control and transparency in practice.

What’s new?

Previously, reclassifications in SAP Group Reporting were carried out by default on the basis of totals values. With the new function, you can now specifically control the conditions under which aggregation should take place – for example, only for certain characteristics or data constellations.

What does this mean for you as a user?

Imagine you only want to carry out a reclassification if a certain value (e.g. an account or a transaction type) exists. With the new aggregation condition, you can define exactly that – without additional manual filters or post-processing.

An example from practice

Let’s assume you only want to carry out a reclassification if the account “300000” is assigned a transaction type “100”. With the new configuration option, you can define this condition directly in Customizing. The system then automatically checks whether the condition is fulfilled – and only executes the reclassification if it is.

Advantages at a glance

• Targeted control of reclassifications
• Less manual rework
• Greater transparency in the consolidation logic
• Easier maintenance thanks to clear conditions

New: Aggregation conditions with SQL expressions

A real highlight is the ability to define SQL-like conditions that have a direct effect on the database. These conditions are stored in Customizing as so-called “aggregation conditions” and can look like this, for example (note: this is not a complete statement):

[GL_ACCOUNT] = ‘300000’ AND [MOVEMENT_TYPE] = ‘100’

This condition means that aggregation only takes place if the account “300000” with transaction type “100” exists. The syntax is based on SQL WHERE clauses and also allows more complex expressions with AND, OR, IN, NOT, LIKE etc. Furthermore, defined selections that serve as triggers can be used in the aggregation condition.

Another example

Imagine you only want to carry out a reclassification if a certain company code (COMP_CODE) occurs in combination with a certain partner (PARTNER). Your condition could then look like this in parts (note: this is not a complete statement): [COMP_CODE] = ‘1000’ AND [PARTNER] IN (‘2000’, ‘2001’). This logic is maintained in Customizing for the reclassification rule and is automatically taken into account by the system.

Conclusion

The new aggregation condition in SAP Group Reporting enables you to control reclassifications in a targeted manner, reduce manual rework and implement complex consolidation rules much more transparently.

If you currently invest a lot of time in time-consuming filters or subsequent corrections or regularly work with complex reclassification logic, this function offers exactly the leverage you need to noticeably simplify your processes.

Do you have a use case for which you do not know exactly how it can be converted into aggregation conditions? Fill out our web form and briefly state your current starting position.

Our team of experts will get back to you promptly, analyze your requirements with you and show you how you can optimally implement the new aggregation condition in your SAP Group Reporting – including lessons learned from our many years of practical experience and the resulting concrete recommendations for action.