How To Fix /SCMTMS/TCC_MSG658 - No calculation date determined by BAdI; defaulting to &1 (system date)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_MSG -

• Message number: 658

• Message text: No calculation date determined by BAdI; defaulting to &1 (system date)

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_MSG658 - No calculation date determined by BAdI; defaulting to &1 (system date) ?

  The SAP error message /SCMTMS/TCC_MSG658 No calculation date determined by BAdI; defaulting to &1 (system date) typically occurs in the context of SAP Transportation Management (TM) when the system is unable to determine a calculation date for a specific operation or process. This can happen due to various reasons, often related to the configuration or implementation of Business Add-Ins (BAdIs) that are supposed to provide this information.
  Cause:
  
  
  BAdI Implementation: The BAdI (Business Add-In) that is supposed to provide the calculation date is either not implemented or not correctly configured. The system is looking for a specific implementation to determine the calculation date but cannot find one.
  
  
  Missing Logic: Even if the BAdI is implemented, the logic within it may not be returning a valid date, leading the system to default to the current system date.
  
  
  Configuration Issues: There may be configuration issues in the Transportation Management settings that affect how dates are calculated or retrieved.
  
  
  Data Issues: There could be missing or incorrect data in the relevant master data or transactional data that the BAdI relies on to determine the calculation date.
  
  
  Solution:
  
  
  Check BAdI Implementation: 
  
  Go to transaction SE18 or SE19 to check if the BAdI /SCMTMS/EX_TCC_CALC_DATE is implemented.
  If it is not implemented, you may need to create an implementation that provides the necessary logic to determine the calculation date.
  
  
  
  Review BAdI Logic: 
  
  If the BAdI is implemented, review the code to ensure that it correctly calculates and returns a valid date. Make sure that all necessary conditions and data are being considered.
  
  
  
  Configuration Review: 
  
  Check the configuration settings in SAP TM related to transportation planning and execution. Ensure that all necessary settings are correctly configured.
  
  
  
  Data Validation: 
  
  Validate the relevant master and transactional data to ensure that there are no missing or incorrect entries that could affect the calculation date.
  
  
  
  Consult Documentation: 
  
  Review SAP documentation or notes related to this specific error message for any additional guidance or known issues.
  
  
  
  Testing: 
  
  After making changes, perform thorough testing to ensure that the calculation date is now being determined correctly and that the error no longer occurs.
  
  
  
  Related Information:
  
  SAP Notes: Check for any SAP Notes related to this error message for additional insights or patches that may address the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered and resolved similar issues.
  Debugging: If necessary, use debugging tools to trace the execution of the BAdI and identify where the logic may be failing.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.