How To Fix /SCTM/RG073 - Request &1: route &2 not designed for total volume &3 &4

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCTM/RG -

• Message number: 073

• Message text: Request &1: route &2 not designed for total volume &3 &4

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 /SCTM/RG073 - Request &1: route &2 not designed for total volume &3 &4 ?

  The SAP error message /SCTM/RG073 typically occurs in the context of SAP Supply Chain Management (SCM) and is related to route planning and transportation management. This error indicates that a specific route is not designed to handle the total volume of goods being requested for transportation.
  Cause:
  The error message /SCTM/RG073 can be triggered by several factors, including:
  
  Route Capacity Limitations: The route defined in the system may have a maximum capacity that is being exceeded by the total volume of goods being planned for transportation.
  Incorrect Route Configuration: The route may not be properly configured to handle the specific type of goods or the volume being requested.
  Data Entry Errors: There may be errors in the data entered for the transportation request, such as incorrect quantities or weights.
  Planning Parameters: The planning parameters set in the system may not align with the requirements of the transportation request.
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Route Capacity: Review the capacity settings for the route in question. Ensure that the route can accommodate the total volume of goods being requested. If necessary, adjust the capacity settings or select a different route that can handle the volume.
  
  
  Review Route Configuration: Verify that the route is correctly configured for the type of goods being transported. This includes checking the transportation lanes, vehicle types, and any restrictions that may apply.
  
  
  Validate Data Entry: Double-check the transportation request for any data entry errors. Ensure that the quantities, weights, and other relevant information are accurate.
  
  
  Adjust Planning Parameters: If applicable, review the planning parameters in the system to ensure they are set correctly for the transportation request.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for additional guidance on configuring routes and handling transportation requests.
  
  
  Contact Support: If the issue persists after checking the above factors, consider reaching out to SAP support or your internal IT team for further assistance.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP SCM, such as /SCMTMS/PLANNING for transportation planning.
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may address the issue.
  Training and Documentation: Ensure that users involved in transportation planning are adequately trained on the system and have access to relevant documentation.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.