Guide Custom Development Management cockpit Document Version 3.00 May 2014 Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP Library document classification: PUBLIC Disclaimer Some components of this product are based on Java. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java Source Code delivered with this product is only to be used by SAPs Support Services and may not be modified or altered in any way. SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com

Typographic Conventions Type Style Represents Example TextWords or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options. Cross-references to other documentation Example textEmphasized words or phrases in body text, titles of graphics and tables EXAMPLE TEXTNames of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE. Example textScreen output. This includes file and directory names and their paths, messages, names of variables and parameters, source code as well as names of installation, upgrade and database tools. Example textExact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries. EXAMPLE TEXTKeys on the keyboard, for example, function keys (such as F2) or the ENTER key. Icons IconMeaning Caution Example Note Recommendation Syntax 1 Getting Started Contents 1 Getting Started .............................................................................. 6 1.1Documentation Types ..................................................................... 7 1.1.1 Generic Cross-Phase Documentation ............................................... 7 1.1.2 Implementation .................................................................................... 7 1.1.3 Production Operation ......................................................................... 8 1.2 Important SAP Notes ....................................................................... 8 List of Related SAP Notes ............................................................... 8 2 CDMC Overview ............................................................................ 9 2.1 Implementation Considerations ..................................................... 9 2.2 Installation ...................................................................................... 10 2.3 User Roles ...................................................................................... 10 2.4 Control Center ................................................................................ 11 2.5 Notes Maintenance ........................................................................ 11 2.6Project-Specific Overview Screen ............................................... 11 2.7 Global Settings ............................................................................... 11 3Clearing analysis ........................................................................ 13 3.1 System Landscape ......................................................................... 13 3.2 Activities and Functions ................................................................ 13 3.2.1 Preparations and Project Settings ................................................... 14 3.2.2Collect Phase .................................................................................... 14 3.2.3Analysis Phase ................................................................................. 15 3.2.4Display Analysis Results ................................................................. 15 3.2.5Work with Analysis Results (Clearing) ........................................... 16 4Upgrade/change impact analysis .............................................. 17 4.1 System Landscape ......................................................................... 17 4.2 Activities and Functions ................................................................ 17 4.2.1 Preparations and Project Settings ................................................... 18 4.2.2 Analysis Phase .................................................................................. 18 4.2.3 Display Analysis Results .................................................................. 19 5 Change and Transport System Analysis ................................... 21 5.1 System Landscape ......................................................................... 21 5.2 Activities and Functions ................................................................ 21 5.2.1 Preparations and Project Settings ................................................... 21 5.2.2 Collect Phase ..................................................................................... 22 5.2.3 Analysis Phase .................................................................................. 22 1 Getting Started

5.2.4 Display Analysis Results .................................................................. 22 Appendix 1 Overview of clearing analysis Activities (Analysis Phase) ............................................................................ 24 Appendix 2 Examples for Ratings for UCIA .............................. 25 Appendix 3 Object Types considered for Clearing Analysis ... 27 Appendix 4 Object Types considered for Upgrade Change Impact Analysis .............................................................................. 28 1 Getting Started 1 Getting Started This guide provides a central starting point for the implementation and use of the Custom Development Management cockpit (CDMC). The Custom Development Management cockpit consists of three standard parts: Clearing analysis (CA) Upgrade/change impact analysis (UCIA) Change and Transport System Analysis (CTS) This guide gives an overview of the functions of CA, UCIA, and CTS, and describes how the system landscapes need to be set up and provides other information to help you install and work with the Custom Development Management cockpit. Getting Started [page 6] explains how to use this document and provides links to additional documentation materials and relevant SAP Notes. CDMC Overview [page 9] contains the following information: A short introduction to the Custom Development Management cockpit and its functions General considerations regarding implementation and use of CDMC Information about CA, UCIA and CTS is provided in the last part of this guide [starting on page 14]. This section covers the following topics for each of the three standard parts of CDMC: OverviewSystem landscape Activities and functions 1 Getting Started

1.1Documentation TypesThe following is an overview of the documentation types that you may find helpful when working with CDMC. It covers texts that have been written specifically for CDMC as well as general SAP reference materials. 1.1.1 Generic Cross-Phase Documentation SAPtermSAPterm is SAPs terminology database. It contains SAP-specific vocabulary in over 30 languages, as well as many definitions and glossary entries in English and German. Target group:Relevant for all target groups Current version: Located in the SAP Service Marketplace at service.sap.com/sapterm SAP Library The SAP Library is a collection of function- and process-oriented documentation for SAP components. The SAP Library also contains the Business Scenario Descriptions.Target group: System administrators Project teams for implementations or upgradesCurrent version: Located in the SAP Help Portal at http://help.sap.com Learning Maps http://service.sap.com/rkt-solman Service Market Place: http://service.sap.com/upgradetools http://service.sap.com/enterpriseedition 1.1.2 Implementation The guide for CDMC (the current document) provides high-level description of the different parts of CDMC and explains how to implement and use them. Target group: System administrators CDMC users 1 Getting Started 1.1.3 Production Operation Activity Documentation All activities in a clearing analysis or upgrade/change impact analysis or change and transport system analysis project are listed in a process tree. Documentation is available for each of these activities. The activity documentation is shipped along with the CDMC software. Target group: CDMC users 1.2 Important SAP Notes Please consider the SAP Notes listed below before you start with the installation.Make sure to use the most recent version of each SAP Note, which you can find in SAP Service Marketplace under the following address: http://service.sap.com/notes List of Related SAP NotesSAP Note Number TitleDescription 1348772CDMC Corrections - Composite SAP Note Collective note for Custom Development Managment Cockpit CDMC1244713 Configuration of Custom Development Management cockpit Information about how to configure the Custom Development Management cockpit 2 CDMC Overview

2 CDMC Overview Most SAP systems contain not only standard software, but also custom-developed objects for the given companys specific needs. In this context, the terms custom-developed objects and customer-specific objects refer to repository objects such as programs or tables that are not shipped with SAP standard software, but created in the customer namespace. As the number of customer-specific objects increases, maintaining them becomes a more and more challenging task. In particular, it is difficult to determine which of the custom-developed objects are actually used and which ones have become obsolete. During upgrades, support package installation and other technical changes (such as system consolidation activities), each and every custom-developed object in the relevant SAP system must be considered for its possible impact. Each obsolete custom-developed object causes unnecessary effort. In addition, it is difficult to estimate the amount of work required for upgrades because not enough information about the custom-developed objects and the necessary changes to them is available. Companies that have a central development environment with subsequent roll-out to other systems face the additional challenge of having to ensure that the custom-developed objects are up-to-date and consistent in all the relevant systems. The Custom Development Management cockpit (CDMC) provides a comprehensive set of functions for optimization tasks in the area of customer-specific developments: Clearing analysis (CA): With the clearing analysis, you can identify and analyze obsolete repository objects. The results of a clearing analysis project are an ideal starting point for the clearing process for custom development. Upgrade/change impact analysis (UCIA): With the upgrade/change impact analysis, you can analyze the technical impact of an SAP Upgrade or Support Package on your custom developments and estimate the amount of work required for adapting them. Change and Transport system analysis (CTS): With change and transport system analysis, you can perform the quality checks by doing a usage analysis, environment analysis and remote comparison for a specified object set of requests in the analysis (QAS/Test) systems. It gives the list of the objects that were used during the test phase. It also helps to check if the objects in the request are identical across the landscape. CDMC has a project-based concept, that is, you create a project for every instance of a clearing analysis or upgrade/change impact analysis or change and transport system analysis you execute. Each project has its own process tree that lists the activities in the project. The activities in the tree are grouped into phases. 2.1 Implementation Considerations Before you can start to work with CDMC, you should consider the options it offers and decide on how you are going to work with it: For one thing, you may have fairly specific requirements regarding CDMC. You might want to use it to single out custom objects that cause a disproportionate amount of work. Or you may be preparing for a system consolidation and want to find out which of your custom objects 2 CDMC Overview need to be considered and which ones are in fact obsolete. In any case, it is helpful if you define beforehand what exactly you want to achieve using CDMC, so that you can plan your projects accordingly and concentrate on the aspects that are most important for your company. Also, it makes sense to clarify early on who will take care of the different tasks in your CDMC projects, and to draw up an authorization and security concept. From a technical perspective, one of the most important decisions concerns the systems that will participate in your CDMC projects and their respective roles. This aspect will be discussed in more detail below, because the system landscape for CDMC differs a little depending on whether you are doing a clearing analysis (CA) or an upgrade/change impact analysis (UCIA) or a change and transport system analysis (CTS). However the basic principles remain the same: You have a system whose data you want to analyze. This system is also referred to as collector system. Then you have one central system, also referred to as control center. The control center and the collector system(s) (as well as the reference system for UCIA and target system for CTS) are connected by Remote Function Calls (RFCs). In a CDMC project, you start all functions from the control center, and any functions in the remote systems are then carried out through the RFCs. The analysis results are stored and evaluated in the control center and incase of a CTS project the results are stored in the analysis system. With regard to the RFC users, you need a CPIC user for the statistics system in CA and UCIA and a dialog user for all other system roles in CA and UCIA and CTS. 2.2 Installation CDMC is shipped with the Solution Manager Enterprise Edition. The tool is technically shipped via ST-PI which needs to be installed on the relevant satellite systems as well as on the central solution manager system. For further instructions on how to install CDMC within your system landscape, please follow installation note 1244713. The IDs of all objects that come with CDMC lie in SAP namespace CNV*. 2.3 User Roles The following user roles are available in CDMC: SAP_CDMC_USER SAP_CDMC_MASTER: Only users with role SAP_CDMC_MASTER can make global settings and delete projects. For the other tasks within CDMC, the role SAP_CDMC_USER is sufficient. SAP_CDMC_STAT_SYSTEM: This role can be used for the RFC user to the statistics system in clearing analysis. It contains only the authorizations necessary for the tasks carried out on the statistics system (activation of statistics collection, import of the collected statistics to the control center, determination of empty tables, syntax check for source code objects). Since the statistics system is normally a production system, enhanced security requirements may apply to the RFC user for this system. User role SAP_CDMC_STAT_SYSTEM has been designed to meet these requirements; it should be assigned to a CPIC user (not a dialog user). 2 CDMC Overview

If the control system is an SAP Solution Manager system, you can select a system from the solution manager landscape. You must use a TMW destination to the statistics system. Ensure that the RFC user for the TMW destination you have selected has the profile S_SM_EXECUTE. This RFC user does not need the CDMC master role SAP_CDMC_MASTER. The TRUSTED destination requires the CDMC roles to be assigned. For further instructions on how to adapt the above mentioned CDMC roles, see SAP Note 1244713 (under Post-Installation steps for CDMC) 2.4 Control Center When you execute transaction CNV_CDMC in the control system, the control center entry screen is displayed. This screen is your starting point for all cross-project activities in CDMC. You get an overview of all your CDMC projects grouped by project types. You can create new projects and access (or delete) existing projects. In addition, you can maintain the settings that apply at cross-project level (also referred to as global settings) - such as SAP Note maintenance. 2.5 Notes Maintenance As a rule, you need to consider quite a number of SAP Notes in connection with your custom objects. For example, there are SAP Notes containing general information about how to handle custom objects in an SAP system. Also, you may want to mention SAP Notes that have been applied to the participating systems and could be relevant in connection with your CDMC projects.CDMC offers you the possibility of maintaining a list of relevant SAP Notes so that you have them available for reference purposes at any time during your CDMC project. Each SAP Note number in the list is linked to the respective SAP Note in SAP Service Marketplace. So when you select an SAP Note from the list, the SAP Note text as stored in SAP Service Marketplace is displayed in a browser window. 2.6Project-Specific Overview Screen The project-specific overview screen is your central cockpit for all activities in a CDMC project. In the upper part of the screen, you can find general information about your project and the participating systems, so that you have it at hand at any time during your project. The project tree in the lower part of the screen contains all activities for your CDMC project. Each activity has an executable function, which you start by choosing the Execute symbol next to the relevant activity. You also get the admin information that you require to monitor the progress of each activity and of the project as a whole, for example the activity status and the runtime. An activity log with more status information is available for each activity that has been executed. 2.7 Global SettingsGlobal settings phase is the first step to start the CDMC project (CA, UCIA, or CTS).Here, the most impotant activity is to collect staticstics on which the Usage Analysis works.2 CDMC Overview The activity Activate Statistics Collection can help in collecting the data of the usage. SAP recommends that the statistics should cover at least three months and one fiscal year or a quarter year change. The statistics are usually collected for different objects from the production system (also known as statistics system). The statistics are collected are from transaction ST03N. The objects collected from ST03N are stored with the evaluation type 00.From ST-PI SP08, an additional way to collect the statistics is integrated using the standard Solution Manager functionality - Usage and Procedure Logging (UPL).For further details on UPL you can check SAP Note 1683134. UPL helps in collecting data about all the objects already collected by ST03N plus the Smartforms. UPL gives 100% coverage of usage. The added advantage is the detection of the dynamically called ABAP elements.With the Integration of UPL with CDMC the staistics collection capability of CDMC is enhanced thus giving a better view of the Usage of the Objects for Clearing Analysis and the Upgrade and Change Impact Analysis. The activity Activate Statistics Collection will also collect usage details from the UPL if it is activated in the system.A new background job CNV_CDMC_CA_COLLECT_UPL_STAT will be triggered to collect the data. This usage data thus collected from UPL will be stored with Evaluation Type 01. 3Clearing analysis

3Clearing analysis The purpose of a clearing analysis is to identify and analyze customer-specific repository objects along with the project documentation information. The analysis results are an ideal starting point for the clearing process for custom objects. 3.1 System Landscape There are three types of systems (or system roles) you need to consider when planning the system landscape for a clearing analysis project: In the statistics system (system with role S), the collection of statistical data takes place. A job that is executed periodically (daily or weekly) transfers and condenses SAP standard statistics data and short dump evaluation in a CDMC database table.If the UPL is activated in the Solution Manager system then on activating the statistics collection a new job would be added in the control system for collecting Usage information using UPL. In addition, the project-specific queries such as syntax check for customer programs or empty customer tables are executed once per project in the background and stored in a CDMC database table. The statistic system is the production system. In the analysis system (system with role A), all project-related analyses (including selection of relevant objects) are performed in the background, and the results are stored in a CDMC database table. The analysis system is typically a QA system, which should be a fresh copy of the production system. In the control system (system with role C), the control center for all CDMC projects is located. All activities in systems with other system roles are triggered from here via RFC connections. CDMC projects and their process trees are created and accessed in the control center. The results of the analyses are transferred from all other systems to this system, so that they can be viewed and maintained here. The production system takes over the role of the statistics system. The analysis system should be a consolidation system in the same transport chain or similar system guaranteeing a stable environment and no performance risks. The control system should be the central solution manager system which additionally provides the user with integration features into other solution manager applications in the upgrade context. Alternatively, a development system or any other system that is part of the RFC network can be used as the control system. However, in this case, integration features to other SAP Solution Manager applications will not be available. You need exactly one instance of a Control System (C), Analysis System (A) and Statistic System (S) respectively. However this does not necessarily mean that you need three separate SAP systems. In particular, a single SAP system can take the roles of control system and analysis system. 3.2 Activities and Functions 3Clearing analysis 3.2.1 Preparations and Project Settings Once you have planned your CDMC projects and defined the system landscape, you can start with the preparations for your first clearing analysis project.First of all, you need to make sure that you have the required statistics information available. To this purpose, start transaction ST03N in the system(s) you plan to use as the statistics system(s). Switch to the expert mode and check the values for the total workload. Then start program CNV_CDMC_CA_COLLECT_STAT_700 (for Netweaver Release 2004s) or program CNV_CDMC_CA_COLLECT_STAT_EVAL (for lower releases) to store the statistics in CDMC-specific tables in the statistics system(s) and make them usable for your CA projects. To ensure that the statistics continue to be collected and stored as required, choose Activate Statistics in the control center entry screen. For each relevant system, specify the RFC destination and choose Activate. Then specify the frequency with which the statistics should be collected as well as the number of periods for which the statistics information is available. In the next popup Schedule Jobs, you can control the periodicity of the jobs by specifying the Period and Period Type. You can also see an Enabled flag against each job/report, and if it is set to X then it is executed in the statistic system otherwise it will not be scheduled/executed. For more information on this, you can refer to the documentation of this activityThe necessary jobs are then automatically scheduled in the system you specified as the statistics system. During the Collect phase of a clearing analysis project, the collected information is then transferred to the control system, where it is analyzed. Note that the statistics collection continues as long as the related jobs are active. You can also get the usage information for the customer exits in a clearing analysis project by following the below steps. 1. Before you execute the activity Activate Statistics Collection in the Global Settings phase, execute the transaction CNVCDMCCA_GET_EXITS in the control system. The underlying report for this transaction collects all the implemented customer exits and the associated reports and transaction codes from the analysis system, and updates the database table CNVCDMCCA_ENHS in the analysis system.2. Execute the transaction CNVCDMCCA_UPLD_EXITS in the control system. The underlying report for this transaction imports the data collected in the previous step from the analysis system, and uploads it to the control and the statistics systems. Note that this transaction can also be triggered during the activity Activate Statistics Collection on click of the push button Include Customer Exits in the pop-up Maintain Systems for Statistics Collection.3. Execute the activity Activate Statistics Collection. This activity now extracts the workload statistics for the customer exits. Note, in the subsequent activity Enhancements, the usage information for the customer exits is determined. Finally, you check the Notes maintenance area for SAP Notes that might be relevant in your project and consider the information provided in the Notes. You can also add other SAP Notes that are of interest to you in this context. 3.2.2Collect Phase When you have completed the preparations, the next step is to collect the data you want to analyze. 3Clearing analysis

In the first activity in the collect phase, a program searches the analysis system(s) for customer-specific objects and stores the found objects. Please see Appendix 3.section to find the object types that are considered for Clearing Analysis. The function for the next activity also runs in the analysis system(s). This function finds SAP objects that have been modified in the analysis system(s), and stores these objects. Finally, you import the collected statistics information from the statistics system(s) to the control system. The import covers all customer-specific objects that have actually been executed (according to the statistics files on each application server) as well as customer-specific objects that have caused dumps. These objects are marked as used. The information collected here is the basis for the subsequent analysis activities. 3.2.3Analysis Phase During the analysis phase, the collected data for custom objects is analyzed by various programs with the aim of identifying the objects that are likely to be obsolete. Once you have executed the function for an activity, the related program runs in the background in all the systems with the corresponding system role, and no further user interaction is required. You can find a list of the activities in this phase together with information about where each activity is used in the appendix. The activities Import Statistics and Perform Usage Analysis are executed if you want to find the usage information of the objects. For this the statistics system has to be maintained in the project landscape. The program statistics is collected from the imported statistics data in the Control system and the analysis is carried out in the Analysis system . As the data is now being collected using UPL the usage information of dynamically call objects would be available. This activity analyzes the environment of these collected program objects and compiles a list of all the objects that they use. The results for all analysis activities are presented together in the next phase. A more detailed description of each activity is given in the activity documentation that comes with the CDMC software. For a list of all activities in this phase and the systems in which they run, see Appendix 1. None of the activities in this phase is mandatory; so if you are sure that an activity is not relevant or suitable for your project, you can skip it. Nevertheless we recommend that you execute all functions in the given order to get a complete picture of your custom objects. When you have carried out all analyses you consider necessary, the last thing you do in this phase is to confirm the analysis by executing the function for the respective activity. Once you have confirmed the analysis, the system starts to compile and process the analysis results, and you cannot execute any more analyses in this project. 3.2.4Display Analysis Results When the system has finished compiling and processing the analysis results, you can look at the results and decide how to proceed with the found objects. You have various options for viewing and filtering the data. You can also go to the detail view and even do a remote comparison for individual objects. 3Clearing analysis You can set the status for each object you analyzed and assign a processor, that is, a person who should analyze the given object in more detail and decide how to handle it. You can download the results in a special report and send them to the assigned processors. 3.2.5Work with Analysis Results (Clearing) The CDMC HowTo guide for Clearing provides you with helpful information about how to proceed when clearing obsolete custom objects and what you should keep in mind in connection with the different object types and their possible uses. This guide comes with the CDMC software. To display it, choose the Documentation icon for the related process tree activity. 4Upgrade/change impact analysis

4Upgrade/change impact analysis With the upgrade/change impact analysis, you can find out about the technical impact of an SAP Upgrade or Support Package on your custom developments and estimate the amount of work required for adapting them along with the project documentation information. Please see Appendix 4.section to find the object types that are considered for Upgrade Change Impact Analysis. 4.1 System Landscape There are three types of systems (system roles) you need to consider when planning the system landscape for an upgrade/change impact analysis (UCIA) project: Control system (C): This is the system which acts as the control center. The administration of a UCIA project is carried out from a system of this role, and all activities (even the ones that run in one of the other systems) are triggered from here. The control system should be the central solution manager system. Analysis system (A): This is the system where the custom objects are evaluated for the impact of the change on SAP Objects. Reference system (R): The upgrade or other change whose impact you want to evaluate must be implemented in this system. During the Analysis phase of a UCIA project, the SAP Objects in the analysis system are compared with their corresponding versions in this system. Reference Information Base: If the user has chosen to use the Reference Information Base instead of the Reference System option, then Control System and Analysis System with roles C and A as indicated above are involved in the upgrade/change impact analysis Project. The Reference System is maintained empty to indicate the usage of Reference Information Base. Further, when choosing the Reference Information base, the user has to specify the end release of the target system and a Reference Information base name. The Reference Information base name will be used later on for storing the Reference Information base content. The Reference Information base contains of a Cluster table (CNVCDMCUCIA_KSP8) in which all SAP objects along with the details of each object for the target release will be stored.Statistics system: In the statistics system (system with role S), the collection of statistical data takes place. A job that is executed periodically (daily or weekly) transfers and condenses SAP standard statistics data and short dump evaluation in a CDMC database table. If the UPL is activated in the Solution Manager system then on activating the statistics collection a new job would be added in the control system for collecting Usage information using UPL. This is an optional system and should be added only incase you need to perform the usage of the objects along with their impact in UCIA project. You need exactly one instance of a Control System (C), Analysis System (A) and Reference System (R) respectively. However this does not necessarily mean that you need three separate SAP systems. In particular, a single SAP system can take the roles of control system and analysis system. 4.2 Activities and Functions 4Upgrade/change impact analysis 4.2.1 Preparations and Project Settings The only required activity at cross-project level is maintenance of the adjustment times. That is, you enter the estimated average effort (in hours per object, based on your experience) for adjusting different types of custom objects in connection with a change in the related SAP objects (resulting from an upgrade or support package application). The values you enter here are used for calculating the average total amount of required work that is output in the Display Results phase. Another activity for maintaining adjustment times exists at project level. If you want to apply the values defined at cross-project level for a given project, simply execute the activity in the project without making any further changes. Otherwise, execute the activity at project level and enter project-specific values as required. For a concrete UCIA project, the preparatory steps are as follows: Setting up the system landscape Considering the relevant SAP NotesGetting the clones of the report programs along with the percentage of similarity. Maintaining project-specific adjustment times (if required). To get the clones of the report programs present in the analysis system you need to execute the activity Get Copied Program List and the results can be seen in the activity Maintain Copied Program List. 4.2.2 Analysis Phase The analysis phase for UCIA consists of multiple activities. Once you have executed the function for an activity, the related program runs in the background, and no further user interaction is required. In the first activity, you can provide the list of objects that you want to exclude from the analysis. You upload a list of the relevant objects in this activity.Next, a list of all the SAP objects that are being referred by your custom developments is prepared in the analysis system. You can choose if you want the list to cover all objects in the customer namespace or only objects from the specified development classes (packages) or the customer objects associated to the solution manager projects/solutions. In the latter case the customer objects maintained under the Development or Transaction tab of solution manager projects/solutions are considered for the analysis. You can also exclude indirectly referred objects (which will ensure that only directly referred SAP objects will be considered for the analysis).In case of the Reference Information base, the customer will download the list of SAP objects that are referred by the custom developments to a Microsoft Excel file or as a piece list and sends it to the partner/service provider to extract the upgrade relevant details of these objects. The partner/service provider then extracts the upgrade relevant details of these objects via a CDMC Reference Informationbase extractor program and transports the contents to the Control system of the customer where it will be imported. In the next activity, you find the SAP objects that are referred by customer-specific objects and will be changed during the upgrade (or other change). The program for this activity runs in the reference system. If you want to check the implications of one or more 4Upgrade/change impact analysis

transports, you can specify this transport in the dialog box that is displayed when you execute the function. You can also use this latter function to check for the implications of a Support Package implementation (Support Packages are shipped as transports of type Delivery.) You can also compare all SAP objects used by the custom objects, which is useful if you are preparing for a system merge and want to get information about the differences between the systems to be merged. In case of the Reference Information Base this activity checks if the Reference Information Base content is available in the Control System of the customer. Otherwise if the user tries to execute this activity even before importing the Reference Information Base contents he will get an Error Message stating that the Reference Information Base Contents are not present in the control system. Finally, you compare the SAP objects found in the analysis system against their counterparts in the reference system. Note that this activity, like all the others, is triggered from the control system and obtains the required information from the analysis system and the reference system through the RFC connections. Using the results of the comparison and the adjustment times you specified earlier, the acitivity Calculate Adjustment Time calculates the estimated effort required to adjust the custom-developed objects which refer these SAP objects. In case of the Reference Information Base for each of the SAP Objects, object details are fetched from the Analysis System and from the Reference Information base into the Control System for comparison. Please consider that when using the Reference Information base, no SP Upgrade Scenario can be used, only the Upgrade Scenario. The activities Import Statistics and Perform Usage Analysis are executed if you want to find the usage information of the objects along with its impact during the upgrade. For this the statistics system has to be maintained in the project landscape. The program statistics is collected from the imported statistics data in the Control system and the analysis is carried out in the Analysis system . As the data is now being collected using UPL the usage information of dynamically call objects would be available. This activity analyzes the environment of these collected program objects and compiles a list of all the objects that they use. The activities Customer Batch Input Analysis and Analyze Ext. Subroutine Calls finds the impact on customer objects (related to the BDC programs and External subroutines) because of a change in the underlying referred SAP objects. 4.2.3 Display Analysis Results When the comparison is finished, you can look at the analysis results and decide how to proceed with the listed objects. You have various options for viewing and filtering the data. You can set the processing status for each object you analyzed. You can even do extended syntax checks for custom objects and get where-used lists for SAP objects from the list. You can also perform the code inspector checks for the source code objects like Program, Class and Function groups. You can view the total adjustment times at the customer object level calculated for different sets of objects to get a clearer idea of the amount of work that is required in different areas.The results list (overview screen) also contains a rating for each custom object to indicate the probability that it will require a change: A green traffic light means that no adaptation of the object is required in connection with the planned upgrade or change. A yellow traffic light means that adaptation of the object is probably required. 4Upgrade/change impact analysis A red traffic light means that there is a very high probability that the object must be adapted to ensure its correct functioning after the upgrade or change. This summary rating for each custom object is based on the detailed analysis of each custom object and the SAP objects it uses: For each SAP object referred by a custom object, the version from before the upgrade (or other change) is compared against the version from after the change. Depending on the results of this comparison, the object is rated green, yellow or red. (A list of rating criteria is provided in Appendix 2.). The summary rating for a custom object is determined by the worst rating an SAP object used by this custom object has been given. If, for example, a custom object refers five SAP objects, of which two are rated yellow and three are rated green, the summary rating for this custom object on the overview screen will be yellow. To review the results of the detailed analysis for each custom object / SAP object relation and the related detailed ratings, choose Detailed View. In addition, in the Summary View, you can view summary information for the analysis. 5 Change and Transport System Analysis

5 Change and Transport System AnalysisChange and Transport System Analysis analyzes objects in a set of transport requests. For these objects, you can determine the usage information and also compare the status of these objects in the different systems. This allows a project manager, or release manager, to perform a risk assessment before the transport set is imported into a productive system. 5.1 System LandscapeThere are four types of systems (system roles) you need to consider when planning the system landscape for a change and transport system analysis (CTS) project: Control System (C): This is the system which acts as the control center. The administration of a CTS project is carried out from a system with this role, and all activities (even the ones that run in one of the other systems) are triggered from here. The control system should be the central SAP Solution Manager system. Analysis System (A): This is the system where all project-related analyses (including selection of relevant objects in a transport request) are executed, and the results are stored in a CDMC database table. Target System (T): This is the system in which the object set in the transport request (selected during the activity Determine Object Set) would be released to. In the analysis activities like Remote Comparison and Perform Environment Analysis, the version of the object in the analysis system is compared against with the target system. Statistics System (S): In the statistics system, the collection of statistical data takes place. A job that is executed periodically (daily or weekly) transfers and condenses SAP standard statistics data and short dump evaluation in a CDMC database table. This is an optional system and should be added only if you need to check the usage of objects inside transport requests. You need exactly one instance of a control system (C), analysis system (A) and target system (T) respectively. However, this does not necessarily mean that you need three separate SAP systems. In particular, a single SAP system can assume the roles of the control system and the analysis system. 5.2 Activities and Functions5.2.1 Preparations and Project SettingsOnce you have planned your CDMC CTS project and defined the system landscape, you can start with the preparations for your first change and transport system analysis project.First of all, you need to make sure that you have the required statistics information available. To execute the activities Test Scope Identification and Test Coverage Analysis you need to have the ST03N data available in the systems you have added as statistics and analysis systems. After this, activate the statistics collection in these systems by following the procedure mentioned under Preperations and Project Settings of Clearing Analysis.5 Change and Transport System Analysis For a CTS project, the preparatory steps are as follows: Setting up the system landscape Determining the object set. In the Determine Object Set activity, you can select the set of transport requests from the analysis system for which you want to perform the analysis.5.2.2 Collect PhaseWhen you have completed the preparations, the next step is to collect the data you want to analyze.In the first activity in the collect phase, a program searches the analysis system(s) for the SAP objects that have been modified and stores the found objects.The function for the next activity also runs in the analysis system(s). This function finds the enhancements such as user exits, BAdIs, and BTEs from the original object set.The function for the next activity also runs in the analysis system(s). This function finds the customer objects which are part of the original object set. In addition, the SAP objects which are referred by these objects are determined.5.2.3 Analysis PhaseThe analysis phase for CTS consists of four activities. Once you have executed the function for an activity, the related program runs in the background; no further user interaction is required.The statistical data collected by CDMC is used for the activities Test Scope Identification/Test Coverage Analysis in CTS.The prerequisite for the activity Test Scope Identification is to add the statistics system to the project landscape, and to activate the statistics collection. If you execute Test Coverage Analysis then the prerequisite is to activate the statistics collection in the analysis system as CDMC determines the usage information against the analysis system.During the execution of these activities you are prompted to give the time period that is relevant for determining the usage analysis.You use the activity Perform Environment Analysis to determine the objects referred within the initial object set and performs the remote comparison of the referred objects between the analysis and the target system and provide the status information for the referred objects between the analysis and the target system.You use the activity Perform Remote Comparison to determine the objects in the transport requests and perform the remote comparison for these objects between the analysis and the target systems.5.2.4 Display Analysis ResultsWhen the comparison is finished, you can view the analysis results and decide how to proceed with the listed objects. You have various options for viewing and filtering the data. You can create a where-used list, and execute a remote comparison for the objects against a specific target system.There are different views for the results. You can see the initial view that contains the list of the objects together with their comparison result. You can also see the list of used objects from the statistics system using the functional view Test Scope Identification Used Objects, and the list of referred objects using the Environment Analysis view.The list of used objects from the analysis system can be seen using the functional view Test Coverage Analysis Used ObjectsTo review the results of the detailed analysis for each object from the request choose Detailed View. Here you can see the comparison status and the severity.The object status can be:1. Only in analysis system 2. Only in target system

3. Different version4. Same version The status Same version has a green traffic light. All the others have a red traffic light. You can create piece lists in the analysis system or in the target system for different object selections based on the status.A Remote Comparison considers only the following objects: Domains, Domain Definitions, Data Elements, Data Element Definitions, Search Helps, Search Help Definitions, Lock Objects, Lock Object Definitions, Views, View Definitions, Tables, Table Definitions, Function Modules, Programs, Reports, Table Types, Table Type Definitions, Class, Methods, Dynpros. An Environment Analysis considers only the following objects. All R3TR Objects, Domain Definitions, Data Element Definitions, Search Help Definitions, Table Definitions, View Definitions, Function modules, Methods, Reports. Usage Analysis - the following are the object types that are supported by the usage analysis in CTS: Programs, Function Groups, Messages, Transactions, Function Modules, Tables, Domains, Data Elements, Views, Type Groups, Table Types, Structures, Class, Search Helps, Matchcode Objects, Matchcode ID, SPA/GPA Parameters, Authorization Objects, Logical Databases, Dialog Modules, Interfaces, Data Models, Entity Types, Lock Objects, Pooled/Cluster Tables, Reports, Conversion Exits. Appendix 1 Overview of clearing analysis Activities (Analysis Phase) Appendix 1 Overview of clearing analysis Activities (Analysis Phase) ActivityRuns in which system? Duplicate domainsAnalysis system Determine empty databasesStatistics system Syntax checkStatistics system Transport frequencyAnalysis system Inactive customer objectsAnalysis system Perform Usage analysisAnalysis system Objects with no referenceAnalysis system EnhancementsAnalysis system Confirm analysisControl center Appendix 2 Examples for Ratings for UCIA

Appendix 2 Examples for Ratings for UCIA Object TypeDescriptionRating CLASATTRIBUTESRed CLASMETH_CHANGEDRed CLASMETH_PARAMETERSRed CLASMETH_PROPERTIESRed DOMAATTRIBUTESYellow DOMADATATYPERed DOMADOMA_CONV_EXITYellow DOMADOMA_VALUESYellow DTELATTRIBUTESYellow DTELDATATYPERed DTELSEARCH_HELPYellow DYNPFIELD_NOT_EXISTRed DYNPLENGYellow DYNPNEWLY_ADDEDYellow DYNPNOT_EXISTRed DYNPTYPERed DYNPUCNVYellow ENQUENQU_MODEYellow ENQUENQU_PARAMETERSRed ENQUENQU_TABLEYellow FORMFIELD_NUMBERYellow FORMFORM_INTERFACERed FORMFORM_INT_ATTRRed FORMFORM_INT_REFTYPEYellow FORMNOT_EXISTRed FUNCFIELD_NUMBERYellow FUNCFUNC_INTERFACERed FUNCFUNC_INT_ATTRRed FUNCFUNC_INT_REFTYPEYellow FUNCFUNC_OBSOLETERed PROGREPSDELTAYellow SHLPFIELD_NUMBERRed Appendix 2 Examples for Ratings for UCIA SHLPSEARCH_HELPYellow TABLATTRIBUTESYellow TABLCHECK_TABLEYellow TABLFIELD_NUMBERYellow TABLPRIMARY_KEYRed TABLREF_TYPEYellow TTYPATTRIBUTESRed TTYPPRIMARY_KEYRed TTYPROWTYPERed VIEWFIELD_NUMBERRed VIEWVIEW_DB_NUMBERRed VIEWVIEW_FIELD_DELYellow VIEWVIEW_JOIN_CONDYellow NoteHowever, in some cases though reason is same but serverity may be a different (red instead of yellow) because it takes the severity of a refered object down the hierarchy. Example:The iteration of the environment analysis is based on the setting in user profile. Scenario 1:Object PROG ZREPORT contains a referred object TABL which is refering to object DTEL which in turn refers to object DOMAIN If the no. of fields have changed in Analysis/Reference System for TABL then it has Yellow severity with the reason TABL number of fields changed from N to N1'. Now if the DOMAIN has a severity Red due to change in DATATYPE in the Analysis/Reference system then the severity of TABL is marked as Red with the same reason 'TABL number of fields changed from N to N1' due to a greater severity of the referred object DOMAIN. Scenario 2:Object PROG ZREPORT1 contains a referred object: TABL1 which is refering to object: DTEL1 which in turn refers to object: DOMAIN1 If the no. of fields have changed in Analysis/Reference System for TABL1 then it has Yellow severity with the reason 'TABL number of fields changed from N to N1'. Now if the referred objects DTEL1 and DOMAIN1 have no issues during remote comparison then the severity of the object TABL1 remains Yellow. Therefore in the activity Display Results, we can see the following: Appendix 3 Object Types considered for Clearing Analysis

Appendix 3 Object Types considered for Clearing Analysis Determine Customer Objects Remote Comparison in Display Results Usage Analysis (Supported)Usage Analysis(Not Supported) ACGRDOMADOMA, DOMDDOMADTELDTEL, DTEDDTELTABLTABL, TABDTABLTRAN TRANTTYPTTYPTTYPObject Type Object NameReferred Obj. TypeReferred Obj. NameSeverity ReasonPROGZREPORTTABLTABLRed TABL number of fields changed from n to n1 PROGZREPORT1TABLTABL1Yellow TABL number of fields changed from n to n1 Appendix 4 Object Types considered for Upgrade Change Impact Analysis VIEWVIEW, VIEWDVIEWMCOBMCOB ENQUENQU, ENQDENQUSHLPSHLP, SHLDSHLPINTF INTFDIAL DIALPINFUDMO UDMOUENO UENOLDBA LDBASMEHSUSO SUSOIAMAWDYN WDYN*WDYAFORMFORM SSFOSSFO CLAS CLASFUGRFUNC, REPOFUGRPROG PROG, REPS REPT, REPO PROGTYPETYPETYPEAll Sub objects except DOCU INDX,MCID, DYNP MSAG, STRU, SHI3, FUNC BADI, BTE *Full support with UPL Appendix 4 Object Types considered for Upgrade Change Impact Analysis Find Referred SAP Objects Perform Remote Comparison Remote Comparison in Display Results Usage Analysis (Supported) Usage Analysis (Not Supported) ACGR DOMADOMA, DOMDDOMA, DOMDDOMADTELDTEL, DTEDDTEL, DTEDDTELTABLTABL, TABDTABL, TABDTABL Appendix 4 Object Types considered for Upgrade Change Impact Analysis

Find Referred SAP Objects Perform Remote Comparison Remote Comparison in Display Results Usage Analysis (Supported) Usage Analysis (Not Supported) TRANTRANTTYPTTYP, TTYDTTYPTTYPVIEWVIEW, VIEDVIEW, VIEWDVIEWMCOB MCOBMCOBENQUENQU, ENQDENQU, ENQDENQUSHLPSHLP, SHLDSHLP, SHLDSHLPINTFINTFDIALDIALPINF UDMOUDMOUENOUENOLDBALDBASMEH SUSOSUSOIAMA WDYNWDYN*WDYA FORM FORM SSFO SSFO CLASCLAS CLASFUGRFUNCFUNC, REPOFUGRPROG PROG, REPS, REPT, REPO PROG, REPS REPT, REPO PROGTYPETYPE, notSub object TYPD TYPEIf the input is piece-list then fetching all the object types, there is no restriction.

INDX,MCID, DYNP MSAG, STRU, SHI3, FUNC Collection of BAdI, BTE and Customer exits and their usage analysis is out of scope *Full support with UPL Appendix 4 Object Types considered for Upgrade Change Impact Analysis