Look and feel for contextual help for SAP GUI transactions

[former_member822654]

Hi,

We are exploring the different ways to display contextual help or learning content to our Apps deployed in Fiori Launchpad.

We have SAP Fiori Apps, for which SAP Companion can be used to enrich contextual help provided by SAP via our SAP Enable Now.

We also have App launching SAP GUI transactions (standard or custom ones) :

I understand that we should use SAP Companion for Desktop to add contextual help or learning material to these Apps.

My question is about how the end user will access this contextual help. I can’t find any document or video showing how it would look like for the end-user.

Will he use the button as for SAP Fiori App ?Will the look and feel be the same as contextual Help for Fiori Apps ?

I am concerned with what I read about SAP Companion for Desktop, and that there will not be a seemingless user experience for our end users, meaning there will be a different way to access contextual help, whether they will be using Fiori or SAP GUI Apps.

Thanks for your help.

[Anton_Mavrin1 · Accepted solution]

Hi saguettaz,

You can still use SAP Companion (fka Web Assistant) for the GUI for HTML and Webdynpro applications provided they are opened within the Fiori Launchpad.

If you mean the "classic" SAP GUI running in SAP Logon/NWBC, then there are 2 options:

1) Start with the GUI Help Menu Integration with SAP Enable Now content

2) Add the SAP Companion for Desktop Applications for transactions/screens where the Help menu integration is not enough.

You are correct, the startup process of the SAP Companion Desktop is diametrically different from the SAP Companion for Web. To start it automatically when the user opens the target app you'll probably need to involve your infrastructure team (Microsoft, not SAP). Also, you can choose the manual method, by adding a custom link to the SAP User Menu that will trigger the SAp Companion Desktop.

Hope this helps somehow.

[DirkManuel]

There's a couple of things you should research:

• Using the enableClassicIntent parameter to allow you to provide help for WebGui transactions opened via Fiori Logonpad - this may work for you depending on where these transactions are launched from.
• Using the useGlobalHelp parameter to provide something in the way of help, if you can't actually provide SAP Companion help.

They are both explained in the SAP Companion Integration Guide.