How To Fix /SCMB/LDDD006 - Request &1: Duration could not be determined (MTr &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMB/LDDD -

• Message number: 006

• Message text: Request &1: Duration could not be determined (MTr &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 /SCMB/LDDD006 - Request &1: Duration could not be determined (MTr &2) ?

  The SAP error message /SCMB/LDDD006 Request &1: Duration could not be determined (MTr &2) typically occurs in the context of SAP Advanced Planning and Optimization (APO) or Supply Chain Management (SCM) when the system is unable to calculate the duration for a specific transportation request or movement type (MTr). This can happen for various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Missing Master Data: The system may lack the necessary master data, such as transportation lanes, routes, or time schedules, which are required to calculate the duration.
  Incorrect Configuration: There may be issues with the configuration of transportation planning, such as missing or incorrect settings in the transportation management module.
  Inconsistent Data: There could be inconsistencies in the data related to the transportation request, such as incorrect or missing details about the source or destination locations.
  Transportation Mode Issues: The transportation mode defined for the request may not be set up correctly, leading to the inability to determine the duration.
  System Performance Issues: Sometimes, performance issues or system errors can lead to temporary failures in processing requests.
  
  Solutions:
  
  Check Master Data: Ensure that all necessary master data is correctly maintained. This includes transportation lanes, routes, and time schedules. Verify that the relevant data is complete and accurate.
  Review Configuration: Check the configuration settings in the transportation management module. Ensure that all necessary settings are in place and correctly configured.
  Validate Data Consistency: Review the transportation request for any inconsistencies or missing information. Ensure that all required fields are filled out correctly.
  Examine Transportation Modes: Verify that the transportation modes used in the request are correctly defined and configured in the system.
  System Logs and Performance: Check system logs for any errors or warnings that may provide additional context. If performance issues are suspected, consider running performance checks or consulting with your IT team.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message. SAP frequently releases updates and patches that can resolve known issues.
  Documentation: Review the SAP documentation for transportation management and APO to ensure that you are following best practices for configuration and data maintenance.
  Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. Provide them with detailed information about the error, including the request number and movement type.
  
  By systematically addressing these areas, you should be able to identify the cause of the error and implement a solution.