Workflow cannot be activated after upgrade to ECC 6.3

[Former Member]

We have an existing Workflow that has not been modified since a year. Now our system has been upgraded to ECC 6.03 and the Workflow gives an ERROR.

When performing a check we receive a number of warnings with the description u2018'The node violates the block structure required' (WD344) and 1 ERROR u2018Subsequent node not foundu2019. (WD432). Block correction is not possible.

u2022 I checked the SWU3 and there everything is ok.

u2022 Also performed the SWU_OBUF.

u2022 By using tx PFTC (tip from another SDN message) I regenerated the agent assignment by clicking on Additonal Task -

---

> Agent Assignment---> Maintain and clicking on the red and white Icon for UPDATE INDEX (SHIFT+F1)

u2022 I used SWDD to generate a new version in the hope this should resolve the problem but the result is still the same.

u2022 I have taken a look to oss note 1068627 but still did not find a solution.

Kind regards,

Kris Verschueren.

[former_member185167 · Accepted solution]

Hello,

Did you try copying the workflow? If that doesn't work, try reconstructing it by hand, if it isn't too complicated.

Or you could copy and remove bits until it works to narrow down where the problem is and then just reconstruct that part by hand.

Also, does the error message indicate which node it's having a problem with? If so, you could try copying and removing & reconstructing that part (a node is a part of a workflow, which includes steps but a lot more other things as well).

regards

Rick Bakker

Hanabi Technology

[Former Member · Accepted solution]

Hi Rick,

I tried already to copy the Workflow but the problem is still the same. The message "Subsequent node not found" refers to a non-existing node!? Even in previous versions I don't find it.

Reconstruction might be an option. However this Workflow has been made a while ago (not by me) and it is one huge Workflow (so w/o subworkflows). So, reconstructing will take a lot of time.

Thx anyway.

Regards,

Kris.

[bpawanchand]

HI,

I feel like this could be the problem of getting updated the standard table of Workflow nodes. In SAP system there is a standard table in which alll the successor and predecessor nodes are saved for each node with respect to a specific workflow. The problem could be this table. I think you can try to regenerate the Index of the workflow temaplte ..

Regards

Pavan

[Former Member]

Hi Pavan,

do you mean the index of SWDSSTEPS?

Kris.

[Former Member]

Hi guys,

I can tell you that my issue has been resolved now. A new note has been recently created for this problem: "SAP Note 1478128 - Workflow Builder: Error WD 432 regarding subsequent node".

Regards,

Kris.

[narin_nandivada3]

Hi,

Try exporting the correct one to XML Format and Import that XML format into you upgraded system.

Please find below for the steps:

1. Export --> "Workflow->Import/Export->Export to XML File

2. Import --> "Workflow->Import/Export->Import from XML File

Note: First Try it with a different copy. save as your upgraded workflow and test it.

Hope this helps!

Regards,

Narin.

[Former Member]

Hi Narin,

thx for your help. I tried with import/export but unfortunatly SAP looses some bindings and outcomes. No problem if there are just a few but there are many... And because this is a huge Workflow (w/o subworkflows) it still will take a lot of time to resolve this.

Kris.

[keohanster]

In the workflow builder, you should go to Extras> Special Functions > Block Correction and execute this, save and regenerate your workflow. This is a common issue when upgrading from 4.6 - ECC. Fortunately for most, the Block Correction feature works just fine.

Sue

[Former Member]

Hi Sue,

thx for your advise but we only upgraded from ECC 6.0 to ECC 6.3 (enhancement package 3). The block correction I tried already but the problem remains.

Kris.