|
Your SAP Resource » Publications » SAP Experts » Solution Manager Expert Online |
|
|
SAP Solution Manager
|
Part of the
|
|
|
|
|
|
|
|
Knowledgebase » Volume 3 (2010) » Update 6 Take Control of Your SAP System Development with Change Request Management
|
|
Increase the security of your satellite systems by performing a few simple configuration changes. With these changes, you can prevent developers and testers from creating, managing, and releasing transport requests directly in satellite systems, which will ensure that only the person responsible for these actions (usually the change manager) can execute them. |
Categories: Administration, Change Request Management, IT, Solution Manager
| Key Concept |
| Change Request Management (ChaRM) manages the entire change process in your SAP systems. It is the central point of access for all SAP non-productive systems in an organization, which include the development and test systems. ChaRM is not used to access the productive systems, as it only transports tested changes into these systems. |
Transport requests store every change performed in a SAP system, and you can think of them as change packages. These packages are transferred among the systems in an SAP landscape for testing or to become active and used. The number of transport requests in your environment can grow exponentially, especially when your project reaches the test phase. In that particular phase, key users identify defects or enhancements that need to be performed while developers perform changes — all this, in turn, creates more and more transport requests.
A lack of control over transport requests is one of the greatest concerns facing project managers that lead large development teams. Development teams are usually comprised of programmers (who create and change programs), functional resources (who perform configuration changes), testers, and key users. Before SAP Solution Manager, teams worked with several techniques because the SAP native transport system (the Transport Management System [TMS]) does not offer advanced tools to perform this task. Most teams worked with spreadsheets that needed to be filled out by each team leader and had to include the number of each transport request, the transport sequence, and the dependencies between them. Considering normal projects have several teams, you can see how complicated this can become when you factor in consolidating all the spreadsheets and managing the cross-dependencies. Problems that result from incorrect transports are the most common reason for long rework nights.
Would you like to see the full version of this article?If you are an electronic license holder to Solution Manager Expert, please click here to log in. If you would like information about becoming an electronic license holder — and having 24/7 unrestricted access to all articles and content in the Solution Manager Expert online knowledgebase — click here to see the available subscription options. Or call 1-781-751-8799 to speak directly with a subscription and licensing specialist about customized access for you and your team. Isn't your SAP implementation worth world-class information support? |
|
Copyright © 2010 Wellesley Information Services. All rights reserved. Email: customer.service@solutionmanagerexpert.com.
|
