How To Fix WTADDI_APPL017 - Class &2 contains plant/customer &1 for additionals procedure

WTADDI_APPL017 - Overview

• Message type: E = Error

• Message class: WTADDI_APPL - Messages for Application Log LO-ADM/APPL

• Message number: 017

• Message text: Class &2 contains plant/customer &1 for additionals procedure

Diagnosis
You can limit the usage of an
<DS:GLOS.3526BC88AFAB52B9E10000009B38F974>additional</> by stating a
<DS:DE.ADDI_CLINT>class</> that is assigned to the material.
You can also limit the execution of the follow-up action for an
additional by limiting the
<DS:GLOS.3526BC3AAFAB52B9E10000009B38F974>procedure for additional
</> to those plants and customers which are assigned to the class.
When analyzing additionals, the system searches each
<DS:DE.ADDI_APPL>application</> to determine if the entries for plants
or customers are contained in the class that was stated for the
additional.
Notes
If no class has been assigned to an additional, it is valid for the
current plant or customer. Depending on the application, the fields for
the check are taken from the following table:

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

Application ,,Name ,,Table ,,Field
Purchasing ,,Plant ,,EKPO ,,WERKS
Goods movements ,,Plant ,,MSEG ,,WERKS
Deliveries ,,Plant ,,LIPS ,,WERKS

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WTADDI_APPL017 - Class &2 contains plant/customer &1 for additionals procedure ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  WTADDI_APPL017: Class &2 contains plant/customer &1 for additionals procedure
  
  Meaning / 
  Cause:
  This error occurs in the context of additional procedures in SAP, typically related to tax determination or pricing procedures where classes and characteristics are used to control the behavior.
  
  The message indicates that the class (object class) identified by &2 already contains the plant/customer combination identified by &1 for the additional procedure.
  In other words, you are trying to assign or add a plant/customer to a class for an additional procedure, but this combination already exists in the system.
  This is a duplicate entry error, preventing redundant or conflicting assignments.
  
  
  When does it occur?
  
  When configuring or maintaining additional procedures in transaction codes like OVK1, OVK2, or during customizing of tax or pricing procedures.
  When assigning plants or customers to classes for additional procedures.
  During master data maintenance or configuration steps involving classification.
  
  
  
  Solution:
  
  
  Check existing assignments:
  
  Use transaction