How To Fix EK368 - Determination code for Argentinian taxes was not found

SAP Error Message - Details

• Message type: E = Error

• Message class: EK - IS-U Accounts Receivable and Payable

• Message number: 368

• Message text: Determination code for Argentinian taxes was not found

What causes this issue?

The tax determination code for Argentinian taxes could not be found in
the 2102 posting area. No entry was found for determination code &v1&,
fiscal type &v2&, province &v3&, &v4&.

System Response

Processing cannot continue.

How to fix this error?

Maintain the corresponding entry in the 2102 posting area.

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 EK368 - Determination code for Argentinian taxes was not found ?

  The SAP error message EK368, which states "Determination code for Argentinian taxes was not found," typically occurs in the context of tax determination in the SAP system, particularly when dealing with Argentinian tax regulations. This error indicates that the system is unable to find the necessary tax determination code for processing transactions related to Argentinian taxes.
  Cause:
  
  Missing Tax Configuration: The most common cause of this error is that the tax determination codes for Argentinian taxes have not been properly configured in the SAP system.
  Incorrect Tax Jurisdiction: The tax jurisdiction or the relevant tax codes may not be set up correctly for the specific transaction or vendor/customer.
  Master Data Issues: The vendor or customer master data may not have the correct tax information or may be missing the necessary tax classification.
  Updates or Changes: Recent updates or changes in tax regulations may not have been reflected in the system.
  
  Solution:
  
  
  Check Tax Configuration:
  
  Go to the transaction code OBYZ (for tax determination) and verify that the tax determination codes for Argentinian taxes are set up correctly.
  Ensure that the relevant tax codes are defined and linked to the appropriate tax jurisdiction.
  
  
  
  Review Master Data:
  
  Check the vendor or customer master data (transaction codes XK03 for vendors and XD03 for customers) to ensure that the tax classification is correctly assigned.
  Make sure that the tax information is complete and accurate.
  
  
  
  Update Tax Codes:
  
  If necessary, create or update the tax codes in the system to ensure they comply with Argentinian tax regulations.
  Use transaction code FTXP to maintain tax codes.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to Argentinian tax determination to ensure compliance with local regulations.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
  
  
  
  Consult SAP Support:
  
  If the issue persists, consider reaching out to SAP support for further assistance, especially if there are specific updates or patches related to Argentinian tax determination.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on tax configuration for Argentina.
  Local Tax Regulations: Stay updated on local tax regulations in Argentina, as these can change and may require adjustments in the SAP system.
  Training and Documentation: Ensure that users involved in tax configuration and processing are adequately trained and have access to relevant documentation.
  
  By following these steps, you should be able to resolve the EK368 error and ensure proper tax determination for Argentinian transactions in your SAP system.