Transport Order for Workflow

[Ronen Fox]

Diane,
 
One extra remark to the very clear message Tomasz wrote:
 
Sometime after transporting workflow templates, when you go into the
workflow builder in the target system and display the new transported
workflow you get a 'blank' workflow definition (in the builder screen) or a
previous version is displayed. This is very frustrating and always makes me
miss a heartbeat.
But the solution is very simple: make sure you run transaction SWUD and test
the environment for your new workflow in the target system, and if
afterwards you still get the a strange definition in the workflow builder
just simply go out of the builder and go back in again. I know it sounds
silly but it always works.
Good luck !
Best regards,
Ronen Fox
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]
Sent: Tuesday, November 12, 2002 6:05 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Transport Order for Workflow
 
 
Thanks Tomasz, that was going to be my approach.  I was just looking for
confirmation and assurance, being my first time and all I want everything to
be as smooth as possible.  Will let you know my success!!  Thanks again for
the information.
 
Diane H. Nobles
SAP Proj. Analyst, PM, WF
(757) 380-7250
 
 
-----Original Message-----
From: Zmudzin,Tomasz,VEVEY,GL-DS/DM [mailto:Tomasz.Zmudzin at nestle.com]
Sent: Tuesday, November 12, 2002 9:55 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Transport Order for Workflow
 
 
Diane,
 
as with all transports the sequence needs to be observed.
 
More or less -- think of it as if you needed to recreate your development
manually in the test box. The first dependencies that spring into my mind
are:
 
- because workflow templates use workflow tasks, these need to exist in the
box before the templates are imported, or at least need to be in the same
transport request
 
- because workflow tasks use business objects, these need to exist in the
box before the tasks are imported, or at least need to be in the same
transport request
 
- because business objects often use some external ABAP coding (function
modules etc.), these need to exist in the box before objects are imported,
or at least be in the same transport request
 
- because your additional ABAP coding may need some Data Dictionary
definitions (tables etc.), these need to exist in the box before you import
ABAP, or at least be in the same transport request
 
As you've completed the workflow I'm sure you'll identify the elements by
following the same path as above. Because of the "at least be in the same
transport request" addition the rule of thumb could be: the fewer transport
request, the easier it will be to handle.
 
Kind regards,
Tomasz
 
 
-----Original Message-----
From: Nobles, Diane [mailto:nobles_dh at naptheon.com]
Sent: Tuesday,12. November 2002 15:38
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Transport Order for Workflow
 
 
I am soon to transport my first workflow into our Test box.  We are in 4.6c
system and I am concerned about the order of the transports.  Does it matter
what order they go in or is it ok as long as they are all in place before we
trigger anything and test?  If there is a desired order of transports, i.e.,
WF definitions, conditions, etc., or recommended steps to follow for the
transport process, i.e., things to check for, set-up prior to testing, etc.,
please let me know where I can find them.  Thanks in advance!!!
 
Diane H. Nobles
SAP Proj. Analyst, PM, WF
(757) 380-7250
 
"Small things, done with great love, bring joy and peace."