How To Fix /SCMTMS/TRQ599 - Forwarding agreement &1 version &2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TRQ -

• Message number: 599

• Message text: Forwarding agreement &1 version &2 not found

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/TRQ599 - Forwarding agreement &1 version &2 not found ?

  The SAP error message /SCMTMS/TRQ599 Forwarding agreement &1 version &2 not found typically occurs in the context of SAP Transportation Management (TM) when the system is unable to locate a specific forwarding agreement based on the provided identifiers. This can happen for several reasons, and understanding the cause and potential solutions can help resolve the issue.
  Causes:
  
  Non-Existent Forwarding Agreement: The forwarding agreement with the specified ID (&1) and version (&2) does not exist in the system.
  Incorrect Version: The version number provided may be incorrect or outdated.
  Data Deletion: The forwarding agreement may have been deleted or archived, making it unavailable for the current transaction.
  Authorization Issues: The user may not have the necessary authorizations to view or access the forwarding agreement.
  Configuration Issues: There may be configuration issues in the Transportation Management module that prevent the system from retrieving the forwarding agreement.
  
  Solutions:
  
  Verify Forwarding Agreement: Check if the forwarding agreement with the specified ID and version exists in the system. You can do this by navigating to the relevant transaction or using the appropriate report in SAP TM.
  Check Version Number: Ensure that the version number you are using is correct. If you are unsure, you can look up the available versions for the forwarding agreement.
  Review Deletion/Archiving: If the forwarding agreement has been deleted or archived, you may need to restore it or create a new forwarding agreement.
  Authorization Check: Ensure that the user has the necessary authorizations to access the forwarding agreement. You may need to consult with your SAP security team to verify this.
  Consult Configuration: If you suspect a configuration issue, consult with your SAP TM configuration team to ensure that all necessary settings are correctly configured.
  Use Transaction Codes: Utilize transaction codes like /SCMTMS/AGREEMENT to search for forwarding agreements and verify their status.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Documentation: Refer to the SAP Help Portal for detailed documentation on forwarding agreements and their management within SAP TM.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution. If the problem persists, consider reaching out to SAP support for further assistance.