cancel
Showing results for 
Search instead for 
Did you mean: 

Problem in standard workflow WS18900023 for Claim and Advance Approval.

Former Member
0 Kudos

I am using standard workflow WS18900023 for Claim and Advance Approval. The workflow works on single level approval. No privileged group is maintained in view V_T77WWW_CLPRVLG. The problem that I am facing is, when approver approves the claim request from portal(UWL), message is displayed 'request approved'. But in workflow log the step history of TS18900010 shows, it was forwarded. And a new approver is added to the agent received list along with the earlier approver.

This is repeated again when the approver approves again, till a max. of 4 values in the agents list.

When the approver tries to approve now, it shows 'No item(s) available for approval'. But the workitem still appears in the UWL list.

Workflow log shows workflow 'In Progress' and step TS18900010 'Ready'.

The workflow is 'Completed' in case approver tries to 'Reject' request, and works fine.

I have tried debugging the request approval from portal, but it does not stop at any debugging point.

No BADI for 'GET_NEXT_APPROVER' has been implemented.

Kindly suggest how to resolve this.

Accepted Solutions (0)

Answers (3)

Answers (3)

former_member16044
Active Participant
0 Kudos

In case the problem is solved, share how is was resolved and close the thread.

Regards,

Rahul Kulkarni

former_member16044
Active Participant
0 Kudos

Hi Neha,

Check for a possible entry in multiline element under miscellaneous data tab of decision task. In case any container is maintained there, remove, in case the process doesn't demand.

Also, check the OSS note: 1313761

Regards,

Rahul Kulkarni

suresh_subramanian2
Active Contributor
0 Kudos

Hello Neha !

    Is your requirement is for one level approval but the workflow triggers for four level approval ?

    Check the AGENTS container in the workflow. Whether any agent details are hard coded ?

    Check whether any other workflow for advanced claims is maintained at V_T77WWW_GADEF view.

    To stop at debugging, log on to employee's ECC logon account. Set the external break point at the ABAP class CL_EXITHANDLER(method : get_instance). As a precautionary measure, set session break point too and submit the claim from the same employee portal.

     If debugger doesn't starts, still follow the steps mentioned in the above paragraph and in addition to it, in the method GET_INSTANCE, from the menu bar, take the path : SETTINGS -> ABAP EDITOR -> DEBUGGING and maintain the same employee ECC log on name in "External debugging" window.

    Now, from portal, from the same employee id, while submitting the claim, debugger should start running in the background.

Regards,

S.Suresh.