Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: EEDMSET - Messages for Settlement
Message number: 117
Message text: There are no messages to be saved
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.
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.
EEDMSET117
- There are no messages to be saved ?The SAP error message EEDMSET117, which states "There are no messages to be saved," typically occurs in the context of the SAP Event Management or SAP Business Workflow when attempting to save messages or notifications that are expected to be processed or logged.
Cause:
- No Messages Available: The most straightforward cause is that there are genuinely no messages available to be saved. This could happen if the process that generates messages has not been executed or if the messages have already been processed.
- Filter Criteria: If there are filters applied that restrict the visibility of messages, it may result in no messages being available for saving.
- System Configuration: There may be configuration issues in the system that prevent messages from being generated or saved.
- Authorization Issues: Lack of proper authorizations may prevent the user from accessing or saving messages.
Solution:
- Check Message Generation: Ensure that the process that is supposed to generate messages has been executed. Verify that the relevant events or transactions have occurred.
- Review Filters: Check any filters that may be applied in the message processing area. Remove or adjust filters to see if messages become visible.
- System Configuration: Review the configuration settings related to message handling in the relevant SAP module. Ensure that all necessary settings are correctly configured.
- User Authorizations: Verify that the user has the necessary authorizations to view and save messages. Consult with your SAP security team if needed.
- Check Logs: Look into system logs or application logs for any additional error messages or warnings that might provide more context about the issue.
Related Information:
If the issue persists after trying the above solutions, it may be beneficial to contact SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
EEDMSET116
Method &1 was not processed
What causes this issue? You cannot call method &V2& of class &V3& without first calling method &V1&.System Response The data...
EEDMSET115
There is a message without a message class
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EEDMSET118
Do not enter data in field &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
EEDMSET119
Problem class &1 is not permitted
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.