SWEQADM - upgrade related

[Trant, David]

This topic came up at the Fall ASUG BITI Forum.  SAP has gone back and fort=
h through recent versions on whether activation should require or transport=
 or not.  A poll of the group in attendance at the forum indicated that cus=
tomers wanted it both ways!  They'd like to be able to include activation i=
nformation in a transport so they don't have to go into the target system a=
nd manually activate objects and linkages, but they'd also like to have the=
 ability to activate directly in a target environment rather than be forced=
 to create a transport.  Alan Rickayzen from SAP took the request under adv=
isement.  There are system settings to allow transports to be created in ta=
rget environments, but Basis usually discourages this for obvious reasons. =
 We actually do allow this for select users in our productive environment a=
nd review the transports from time to time to ensure it's not getting out o=
f hand.
 
David
 
 -----Original Message-----
From:   SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]  On Behalf Of Koe=
nraad Janssens
Sent:   Monday, March 08, 2004 8:56 AM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        SWEQADM - upgrade related
 
Hello All
 
We're busy testing our new 4.7 system here and we have an event linkage
problem.  In our 4.6B system we could just change the status of an event
light in the events with error tab without a problem.  Now in 4.7 we get a
transport request in our dev. system and we can't change it in our
acceptance system.
 
Is this possibly a system setting?
 
Kind regards
 
Koenraad Janssens
SIDMAR N.V. - ISM
Leverage Team - Programmer
 
***************************************************************************=
********
This message should only be read by those persons to whom it is
addressed, and may contain confidential information, the disclosure
of which is prohibited. This message is not intended to create rights
or obligations without subsequent written confirmation of its contents.
If you have received this message in error, please notify us immediately
***************************************************************************=
********
 
---------------------------------------------------------------------------=
---------------------
This message is for the designated recipient only and may
contain privileged, proprietary, or otherwise private information. =20
If you have received it in error, please notify the sender
immediately and delete the original.  Any unauthorized use of
this email is prohibited.
---------------------------------------------------------------------------=
---------------------
[mf2]