cancel
Showing results for 
Search instead for 
Did you mean: 

Record locks in R/3 while using SSO in the portal

Former Member
0 Kudos

While using the R/3 transaction TRIP via the portal, we intermittently have users who close Internet Explorer without logging off the portal. When the user tries to go back into the portal and retry the transaction, we are getting a message that they are locked in R/3. Investigation reveals that there is an existing record lock on a table in R/3 for that user and we have to use R/3 transaction SM12 to remove the lock. From the development team, we have tried unsuccessfully to recreate this situation and can not, but it is still happening periodically with our users.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello,

The ITS service is setting the lock. I have had the same problem with the timesheet (transaction catw)

the solution is that you have to upgrade the ITS to min. level 14 and apply the distributed session management as mentionned in OSS note 766287; ITS 6.20: DSM - Distributed Session Management.

Do take into account that the session management only works if the user waits until the whole page has been loaded.

Kind Regards

Koen Van Loocke

MartyMcCormick
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ted,

Are you using ITS to access SAP R/3? If so, set the paremeter ~disconnectOnClose 1 in your webgui.srvc file on the ITS AGate. This provides session management for ITS, thus when a user closes his/her browser without logging off, the backend session will be killed.

Hope this helps,

Marty