How To Fix /SCMTMS/TRQ843 - &1 has been deleted after &2 was changed

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TRQ -

• Message number: 843

• Message text: &1 has been deleted after &2 was changed

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/TRQ843 - &1 has been deleted after &2 was changed ?

  The SAP error message /SCMTMS/TRQ843 &1 has been deleted after &2 was changed typically occurs in the context of SAP Transportation Management (TM). This error indicates that a transportation request (TRQ) has been deleted due to changes made to a related object, such as a transportation lane, shipment, or other relevant data.
  Cause:
  
  Data Change: The error is triggered when a change is made to an object that is linked to the transportation request. For example, if a transportation lane is modified, any transportation requests that depend on that lane may become invalid and thus be deleted.
  Inconsistency: The system detects an inconsistency between the transportation request and the modified object, leading to the automatic deletion of the request to maintain data integrity.
  
  Solution:
  
  Review Changes: Check the changes made to the related object (e.g., transportation lane, shipment) that triggered the deletion. Understanding what was modified can help in determining the next steps.
  Recreate Transportation Request: If the transportation request is essential, you may need to recreate it after ensuring that the related objects are correctly configured.
  Check Dependencies: Ensure that all dependencies and relationships between transportation requests and other objects are correctly set up. This may involve reviewing the configuration in SAP TM.
  Consult Logs: Look at the application logs or change logs to get more details about what changes were made and why the request was deleted.
  Testing: If possible, test the changes in a development or quality assurance environment before applying them in production to avoid unexpected deletions.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional context or fixes.
  Documentation: Review the SAP TM documentation for information on how transportation requests interact with other objects and the implications of changing those objects.
  Support: If the issue persists or if you need further assistance, consider reaching out to SAP support or your internal SAP team for help.
  
  By following these steps, you should be able to address the error and prevent it from occurring in the future.