How To Fix EDOCUMENT_IT025 - Use an SD condition type with zero amount for bollo instead of always

SAP Error Message - Details

• Message type: E = Error

• Message class: EDOCUMENT_IT - eDocument Italy Fattura Messages

• Message number: 025

• Message text: Use an SD condition type with zero amount for bollo instead of always

What causes this issue?

You have maintained the value <ZK>always</> in the additional data for
company code &V1& for the <ZK>Fattura GL account for Bollo</> parameter.
This value is not supported anymore.

System Response

The system does not create the ITFATTURA.

How to fix this error?

Instead of <ZK>always</>, do the following:
Enter the respective G/L account in the <ZK>Fattura GL account for Bollo
</> parameter. If bollo is always zero, you can leave the parameter
empty.
Use an SD condition type for bollo with condition value = 0 in the
invoices. Assign the condition type to <ZK>Fattura cond. type for Bollo
</> parameter in the additional data for company code &V1&.

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 EDOCUMENT_IT025 - Use an SD condition type with zero amount for bollo instead of always ?

  The SAP error message EDOCUMENT_IT025 typically indicates that there is an issue with the configuration of condition types in the Sales and Distribution (SD) module, particularly related to the handling of certain conditions like "bollo" (which may refer to a specific tax or fee in your context).
  
  Cause:
  The error arises when the system expects a specific condition type to be used with a zero amount, but it is not configured correctly or is being used incorrectly in the transaction. This can happen due to:
  
  Incorrect Configuration: The condition type for "bollo" may not be set up to allow zero amounts, or it may not be linked correctly to the relevant pricing procedure.
  Transaction Data: The transaction might be trying to apply a condition type that is not appropriate for the current context, leading to the error.
  Business Rules: There may be specific business rules or legal requirements that dictate how certain fees or taxes