How To Fix /ACCGO/BR_CAKAPPL002 - Split scenario in application must match with LDC split scenario

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/BR_CAKAPPL -

• Message number: 002

• Message text: Split scenario in application must match with LDC split scenario

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 /ACCGO/BR_CAKAPPL002 - Split scenario in application must match with LDC split scenario ?

  The SAP error message /ACCGO/BR_CAKAPPL002 typically relates to issues in the configuration of split scenarios in the context of the SAP General Ledger (G/L) accounting. This error indicates that there is a mismatch between the application split scenario and the Local Data Consistency (LDC) split scenario.
  Cause:
  
  
  Configuration Mismatch: The error usually arises when the split scenario defined in the application does not align with the split scenario defined in the LDC settings. This can happen if the configurations for the two scenarios are not synchronized or if there are discrepancies in the settings.
  
  
  Incorrect Document Type: The document type being used may not be compatible with the defined split scenarios.
  
  
  Missing or Incorrect Settings: There may be missing or incorrect settings in the configuration of the split scenarios in the Financial Accounting (FI) module.
  
  
  Solution:
  
  
  Check Split Scenario Configuration:
  
  Go to the configuration settings for split accounting in the SAP system.
  Verify that the split scenario defined in the application matches the LDC split scenario. This can be done in the SPRO transaction under:
  Financial Accounting (New) -> General Ledger Accounting (New) -> Business Transactions -> Document Splitting -> Define Split Scenarios
  
  
  
  
  Adjust Document Type Settings:
  
  Ensure that the document type being used is correctly configured to work with the defined split scenarios. You can check this in the document type configuration settings.
  
  
  
  Review Customizing Settings:
  
  If there are any customizations or enhancements in place, review them to ensure they do not interfere with the standard split scenario configurations.
  
  
  
  Testing:
  
  After making the necessary adjustments, perform tests to ensure that the error no longer occurs and that the document splitting works as expected.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to document splitting and split scenarios for additional guidance and best practices.
  
  
  
  Related Information:
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional insights into the configuration of split scenarios.
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SPRO for configuration settings.
  FB01 for posting documents.
  OBY6 for document type configuration.
  
  
  
  Community Forums: Engage with SAP community forums or support channels for shared experiences and solutions from other users who may have encountered the same issue.
  
  
  By following these steps, you should be able to resolve the error and ensure that your split scenarios are correctly configured in SAP.