Skip to Content
Author's profile photo Former Member

How to generate HANA indexserver logs from a client browser for S&OP on HANA

They say knowledge is power. Previously, one had to jump through a few hoops to get logs which imparted the knowledge of what was happening at a low level on the HANA server. They may have had to go to HANA studio and open the administration view with a user that had access to do so. Or perhaps they had to request that their system administrator get the logs for them which would be done on the administrator’s timeline. There is now an option to generate the logs by first creating a role and granting it to a user and then simply running a URL in a browser.

I’m sure many of us have gotten an error similar to the following:


With this type of error message, obtaining logs is essential. Below I’ll show how it’s done.


1) Create a DEBUG role (only needs to be done once) in the S&OP web ui


2) Assign the newly created DEBUG role to the user wishing to generate logs:



1. Login to the Web UI with the user that has DEBUG access – https://<server>/sap/sop/ui/login.html

2. Once you log into the UI, you can launch one of the below URLs, in the same browser window, to get the error log (please note that if you don’t have an error id, just use the first URL).

To return last 200 lines of the error log:


To get the error log neighboring the error id “0bc82458-719d-47fc-b2b9-2a1cb9c606d6”


I hope this empowers you in your use of S&OP on HANA.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Alecsandra Dimofte
      Alecsandra Dimofte

      Thank you!

      This is very useful specially for those working with productive systems, not having db exposed to ui.

      Now I should grab my spectacles 🙂



      Author's profile photo Lars Breddemann
      Lars Breddemann

      Hey John,

      thanks for putting the description together.

      Still, I've got to say, that this way of getting to error related information is pretty much broken.

      Handing the end-user a 32-digit hexadecimal log entry identifier is beyond all doubt not the right way to communicate system failure - especially not for an application that prides itself with a first class UX design.

      Hope to see large improvements here...

      - Lars

      Author's profile photo Pablo Tortosa
      Pablo Tortosa

      Hi John,

      we are working on a SOP IBP 4.0 and I cannot find the role "Application debugging" you are mentioning. Has this option somewhat disappeared in the new version?

      SOP IBP 4 permissions.pngregards,


      Author's profile photo Former Member
      Former Member

      Hi Pablo,

      Application debugging permission is not available anymore and debugging has been shifted to HANA database through index server logs.


      Aditya G