Skip to Content
0

Replace obsolete task in an existing workflow

May 03, 2017 at 12:34 AM

104

avatar image
Former Member

Hello,

We are currently doing an upgrade and we have a custom workflow copied from a standard sap workflow. We have a standard task that does not exist anymore in the new SAP version.

We cannot close all the workflows in production so we will have a lot of errors if the user process it.

I checked on the forum but I did not find a solution.

Could anyone help me?

Thank you in advance

Marie

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

7 Answers

Anjan Paul May 03, 2017 at 06:19 AM
0

Hi,

Then you have to approach SAP for current list of task which replacing old task.

Another way, Create custom Task same like old Task and use it in workflow.

Thanks

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 03, 2017 at 12:53 PM
0

Hello,

Thank you for your answer.

I cannot create a custom task unless you have a trick to create this task with the same SAP number.

Marie

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

Hi,

You're talking about a custom workflow so why not just change that.

I would also check to see if there is a new standard solution provided by SAP and determine if this conforms to business specifications. And if not use the new one as a basis.

Kind regards, Rob Dielemans

0
avatar image
Former Member May 03, 2017 at 04:12 PM
0

Hello,

we copied a standard workflow to a custom one to include few steps. The standard task was used in the previous version. In the current upgrade, SAP do not use this task anymore and SAP decided to delete this task.

We adjust our custom workflow to follow the standard one.

The new workflow is working fine but the workflow opened before the upgrade are in problem. It search for this task and it connot find it so it gives an error 'Missing task'

We are not able to close all the workflow in production before the Go-Live

Marie

Share
10 |10000 characters needed characters left characters exceeded
Mike Pokraka May 04, 2017 at 08:07 AM
0

If it's a standard task then this is the wrong place. Raise a note with OSS, they should help you out.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member May 04, 2017 at 12:08 PM
0

Thank you for your reply.

I was hoping to find another solution but I already opened an OSS message and I am waiting for them...

Share
10 |10000 characters needed characters left characters exceeded
Mike Pokraka May 08, 2017 at 10:26 PM
0

Why can't you complete all existing workflows? With a bit of planning it should be fairly simple: Copy the task, insert into a new version of your WF. Transport. All new workflows should now be using your new task.

Unless your go live is next week, most of your currently open WFs should complete in their own time, and at go live the active workflows will all have the copied task. There may be a handful of exceptions that you would need to deal with by hand, but those should be of a manageable number.

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

Hello,

by far, this would the best solution but there is a lot of open workflows and the business cannot close them. Our go live is in 2 weeks...

Marie

0

Hi,

You should first assess the situation and see how much effort it would take to manually complete the open business processes or to restart them as Mike suggested.

If there are too many workflows and it is business critical then you can change the prio to high.

Kind regards, Rob Dielemans

0

...hence the "with a bit of planning" qualifier :-)

Two weeks is a bit short, but on the average workflow process this could still provide over 50% turnover - i.e. if you have 200 WFs in process at a time then only 100 would still have the issue.

One way of manual is to take a note of the state of the WF (including container contents), cancelling the WF and restarting a new one. With SWIA you then progress that to the point of the old one. Feasible for up to 20-50 WFs, a bit time consuming if you're talking hundreds.

0
avatar image
Former Member May 11, 2017 at 11:08 AM
0

Hello,

we cannot close it manually because there is more than one approbation level with email. Finally, we will export the standard task from production and import it in the new environment.

Marie

Share
10 |10000 characters needed characters left characters exceeded