Do you have any question about this error?
Message type: E = Error
Message class: E0 - SAP EDI messages
Message number: 849
Message text: Status record outbox: Temporary IDoc number list not deleted
IDoc numbers which were saved temporarily in the INDX file could not be
deleted.
Status records for the IDocs had already been sent. To prevent the
status records being sent again, you should ensure that the data
cluster has been deleted.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Technical information, i.e. parameters for the INDX-Delete command:Error message extract from SAP system. Copyright SAP SE.
E0849
- Status record outbox: Temporary IDoc number list not deleted ?The SAP error message E0849, which states "Status record outbox: Temporary IDoc number list not deleted," typically occurs in the context of IDoc processing in SAP. This error indicates that there is an issue with the temporary IDoc number list not being cleared or deleted as expected. Here’s a breakdown of the cause, potential solutions, and related information:
Cause:
- IDoc Processing Issues: The error may arise if there are issues during the processing of IDocs, such as failures in the communication with the partner system or problems in the IDoc itself.
- System Configuration: Incorrect configuration settings in the IDoc processing or in the partner profiles can lead to this error.
- Database Locking: If there are database locks or issues with the database that prevent the deletion of the temporary IDoc number list, this error can occur.
- Program Errors: Bugs or issues in the custom programs or enhancements that handle IDoc processing may also lead to this error.
Solution:
- Check IDoc Status: Use transaction WE02 or WE05 to check the status of the IDocs. Look for any IDocs that are in error status and analyze the error messages associated with them.
- Reprocess IDocs: If there are IDocs in error, you may need to reprocess them. You can use transaction BD87 to reprocess IDocs that have failed.
- Review Configuration: Check the configuration settings for IDoc processing in transaction WE20 (Partner Profiles) and ensure that they are set up correctly.
- Database Check: Ensure that there are no database locks or issues. You can use transaction SM12 to check for locks and SM21 for system logs to identify any underlying issues.
- Check for Updates: Ensure that your SAP system is up to date with the latest support packages and notes, as there may be known issues that have been resolved in later versions.
- Debugging: If the issue persists, consider debugging the IDoc processing program to identify where the deletion of the temporary IDoc number list is failing.
Related Information:
If the problem continues after trying the above solutions, it may be beneficial to consult with your SAP Basis or technical team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
E0848
Inbound IDocs: Temporary IDoc number status could not be deleted
What causes this issue? IDoc numbers which were saved temporarily in the INDX file could not be deleted. The IDocs had already been transferred to th...
E0847
Port '&' does not exist in the table of port descriptions
What causes this issue? For port &v1&, IDocs should be transferred with an R/2 system. The port no longer exists in the port description tabl...
E0850
IDoc transfer: Logon to R/2 System failed (no confirmation)
What causes this issue? The SAP system could not log on to the R/2 System. The confirmation from the R/2 System was not received.System Response The...
E0851
IDoc transfer: Logon to R/2 System failed (no confirmation)
What causes this issue? The SAP system could not log on to the R/2 System. The confirmation from the R/2 System was negative. The system issues an er...
Click on this link to search all SAP messages.