Do you have any question about this error?
Message type: E = Error
Message class: 6D - Real Estate Messages
Message number: 310
Message text: Settlement & was already reversed; temp.-stored docs. will be deleted
A reversal has already been carried out for the settlement run with
identification &v1&.
Documents for this ID that have been temporarily stored that now have
to be subsequently posted will be deleted from the database as no
further postings can be made on them.
Check the settlement identification and correct it, if necessary.
Error message extract from SAP system. Copyright SAP SE.
The SAP error message 6D310 indicates that a settlement document has already been reversed, and as a result, any temporary stored documents related to that settlement will be deleted. This error typically occurs in the context of the SAP Controlling (CO) module, particularly when dealing with settlement processes in Project Systems (PS) or Internal Orders.
Cause:
- Reversal of Settlement: The primary cause of this error is that a settlement document has already been reversed. In SAP, once a settlement is reversed, the system marks it, and any associated temporary documents are flagged for deletion.
- Incorrect Process Flow: Attempting to settle an order or project that has already been reversed can lead to this error.
- Data Integrity Issues: There may be inconsistencies in the data or the status of the documents involved in the settlement process.
Solution:
- Check Settlement Status: Verify the status of the settlement document. If it has indeed been reversed, you may need to determine if you need to re-settle the original document or if further action is required.
- Review Document Flow: Look at the document flow for the order or project in question. Ensure that all necessary steps have been completed correctly and that there are no pending actions.
- Re-Execute Settlement: If you need to settle the document again, ensure that you are working with the correct version of the document and that it has not been marked for deletion.
- Consult with SAP Support: If the issue persists, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues or patches related to this error.
Related Information:
By following these steps, you should be able to address the error message 6D310 effectively. If the problem continues, further investigation into the specific configuration and data in your SAP system may be necessary.
Get instant SAP help. Start your 7-day free trial now.
Feature | Free Access | Free Trial |
---|---|---|
Basic SAP error explanation | ![]() |
![]() |
Step-by-Step Usage Guide | ![]() |
![]() |
Interactive SAP Coach Assistance | ![]() |
![]() |
AI Troubleshooting for T-Code Errors | ![]() |
![]() |
6D309 No documents to be cleared found for this settlement ID
Self-Explanatory Message Since SAP believes that this specific error message is ...
6D308 LO &1 flow type &2 no matching viak20 entry found for AP
What causes this issue? An advance payment of &v3& &v4& for flo...
6D311 No status records found for request &1 and offer &2
Self-Explanatory Message Since SAP believes that this specific error message is ...
6D312 No status records found for request &1
Self-Explanatory Message Since SAP believes that this specific error message is ...
SAP messages fall into 3 different categories: Error messages
(message type = E), Warnings (W) or Informational (I) messages.
An error message will prevent you from continuing your work - it is a hard stop and you need to fix the error before you can proceed. A warning message will stop your work, however, you can then bypass the warning by pressing the Enter key on your keyboard. That said, it is still good practice to investigate the cause of the warning message and address it. An information message will not stop your work and is truly just for informational purposes.
Click on this link to search all SAP messages.