How To Fix /ISDFPS/PM_DIS358 - The log could not be saved

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/PM_DIS -

• Message number: 358

• Message text: The log could not be saved

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 /ISDFPS/PM_DIS358 - The log could not be saved ?

  The SAP error message /ISDFPS/PM_DIS358: The log could not be saved typically occurs in the context of the SAP Discrete Industries and Manufacturing (DIS) module, particularly when dealing with production or maintenance logs. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Authorization Issues: The user may not have the necessary permissions to save logs in the system.
  Database Issues: There could be problems with the database connection or the database itself, such as being full or having corruption.
  Configuration Errors: Incorrect configuration settings in the system may prevent logs from being saved.
  System Performance: If the system is under heavy load, it may not be able to process the log saving request.
  Missing or Incomplete Data: Required fields or data may be missing, leading to the inability to save the log.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the action. This can be done by reviewing the user's roles and permissions in the SAP system.
  Database Health Check: Verify the health of the database. Check for any issues such as space limitations or corruption. If necessary, consult with your database administrator to resolve any database-related issues.
  Review Configuration: Check the configuration settings related to logging in the DIS module. Ensure that all necessary parameters are correctly set.
  System Performance Monitoring: Monitor the system performance to identify any bottlenecks. If the system is under heavy load, consider scheduling the log-saving operation during off-peak hours.
  Data Validation: Ensure that all required fields are filled out correctly before attempting to save the log. Validate the data being entered to ensure completeness and correctness.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in troubleshooting, such as SM21 (System Log), ST22 (Dump Analysis), and SLG1 (Application Log).
  Support: If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance. Provide them with detailed information about the error, including any relevant logs or screenshots.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.