How To Fix SECAUDIT091 - No hits in the selection (reason: &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: SECAUDIT - Message class for security audit

• Message number: 091

• Message text: No hits in the selection (reason: &1)

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 SECAUDIT091 - No hits in the selection (reason: &1) ?

  The SAP error message SECAUDIT091 "No hits in the selection (reason: &1)" typically occurs when you are trying to execute a security audit log report or transaction, and the system does not find any entries that match the selection criteria you have specified. The &1 in the message will usually provide additional context about why no hits were found.
  Causes:
  
  No Audit Logs Available: There may not be any security audit logs generated for the specified time period or criteria.
  Incorrect Selection Criteria: The filters or selection criteria you have set (such as date range, user, transaction code, etc.) may be too restrictive or incorrect.
  Audit Logging Not Activated: Security audit logging may not be activated in the system, meaning no logs are being recorded.
  Data Purged: The audit logs may have been purged or deleted, leading to no available entries.
  
  Solutions:
  
  
  Check Audit Log Activation:
  
  Ensure that security audit logging is activated in your SAP system. You can check this in transaction SM19 (Security Audit Log Configuration).
  If it is not activated, you will need to enable it and configure the necessary parameters.
  
  
  
  Review Selection Criteria:
  
  Revisit the selection criteria you are using. Make sure that the date range and other filters are set correctly and are not too restrictive.
  Try broadening the criteria to see if any entries are returned.
  
  
  
  Check for Existing Logs:
  
  Use transaction SM20 (Security Audit Log) to check if there are any logs available for the specified period.
  If there are no logs, you may need to wait for new logs to be generated or check if the logs have been archived or deleted.
  
  
  
  Consult System Administrator:
  
  If you suspect that logs have been purged or if you are unsure about the configuration, consult your system administrator or security team for assistance.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  SM19: Configuration of Security Audit Log
  SM20: Display Security Audit Log
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to security audit logging.
  Documentation: Review SAP documentation on security audit logging for best practices and configuration guidelines.
  
  By following these steps, you should be able to diagnose and resolve the SECAUDIT091 error in your SAP system.