How To Fix FWTM391 - Table &1, chart of accounts &2: Inconsis. type &3, code &4 (==> long txt)

FWTM391 - Overview

• Message type: E = Error

• Message class: FWTM - Messages: Withholding Tax Changeover

• Message number: 391

• Message text: Table &1, chart of accounts &2: Inconsis. type &3, code &4 (==> long txt)

What causes this issue?

One or more of the withholding tax codes that you use for classic
withholding tax is reflected in the following combination: Withholding
tax type &V3&/withholding tax code &V4&. The accounts defined in table
&V1& for posting withholding tax for this combination are different to
those defined for the corresponding withholding tax code for classic
withholding tax. Withholding tax would therefore be posted to different
G/L accounts before and after the conversion.

How to fix this error?

Check the following settings and correct them if necessary:
Customizing for extended withholding tax: Posting withholding tax
Assignment of withholding tax types/codes (second step in conversion
run)

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FWTM391 - Table &1, chart of accounts &2: Inconsis. type &3, code &4 (==> long txt) ?

  The SAP error message FWTM391 indicates an inconsistency in the configuration of a specific table related to the chart of accounts. This error typically arises in the context of financial accounting and can be related to various settings in the system.
  
  Cause:
  The error message FWTM391 is triggered when there is an inconsistency in the configuration of the specified table, which could be due to:
  
  Incorrect Configuration: The chart of accounts may have been incorrectly configured, leading to mismatches in the account types or codes.
  Data Migration Issues: If data has been migrated from another system or from a previous version of SAP, inconsistencies may arise if the data does not conform to the current configuration.
  Manual Changes: Manual changes to the configuration or data entries that do not adhere to the defined rules can also lead to this error.
  Missing Entries: Required entries in the configuration tables may be missing or incorrectly defined.
  
  
  Solution:
  To resolve the