/ACCGO/CAS_APPL_MSG035 - Split profile type &1 used for vendor split

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_APPL_MSG -

• Message number: 035

• Message text: Split profile type &1 used for vendor split

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.

AnswerBot

• What is the cause and solution for SAP error message /ACCGO/CAS_APPL_MSG035 - Split profile type &1 used for vendor split ?

  The SAP error message /ACCGO/CAS_APPL_MSG035 indicates that there is an issue related to the split profile type used for vendor splitting in the context of the SAP system, particularly in the area of account assignment and cost accounting.
  Cause:
  This error typically arises when:
  
  Incorrect Split Profile Configuration: The split profile type specified for the vendor is not correctly configured or is not compatible with the transaction being processed.
  Missing or Incomplete Data: The necessary data for the split profile may be missing or incomplete, leading to the inability to process the vendor split correctly.
  Inconsistent Master Data: The vendor master data may not be set up properly, or there may be inconsistencies in the data that prevent the system from applying the split profile.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Split Profile Configuration:
  
  Go to the configuration settings for split profiles in the SAP system (Transaction code: SPRO).
  Navigate to the relevant section for vendor splitting and ensure that the split profile type is correctly defined and activated.
  
  
  
  Review Vendor Master Data:
  
  Check the vendor master data to ensure that all required fields are filled out correctly.
  Ensure that the vendor is assigned the correct split profile type.
  
  
  
  Validate Transaction Data:
  
  Review the transaction data that is causing the error to ensure that it aligns with the expected input for the split profile.
  Make sure that all necessary fields are populated and that there are no discrepancies.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific details on the split profile configuration and requirements.
  
  
  
  Testing:
  
  After making the necessary adjustments, test the transaction again to see if the error persists.
  
  
  
  Seek Support:
  
  If the issue continues, consider reaching out to your SAP support team or consulting with an SAP expert who can provide more tailored assistance based on your specific configuration and setup.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO for configuration, MK01 for vendor creation, and MK02 for vendor modification.
  SAP Notes: Check for any SAP Notes related to vendor splitting and split profiles that may provide additional insights or patches.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.