How To Fix FTR0558 - Table &1: Number of deleted entries is &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FTR0 - Treasury: Financial Transaction

• Message number: 558

• Message text: Table &1: Number of deleted entries is &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTR0558 - Table &1: Number of deleted entries is &2 ?

  The SAP error message FTR0558, which states "Table &1: Number of deleted entries is &2," typically occurs in the context of financial transactions, particularly when dealing with the management of financial instruments in the SAP system. This error indicates that there is a discrepancy in the number of entries that were expected to be deleted from a specific table.
  Cause:
  
  Data Inconsistency: The error often arises due to inconsistencies in the database, where the system expects a certain number of entries to be deleted, but the actual number differs.
  Transaction Issues: It may occur during the execution of a transaction that involves deleting or modifying financial instruments or related data.
  Custom Code or Enhancements: If there are custom developments or enhancements in the system that manipulate data in the relevant tables, they may lead to unexpected results.
  Database Locking Issues: If multiple users or processes are trying to access or modify the same data simultaneously, it can lead to inconsistencies.
  
  Solution:
  
  Check for Data Consistency: Use transaction codes like SE11 or SE16 to check the relevant tables for inconsistencies. Ensure that the data is as expected.
  Review Custom Code: If there are any custom programs or enhancements, review them to ensure they are functioning correctly and not causing the issue.
  Database Locking: Investigate if there are any locking issues. You can use transaction SM12 to check for locks on the relevant tables.
  Re-run the Transaction: Sometimes, simply re-running the transaction after ensuring that no other processes are interfering can resolve the issue.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error. There may be patches or updates available that resolve known issues.
  Contact SAP Support: If the issue persists, consider reaching out to SAP Support for assistance. Provide them with detailed information about the error, including the context in which it occurs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11 (Data Dictionary), SE16 (Data Browser), SM12 (Lock Entries), and others that may help in diagnosing the issue.
  SAP Documentation: Review SAP documentation related to financial transactions and the specific modules you are working with (e.g., Treasury and Risk Management).
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the FTR0558 error and implement a suitable solution.