How To Fix DTINF090 - Could not update Purpose '&' as requests in state 'started'

SAP Error Message - Details

• Message type: E = Error

• Message class: DTINF - Information Retrieval Framework texts

• Message number: 090

• Message text: Could not update Purpose '&' as requests in state 'started'

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 DTINF090 - Could not update Purpose '&' as requests in state 'started' ?

  The SAP error message DTINF090 indicates that there is an issue with updating a specific purpose (identified by the placeholder '&') because the requests are in a state labeled 'started'. This typically occurs in the context of data transport or data transfer processes within SAP systems, particularly when dealing with transport requests or change requests.
  
  Cause:
  
  Transport Request Status: The error usually arises when a transport request is in a 'started' state, meaning that it has been initiated but not completed. This can happen if the request is still being processed or if there was an interruption during its execution.
  Locking Issues: There may be locks on the transport request or the objects it contains, preventing updates.
  System Configuration: There could be configuration issues in the transport management system or the way the requests are being handled.
  
  
  Solution:
  
  
  Check Transport Request Status:
  
  Use transaction code SE09 or SE10 to check the status of the transport requests. Look