How To Fix /UI2/BAC103 - Split created &1 new candidates

SAP Error Message - Details

• Message type: E = Error

• Message class: /UI2/BAC -

• Message number: 103

• Message text: Split created &1 new candidates

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 /UI2/BAC103 - Split created &1 new candidates ?

  The SAP error message /UI2/BAC103 Split created &1 new candidates typically occurs in the context of the SAP Fiori Launchpad or when dealing with the SAP UI5 framework. This message indicates that a split has been created, resulting in the generation of new candidates for a particular application or tile. 
  Cause:
  
  Multiple Instances: The error often arises when there are multiple instances of a particular application or tile that are being processed simultaneously, leading to the creation of new candidates.
  Configuration Issues: There may be issues with the configuration of the Fiori Launchpad or the specific application, causing it to not handle the instances correctly.
  Performance Issues: If the system is under heavy load, it may not be able to manage the requests efficiently, leading to the creation of multiple candidates.
  
  Solution:
  
  Check Configuration: Review the configuration settings for the Fiori Launchpad and the specific application. Ensure that the application is set up correctly and that there are no conflicting settings.
  Monitor System Performance: Check the system performance and load. If the system is under heavy load, consider optimizing performance or scaling resources.
  Clear Cache: Sometimes, clearing the cache of the Fiori Launchpad can resolve issues related to stale data or configurations.
  Update SAP Notes: Check for any relevant SAP Notes that may address this specific error. Applying the latest patches or updates can often resolve known issues.
  Review Logs: Look into the application logs and system logs for any additional error messages or warnings that could provide more context about the issue.
  
  Related Information:
  
  SAP Fiori Launchpad: Understanding how the Fiori Launchpad manages applications and tiles can help in troubleshooting issues related to application instances.
  SAP UI5: Familiarity with the SAP UI5 framework can provide insights into how applications are built and how they interact with the backend.
  SAP Community: Engaging with the SAP Community forums can provide additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.