On 6.2 there was a profile parameter called ~webgui _ easy _ access _ menu, setting it to 0 controlled the easy access screen. Where can I find it in v7?
The ~webgui_easy_access_menu = 0 from the ITS 6.20 should show the user a button that must be pressed before the SAP Easy Access menu is displayed. The same effect can be achieved if you set ~transaction to S000 in the Integrated ITS. To do this you go to transaction SICF, execute, and then expand the tree: default_host > sap > bc > gui > sap > its, double click on webgui, go to change mode, click on the GUI Configuration button and add ~transaction as a new Parameter Name with Value of S000. Save this and then test again.
There is no longer a global.srvc file or a similar location with the Integrated ITS. You should maintain this in each service, though I'm a little confused as to why this would be needed in any other service. In other services there should be a ~transaction parameter and value, so the SAP Easy Access Menu is skipped anyways. Only the webgui (or a copy of it) would present the user with the SAP Easy Access Menu to start with. Please be specific in your question and list a service and URL example. Thanks.
Correct me if I'm wrong but isn't the value for the ~transaction is a specific transaction? I would like to apply this to any transaction I expose through the portal as an iView and not just specific one. Or am I missing something here...?
I'm failing to understand what the goal is. But generally system administrators like to limit the access users have. When the webgui service is used there is the possibility that users can gain access to a transaction that was not intended. This can be avoided a few ways. The first is to turn off the okcode field, this can be done with note 1010519. The next way is to use a session that is opened for a valid purpose, but then changing the transaction, this can be avoided with note 959417.
From the Portal an iView basically creates a URL to call the ITS. Sometimes the URL is:
In your case you just want the SAP Easy Access Menu suppressed. From my understanding the only time the SAP Easy Access Menu is displayed by default is when there is no ~transaction and the webgui service is called (basically the first Portal iView example without the transaction portion) or when using the webgui service and the user uses the "up" or "back" button to end the transaction. If it is the first case then my workaround (transaction=S000) is valid. If it is the second case that you're trying to avoid then maybe you should look into note 959417 and 1010519 from my above comment.
I know that it doesn't make sense but that's the client requirements: There are cases that we expose users to iViews that expose transactions in the portal which they are not authorised to use.
The standard SAP behaviour in such a case is exposing the SAP easy access button and showing the user an unauthorised message at the button. We would like to replace this page by a unauthorised page (an html for example that we will create and reference to) and suppress any access to easy access.
You should try the previously mentioned ~singletransaction to see if that helps limit what the user can do.
Besides that the only option on the ITS side is to create custom SICF entries for each of these services and maybe even templates so that you're not using ~webgui=1, which then would not dynamically generate the page with the Easy Access Menu button. But that can be a huge undertaking depending on the number of iViews you see this issue with.
The other option is to tighten user authorization so that users can only use transactions they're meant to use or to tighten the roles in Portal so that users only see transactions they're meant to use in the Portal menu.
When you say ~singletransaction I assume you mean ~transaction as I have need seen a solution that involves the ~singletransaction parameter...
Can you please elaborate on the templates solution that you've mentioned?
Is it possible to add an error parameter (for example, when the user is not authorised) and redirect to an error html file that I will build for that? If yes then a step by step solution will be great.
Like I said, tighten the user's authorizations is not something which they are willing to consider from internal design consideration although I agree that this will be the most simple and correct approach. bottom line is there are users who are exposed to transaction iViews that they don't suppose to be able to run. We would like not to let them into SAP GUI at all in such a case and direct them to an error page if possible.
What you see now is before templates have been developed and an entry in the SICF. If you create your own templates for this transaction, ZTAH_ABS_QUOTAS, then you will need to tell the ITS about the ~transaction in the GUI Parameters of SICF. You could also tell the ITS where the templates are located using ~sources and ~theme.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.