workflow's transports? what a disaster!!!!
Vera, Luis
luis.vera at sap.com
Tue Apr 23 08:46:57 EDT 2002
Hi Angelo Besenzoni,
At OSS (or at http://service.sap.com), please review Notes:
0315515 WF Editor/Builder:Versns overwr. w/ incorrct versn 46C-All Patches
0355134 WF Builder: all versions transported 46C-All Patches
0378487 WF Builder: transported version not set to active SAPKB46C16
0424725 WF Builder: Undesired new versions SAPKB46C26
Hope they help...
Regards,
Luis Vera
SAP Global Support
-----Original Message-----
From: Angelo Besenzoni [mailto:"Angelo
Besenzoni/SAP_CONSULTING%SAP_CONSULTING"@jaguar.ibm.it]
Sent: Tuesday, April 23, 2002 9:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: workflow's transports? what a disaster!!!!
Hi workflower....
Workflow's transports? what a disaster!!!!
We are running on 4.6C and the situation is very dangerous.
When we transport a workflow existing already in the target system, we are
never
sure about the result.
Especially when the workflow is running, it is very difficult to store the
latest version on new process (i understand that not completed processes are
linked to old version, but new processes don't catch new version, too).
In other words, the new version is not activated and you can't activate it.
Only if all workitems of the workflow are completed (and nobody is in
error),
the transport is ok...
Any solutions for dark world of workflow's transports???
Thanks for all...
---------------------------------------------------------------------
Angelo Besenzoni
Sap Italia Consulting s.r.l.
e-mail: angelo_besenzoni at sap-consulting.it
tel: +393351357236
---------------------------------------------------------------------
More information about the SAP-WUG
mailing list