Transaction iViews default to SAP-GUI Windows

[Lukas_Weigelt]

Hi,

System Information: ECC 6.0 EHP 4 SP 46 Stack 10. Portal Netweaver 7.01 SP 11 (Our basis guys said, it wouldn't be a problem if Portal Stack is higher than Backend ).

First of all, what makes this issue particulary deceptive is, that it is somehow related to permissions in Backend. Whenever I open transaction iViews (property configured as "SAP-GUI for HTML") with users that have certain permissions (up until know I've observed SAP_ALL and the default Developer Role), it works just fine.

However, if I try to open these iViews with a user that has neither Role/Profile, a download prompt from Inet Explorer opens up and defaults to SAP-GUI for Windows which inevitably fails:

I tried to track this down using ST01 because I wagered there has to be SOMETHING, at least a security check or a database query, but the ST01 Trace is completely empty... the NWA tracelog shows nothing either, except "LOGIN OK!" -.- so I'm really stuck here. Does anybody have an idea? I fear for the worst (probably it's due to stack missmatch). Has somebody ever experienced something alike?

Please help ;-/

Cheers, Lukas

[siddharthrajora · Accepted solution]

very interesting indeed, i would check your kernel patches then, you can contact sap for component BC FES GUI, there might be a parameter settings for this in SICF

[Lukas_Weigelt · Accepted solution]

Will do that, Siddarth, thanks!

Other replies are welcome!

[Former Member · Accepted solution]

Hi Lukas, did you check that User does not have the Accesibility feature enabled in Portal?

If WinGUI as GUI Type is not working, you can also force it by setting the "Technique to Start SAP GUI for Windows" property to Structured Storage Document.

Also, you could use an IAC iView, which is more flexible than a Transaction iView (in terms of window and other properties, and error handling). In the SAP side you just have to:

1. create the service who calls the tx (use the path /sap/bc/gui/sap/its/)

2. to understand the main properties you can check the following links (use PV7I or WEBGUI service as an example):

http://help.sap.com/saphelp_erp60_sp/helpdata/en/a6/cf3d4050d89523e10000000a1550b0/content.htm

http://help.sap.com/saphelp_erp60_sp/helpdata/en/77/8b3d408ae01f24e10000000a1550b0/content.htm

http://wiki.sdn.sap.com/wiki/display/HOME/Article+-+Employ+SAP+GUI+for+HTML+instead+of+an+Internet+s...

As you can see in the last link that is strongly suggested to create the SICF service as "SAP GUI for HTML".

Regards

Sergio

[dsharmak · Accepted solution]

Please check the note

1010519   SAP GUI for HTML: Simplified title area w/o menu and  OK code

[Lukas_Weigelt · Accepted solution]

Hi Sergio,

it was the accessibility check mark! ;-/ This poses another problem which can then again probably be dealt with using your suggestion of "IAC iViews". I'll check out your Links as well and give a feedback how it turned out. The ogirinal problem however, has been solved. Many kudos for you! 🙂

Thanks + Cheers,

Lukas

[Lukas_Weigelt]

Feedback for IAC iViews: I replaced the Transaction-iView and use a IAC iView now. Since the SAP-GUI HTML property in the ICF-Service seems to be "stronger" than the iView, this does not cause the issue the Transaction-iView did, i.e. this iView can now be used even with the Accessibility feature and is still using SAP-GUI for HTML! 🙂

Cheers, Lukas