How To Fix RSL_UI359 - Starting request deletion...

RSL_UI359 - Overview

• Message type: E = Error

• Message class: RSL_UI -

• Message number: 359

• Message text: Starting request deletion...

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 RSL_UI359 - Starting request deletion... ?

  The SAP error message RSL_UI359, which states "Starting request deletion...", typically occurs in the context of the SAP system when there is an issue related to the deletion of requests in the transport management system (TMS) or during the deletion of requests in the change and transport system (CTS).
  
  Cause:
  
  Authorization Issues: The user may not have the necessary authorizations to delete requests.
  Request Status: The request may be in a status that does not allow deletion (e.g., it might be released or already transported).
  System Lock: There may be a lock on the request or the transport directory that prevents deletion.
  Technical Issues: There could be underlying technical issues with the transport directory or database inconsistencies.
  
  
  Solution:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to delete transport requests. This can be checked in transaction SU53 or by consulting with your security team.
  Check Request Status: Verify the status of the transport request. If it