Skip to Content
0

Workflow transport and prefix problem

Apr 16 at 09:20 AM

42

avatar image

Hello workflow experts,

I wanted to import a workflow template and several tasks in to the test system without knowing that the framework was not customized. The objects couldn't be created the in import and the customizing also had errors.

I've started the automatic customizing and it worked except I did't activate the prefix. After several attempts I've finally managed to activate the prefix direct in the test system .... but unfortunately the import still does not work. The workbench transport request is imported without any errors but the tasks in the workflow template are still missing ?!

Does anyone have any ideas why this is happening?

Thankx

Johann.

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

6 Answers

Rob Dielemans Apr 25 at 06:25 AM
1

Hi,

So the import shows workflow template (WS) succesfully imported? And can you open them in pftc in the test system?

There is an off chance that this is related to missing HR authorizations, but first you need to verify that the workflow exists in the test system, check table HRS1000 if the template is visible there.

If you can open them in pftc then do a check in the builder to understand what items are missing and import them accordingly.

Kind regards, Rob Dielemans

Share
10 |10000 characters needed characters left characters exceeded
Florin Wach Apr 24 at 10:16 AM
1

Hello Johann,

the missing prefix is not the problem at all: The target system doesn't need to have it configured at all, unless you'd like to create NEW tasks within that system. Also the prefixes can be used to have distinct number ranges across various development systems for larger companies / implementation scenarios.

However, if you transport a Workflow Pattern WS.... you'll also need to transport all non-standard taskt types/activities TS...., which are referenced by the workflow pattern. And mayhaps you also need to include extensions on BOR objects types (including the system-wide delegation) or any other references that you may need.

This is, why the workflow wasn't activated in the target system; ... and therfore the SWU3 is complaining about a missing definition, because there's no /active/ one.

So one by one you need to walk through all the errors in the Workflow definition first, until you've got an error-free active version. From there on you can start the customizing for general tasks or whatever is needed.

Best wishes

Florin

Share
10 |10000 characters needed characters left characters exceeded
Rob Dielemans Apr 16 at 09:53 AM
0

Hi,

Prefix should only be maintained in the development system.

What does the transport log say when you try to import it? If it is from an entirely different system, you might have to download the transport and import it through client-copy.

Kind regards, Rob Dielemans

Share
10 |10000 characters needed characters left characters exceeded
Johann Konstantin Apr 16 at 10:03 AM
0

Hi Rob,

the workbench transport has no errors. The customizing transport has warnings: object x,y,z does not exist.(TS tasks) so the customizing for the agent assignment cannot be saved.

If I try to open the missing tasks with PFTC I get the message "... does not exist".

I have changed the workflow template (which got imported) and all of the tasks, so that they would be registered in a transport request and that I could import them. I tried this 3-4 times without succes.

Regards

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

Hi,

Not only all tasks, also all methods (bor or class) and all data dictionary references in container elements.

Kind regards, Rob Dielemans

1
Johann Konstantin Apr 16 at 11:38 AM
0

Also, I can't start the verification workflow(transaction SWU3) in the test system. I'm getting the following error message: Workflow: No workflow definition found.

Share
10 |10000 characters needed characters left characters exceeded
Johann Konstantin Jul 11 at 08:52 AM
0

I found a part of the problem eventually. The transport user was missing HR (SU53 - in the bottom) authorisation/rights. I've opened a OSS.

Share
10 |10000 characters needed characters left characters exceeded