How To Fix /SCMTMS/INV_DISP020 - No upr limit tolerance specified in Customizing for amt &1 charge type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/INV_DISP -

• Message number: 020

• Message text: No upr limit tolerance specified in Customizing for amt &1 charge type &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/INV_DISP020 - No upr limit tolerance specified in Customizing for amt &1 charge type &2 ?

  The SAP error message /SCMTMS/INV_DISP020 indicates that there is no upper limit tolerance specified in the Customizing settings for a specific charge type in the SAP Transportation Management System (SAP TM). This error typically arises when the system is trying to process an invoice or a charge that requires a tolerance limit, but none has been defined for the specified charge type.
  Cause:
  
  Missing Configuration: The primary cause of this error is that the upper limit tolerance for the specified charge type has not been configured in the system.
  Incorrect Charge Type: The charge type being referenced may not have been set up correctly in the system.
  Customizing Settings: The relevant Customizing settings for charge types and tolerances may not have been properly maintained.
  
  Solution:
  To resolve this error, you need to define the upper limit tolerance for the specified charge type in the Customizing settings. Here are the steps to do this:
  
  
  Access Customizing:
  
  Go to the SAP Easy Access screen.
  Navigate to the Customizing area (SPRO).
  
  
  
  Find the Relevant Configuration:
  
  Follow the path: Transportation Management -> Basic Settings -> Charge Types -> Define Charge Type Tolerances.
  Alternatively, you can search for the specific configuration using transaction code SPRO.
  
  
  
  Define Upper Limit Tolerance:
  
  In the configuration screen, locate the charge type that corresponds to the one mentioned in the error message (charge type &2).
  Define the upper limit tolerance for that charge type. This typically involves specifying a percentage or a fixed amount that can be tolerated above the expected charge.
  
  
  
  Save Changes: After making the necessary changes, save your configuration.
  
  
  Test the Changes: After saving, try to reprocess the invoice or transaction that triggered the error to ensure that the issue has been resolved.
  
  
  Related Information:
  
  Charge Types: Charge types in SAP TM are used to categorize different types of costs associated with transportation. Each charge type can have its own rules and tolerances.
  Tolerance Management: Tolerance management is crucial in financial processes to allow for minor discrepancies in invoicing without causing errors or rejections.
  Documentation: Refer to SAP Help documentation for more detailed information on configuring charge types and tolerances in SAP TM.
  
  If the issue persists after following these steps, it may be necessary to consult with your SAP support team or check for any additional dependencies or configurations that may be affecting the charge type in question.