Workitem stuck in SAP inbox

[Former Member]

Hi all,

This cases happen a few times already.

We are using ECC 6.0.

Workflow: Purchase Order

1. PO created.

2. Workflow started.

3. User approve the PO.

4. In ME23N, PO status is changed to released.

5. Workitem is still in inbox.

I check the workflow log, and the workflow stops at the release step.

User already executed the step, and the PO status has already been changed.

I even checked SWEL, the event RELEASED is being triggered without error. And from here if I view the workitem, it will direct me back to the workflow log that I had seen.

How come the workflow still stops at the release step?

This case doesn't happen everytime, only in a few documents.

Not only for PO, even PR is having this problem.

Anyone got any idea how to solve this issue?

Any SAP notes that I should look into?

Thanks for your help.

[Former Member]

Hi,

some times the WF bachground jobs get stuck, these happen when multiple background tasks executed at same time. since WF-BATCH is a background job user, which performs all the back ground jobs.

check the following,

in SWU3 transaction, 'Maintain Runtime Environment' tab and activate all schedule background job activities. the user having SAP-ALL access can activate these. if they are already active then the problem could be different.

Krishna.

[former_member184495]

Hi JW,

Does your WF has Multiple Release ?

If yes, does your WF Definition have any Loop Step ?

Is your WF triggering twice ?

Reply,

Cheers,

Aditya

[Former Member]

Hi Arghadip Kar

I don't think it has any problem with the release code.

As the PO status are already in release mode.

Only the workflow hang at release step.

Hi Balaji Kalaivani

1. It's not happening for all PO. Just some of it.

2. No fork step. If there is fork step then I can guess what's the problem.

Anyway, I found out 1 thing kind of suspicious. All documents that are released on that day, the workflow hang on the release step.

And i got this message from SWEL:

User WF-BATCH has no RFC authorization for functio

Unfortunately, it didn't shows the whole sentence.

Then, I went to ST22 to check for short dump for that day.

And it happens to have short dump of RFC_NO_AUTHORITY for user wf-batch.

wf-batch is already assign with SAP_ALL and SAP_NEW.

I already asked BASIS to help to investigate if they did any maintenance on that day.

[Former Member]

Hi Jack,

when you do the rfc connection configuration in swu3 it will create a new user wf_batch with all authorization and it is made automatically. So i am sure that it will not be the cause of the problem.

Better try with this,

After the release step create process control step, and terminate the process or complete the workflow.

Regards

Balaji K.

[Former Member]

Hi Balaji,

I run through a number of documents that are released on that day and documents that are released before and after that day.

Only those documents released that day are having this issue.

Those that before and after that day, are running perfectly.

The shortdump RFC_NO_AUTHORITY only happens during that day as well.

BASIS are checking on the issue.

[martin_nooteboom]

Hi Jack,

You could check SWU2 for that day to see the RFC errors. Probably there was a problem with the workflow RFC that day. Check if the workflows can be continued with transaction SWPC.

Regards,

Martin

[Former Member]

Hi Jack,

Thats good, ask your basis team check for that particular date, did any RFC connnection got failed or did any one changed the authorization of wf_batch user or they restarted the system manually on that day or the system got restarted automatically or is there any batch programm run on that day.

Thanks and Regards

Balaji K.

[Former Member]

Hi Jack,

Tell me this things,

1. Is this happening for all the PO document type or some particular document type.

2. Are you using any fork step before the release step.

Regards

Balaji K.

[Former Member]

I think this is quite a weird condition. If the Released event has been triggered anf it has not been picked by the standard task then it is a problem with the system.

I am just guessing are you sure the Release Code is correct now. I mean to say the Release Code that is now associated with PO is same in the wflow instance.

Thanks

Arghadip