cancel
Showing results for 
Search instead for 
Did you mean: 

Leave request approval work is stuck at if Multi Level Approval required background step

naimkhans_babi
Active Participant
0 Kudos

Dear Friends,

     My workflow ( WS90000007 ) is stuck at the backgroun step "Multi Level Approval required". this happends when user tries to apply for EL ( earned leave ) or CL ( casual leave ) where as SL ( Sick leave process perfectly ).

I tried to debug the method (CHECK_MULTI_LEVEL_APPROVER_REQ ) but it is not going in debugging mode. 

Multi-level approver is required only when leaves are 7 or more than 7 days rest all the cases it is single step workflow ( initiator --> approver ).

I have attached the documents with this message please help me to make this thing running.  or atleast guide how to debug it as method is not letting me in.

further more we have implemented BADI PT_ABS_REQ

for  Additional checks while applying leave from ESS to ensure that organizational rules are followed when applying leave and All messages were refreshed due to the use of FM we save all the messages before calling this FM and add them back after the call.

if I put a break-point here it goes in the debugging.  but not going for above multi level approver method.

please help me to understad the cause of why CL and EL are not processing with this workflow nicely.

We are applying leaves from EP - ESS and approval is done in EP as well.

your any help will be appreciated greatly.

Thanking you

Regards

Naim

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Where is this method CHECK_MULTI_LEVEL_APPROVER_REQ. Is it in a custom class? Perhaps you can execute it directly from SE24 (if you know the correct parameters - see them from the workflow log) and then debug it there.

If because of some reason you cannot debug the method in SE24 (why?), then go with Rick's suggestions. Here is a nice step by step tutorial how to debug a background step (Of course it needs to be a custom method, so you can add there your own code):

http://scn.sap.com/community/bpm/business-workflow/blog/2015/01/12/workflow-debugging-trick

Kind regards,

Karri

former_member185167
Active Contributor
0 Kudos

Hello,

Check in ST22 if this method caused a shortdump - this is usually the case.

If the method is run in the background then it will be run by WF-BATCH which makes debugging problematic. You could temporarily set WF-BATCH to a Dialog user (if this is a Test system) or you could use the infinite loop trick. But check ST22 first.

regards

Rick Bakker