How To Fix REXCRAIT034 - New calculation type must be with VAT

SAP Error Message - Details

• Message type: E = Error

• Message class: REXCRAIT - Italian localisation RE-FX

• Message number: 034

• Message text: New calculation type must be with VAT

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 REXCRAIT034 - New calculation type must be with VAT ?

  The SAP error message REXCRAIT034, which states "New calculation type must be with VAT," typically occurs in the context of the SAP system when dealing with tax calculations, particularly in the area of VAT (Value Added Tax) in the SAP Revenue Accounting and Reporting (RAR) module or similar financial transactions.
  Cause:
  This error usually arises when:
  
  Incorrect Calculation Type: The system expects a calculation type that is associated with VAT, but the one provided does not meet this requirement.
  Configuration Issues: There may be a misconfiguration in the tax calculation settings or in the definition of the calculation types in the system.
  Data Entry Errors: The user may have entered an incorrect calculation type in the transaction or document that does not align with VAT requirements.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Calculation Type:
  
  Verify the calculation type being used in the transaction. Ensure that it is one that is defined for VAT calculations.
  If you are unsure which calculation types are valid, consult your SAP configuration or documentation.
  
  
  
  Review Configuration:
  
  Go to the configuration settings for tax calculation in SAP. This can typically be found in the SPRO transaction under Financial Accounting (FI) > Tax on Sales/Purchases > Basic Settings.
  Ensure that the calculation types are correctly defined and that they include VAT-related types.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help files related to VAT and calculation types to ensure compliance with the expected formats and types.
  
  
  
  User Training:
  
  If the error is due to user input, consider providing training or guidelines for users on how to select the correct calculation types when entering transactions.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may provide insights specific to your system configuration.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide updates/patches that could resolve the issue.
  Transaction Codes: Familiarize yourself with transaction codes related to tax configuration, such as OB40 (for defining tax calculation types) and OBYZ (for tax codes).
  Testing: After making changes, conduct thorough testing to ensure that the error does not recur and that VAT calculations are functioning as expected.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.