How To Fix /ACCGO/UIS_MSG796 - Split data passed is not same as profile maintained in BRF+ for split ID

/ACCGO/UIS_MSG796 - Overview

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 796

• Message text: Split data passed is not same as profile maintained in BRF+ for split ID

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/UIS_MSG796 - Split data passed is not same as profile maintained in BRF+ for split ID ?

  The SAP error message /ACCGO/UIS_MSG796 indicates that there is a mismatch between the split data being passed in a transaction and the profile that has been maintained in the Business Rule Framework plus (BRF+) for the specified split ID. This error typically occurs in the context of financial processes where data needs to be split according to predefined rules.
  
  Cause:
  
  Mismatch in Split Data: The data being passed for processing does not conform to the rules defined in the BRF+ profile for the specific split ID. This could be due to incorrect or incomplete data being sent to the system.
  Profile 
  Configuration Issues: The BRF+ profile for the split ID may not be configured correctly, or it may have been changed without updating the corresponding data being processed.
  Versioning Issues: If there are multiple versions of the BRF+ rules, the system might be referencing an outdated version that does not match the current data