How To Fix RS2HANA_CHECK079 - Privilege on procedure is missing in SQL analytic privilege

RS2HANA_CHECK079 - Overview

• Message type: E = Error

• Message class: RS2HANA_CHECK - RS2HANA Check Report

• Message number: 079

• Message text: Privilege on procedure is missing in SQL analytic privilege

What causes this issue?

The privilege for calling the generated stored procedure of the
InfoProvider<(>,<)> in order to retrieve the filter string from table
RS2HANA_AUTH_STR<(>,<)> is missing in the generated SQL analytic
privilege.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Activate the InfoProvider again. This should generate the correct SQL
analytic privilege - including the privilege for calling the stored
procedure.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RS2HANA_CHECK079 - Privilege on procedure is missing in SQL analytic privilege ?

  The SAP error message RS2HANA_CHECK079 indicates that there is a missing privilege on a procedure in the context of SQL analytic privileges. This error typically arises when a user or role does not have the necessary permissions to execute a specific procedure or access certain data in SAP HANA.
  
  Cause:
  The error is usually caused by one of the following reasons:
  
  Missing Privileges: The user or role does not have the required privileges to execute the procedure or access the data defined in the SQL analytic privilege.
  Incorrect Role Assignment: The user may not be assigned the correct role that includes the necessary privileges.
  Changes in Analytic Privileges: If there have been recent changes to the analytic privileges or the underlying data model, it may lead to this error if the privileges are not updated accordingly.
  
  
  Solution:
  To resolve the RS2HANA_CHECK079 error, you can follow these steps:
  
  
  Check User Roles:
  
  Verify that the user encountering the error has the