cancel
Showing results for 
Search instead for 
Did you mean: 

wy there is sometimes no entry in sap Table SWWWIHEAD

tkuebler1
Explorer
0 Kudos

Hello,

i created a workflow event with FB: SAP_WAPI_CREATE_EVENT

And after that, i have to check if the Workitem was created.

I Tryed severel ways to do that.

My last one was by simply make a select in table SWWWIHEAD to search my Workitem.

But sometimes the workitem simply is not there at the time i do the check...I also tryed the FB: SAP_WAPI_WORKITEMS_TO_OBJECT

same effect ...sometimes the workitem simply is not there when i do the checks. later it is there!!!

so i tryed to make a time delay from 1 to 4 seceonds...but not effect.

I am on Relase

SAP_BASIS 702 0017 SAPKB70217 SAP Basiskomponente

I would be ready happy if i get any help here !

Kind regards

Tobi

Accepted Solutions (0)

Answers (4)

Answers (4)

tkuebler1
Explorer
0 Kudos

Thanks Rob,

but our wf customize is ok and we dont have millions of workfow entrys..

sm21 is ok..

so lets see what sap is saying

tkuebler1
Explorer
0 Kudos

Hi Rob,

Commit_work is flagged...and the problem is also in Productive system ...

i think i have to open a sap ticket..--

former_member186746
Active Contributor
0 Kudos

Hi Tobias,

Before you do that first check if your system is correctly set up for workflows, SWU3.

If, for instance, someone manually tried to create the WF-BATCH user and its local RFC then this might be the reason why it is not working as intended. Also check if the reason why it is slow is because there is no archiving and there are millions of workflow entries, also check SM21 for weird basis related issues.

Kind regards, Rob Dielemans

tkuebler1
Explorer
0 Kudos

Hi,

thanks for the answer

the event queue was off. i only had the trace on.

former_member186746
Active Contributor
0 Kudos

Hi,

There is an option in SAP_WAPI_CREATE_EVENT to immediately deliver the event by giving COMMIT_WORK = 'X'

Oh and also check if the problem you are having will exist on production or not. I remember having to build lots of execution time dependant controls in a workflow only to figure out that this was a development system only problem.

Kind regards, Rob Dielemans

former_member186746
Active Contributor
0 Kudos

Hi,

This is caused by the event queue. In my opinion this is rarely needed anymore.

Most systems can handle thousands of events in a short period of time.

If I were you I would check if at the company mass changes occur and if those changes trigger tens of thousands of events in seconds. Then you might need the event queue, otherwise just deactivate it. Transaction SWEQADM

Kind regards, Rob Dielemans