Do you have any question about this error?
Message type: E = Error
Message class: FTR0 - Treasury: Financial Transaction
Message number: 258
Message text: Correspondence planned record deleted in background
Before you reversed/changed business transaction &V1&, at least one
status-relevant correspondence planned record (correspondence type:
&V2&) was created. The system will generate correspondence for this
transaction which will not include the current changes.
<ZH>Case 1: </>The correspondence planned record is deleted for
consistency reasons. This correspondence cannot therefore be output
after the transaction has been changed and/or reversed.
<ZH>Case 2: </>You have selected the setting 'No initial reversal
correspondence' for a correspondence type in Customizing. The system
deletes an existing planned record; you deliberately want to suppress
the reversal correspondence.
Error message extract from SAP system. Copyright SAP SE.
FTR0258
- Correspondence planned record deleted in background ?The SAP error message FTR0258 indicates that a correspondence planned record has been deleted in the background. This error typically occurs in the context of financial transactions, particularly in the area of treasury and risk management, where correspondence records are used to manage communications related to financial instruments.
Cause:
The error can be caused by several factors, including:
- Background Job Deletion: A background job that processes correspondence records may have deleted the planned record before it could be executed.
- Data Consistency Issues: There may be inconsistencies in the database or issues with the data integrity that lead to the planned record being unavailable.
- User Actions: A user may have manually deleted the correspondence record or made changes that affected its availability.
- System Configuration: Incorrect configuration settings in the SAP system related to correspondence processing could lead to unexpected deletions.
Solution:
To resolve the FTR0258 error, consider the following steps:
- Check Background Jobs: Review the background jobs that are scheduled to run in your SAP system. Look for any jobs that may have processed or deleted correspondence records.
- Review Logs: Check the application logs (transaction SLG1) for any messages related to the deletion of correspondence records. This may provide insights into why the record was deleted.
- Data Consistency Check: Perform a data consistency check to ensure that all related records are intact and that there are no orphaned entries in the database.
- Recreate the Record: If the correspondence record is essential, you may need to recreate it manually or through a batch process, depending on your business processes.
- Consult Documentation: Review SAP documentation or notes related to the FTR0258 error for any specific recommendations or patches that may address the issue.
- Contact SAP Support: If the issue persists and you cannot determine the cause, consider reaching out to SAP support for assistance. They may provide additional insights or solutions based on your specific system configuration.
Related Information:
By following these steps, you should be able to diagnose and resolve the FTR0258 error effectively.
Get instant SAP help. Start your 7-day free trial now.
FTR0257
Copy form &?
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FTR0256
Correspondence planned record created manually is deleted in background
What causes this issue? Before business transaction &V1& was changed and/or deleted, at least one correspondence planned record (corresponden...
FTR0259
Info: Languages form &1 from &2 to &3
What causes this issue? The SAPscript form is not available in the required language &V2&. The system therefore calls up the original languag...
FTR0260
Communication interface for telefax not yet configured
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.