Skip to Content
Feb 20, 2013 at 08:35 AM

On hold/Priv dialog work process not ending after AS timeout expiration



This morning, there was a Dialog Work Process in mod On Hold / Priv.

The Runtime reported in sm50 was more than 18 hours.

The report name in sm50 was SAPLSMTR_NAVIGATION.

The last transaction (FS10N) in the audit log for this user dated for more than two days ago.

The user told me that he did not restart a new transaction since the day before.

The following parameters are set in our system:

rdisp/max_wprun_time = 6000

rdisp/gui_auto_logout = 9000

Could you explain me why this user was not auto logged out?

Naively I thought that after 1.66 hour a working transaction would end.

Then after 2.5 hour there would be an automatic logout.

But I misunderstand these timeouts behaviors.

Thanks in advance for your answers.