How To Fix G4058 - JVA is running on ACDOCA, but not all cost objects are split criteria

SAP Error Message - Details

• Message type: E = Error

• Message class: G4 - EC-CS Consolidation

• Message number: 058

• Message text: JVA is running on ACDOCA, but not all cost objects are split criteria

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message G4058 - JVA is running on ACDOCA, but not all cost objects are split criteria ?

  The SAP error message G4058 indicates that there is an issue with the Joint Venture Accounting (JVA) configuration in relation to the ACDOCA table, which is the universal journal in SAP S/4HANA. This error typically arises when the system detects that not all cost objects associated with a transaction are set up as split criteria, which is necessary for proper joint venture accounting.
  Cause:
  
  Incomplete Configuration: The cost objects involved in the transaction may not be fully configured to support split criteria. This means that some cost objects are not set up to allow for the necessary splitting of costs and revenues according to the JVA requirements.
  Missing Split Criteria: The specific cost objects used in the transaction may not have been defined as split criteria in the JVA configuration.
  Data Entry Issues: There may be issues with the data entry where certain cost objects are not correctly assigned or recognized by the system.
  
  Solution:
  
  
  Review JVA Configuration:
  
  Check the configuration settings for Joint Venture Accounting in the SAP system. Ensure that all relevant cost objects are defined as split criteria.
  Navigate to the JVA configuration settings and verify that the necessary cost objects are included in the split criteria setup.
  
  
  
  Update Cost Object Settings:
  
  If certain cost objects are missing from the split criteria, update their settings to include them. This may involve modifying the configuration in the JVA settings to ensure that all relevant cost objects are accounted for.
  
  
  
  Data Validation:
  
  Validate the data entries for the transactions that are causing the error. Ensure that all cost objects are correctly assigned and that there are no discrepancies in the data.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes related to JVA and ACDOCA for specific guidelines on how to configure split criteria and resolve related issues.
  
  
  
  Testing:
  
  After making the necessary changes, perform tests to ensure that the error does not reoccur. Create test transactions to verify that the system processes them correctly without generating the G4058 error.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or patches related to this error.
  Transaction Codes: Familiarize yourself with transaction codes related to JVA configuration, such as OJVA (for Joint Venture Accounting) and other related transaction codes for managing cost objects.
  User Roles: Ensure that users have the appropriate roles and authorizations to make changes to JVA configurations and cost object settings.
  
  By following these steps, you should be able to identify the root cause of the G4058 error and implement the necessary solutions to resolve it.