How To Fix SECAUDIT213 - Display filter &1 (display profile &2) does not contain any events


SAP Error Message - Details

  • Message type: E = Error

  • Message class: SECAUDIT - Message class for security audit

  • Message number: 213

  • Message text: Display filter &1 (display profile &2) does not contain any events

  • 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 SECAUDIT213 - Display filter &1 (display profile &2) does not contain any events ?

    The SAP error message SECAUDIT213 indicates that the display filter you are trying to use does not contain any events. This typically occurs when you are attempting to view security audit logs or events in the SAP system, but the specified display filter (or display profile) does not have any associated events to show.

    Cause:

    1. Empty Display Filter: The display filter you are using may not have been configured to include any events. This can happen if the filter was created without selecting any relevant event types.
    2. Incorrect Display Profile: The display profile you are using may not be set up correctly or may not correspond to any events that have been logged.
    3. No Events Logged: There may simply be no events that match the criteria defined in the display filter or profile.
    4. Configuration Issues: There could be issues with the configuration of the security audit log settings in the SAP system.

    Solution:

    1. Check Display Filter Configuration:

      • Go to the transaction code SM19 (Security Audit Log Configuration).
      • Review the display filter settings to ensure that it includes the necessary event types.
      • If needed, create a new display filter that includes the relevant events.
    2. Verify Display Profile:

      • Check the display profile you are using to ensure it is correctly set up.
      • You can do this in the same SM19 transaction or by using the appropriate transaction for managing display profiles.
    3. Review Logged Events:

      • Use transaction SM20 (Security Audit Log) to check if any events have been logged at all.
      • If no events are present, you may need to adjust your logging settings in SM19 to ensure that events are being captured.
    4. Adjust Logging Settings:

      • If you find that no events are being logged, you may need to adjust the logging settings in SM19 to ensure that the desired events are being recorded.
    5. Consult Documentation:

      • Refer to SAP documentation or help resources for more detailed guidance on configuring security audit logs and filters.

    Related Information:

    • Transaction Codes:
      • SM19: Security Audit Log Configuration
      • SM20: Security Audit Log Display
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues or bugs related to security audit logging.
    • User Authorizations: Ensure that you have the necessary authorizations to view the security audit logs and that the logging is enabled for your user profile.

    By following these steps, you should be able to resolve the SECAUDIT213 error and successfully view the desired security audit events.

    • 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker