Migration and Switching to Joint Venture Accounting on ACDOCA
Would you like to use the Universal Journal for Joint Venture Accounting to automatically reconcile accounting data, but you don’t know yet how to change from your current system?
In this article I give you an overview of the migration and switch scenarios, restrictions and required reports, and I list some resources. That information should help you to decide whether this migration is what you are aiming for.
You can consider migrating or switching to Joint Venture Accounting on ACDOCA if you are currently running one of the systems listed in the Migration and Switch sections below.
Migration means coming from an ERP system and going to an SAP S/4HANA system with JVA on ACDOCA. It is a prerequisite to have New G/L active with G/L splitter and New G/L-JVA integration.
Make sure that the data from separate tables in the ERP system is converted and combined in the ACDOCA table.
List of supported scenarios:
- ECC classic G/L + classic JVA (only partly supported)
- ECC New G/L with G/L splitter + non-integrated classic JVA (only partly supported)
- ECC New G/L with G/L splitter + new G/L-JVA integration
If you are running an SAP S/4HANA system with classic JVA, you need to switch to JVA on ACDOCA. Adapt the configuration accordingly. Be aware that there will be a certain level of disruptions between the transaction data posted before and after the switch.
List of supported scenarios:
- SAP S/4HANA with G/L splitter + new G/L-JVA integration + cost objects defined as split criteria
- SAP S/4HANA with G/L splitter + new G/L-JVA integration + cost objects not defined as split criteria (only partly supported)
The scenario with SAP S/4HANA without G/L splitter + classic JVA is not supported.
Some scenarios have restrictions. You need to be aware of them before you start planning the migration or switch process. Have a look at the disclaimers for the migration and switch scenarios in SAP Note 2941622. The descriptions of the individual scenarios contain the information whether a scenario is supported, supported with restrictions, or not supported.
One of the migration steps is to run special JVA reports. These reports are necessary to make sure that the data is as complete and correct as possible:
- RGJV_UPDATE_CBRUNID_IN_ACDOCA: update the historic data that should not be picked up by cutback because the affected periods are probably closed (SAP Note: 3050563)
- RGJV_UPDATE_INT_DOCS_IN_ACDOCA: create missing internal JVA documents in the ACDOCA table (SAP Note 3058813)
- RGJV_UPDATE_ACC_DATA_IN_ACDOCA: update the ACDOCA table with accounting data from the JVA ledgers due to differing cost object information (SAP Note 3058813)
Before you start the migration process, familiarize yourself with the SAP Notes and documentation and consider possible restrictions for your scenario.
Blog post: Understanding the Universal Journal in SAP S/4HANA
SAP Help Portal documentation: Migration and Switching to SAP S/4HANA with JVA on ACDOCA
- 2941622 – Migration to S4HANA with Joint Venture Accounting running on ACDOCA
- 3058813 – JVA on ACDOCA activation: Reports to update the ACDOCA table with internal JVA documents and with accounting data from the JVA ledgers
- 3050563 – JVA on ACDOCA activation: Report to update the CBRUNID value in the ACDOCA table
- 3082514 – Integration of JVA into the S4HANA migration
Thanks for sharing this blog for an overview when we are planning to switch to S/4HANA. This document provide lot of information post migration to HANA. Also if possible could you please mention any note which describe about the reports or any other process which we should consider before making this switch to S/4HANA.
Thanks for your comment. I added the SAP Note 3082514 - Integration of JVA into the S4HANA migration now.
Is there any concrete information you miss about reports in the SAP Notes 3058813 and 3050563?
Actually we are migrating from ECC to S/4 HANA 106 (version02) and not sure what activities we should perform post migration from JVA perspective as we tried to implement OSS note 3082514 but we are already in higher version of S/4 HANA 106 and this note can not be implemented
So may be if you have any information with this regard that what activities we should perform after migration.
Thanks for the details! However, all information is already covered by the notes in the blog article. And I would like to emphasize the importance of note 2941622. It needs to be read through thoroughly. And note 3058813 needs to be implemented to get the JVA migration reports.
Apart from that, we can only give general technical tips via this blog post channel.
Thanks for your feedback :). Hope to see many more such blogs in future. All the best !!!
Thank you! And thanks again for your comment.
In a Migration project approach, you mention the case: ECC classic G/L + classic JVA (only partly supported). What do you mean by Partially Covered? What is supported and what is not? Any Updated OSS about this specific topic? (2941622?)
Does the SAP LT 2.0 tool cover the features and complexity of migration with a Source System: ECC Classic + Classic JVA to a Target System: S/4 HANA JVA ON ACDOCA scenario?
Pablo A. Badaroux
The migration case (2) ERP NewGL with GL splitter + Non-integrated classic JVA means that the past activation of NewGL and the prior finance migration project considered only the split of documents by finance split characteristics (e.g. profit center and segment). The JVA split characteristic is not active and the finance document split by venture is still done in JVA. As mentioned in the note "there is no guarantee that the results of the GL splitter can be combined with the results of the JVA splitter.
A migration path which supports the retroactive activation of the venture split characteristic in the finance document split (which ensures the consistent document split) and which allows the proper enrichment of historical finance data (e.g. split by profit center and segment) does not exists as standard migration path.
To ensure a consistent document split according finance and JVA document split rules for the historical and future documents we recommend to consider the support of our SAP DMLT migration experts (date management and IT landscape transformation services (formerly known as SAP SLO).
Jürgen Newrzella O&G Upstream Product Management
Thanks, Jürgen for your answer.
Pablo A. Badaroux