The level of granularity coming from Universal Journal (ACDOCA) via the Release Task has a major impact on the performance/runtime of the Release task itself and on the data-volume being posted into ACDOCU table.
The reported financial data is then the basis for all subsequent consolidation tasks (like currency translation, validation, reclassification etc.) and the data volume being processed by the several automatic consolidation tasks heavily influences the response time and resource consumption (memory and CPU).
So, when implementing Group Reporting – as early as possible in the project – the granularity of the transferred data from ACDOCA into ACDOCU should be analyzed. If some additional characteristics are not needed by the business, these fields should not be taken over into Consolidation, to reduce data volume and hence to potentially have better performance and lower resource consumptions.
It will be always a tradeoff between business requirements and data volume/performance.
Image/data in this KBA and in its attachment is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SAP S/4HANA Cloud
- SAP Group Reporting
ACDOCU, ACDOCA, Release Universal Journal, Performance, Data Volume, Additional characteristics, FINCS_ADDLCHARC, Memory , KBA , FIN-CS-COR , S/4HANA Financial Consolidation, Core Processing , How To
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.