How To Fix WTADDI402 - Database error: existing additionals could not be changed

SAP Error Message - Details

• Message type: E = Error

• Message class: WTADDI - Additionals: Messages

• Message number: 402

• Message text: Database error: existing additionals could not be changed

What causes this issue?

You have made changes to existing <GL:additional>additionals</> and
want these changes to be written to the database. The database table
has not been refreshed with this data, however.

How to fix this error?

INCLUDE ISR_VERWALTUNG

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WTADDI402 - Database error: existing additionals could not be changed ?

  The SAP error message:
  WTADDI402 Database error: existing additionals could not be changed
  typically occurs in the context of time evaluation (PT - Personnel Time Management), specifically when dealing with additional time data (such as additional time types or time wage types) that are stored in the database.
  
  Cause
  
  The error indicates that the system tried to change or update existing additional time records in the database, but the update failed.
  This can happen due to:
  
  Database lock conflicts: The record is locked by another process.
  Inconsistent or incorrect data: The additional time records to be changed do not match the expected structure or keys.
  Authorization issues: The user or process does not have sufficient rights to update the records.
  Custom code or user exits: Custom enhancements or user exits that manipulate additional time data may cause inconsistencies.
  Transport or system inconsistencies: If the system is in an inconsistent state or after a transport, the database tables might be out of sync.
  Incorrect time evaluation schema or rules: The time evaluation schema might be trying to update additionals that are not allowed or incorrectly configured.
  
  
  
  
  Solution
  
  
  Check for database locks:
  
  Use transaction SM12 to check if the relevant records are locked.
  If locks exist and are stale, release them carefully.
  
  
  
  Verify time evaluation schema and rules:
  
  Review the time evaluation schema (transaction PE01) and the rules that generate or update additional time records.
  Ensure that the rules are consistent and do not try to update additionals incorrectly.
  
  
  
  Check for authorization issues:
  
  Verify that the user or batch job running the time evaluation has the necessary authorizations.
  
  
  
  Review custom code:
  
  If there are user exits or BAdIs related to time evaluation (e.g., PT60, HR00), check if they manipulate additional time data.
  Debug or review the custom code for errors or inconsistencies.
  
  
  
  Database consistency check:
  
  Run consistency checks on the relevant time management tables (e.g., PA2006, PA2006A).
  Use transaction SE14 or database tools to check and repair table inconsistencies if needed.
  
  
  
  Re-run time evaluation:
  
  After corrections, re-run the time evaluation (transaction PT60) for the affected personnel number and period.
  
  
  
  SAP Notes and Support:
  
  Search for SAP Notes related to message WTADDI402.
  For example, SAP Notes might provide patches or corrections if this is a known issue in a particular SAP version.
  
  
  
  
  Related Information
  
  Message Class: WTADDI (Time Evaluation Additional Data)
  Transaction: PT60 (Time Evaluation)
  Tables involved: PA2006 (Absences), PA2006A (Additional Time Data), or other related time management tables.
  SAP Notes: Check SAP Support Portal for notes related to WTADDI402.
  Debugging: Use debugging in PT60 to trace where the update fails.
  User Exits/BAdIs: HR00, HR00_TIME, or other time evaluation related enhancements.
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  Attempt to update existing additional time records failed due to locks, data, or config
  
  
  Solution
  Check locks (SM12), verify schema/rules, check authorizations, review custom code, run consistency checks, re-run PT60
  
  
  Related Info
  Message class WTADDI, transaction PT60, tables PA2006/PA2006A, SAP Notes, debugging
  
  
  
  
  If you provide more context (e.g., when exactly the error occurs, any customizations, or system version), I can help with more specific guidance.