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.
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