How To Fix EB343 - Baseline date for tax determination (tax jurisdiction code) is not unique

SAP Error Message - Details

• Message type: E = Error

• Message class: EB - IS-U invoicing

• Message number: 343

• Message text: Baseline date for tax determination (tax jurisdiction code) is not unique

What causes this issue?

The calculation of taxes in invoicing takes place during invoicing with
the tax jurisdiction code. The base date for tax determination from the
company code Customizing settings is not unique.
This results in incorrect data during the extraction of tax data to the
sales statistics.

System Response

The current invoicing unit is terminated.

How to fix this error?

There are two options for avoiding this error. Choose the option that
best suits your situation:
Make sure that the same base date is always used in the participating
company codes (either the posting date or the document date).
In the "Specifications for Sales Statistics Extractor", deactivate the
field group for the tax information.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EB343 - Baseline date for tax determination (tax jurisdiction code) is not unique ?

  The SAP error message EB343 indicates that there is an issue with the baseline date for tax determination related to a specific tax jurisdiction code. This error typically arises when there are multiple entries in the system for the same tax jurisdiction code with overlapping or conflicting baseline dates, which makes it impossible for the system to determine which entry to use for tax calculations.
  Cause:
  
  Duplicate Entries: There are multiple records in the tax jurisdiction table (e.g., T007S) for the same tax jurisdiction code with overlapping baseline dates.
  Configuration Issues: Incorrect configuration in the tax determination settings or master data that leads to ambiguity in baseline dates.
  Data Migration Issues: If data was migrated from another system, it may have resulted in duplicate or conflicting entries.
  
  Solution:
  
  
  Check for Duplicates:
  
  Go to the relevant tax jurisdiction table (e.g., T007S) and check for duplicate entries for the specific tax jurisdiction code.
  Use transaction codes like SE16 or SE11 to view the table entries.
  
  
  
  Correct the Data:
  
  If duplicates are found, determine which entries are valid and remove or adjust the duplicates to ensure that each tax jurisdiction code has a unique baseline date.
  Ensure that the baseline dates do not overlap for the same jurisdiction code.
  
  
  
  Review Configuration:
  
  Check the configuration settings for tax determination in the SAP system (transaction code SPRO).
  Ensure that the tax codes and jurisdiction codes are correctly set up and that there are no conflicting settings.
  
  
  
  Test Changes:
  
  After making corrections, test the changes by attempting the transaction that previously resulted in the error to ensure that the issue is resolved.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to tax determination and jurisdiction codes for any additional guidance or best practices.
  
  
  
  Related Information:
  
  Transaction Codes: SE16 (Data Browser), SE11 (Data Dictionary), SPRO (Customizing).
  Tables: T007S (Tax Jurisdiction Codes), T007 (Tax Codes).
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists after checking for duplicates and correcting the data, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to resolve the EB343 error and ensure that your tax determination process functions correctly.