Improve Custom Code Life Cycle Decision Making and Governance with the Custom Code Score Card

  • by Veit Eska, Solution Architect, SAP
  • Oliver Kapaun, Expert Support Consultant, SAP
  • February 3, 2012
Companies are creating custom code on a continuous basis. Once built, it remains in their systems and the previous system state is irreversible. Uncontrolled custom code growth leads to high maintenance and operations, as well as upgrade costs, and bears unforeseeable risks. Discover how to control custom developments with Custom Code Lifecycle Management. With the Custom Code Score Card (CCSC), you can make custom developments more transparent among stakeholders. The CCSC enables you to gain valuable information for your decision-making process. This way, you can account for governance and establish effective, efficient custom development.
Key Concept
Custom code assets are constantly increasing. As a result, companies struggle to find out what their major assets are and what kind of maintenance is required. The support organizations on a management level have no comprehensive method to ensure quality on a broad basis throughout the company. Outsourced and development units might have no vested interest in making their work effort and costs transparent. From the perspective of an accountant, most of the costs are overhead costs rather than direct costs that are assignable to individual developments. Maintaining custom code assets, therefore, covers a broad range of organizational functions.
Custom code is necessary for company-specific requirements and innovations required by the business. During an upgrade or Support Package implementation, custom code with a lot of references to SAP coding must be handled and needs to be adjusted. Often, custom code is created by a third party, such as an outsourcing partner. Therefore, associated IT governance is becoming more important. Most companies have created a huge amount of custom code and want to know what’s in their custom code assets. They also want to have costs under control on a global scale. Proper IT governance is a continuous improvement process, and part of this process is the control of IT custom code.

We’ll show you how to gain control by putting together the available custom code into a custom code library, the central part of the Custom Code Lifecycle Management (CCLM) application. This library allows you to plan in an appropriate way and reinforce actions from the responsible parties. We’ll also show you the Custom Code Score Card (CCSC), a concept built off the well-known Balanced Score Card (BSC) that focuses on custom code management. The CCSC aggregates the available master and transaction data contained in CCLM for management reporting. The CCLM application is a new central application available with SAP Solution Manager 7.1 that is ABAP based.

Let’s start by looking at how to use the CCSC concept strategically before moving on to talk about how it works within the CCLM application on the operation level.

Veit Eska

Dr. Veit Eska studied physics at the University of Rostock and the Institute of Atmospheric Physics in Kühlungsborn, where he wrote a doctoral thesis on applied physics. He joined SAP in 1998, where he worked in the technical core competence team on the development of service tools for creating services such as SAP EarlyWatch alert. With regard to SAP Solution Manager 7.1, he is the product owner, architect, and developer of the custom code life cycle management (CCLM) platform.

See more by this author

Oliver Kapaun

Oliver Kapaun graduated in economics and computer science at the University of Technology Darmstadt and has worked at SAP AG since 2002. Oliver is developing on-site services for MaxAttention customers. His areas of expertise include Java and ABAP technology, applications such as ESS, MSS, and MDM, and several other focus areas in the context of SAP technology.

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.