Message type: E = Error
Message class:  SEPMH_DG - EPM HANA DG - Messages 
Message number: 009
Message text: Serious Error - check previous exception
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.
The SAP error message SEPMH_DG009, which indicates a "Serious Error - check previous exception," typically arises in the context of SAP's Mobile Platform or related mobile applications. This error suggests that there was a significant issue during the execution of a process, and the system is prompting you to investigate the underlying cause. Possible Causes:
Configuration Issues: Incorrect configuration settings in the mobile application or the backend system can lead to this error. Network Problems: Connectivity issues between the mobile device and the SAP backend can cause data transmission failures. Data Integrity Issues: Corrupted or invalid data being processed can trigger exceptions. Code Errors: Bugs or exceptions in the custom code or logic implemented in the mobile application. Resource Limitations: Insufficient resources (memory, processing power) on the device or server can lead to failures. Version Compatibility: Mismatches between the versions of the mobile application and the backend system can cause unexpected behavior. Solutions: Check Logs: Review the logs for
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
SEPMH_DG008 DB table '&1' is no EPM child table
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEPMH_DG007 Call of method &1 not allowed in the context of class &2
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEPMH_DG010 A header node has no parent node
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SEPMH_DG011 Rule for creating DB rows for entity '&1' is missing
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.