How To Fix /ISDFPS/MM799 - No current messages exist (log transaction SLG1)

/ISDFPS/MM799 - Overview

• Message type: E = Error

• Message class: /ISDFPS/MM -

• Message number: 799

• Message text: No current messages exist (log transaction SLG1)

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/MM799 - No current messages exist (log transaction SLG1) ?

  The SAP error message /ISDFPS/MM799 No current messages exist (log transaction SLG1) typically indicates that there are no messages or logs available for the specified transaction or process in the application. This error is often encountered in the context of the SAP IS-DFPS (Industry Solution for Defense Forces and Security) module, particularly when dealing with material management or logistics processes.
  
  Cause:
  
  No Logs Generated: The most common cause of this error is that there are simply no logs generated for the transaction you are trying to view. This could be due to the transaction not being executed properly or not having any relevant messages to log.
  Incorrect Selection Criteria: If you are using transaction SLG1 to view logs, the selection criteria (like date range, object, or sub-object) may not match any existing logs.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the logs, leading to the perception that no