Problems with transport of workflows into production

[Getliffe, Daniel]

Hi guys
 
The problem appears to rest with transporting in the wrong sequence again as I have had a copy made of the source system based upon all of the objects in all of the transports and transported it as one transport and it seems to have corrected the problem.  Thanks everyone for their help - it was
getting a bit desparate.  As soon as I've transported I tend to use SWUD and perform a consistency check including sub components which tends to eliminate version problems or go into the workflow via PFTC and generate active version.
 
Thanks,
 
Dan.
 
-----Original Message-----
From: Zmudzin,Tomasz,VEVEY,GL-DS/DM
To: SAP-WUG at MITVMA.MIT.EDU
Sent: 4/10/02 7:00
Subject: Re: Problems with transport of workflows into production
 
Dan,
 
it's so nice to hear from you again -- even thouugh I'm not pleased to
see
which hours you work...
 
As of the transports -- I'd recommend to double-check whether there were
import errors as this could be the case. Possibly also the sequence was
wrong, but it's hard to comment not knowing what was in the transports.
And
face the facts, you have two different systems with two different setups
now, so instead of fiddling with the existing transports I'd rather try
to
put corrective ones through.
 
As of the versions -- be aware of a 4.6C bug: when you enter PFTC after
a
transport has been applied, it complains about "no active version".
Ignore
it, leave the transaction and enter again. Is this it?
 
Cheers -- and all the best,
Tomasz
 
-----Original Message-----
From: Getliffe, Daniel [mailto:dan.getliffe at sap.com]
Sent: Friday,4. October 2002 04: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