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 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