Skip to Content
0

Workflows are automatically getting logically deleted ?

Feb 24, 2017 at 09:48 AM

983

avatar image
Former Member

Hello Experts,

Few of my workflows are getting logically deleted automatically. We are unable to identify root cause. In some of the cases, I saw, one work step is giving error as below:

"Object cannot be locked, since locked by User-Id."

After getting this error message 27 times, Work Item is getting automatically logically deleted by another user id.

Please help all the possible causes why any workflow or task is getting deleted logically?

10 |10000 characters needed characters left characters exceeded
Former Member

Hello Experts, Please advise for this issue.

0

Hi

You have a bit of a gap between the last error No Action Date (27.10.2016) and the work item logically deleted (22.01.2017).

By any chance is someone manually logically deleting them via SWIA or scheduling the job in background once item is a certain age?

2
Former Member
Colleen Hebbert

Hello Hebbert,

Thank you so much for your input.

As per above screen shot, logically deletion action has been performed by one user (as showing his name in last agent column). But we are not sure, what action he is performing as he do not have administrative access.

That's why I am searching possible causes of logically delete status.

Thanking in anticipation.

0

Hi Anand

I would recommend looking at that user's buffer to see if they actually do have the permissions to logically delete/cancel the workflow. Another option, can you just ask them what/why they are doing that? It might at least help isolate your investigation as to how they are logically deleting

Regards

Colleen

1
Former Member
Colleen Hebbert

Hello Hebbert,

I took much time to reply you, I am sorry. But we tried to create the issue in DEV, and it seems user is cancelling the process from portal. Now I would like to ask can we re trigger the cancelled workflow ? Is there any way to proceed the logically deleted workflow?

0

Hi Anand

if it is an end users cancelling from the workflow then they are probably choosing the reject button. you will need to look at Workflow Task (SWDD) to see how the event it being handled. It might be that your workflow is configured to call a function module or method to trigger a logical deletion (cancellation) of the event and that it is being executed via WF-Batch on behalf of the user.

I'm not a workflow person (I find with security I end up in workflow troubleshooting space to figure out agent determinations and authorisations issues) but I got the impression that once the workflow is cancelled you can't retrigger the same workflow. You would need to perform the necessary actions to trigger a new workflow for that scenario

When I go back to your original question I'm still unsure you if you actual issue is the 27 errors that occurred first or that a user decided to logically delete. Even if you finally understand why it got cancelled it seems like you still have the original issue to resolve

You won't get much more from the community without providing workflow configuration information. Is it a SAP standard workflow (standard tasks) or custom built one? What are the triggers, tasks, events, etc.

0
Former Member

Any answer experts.

0
* Please Login or Register to Answer, Follow or Comment.

5 Answers

Stéphane Bailleul Mar 01, 2017 at 10:47 AM
1

Hi

Do you have another event that could delete the workflow ? Like if the object is significantly modified ?

Or a condition step that could end the workflow ?

Cause all of this can be done for a good reason ...

Cheers

Stephane

Share
10 |10000 characters needed characters left characters exceeded
Anjan Paul Feb 28, 2017 at 08:55 AM
0

Hi,

There might be many reason. You can find the Graphical workflow log to find out. Please share screenshot of workflow log.

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hi Anjan, Thank you so much for your reply. Please see below screen shots and suggest if you are asking for anything else. I have been stuck in this issue since long. And till date, no solution.

graphical-log.png (23.4 kB)
workflow-log.png (18.2 kB)
0
Suresh Subramanian Mar 03, 2017 at 08:34 AM
0

Hello Anand !

Please check is there any program gets executed which contains function module SAP_WAPI_ADM_WORKFLOW_CANCEL to get the work items logically deleted.

May be in the program from where the message "Object cannot be locked, since locked by User-Id." gets invoked, may have the above function module.

Regards,

S.Suresh.

Share
10 |10000 characters needed characters left characters exceeded
Rob Dielemans Mar 13, 2017 at 01:40 PM
0

Hi,

I should start from the user-id who logically deletes it. Was it done by a scheduled job, or was it done by a manual activity by that user. So find out who it is and ask them what they did.

Kind regards, Rob Dielemans

Show 2 Share
10 |10000 characters needed characters left characters exceeded
Former Member

Hello Rob,

I took much time to reply you, I am sorry. But we tried to create the issue in DEV, and it seems user is cancelling the process from portal. Now I would like to ask can we re trigger the cancelled workflow ? Is there any way to proceed the logically deleted workflow?

0

Hi,

If the workflow was triggered with an event you can create the event with SWUE.

But usually you just check what is the purpose of the workflow and then execute those steps manually outside of the workflow.

Kind regards, Rob Dielemans

0
Bhoomika Sharma Jul 05 at 10:44 AM
0

Hi mentors,

I am also facing the same issue and the workflow is invoked through Batch Job.

Please help me if any solution is there.

Thank you for the consideration!

Bhoomika Sharma

Share
10 |10000 characters needed characters left characters exceeded