We've run into the following issue in some of our SCM environments:
launch transaction /sapapo/sdp94
pin the tab
exit and re-enter
The result is an error message: /sapapo/sapapo is locked
/n//sapapo/sdp94 works and the transaction lauches
However, for the user benefit of arriving at login to the needed transaction is lost.
This happens for several transactions and in some of our environments.
Has anyone run into this issue or does anyone have a suggestion for a fix?
Thanks,
Lavaughn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.