How To Fix TK765 - Customizing request &1 was split from the workbench request

SAP Error Message - Details

• Message type: E = Error

• Message class: TK - Transport Organizer

• Message number: 765

• Message text: Customizing request &1 was split from the workbench request

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 TK765 - Customizing request &1 was split from the workbench request ?

  The SAP error message TK765 indicates that a customizing request has been split from a workbench request. This typically occurs when changes made in the SAP system are categorized differently than expected, leading to a separation of the transport requests.
  
  Cause:
  
  Transport Request Configuration: The system may be configured to automatically split customizing requests from workbench requests based on certain criteria.
  Change Types: If changes are made to both customizing and development objects in the same session, the system may decide to split them into separate requests.
  User Actions: A user may have inadvertently triggered the split by performing actions that the system interprets as requiring separate transport requests.
  
  
  Solution:
  
  Review Transport Requests: Check the transport requests in the Transport Organizer (transaction SE09 or SE10) to understand how the requests are structured and what changes are included in each.
  Merge Requests: If appropriate, you can manually merge the customizing request back into the workbench request using the