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

SAP Error Message - Details

• 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 CL20N (Classification: Change) or CL30N (Display) to check the class &2.
  Verify if the plant/customer &1 is already assigned to this class.
  
  
  
  Avoid duplicate entries:
  
  If the plant/customer is already assigned, do not add it again.
  If you intended to change or update the assignment, modify the existing entry instead of creating a new one.
  
  
  
  Correct the configuration:
  
  If you are in customizing, review the additional procedure assignments.
  Remove or adjust duplicate entries in the configuration tables.
  
  
  
  Check related customizing:
  
  Go to the IMG path related to additional procedures (e.g., Sales and Distribution ? Basic Functions ? Pricing ? Pricing Control ? Define Additional Pricing Procedures).
  Ensure that the plant/customer is not assigned multiple times to the same class or procedure.
  
  
  
  
  Additional Information:
  
  Classes and Characteristics: SAP uses classes and characteristics to group objects (plants, customers) for flexible control in pricing, tax, or other procedures.
  Additional Procedures: These are used to extend standard procedures with custom logic or additional conditions.
  Transaction Codes:
  
  CL20N - Change Class
  CL30N - Display Class
  OVK1 / OVK2 - Customizing for additional procedures (depending on module)
  
  
  Table Involved: The assignments are stored in classification tables such as KLAH (Class header), KSSK (Characteristic values), and related tables for additional procedures.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Error Cause
  Duplicate assignment of plant/customer to class for additional procedure
  
  
  Solution
  Check and remove duplicate entries in class assignments; modify existing instead of adding new
  
  
  Tools
  CL20N, CL30N, customizing transactions (OVK1, OVK2)
  
  
  Context
  Additional procedures in pricing/tax/customizing
  
  
  
  
  If you provide the exact scenario or transaction where this error occurs, I can help with more specific steps.