How can hide the command line of a t.code in the portal

Question

Dear Experts.
I have the following doubt:
How can hide the Command Line of a Report that is called with a T.Code in the portal?
Attach Image:
[Image T.Code|http://www.freeimagehosting.net/uploads/eab3b6a03c.jpg]
When I created a service using the T.Code SICF for the T.Code , I can hide buttons and the filed command line  using
~webgui_simple_toolbar
~singletransaction
~NOHEADEROKCODE
With notes 1010519, "SAP GUI for HTML: Simplified Title Area Without Menu and OK Code" and 959417.
But the problem is that when I create the service in the T.Code SICF, I also have that create an Iview IAC in the portal.
The Question is : How can hide this fields and buttons if I want Publish the T.code using an Iview Transaction in the portal?
In this moment I have used the two options:
1 option) I created a service using the t.Code SICF for my Transaction and I also created an Iview IAC in the portal for call the service.
RESULT:
SAP Web Application Server
         500 Connection timed out
        Error: -5
       Version: 7000
       Component: ICM
       Date/Time: Sat Jun 12 20:26:39 2010 
       Module: icxxthr_mt.c
       Line: 2698
       Server: xyxab...
Error Tag: {-}
Detail: Connection to partner timed out after 60s
2)  created an Iview Transaction  in the portal and  call my transaction.
RESULT.
[Image T.Code|http://www.freeimagehosting.net/uploads/eab3b6a03c.jpg]
But not can hide the field Command Line and other buttons.
I think that the command :
~webgui_simple_toolbar
~singletransaction
~NOHEADEROKCODE
Only can be used if I create a service using the T.Code SICF .
Best Regards
Carmen.

Answer 1

Hi Carmen,
The bottom line is that this cannot be done for transaction iviews without modifying the standard webgui service in SICF, which is probably not a good idea (since it affects everyone using SAP GUI for HTML). (You could hack the appintegrator to add the ~webgui_simple_toolbar parameter to the transaction URL template in the portal, but again its not a recommended thing to do ...). Better to create an IAC service in SICF with ~webgui=1 where you set the required appearance using an appropriate value for ~webgui_simple_toolbar, and then create an IAC iview to point at this service.
You can even override the ~transaction value configured in the new service in individual IAC iviews by entering the appropriate value in the application parameter of the iview, for example:
~okcode=/nSU01
And you can pass parameters in the same way:
~okcode=/nSU01 USR02-BNAME=xyz;USREFUS-USERALIAS=abc;
By the way, it would not be recommended to create a URL iview to access an IAC, since you are likely to encounter session management issues in this scenario - better to use an IAC iview.
Regards, Rory