Problems with transport of workflows into production

[BATES,Raymond]

Hi Dan,
 
What we have been shown to do here is to open the Production system and
manually activate the workflow.  I have had to manually select the
version before activation because it sometimes doesn't recognise the new
version transported.  This was done by selecting the "Other
workflow/Version" under the "Workflow" menu item in the workflow
builder.  The transporting of workflow seems to have a lot of problems
associated with it.  If anyone else out there knows an easier way of
activating the latest version of the workflow (with 100% assurance that
it has activated the latest version)without having to open up the
production system, I would be pleased to hear of it. (We are running
4.6C)
 
 
Raymond Bates
SAPfihre ABAP Team
Department of Education, Science & Training.
Level 1 - 14 Mort Street.  Canberra.  ACT.  2601.
Phone: (02) 6240 5481  Fax: (02) 6123 5309
E-Mail:  Raymond.Bates at dest.gov.au
 
 
 
 
-----Original Message-----
From: Getliffe, Daniel [mailto:dan.getliffe at sap.com]=20
Sent: Friday, 4 October 2002 12:50
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Problems with transport of workflows into production
 
 
Hi guys,
 
We currently have a mismatch of transports that are supposed to be in 2
different R3 production systems.  Some transports were never sent at all
and some were only sent to one of the systems.
 
e.g.                R3 system 1    R/3 system 2
Transport 1  01.09    yes              no
Transport 2  10.09    no               yes
Transport 3  01.10    yes              no
 
In order to address the problem we decided to find the sequence that all
of the transports were supposed to go in the first place (i.e. date that
they were sent) and re-transport them all to the two production systems.
 
Comparing the two production systems now there still appears to be a
number of descrepencies.  For example table entries in SWEC do not
reflect those in the sending system (and are different in both
production systems).  There is also an issue with versions.  Is it
possible to change the active version in a system with display access
only in the workflow builder?
 
The logical explanation for our problem would be that the transports
have not been transported in the correct order still but I am wondering
if anyone has experience of entries in tables such as SWEC not being
transported accross correctly i.e. if everything else has come across
correctly we would just have to change the active versions and then
re-transport some of the table entries by deleting them again and
sending a new transport.
 
I would appreciate any comments people have as this is quite a pressing
issue.
 
Regards,
 
Dan Getliffe
SAP Workflow Consultant
 
Notice:
The information contained in this e-mail message and any attached files may
be confidential information, and may also be the subject of legal
professional privilege.  If you are not the intended recipient any use,
disclosure or copying of this e-mail is unauthorised.  If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete all copies of this transmission together with any attachments.