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


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /ISDFPS/MM -

  • Message number: 799

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

  • Show details Hide details


  • 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:

    1. 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.
    2. 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.
    3. Authorization Issues: Sometimes, the user may not have the necessary authorizations to view the logs, leading to the perception that no logs exist.
    4. System Configuration: There may be configuration issues in the logging settings that prevent logs from being created or displayed.

    Solution:

    1. Check Transaction Execution: Ensure that the transaction or process you are trying to log has been executed correctly. If it has not been executed, there will be no logs to display.
    2. Adjust Selection Criteria: When using transaction SLG1, try adjusting the selection criteria. For example, broaden the date range or check different objects/sub-objects to see if any logs exist.
    3. Review Authorizations: Verify that you have the necessary authorizations to view logs. You may need to consult with your SAP security team to ensure you have the right permissions.
    4. Check Configuration: If you suspect a configuration issue, consult with your SAP Basis or technical team to ensure that logging is properly configured for the relevant transactions.
    5. Consult Documentation: Review SAP documentation or notes related to the specific transaction or module to see if there are any known issues or additional steps required.

    Related Information:

    • Transaction SLG1: This transaction is used to display application logs in SAP. It allows users to filter logs based on various criteria, including date, object, and sub-object.
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
    • SAP Community: Engaging with the SAP Community forums can provide insights from other users who may have encountered similar issues.

    If the problem persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant