How To Fix /SCMTMS/TCC_MSG657 - Calculation date determined by Business Add-In (BAdI)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_MSG -

• Message number: 657

• Message text: Calculation date determined by Business Add-In (BAdI)

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_MSG657 - Calculation date determined by Business Add-In (BAdI) ?

  The SAP error message /SCMTMS/TCC_MSG657 typically relates to the Transportation Management System (TMS) in SAP. This error indicates that the calculation date for a transportation charge calculation was determined by a Business Add-In (BAdI), and it may not be set correctly or is not available in the context of the operation being performed.
  Cause:
  
  BAdI Implementation: The BAdI responsible for determining the calculation date may not be implemented correctly or may not be returning a valid date.
  Configuration Issues: There may be configuration issues in the Transportation Management settings that affect how the calculation date is determined.
  Data Issues: Missing or incorrect data in the relevant master data (e.g., transportation lanes, conditions) can lead to this error.
  Custom Logic: If there is custom logic implemented in the BAdI, it may not be functioning as expected, leading to the error.
  
  Solution:
  
  
  Check BAdI Implementation: 
  
  Go to transaction SE18 or SE19 to check the implementation of the BAdI related to transportation charge calculation. Ensure that the logic for determining the calculation date is correctly implemented.
  If necessary, debug the BAdI implementation to see what date is being returned.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the Transportation Management area. Ensure that all necessary settings related to charge calculation and date determination are correctly configured.
  Verify the settings in the relevant customizing transactions (e.g., SPRO).
  
  
  
  Validate Master Data:
  
  Ensure that all relevant master data (e.g., transportation lanes, conditions, etc.) is complete and accurate. Missing or incorrect entries can lead to issues in date determination.
  
  
  
  Check for Notes and Updates:
  
  Look for any SAP Notes or updates related to this error message. Sometimes, SAP releases notes that address specific issues or bugs in the system.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation for the Transportation Management module to understand the expected behavior and configuration for charge calculations.
  
  
  
  Engage SAP 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 context in which it occurs.
  
  
  
  Related Information:
  
  BAdI Documentation: Familiarize yourself with the specific BAdI documentation to understand its purpose and how it should be used.
  Transaction Codes: Use transaction codes like SE18, SE19, and SPRO for BAdI management and configuration.
  Debugging: If you have access to the development environment, you can debug the BAdI implementation to trace the logic and identify where the issue may be occurring.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.