How To Fix /SCMTMS/TRQ824 - 'Set to not submitted' action not possible: Life cycle status is &1

/SCMTMS/TRQ824 - Overview

• Message type: E = Error

• Message class: /SCMTMS/TRQ -

• Message number: 824

• Message text: 'Set to not submitted' action not possible: Life cycle status is &1

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 /SCMTMS/TRQ824 - 'Set to not submitted' action not possible: Life cycle status is &1 ?

  The SAP error message /SCMTMS/TRQ824 'Set to not submitted' action not possible: Life cycle status is &1 typically occurs in the context of SAP Transportation Management (TM) when you are trying to change the status of a transportation request or a related object, but the current life cycle status does not allow for that action.
  
  Cause:
  The error indicates that the life cycle status of the transportation request (or related object) is currently set to a state that does not permit the action of setting it to "not submitted." This could happen for several reasons, including:
  
  
  Current Status Restrictions: The object may be in a status that is not allowed to be reverted to "not submitted." For example, if the request has already been processed or is in a completed state, the system will prevent changes to its submission status.
  
  
  Business Rules: There may be specific business rules or configurations in place that restrict