cancel
Showing results for 
Search instead for 
Did you mean: 

LEA not consistent with workflow

Former Member
0 Kudos

Hi group

Sometimes our system hangs, and this leads to a problem in leave request being incositent between rptarq and workflow.

What happens is:

1. Approver approves the request

2. WF dialog step is completed, and the WF goes to next step which is "Waiting for status change".

3. This status change never happens, and the request remains with status SENT

4. Next time the approver tries to approve, he gets "Specify a class name" since the WF step is already completed.

We run RSWWCOND on a regular basis, and this only happens on occasions when we have system trouble.

The only way we have found to solve this is to cancel the WF, delete the request and ask user to apply again.

This is not good in a situation where we support 60.000 users.

Is there any way to force the leave request to change status from SENT to APPROVED (which is the case here).

Please see attached document for details.

I appreciate your response.

Kirsten

Accepted Solutions (0)

Answers (2)

Answers (2)

0 Kudos

Hi kirsten.blling2,

How to cancel workflow ? I have the same issue , can someone please answer how to cancel the workflow ?

Thank you

Former Member
0 Kudos

A little correction of my initial post:

The WF step is assuming that leave request is in status APPROVED and is waiting for the RPTARQPOST.  The error is that the request is not changed from SENT to APPROVED after dialog step is set to completed in WF.

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

can you ensure if there is an error occurred after approver approved leave request in the WF log? typically payroll lock or something like that You can see see where its hanging with technical details in SWIA or do a wf trace.

try approving again via rptarqqapp or check the status in rptarqdbview

Former Member
0 Kudos

Hi Siddharth,

From what I can see the WF-log shows no sign of errors after the approval step. The WF is in fact not hanging - it is waiting for the status change of the request from APPROVED to POSTED (shown in attachment). But since the request status hasn't been changed from SENT to APPROVED, the posting doesn't pick up the request (naturally). 

The approval times of the inconsistent requests coincide with system problems which made it necessary to restart system. Payroll is not part of the problem.

We believe (without digging into the code) that SAP first completes the WF step and then changes the status of the request. Due to system problems, only half the job is done and we have an inconsistency.

When trying to approve, we get the error "specify a class name" due to the fact that the dialog step in WF is already completed (the error message is a WF message).

My problem is: How can we solve the situation without deleting the leave request?

I was looking for any way of changing the status of the request since we see from WF that it has been approved, but there seems to be no such way.

My last resort is to cancel the WF (to clean up) and delete the request. Last time this happened, this is how we solved it. But I do not like to do that.

Lat time this happened, I  asked SAP if they could code in a manner that avoided this inconsistency (a sort of "begin/end transaction"). But they said this was not possible as there are 2 different parts of system involved here (LEA + WF).

Do you see any other way to resolve the requests?

Regards

Kirsten

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

earlier we use to indicate to use SWU3, we had this similar error earlier, where we asked to remove a step from WF and it was for your company, I ll check the note and see the WF again

Former Member
0 Kudos

I remember that :-), and I followed the note and removed the step.

I still think this current issue is due to the fact that when system "breaks" after completion of the dialog step, there is no way to set correct status on the request itself. It would be interesting to know if the sequence of the code is to first complete dialog step and then set status on request?

We would love to find a way to avoid these errors - I think I will raise a ticket with SAP once more.

But am I right that for the already inconsistent requests, there is no way to fix this - and therefore I have to delete the requests?

/Kirsten

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

no you don't have to delete them, you can kickstart the WF or complete it directly via SWIA> Please can you verify.

Former Member
0 Kudos

We tried that, and get an error message that we cannot start WF with type "F".

We tried pretty much everything. I think as long as there is an inconsistency between the WF and the LEA, I do not really have a choice 😞

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

can you give me the exact error? thanks and also raise a ticket our team will check further

Former Member
0 Kudos

Hi Siddharth

See attachment. We tried both replace and restart.

Former Member
0 Kudos

What I meant, was I tried both from within WF (change) and from swia. Completing it will make no difference on the leave request itself - it never leaves status SENT.

Thanks for your time on this, Siddharth.

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

Change the status (SWWWIHEAD-WI_STAT) back to READY    followed by CALL FUNCTION 'SWW_WI_EXECUTE_INTERNAL_RFC'.    change  currently  the value status (SWWWIHEAD-WI_STAT) back to READY using tcode se16 straight to the table. The workflow successful executed. there is no impact to the other tables. please try this option 2.) or Start a new instance of WS12300111 via SWUS entering the    old container data            AAGENT:                          CL_PT_REQ_WF_ATTRIBS:

Former Member
0 Kudos

Hmm - it sounds risky to change a status in SE16N when error message clearly states the WF cannot be set to ready. I don't like tampering with data in tables directly.

Do I understand you suggestion correctly to be these 2 steps:?

1. Change status in Swwwihead from completed to ready for the dialog step

2. Go to SE37 and execute SWWW_WI_EXECUTE_INTERNAL_RFC

Anyway - I had to deal with the 2 requests I got in so far, so for those 2 I chose to delete. I may look into your suggestion when more comes in to us in 3rd line support.

I will also raise a ticket, as this seems to be a scenario SAP doesn't handle, and we have had it 3 times so far.

Regards Kirsten

siddharthrajora
Product and Topic Expert
Product and Topic Expert
0 Kudos

yes, please raise an OSS for changing status just do this change  currently  the value status (SWWWIHEAD-WI_STAT) back to READY using tcode se16 straight to the table. can you advise your SP Support level?