Skip to Content

Integrated ITS log off handling following application of portal SP22


We have recently applied support packages to our SAP Portal (to SP22 for EP 7.0).

We have an IAC iView which renders a SAP transaction which worked fine prior to the SPs being applied.

To improve the behaviour when the user selects the back/exit/cancel buttons from the IAC application toolbar (within the portal body) we implemented a few lines of Javascript in the ICF service on the backend SAP ECC system (under Error Pages -> Logoff Page) to redirect the user to the home page for the application.

We deemed this was preferable to the standard message issued.

The problem is that the javascript is being triggered now when the user selects 'Log off' from the portal.

The behaviour is not desirable (an extra browser window is opened and for some reason the log off takes about 2 minutes to take effect) hence we don't want the javascript triggered in this instance.

We may need to log this with SAP but does anyone know of a way of determining in the javascript whether the user has selected back/exit/cancel versus logging off from the portal?

Thanks in advance.


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Aug 24, 2010 at 06:11 PM

    Hello Alan,

    What do you have now in the Error Pages > Logoff Page of SICF for the service?

    If you wanted your custom Logoff Page only for when the service is used independent of the Portal than you could check for the Portal cookie, I think it's something like sap_wp. But if you want the Logoff Page to take effect in the Portal too than maybe you could check the ~okcode in the POST.


    Add comment
    10|10000 characters needed characters exceeded

    • Hi Jason,

      We logged the problem with SAP who stated that a note delivered in the portal SPs had altered the way that the log off process is handled.

      They suggested adding a 1 second wait until triggering the custom Javascript but we found the behaviour intermittent.

      Given ITS is not on our long term radar we've removed the Javascript and put in a simple HTML page within KM that we redirect to when logging off the ITS application (using the standard option in transaction SICF).

      This means we can put up a more meaningful message to the users.

      We felt returning to standard was preferable in this case.