How To Fix /SCMTMS/TCC_HL_MSG458 - Agreement not found for org. &1 and business partner group &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_HL_MSG -

• Message number: 458

• Message text: Agreement not found for org. &1 and business partner group &2

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/TCC_HL_MSG458 - Agreement not found for org. &1 and business partner group &2 ?

  The SAP error message /SCMTMS/TCC_HL_MSG458 indicates that there is an issue related to the Transportation Management (TM) module, specifically concerning the absence of a valid agreement for a given organizational unit and business partner group. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Missing Agreement: The primary cause of this error is that there is no existing agreement defined in the system for the specified organizational unit (org. &1) and business partner group (&2).
  Incorrect Configuration: The configuration settings for the transportation management agreements may not be set up correctly.
  Data Inconsistency: There may be inconsistencies in the master data related to the organizational units or business partners.
  Authorization Issues: The user may not have the necessary authorizations to view or access the agreements.
  
  Solution:
  
  
  Check Agreements:
  
  Navigate to the relevant transaction in SAP TM where agreements are maintained (e.g., /SCMTMS/AGREEMENT).
  Verify if there is an agreement defined for the specified organizational unit and business partner group. If not, you will need to create one.
  
  
  
  Create or Update Agreement:
  
  If an agreement is missing, create a new agreement that includes the necessary details for the organizational unit and business partner group.
  Ensure that all required fields are filled out correctly.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the SAP TM customizing (SPRO) to ensure that the agreements are set up correctly.
  Make sure that the organizational units and business partner groups are correctly defined and linked.
  
  
  
  Data Consistency Check:
  
  Run data consistency checks to ensure that there are no discrepancies in the master data.
  Validate that the organizational unit and business partner group are correctly assigned in the relevant master data records.
  
  
  
  Authorization Check:
  
  Ensure that the user encountering the error has the necessary authorizations to access the agreements.
  If needed, consult with your SAP security team to review and adjust user roles and permissions.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  Documentation: Refer to the SAP Help Portal for detailed documentation on Transportation Management agreements and their configuration.
  Community Forums: Engage with SAP community forums or user groups for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary solutions to resolve it.