How To Fix FS793 - MOSS tax country &1 does not exist; adjustment required &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FS - Messages from Tax Routines / Prenumbered Checks

• Message number: 793

• Message text: MOSS tax country &1 does not exist; adjustment required &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 FS793 - MOSS tax country &1 does not exist; adjustment required &2 ?

  The SAP error message FS793 indicates that there is an issue related to the MOSS (Mini One Stop Shop) tax configuration for a specific country. The message typically means that the system is unable to find the tax country specified in the transaction or configuration, which is necessary for processing VAT (Value Added Tax) correctly under the MOSS scheme.
  Cause:
  
  Missing Tax Country Configuration: The specified tax country does not exist in the system's configuration. This could be due to a missing entry in the tax configuration tables.
  Incorrect Country Code: The country code provided in the transaction may be incorrect or not recognized by the system.
  MOSS Configuration Issues: The MOSS settings may not be properly configured for the specified country, leading to the error.
  Data Inconsistency: There may be inconsistencies in the master data or transaction data that reference the tax country.
  
  Solution:
  
  
  Check Tax Country Configuration:
  
  Go to the SAP transaction code OBD2 (Maintain Tax Codes) or OBD3 (Maintain Tax Jurisdictions) to verify if the tax country is correctly configured.
  Ensure that the tax codes for the specified country are set up properly.
  
  
  
  Verify Country Code:
  
  Check the country code used in the transaction. Ensure it matches the standard ISO country codes and is correctly entered.
  
  
  
  MOSS Settings:
  
  Review the MOSS configuration in your SAP system. You can check the settings in transaction S_P00_07000139 (MOSS Configuration) to ensure that the country in question is included in the MOSS setup.
  
  
  
  Adjust Master Data:
  
  If the error is related to specific customer or vendor master data, check the relevant records to ensure that the tax country is correctly assigned.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to MOSS and VAT configuration for additional guidance.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  MOSS (Mini One Stop Shop): A scheme introduced by the EU to simplify VAT compliance for businesses selling digital services across EU member states.
  Tax Configuration in SAP: Proper configuration of tax codes and jurisdictions is crucial for compliance with local tax laws.
  Transaction Codes: Familiarize yourself with relevant transaction codes for tax configuration, such as OBD2, OBD3, and S_P00_07000139.
  
  By following these steps, you should be able to identify and resolve the issue related to the FS793 error message in SAP.