Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Keith, along with communication is management and cooperation. That being said, there appears to be a misunderstanding of the Change Management System. Objects can only be changed in one request at a time. There may be many tasks in a request and each task may be owned by a different user. Your original message implied that transports were being imported in an uncontrolled manner - management and cooperation would prevent this. The duplication of the changes in client 300 and then 100 is foolish and potentially problematic. You should fully test what is in the transport that is being released. You can do this by creating the transport in 100 and then testing it in 300 by using transaction SCC1 to "move" it to 300, test there, and then release it in 100 for other systems. You can use SCC1 while the transport is unreleased, go back and fix it, if necessary, and when complete release it. Why do double the work?
| | | ---------------Original Message---------------
From: Mark Toney
Sent: Thursday, October 06, 2011 9:46 AM
Subject: Security Transports Moving Prematurely
C-O-M-M-U-N-I-C-A-T-I-O-N!!! There is no substitute for it in a multiple admin environment. If you have a Change Control process in place, consider amending it to include peer review, i.e. if there are four SAPSec admins then all four have to sign off on a change before it can go beyond DEV300. In that way everyone will know what's going on and as an additional plus you will all know what the other is doing so if there's any duplication of effort it can be identified and eliminated.
Mark A Toney
SAP Security Analyst |
| __.____._ Copyright © 2011 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| |  Al Fournier
SAP Basis Helper
Posted helpful replies on 5 threads in a group to earn a Bronze Achievement Popular White Papers
In the Spotlight   _.____.__ |
