Take Control of Your SAP System Development with Change Request Management

  • by Cristiano Canzone, SAP Solution Manager Consultant, SAP Brazil
  • July 6, 2010
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.
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.

Cristiano Canzone

Cristiano Canzone is an SAP Solution Manager-certified consultant who has worked at SAP Brazil since 2008. In his 12 years of SAP experience, he has also worked at PricewaterhouseCoopers and IBM as an SAP Basis-certified consultant. Cristiano is currently the SAP resource responsible for the SAP Solution Manager initiatives at Petrobras, the largest oil company in Latin America. He lives in Rio de Janeiro, Brazil with his wife, who is also an SAP consultant (specialized in SAP ERP HCM).

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.