How To Fix FOT_TDT020 - Tax Calculation Date Determination Type '&1' is not allowed

SAP Error Message - Details

• Message type: E = Error

• Message class: FOT_TDT -

• Message number: 020

• Message text: Tax Calculation Date Determination Type '&1' is not allowed

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 FOT_TDT020 - Tax Calculation Date Determination Type '&1' is not allowed ?

  The SAP error message FOT_TDT020 indicates that there is an issue with the tax calculation date determination type specified in your configuration or transaction. This error typically arises when the system encounters a tax determination type that is not valid or not allowed for the current context.
  Cause:
  
  Invalid Tax Calculation Date Determination Type: The specified determination type (&1) is not recognized or is not configured correctly in the system.
  Configuration Issues: The tax calculation settings in the system may not be properly set up, leading to the use of an unsupported determination type.
  Transaction Context: The determination type may not be applicable for the specific transaction or document type you are working with.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for tax calculation in your SAP system. This can typically be found under SPRO > Financial Accounting > Tax on Sales/Purchases > Basic Settings > Tax Calculation.
  Verify that the tax calculation date determination types are correctly defined and that the one you are trying to use is included in the allowed list.
  
  
  
  Review the Document Type:
  
  Ensure that the document type or transaction you are processing is compatible with the tax calculation date determination type you are using. Some types may only be valid for specific document types.
  
  
  
  Adjust the Determination Type:
  
  If the determination type is indeed invalid, you may need to change it to a valid one. This can often be done in the transaction where the error occurs or in the relevant configuration settings.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more details on valid tax calculation date determination types and their configurations.
  
  
  
  Check User Exits or BAdIs:
  
  If there are any custom developments (user exits or BAdIs) that might be influencing the tax determination process, review them to ensure they are not causing the issue.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue through configuration or adjustments, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OB40 (for tax determination) or SPRO (for configuration) to access the relevant settings.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance.
  Testing: After making changes, perform tests to ensure that the tax calculation works as expected without triggering the error.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.