How To Fix MDC_PROCESS_MSG348 - Ending process retention

SAP Error Message - Details

• Message type: E = Error

• Message class: MDC_PROCESS_MSG - MDC Process Object Messages

• Message number: 348

• Message text: Ending process retention

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message MDC_PROCESS_MSG348 - Ending process retention ?

  The SAP error message MDC_PROCESS_MSG348, which refers to "Ending process retention," typically occurs in the context of the SAP Landscape Management (LaMa) or SAP HANA database management. This error can arise due to various reasons related to process management, retention policies, or system configurations.
  
  Cause:
  
  Retention Policy Issues: The error may indicate that the retention policy for processes is not configured correctly or has been exceeded.
  Resource Constraints: Insufficient system resources (CPU, memory, disk space) can lead to process termination.
  Configuration Errors: Misconfigurations in the SAP system or landscape management settings can trigger this error.
  Database Issues: Problems with the underlying database, such as locks or transaction issues, can also lead to this error.
  
  
  Solution:
  
  Check Retention Policies: Review and adjust the retention policies for processes in the SAP system. Ensure that they are set according to your organization's requirements.
  Monitor System Resources: Use monitoring tools to check the system's resource usage. If resources are low, consider scaling