Workflow activation error

[Former Member]

Hi guys,

There is an existing workflow, I made some changes to it in the very top part.

while activating the workflow:

I am getting the 98 warning and 4 errors.

warnings: 'The node violates the block structure required'.

error: 'End node for block xxxxxxxxxx not found;block correction not possible'.

'Node xxxxxxxxxxx not found'.

these errors are not part of my modifications. Can anyone please help me.

Also is it possible to somehow activate a workflow.

I check the version in production. It is active but when compiled it is showing these errors. how is this possible??

Please help

thanks

SAPLOGS.

[Former Member]

Hi, Thanks for all your inputs. We raised a message to SAP who have fixed it for us.

The consultant who solved the issue said he had no idea why the errors cameup. I was on vaccation and by the time I came back, they were fixed so I have no idea at the momnet, how it was fixed but PROBLEM SOLVED.

[Former Member]

Hi,

we've done an upgrade from ECC 6.0 to ECC 6.3.

Now, we have a Workflow that cannot be activated for the same reasons I read here. Could anyone tell me what the oss note because I want to fix it asap.

thx.

Kris.

[Former Member]

Hello,

It would be best if you opened a new tread with the details of your system - were workflows changed, is it happening to all workflows etc. It's a very generic error so it could be a different solution. I would search OSS if you haven't already. As usual, check SWU3, do SWU_OBUF and try to reactivate.

Saplogs, it would good if you could find out what SAP did to solve your problem and post it on this thread.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi,

Sorry for the delay.

Unfortunately Kris, I cannot offer you any help as it was fixed by SAP themselves through remote login. I did refer OSS notes but existing notes dint help my case.

Search OSS as Rick has suggested else raise a product error to SAP.

Sure Rick,

Will try to get hold of the solution and post in another thread.

One more thing, Once we transported our workflow to Quality & later Production, I had to do two things to make the workflow work.

First, For all new relevant workflow steps, make sure Agnet Assignment is active.

Open the workflow in SWDD, click on the activity, then in the CONTROL TAB, in TASK PROPERTIES SECTION, make sure that Agent Assignment is Active.

Second, Do a refresh using SWU_OBUF.

Regards

-saplogs.

Edited by: saplogs on Jul 16, 2010 6:24 PM

[Former Member]

Okay,

thx for your reaction guys. I've taken a look again to this issue taking account of your tips.

However, it still does not work. I'll create an OSS-message and a new message on SDN. So, I hope this will be resolved soon.

KR

Kris.

[Former Member]

Hi all,

Thanks for the replies.

I am new to workflow so still growing up.

I tried refreshing the org. environment by using txn SWU_OBUF and navigating to SBWP ---> Settings -> workflow settings-> refresh org. environement.

This did not help.

In DEV, When I go to workflow header section, there is no version with radio-button in active.

I am making changes to an existing custom workflow and the last changes are almost 2 years ago.

MY CHANGES: when workflow is manually triggered from changes mode (CV02N), since the document is locked by you, the subsequent steps in the workflow fail so the requirement is, once a workflow is started, check the lock status of the document, if locked, throw a popup on the screen and terminate the workflow.

I did this by creating a method and calling a FM in there. If document is locked, call the popup..... FM and raise exceptions so that the workflow task has various outcomes. Next i am using process control in the outcomes to cancel the workflow.

before I mixed my changes with the existing one, i did them in IDES and that was fine.

I used the FM SWD_WFD_REPLICATE_FROM_9999. It generates a new version which does not have my changes. status is Active,saved but when complied, the same 99 warnings and same 4 errors are coming which are as follows:

warning: This node violates the block structure required (99)

- End node for block xxxxxxxxxxxx not found; block correction not possible. (3)

- Node 00000000979 not found.

The same errors are also present in Active version in QA and PRD.

How did the workflow get active in PRD and now have these errors. did basis guys miss any patch.

Also when does this error occur "End node for block xxxxxxxxxxxx not found; block correction not possible."

Please help.

Thanks for reading.

[Former Member]

Hi,

I recommend you to delete all nodes and steps that generates the error and create it again (if this is a z workflow).

Regards,

[Former Member]

When was this workflow last transported to QA and PRD?

[Former Member]

Hi,

I am making changes to an existing custom workflow and the last changes are almost 2 years ago.

The tech spec. document I have only documents the current business requirement and this workflow has not been developed by me so deleting and recreating will mean I will have to understand the whole flow of the workflow and it will take time and I will need the original business requirements.

When does this error occur. "End node for block 000000281 not found; block correction not possible".

Thanks

saplogs

[Former Member]

Hello,

Did you generate a new version or make a backup before you made changes?

Try making a copy of the workflow and deleting a few steps, try to find out which step is causing the error.

Eg, make copy 1, delete the first half of the workflow (in the copy!), see if error persists.

regards

Rick Bakker

Hanabi Technology

[bpawanchand]

I will have to understand the whole flow of the workflow and it will take time

In that case what you can do is that, I think there is block step in the workflow template, So make sure that you generate a new version ot the workflow template and then in the new version try to delete the current block step and try to insert the new block step.

But make sure that what ever that inside the block step, you place them outside of the block and then try to delete the block step and make sure you makea note of all the condidiots that are invived with the block end condition...

This is the simple solution to over the issue, once the changes are done try to refres the buffer and or. environment...

[Former Member]

Thanks for all inputs. At the moment the basis team is looking into the issue as it has been found to be pre existing condition across the whole landscape. Will post an update once I have it.

- saplogs

[Former Member]

Hi, I checked all the above solutions suggested but unfortunately nothing helps.

The task numbers are fine.

Extras>special functions>block correction gives the error message:

Block structure of workflow " cannot be repaired.

When does the error message I previosu posted occur.

Also I checked the PRD today, the version is active but when syntax checked, the same errors are coming. is there anyway to somehow activate a workflow.

Please help.

Thanks

-saplogs

[bpawanchand]

Did you try to refresh teh buffer and refresh teh org. environment by using txn SWU_OBUF and navigating to SBWP ---> Settings -> workflow settings-> refresh org. environement

[Former Member]

Hi,

In tcode PFTC, select menu GoTo > Workflow Builder > Choose Version; choose the previous version, the one that not contain your changes.

Then select menu Workflow > Generate Version. Activate and check the result. If there's no problem, create again your activities.

Regards,

[Former Member]

Hi,

What is the addition which you have done in the top part of the workflow ? If you have added a process control/loop , it gives a pop up before you add it in the block, sometimes this causes the block error.

Revert back to the earlier version and make sure you choose the right option once again and the error will be rectified.

Hope this helps.

Regards,

Saujanya

[bpawanchand]

The reaons could be that the standard nodes table might be inconsistent so inorder to make is consistent.

1. Open PFTC TXn and select the task type as Workflow template and open in display mode.

2. On menu click Additonal Task -

---

> Agent Assignment---> Maintian ---> and try to regenrate the by click on red and white Icon for UPDATE INDEX (SHIFT+F1) wich is located on the application tool bar ..

This will refresh the standard nodes table and this actrivity will make the table consistent...

[Former Member]

check if you are using any block in the workflow and inserted and step inside that.

[Former Member]

Hello,

Try

Extras->Special Functions->Block Correction

regards

Rick Bakker

Hanabi Technology

[Former Member]

Please clck on the error message and try to remove that. Warning message is not important and can be neglected.

Thanks

Arghadip

[Former Member]

Hi,

Check if the prefix numbers of workflow tasks belong to the range defined in tcode SWU3.

Regards,