We’re facing a significant issue with Project Accounting analytics in SAP S/4HANA 1909 where cost data aggregation is producing incorrect totals across multiple projects. The Analytics Workspace shows individual project costs correctly, but when we try to aggregate across project hierarchies or portfolios, the numbers don’t add up.
Specifically, when viewing our multi-project portfolio dashboard, the total aggregated costs are consistently lower than the sum of individual project costs by approximately 15-20%. We’ve verified the source data in transaction CJ13 (Display Project) and all costs are posted correctly at the project level. The issue only appears when Analytics Workspace attempts to aggregate across multiple projects.
Our project structure uses WBS elements with hierarchical relationships, and we have projects spanning different controlling areas. The cost aggregation seems to work fine within a single controlling area, but when the analytics workspace tries to consolidate across controlling areas, that’s where the discrepancy occurs.
We’ve checked the data source configuration and the cost element mappings appear correct. Has anyone encountered similar cost aggregation errors in Analytics Workspace with multi-project scenarios? We need reliable portfolio-level cost reporting for executive dashboards.
This sounds like a summarization level issue in your InfoProvider. When aggregating project costs, the system needs to know which fields to use as aggregation keys. Check your project analytics InfoProvider in transaction RSRT and verify that the WBS element hierarchy is properly defined as a navigation attribute. If the hierarchy isn’t correctly configured, the aggregation will miss parent-child relationships.
We had a similar issue that turned out to be related to the project hierarchy activation status. In Analytics Workspace, hierarchies need to be explicitly activated and the time-dependent versions need to be aligned with your reporting period. Go to transaction RSHIERARCHYREP and check if your project structure hierarchy is active for the periods you’re reporting on. If there are gaps in the hierarchy validity periods, aggregation will fail for those periods and costs will be missing from the totals.
Check your extraction logic for project costs. In 1909, there are multiple datasources for project data (2LIS_PP_ACT, 2LIS_PP_PLN, etc.) and if your Analytics Workspace is pulling from multiple sources, you might have duplicate elimination issues or missing records. Review the delta extraction setup in transaction LBWE and verify that all project cost postings are being captured. Also look at the selection criteria in your datasource - sometimes filters inadvertently exclude certain cost types or project categories.