Ideas

A PALO.DATA function refers to single base or consolidated elements for aggregation. It would be fine to be able to define subsets of elements to get a sum of these,

The rule editor is very powerful but hard to understand from a business user point of view. The user interface could be improved in terms of usability and structure. A grouping of rules in a folder structure would help a lot here rather than havi...

There are uses cases when data input on consolidated level is required and using # is only an additional step for end-user. PALO.DATA function should have an optional argument that would enable inputs on consolidated levels without using #.

For example, After performing 2023-12 consolidation, users should be able to lock all data relating to Actual version and any data 2023-12 and before such that nothing gets changed. current issue: Numbers get changed easily as there is no data loc...

Add a new report that lists all material data points in a structured format, showing whether each has been provided (input) or is still missing. The report would include the following columns: Previous Year Current Year Delta (Change) Input Status...

When you have data in more than one cube, asking AI to leverage more than one cube to bring back a result is the ultimate AI concept. It would require the AI to be able to understand relations in the data and perhaps prompt with a clarification qu...

Add a new column with the thresholds next to the scores for better explanation of the calculation way for the Auditor / Wirtschaftsprüfer. And add an explanation of the calculation way.

When entering numbers like the Energy consumption for a specific data point, then the user should see that this is used in another data point too.

Would be great to add the CapEx logics and reports to the Best Practice Accelerator IFP.

It would be great to have numbers working together between HR, Sales and IFP for PoCs. To track a number From HR to IFP and from Sales to IFP.