Workflow multiple versions in production

[Former Member]

Hi Experts,

when i transport my work flow from development to production

multiple versions are getting created.

e.g

in development i have version 0001

and production also have version 001

i did some changes in development in version 0001

now i transported it to production

then in production new version is getting created. version 0002

I did check the SAP help which says

If a workflow definition is transported into another system, 
only the active version is transported.
If the workflow definition exists in the target system with the same
 version number,  it is overwritten by the transported version if it has
 no workflows running. Otherwise, the transported workflow definition
is saved with a free version number. The transported workflow 
definition becomes the active workflow definition in the target system

but i checked the production server and work flow is not running. still multiple versions are getting created.

any clue experts

Regards,

Umesh Chaudhari.

[surjith_kumar · Accepted solution]

Hi,

When ever you Move a Transport Request from Dev to PRD, a new version of Workflow will be created. Mostly the Latest Version will be active to see the Which Version of the workflow is currently active.

Do the Following Steps,

1) Goto Basic DATA

2) Select “Version- INdependent (Task)” tab

3) In that Goto Tab “ Version Overview”

4) Below the Tab in Colum “Activ” , a Radio Button will be there

5) The Radio Button is always pointing to the “Active” Version

Regards,

Surjith Kumar P

[Former Member · Accepted solution]

Hi surjith kumar,

Well here the question is not where to find the version But why it existes.

we very well know where to find the version.

Regards

Umesh Chaudhari.

[martin_nooteboom · Accepted solution]

Hi Umesh,

SAP creates versions to keep track of the changes in the definition and what definition to use for a running workflow. As you might know changes to workflow will only have an effect in a newly started workflow and not in already started workflow. For this SAP uses the versions so it knows which definition should be used.

Regards,

Martin

[Former Member]

Hi Umesh,

Not just running but with any instance created from said version will casue this effect. It should not cause any issues at runtime.

Regards

Gareth

[Former Member]

Hi Gareth Ellem,

thanks for your immediate reply......

please clarify me on following if my workflow is complete still then it will create a new version in production server.

say i transported my workflow to production and tested it there the cycle ran correctly now i found a bug in the process and i modified the workflow in development and transported it to quality and production still version will get created?

the workflow is not giving me any problem from process point of view. but is it correct from Quality(development standards) point of view to have multiple versions in production?

is there any way to avoid multiple versions?

Regards,

Umesh Chaudhari.

[Former Member]

Hi Umesh,

Yes in your scenario you would get a new version created as an instance has already been started using the older version. This state of affairs used to worry me from a QA perspective as well, but I have seen it now in many sites - both ones where I have built the workflows and ones where I have not - and I can state pretty conclusively that from an operational perspective it is not an issue.

You could generate a new version in your DEV system whenever you transport, but I would not advise this as in this case it is possible to get your versions out of synch and actually deprecate your changes. This is not only poor but proved very difficult to analyse (for my small brain anyway) at the site where this was attempted.

In this case I am firmly of the opinion that I will let the transport system manage the versions in my production system.

Kind Regards

Gareth