transactional rfc (in sm58) from user "DOCSYS"in status Transaction executi

[Former Member]

I have plenty transactional rfc (in sm58) from user "DOCSYS"in status Transaction executing since 4 hour. Target system is "WORKFLOW_LOCAL_001" Function module is "SWW_WI_EXECUTE_INTERNAL_RFC".

Some transactional rfc are in "Transaction recorded" (if i start them sometimes they disappear) and sometimes I get another transactional rfc in status "Transaction recorded" from user "WF-BATCH" and function module "SWW_WI_CREATE_VIA_EVENT_IBF" in status "Transaction recorded".

Sometimes when I want to execute a LUW the screen gets "frozen" meaning I have to exit the transaction with "Stop transaction".

How to deal with this problem.

[Eddie_Morris · Accepted solution]

Hello,

Have you registered the workflow rfc destination WORKFLOW_LOCAL_001 in SMQS? If so this will queue your workflow tRFC's and execute them one at a time. If there are more tRFC's than the settings can handle then you will start to see a delay in processing and entries will appear in SM58.

If you increase the max conn value in SMQS for the destination it means that more entries will be processed. The value for Max Conn you use depends on how many dialog work processes you have in your system. I would suggest you increase it by a small amount first and see if this works well and does not affect anything else. If there is still a delay then increase it again and so on.

Another option would be to remove the rfc destination from SMQS altogether so that all workflow transactions are executed right away. However, if you registered the destination in SMQS in the first place you most likely did so to control workflow traffic. However you could use the evenet queue to stagger the events being delivered instead of SMWS. Note 888279 details the option about registering in SMQS as well as other options.

If your destination is not registered in SMQS then it may be an RFC or resource issue. See note

Regards,

Eddie