Solman user SM<SID> is running SAPLSU_USER_CHANGE_DOC in sattelite system

[tmj_dk]

Let the quest begin

In our Fiori system We have a dump every one hour with the program SAPLSU_USER_CHANGE_DOC started by the solman user SM_<SID>

One thing is that the report ends with a "TIME_OUT" dump, we can proberly solve that with archiving and/or extending the "maxruntime" param,

Question:
Can you tell me from where in Solman this is trikkered?

[peng_wang6]

It is likely triggered by the CCDB extractors. Which can be checked in solution manager via t_cd CCDB.