Hi experts,
we are facing a very annoying problem with Bex queries (mostly executed from the portal). When a query runs for a long time user closes it (and sometimes runs it once again). However, even after the query is closed, in SM50 we can see that data is still being extracted from underlying InfoProviders. As the result sometimes one user can trigger several sessions. Obviously, It affects the performance of the server. Is there any way of dealing with this problem other than killing jobs manually in SM50?
There is an old thread here on SCN (User stops transaction in Bex, process continues to run on server) . It says, that there is no way of dealing wth it automatically. However, the last message there is 3 years old. Maybe something changed since then?
Best regards,
Vlad