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 should be applied, which are not being met.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Condition Type Configuration:
  
  Go to the SAP transaction code V/06 (for condition types) and verify the configuration of the condition type related to "bollo".
  Ensure that the condition type is set to allow zero amounts if that is the intended behavior.
  
  
  
  Review Pricing Procedure:
  
  Check the pricing procedure assigned to the sales document type in transaction V/08.
  Ensure that the condition type for "bollo" is included in the pricing procedure and is configured correctly.
  
  
  
  Adjust Transaction Data:
  
  Review the sales document where the error occurred. Ensure that the correct condition type is being used and that it is appropriate for the transaction.
  If necessary, adjust the document to use the correct condition type with a zero amount.
  
  
  
  Consult Documentation:
  
  Review any relevant documentation or guidelines provided by your organization regarding the handling of "bollo" or similar conditions.
  
  
  
  Testing:
  
  After making changes, test the transaction again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance on configuring condition types.
  User Exits or BAdIs: If your organization has custom logic implemented, check if there are any user exits or BAdIs that might be affecting the behavior of condition types.
  Training and Support: If you are unsure about the configuration, consider reaching out to your SAP support team or a consultant with expertise in SD module configuration.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.