CUSTOM DEVELOPMENTMANAGEMENT COCKPITOVERVIEW

CONTENTS

What is CDMC?Why CDMC?Prerequisites for CDMC.Components of CDMC

Clearing analysis (CA)Upgrade/change impact analysis (UCIA)Additional functions of CDMC

Lessons Learnt

WHAT IS CDMC?

The Custom DevelopmentManagement Cockpit is a toolincluded in SAP Solution Managerwhich is a central point for managing“custom-developed objects” and“customer-specific objects”.

WHY CDMC?

During upgrades, support package installation and othertechnical changes (such as system consolidationactivities), each and every custom-developed object inthe relevant SAP system must be considered for itspossible impact.Each obsolete custom-developed object causesunnecessary effort.In addition, it is difficult to estimate the amount of workrequired for upgrades because not enough informationabout the custom-developed objects and the necessarychanges to them is available.

Prerequisites for SAPCDMC

SAP Solution Manager EnterpriseEditionLatest available ST-PIimplemented

ST-SER 2008_2 (SP01 recommended)

Prerequisites for SAPCDMC cont.

Prerequisite support packages;SAP_BASIS 46C Support Package 20SAP_ABA 46C Support Package 20SAP_BASIS 620 Support Package 20SAP_ABA 620 Support Package 20SAP_BASIS 640 Support Package 11SAP_ABA 640 Support Package 11SAP_BASIS 700 Support Package 05SAP_ABA 700 Support Package 05SAP_BASIS 710 Support Package 00SAP_ABA 710 Support Package 00

Additional Notes for CDMC

Implementationconsiderations for CDMC.

Decide which system is “collectorsystem” and which is the “control centre”Recommended to use SAP SolutionManager as “control centre”

Additional UserRequirements for CDMCThe following user roles are available in CDMC:

SAP_CDMC_USERSAP_CDMC_MASTER: Only users with role SAP_CDMC_MASTER canmake globalsettings and delete projects. For the other tasks within CDMC, the roleSAP_CDMC_USER is sufficient.SAP_CDMC_STAT_SYSTEM: This role can be used for the RFC user to thestatistics system in clearing analysis. It contains only the authorizationsnecessary for the tasks carried out on the statistics system (activation ofstatistics 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, enhancedsecurity requirements may apply to the RFC user for this system. User roleSAP_CDMC_STAT_SYSTEM has been designed to meet theserequirements; it should be assigned to a CPIC user (not a dialog user).

The Custom Development Managementcockpit (CDMC) provides a comprehensiveset of functions for optimization tasks in thearea of customer-specific developments:

Clearing analysis (CA)Upgrade/change impact analysis (UCIA)

Components of CDMC.

HowTo use CDMC.

Start transaction CNV_CDMCThe initial screen is the main cockpitscreen

Main Cockpit Screen

CDMC – Create Project

CDMC project administration involves the following features:Create Project

You can create a new project in the initial screen of the application. Right-clickClearing Analysis Projects or Upgrade / Change Impact Analysis Projects, andchoose Create. Enter a five-digit project ID and a description of the project andchoose Execute.

Open ProjectTo open a project, select a project and choose Execute. You can then view the treestructure that lists the various activities for the project.

Delete ProjectTo delete a project, you must have the role SAP_CDMC_MASTER. In addition,there must be no activity in the project currently running, or scheduled. To delete aproject, select the project and choose Delete.

Ad Hoc AnalysisThis option is only available for Clearing Analysis. You can execute some ClearingAnalysis activities without creating a project. You execute these activities in theanalysis system; they do not require statistics collection.

Analysis Preparation

You need to make sure that you have the required statisticsinformation available.

For this purpose, start transaction ST03N in the system(s)you plan to use as the statistics system(s). Switch to theexpert mode and check the values for the total workload.Then start programCNV_CDMC_CA_COLLECT_STAT_700 (for NetweaverRelease 2004s) or programCNV_CDMC_CA_COLLECT_STAT_EVAL (for lowerreleases) to store the statistics in CDMC-specific tables inthe statistics system(s) and make them usable for your CAprojects.

Clearing Analysis

Clearing AnalysisLandscape

The statistics system (system with role ‘S’),the collection of statistical data takes place.The statistic system is the production system.

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 aCDMC database table.The analysis system is typically a QA system, which should be afresh copy of the production system.

The control system (system with role ‘C’),the control center for all CDMC projects is located in the controlsystem.All activities in systems with other system roles are triggered fromhere via RFCconnections.The control system should be the central solution manager system

Clearing Analysis - AdditionalInfo

Clearing Analysis –Results

Clearing Analysis – Overview ofClearing Activities

Clearing Analysis results –Detailed View

Clearing Objects – SAP Guidelines

Adhering to the SAP clearing guidelines ensures thefollowing:

You minimize the risk of accidentally deleting validobjects.You maximize the ability to recover objects that youmay delete accidentally.The clearing guidelines apply to a 1-1-1 systemlandscape. This system landscape involves onedevelopment system, one quality assurance system,and one productive system.

Clearing Objects – SAP GuidelinesCont.

The initial stage of the clearing process involves deciding whether todelete an object or not.

You can use the CDMC application to determine the customobjects that have not been used for a certain time period (obsoleteobjects).

To identify objects that have not been used for a certain time period:Decide on a date in the past – you can delete the objects that havenot been used since this date.For all objects that have been used at some point between thespecified date and the current date, the system compares theversion of the objects in the three systems. Only consider deletingthe objects that have the same version in all three systems.For the objects that have different versions in the different systems,consider each object individually before deciding to delete it.Different versions of an object may indicate that the object iscurrently in under development or that is has been transported froma remote system outside the normal transport chain.

Clearing Objects – SAP GuidelinesCont.

The next stage involves deciding whether to archive any objects. In thiscontext, archiving means saving the object versions (for example thesource code and technical object settings) externally, for example on acompact disc. There are different archiving options, for example:

Saving the transport files of the transport request of copies. To dothis, create a transport request of copies to which all the objects thatyou want to delete are assigned. Releasing the transport request ofcopies creates a transport file with the current active version of theobjects. In a next step, you create a workbench transport requestthat is then used for deleting the objects.Save the active version of each object, before you delete the object.This approach requires a tool that allows you to download the activeversion of the object to the presentation server so that you can storeit on a compact disc.

All archiving tools face one common issue. As the length of time sincedeleting the object increases, re-importing the object becomesincreasingly difficult. This is because related standard SAP objects maybe changed, or even deleted, because of a support packageimplementation or a system upgrade.

Upgrade/Change Impact Analysis

With the upgrade/change impactanalysis, you can find out about thetechnical impact of an SAP Upgrade orSupport Package on your customdevelopments and estimate the amountof work required for adapting them.

Upgrade/Change Impact Analysis –Cockpit

Check for successresults

Upgrade/Change Impact Analysis –Landscape

Control system (C):This is the system which acts as the control center. Theadministration of a UCIA project is carried out from asystem of this role, and all activities (even the ones that runin one of the other systems) are triggered from here. Thecontrol system should be the central solution managersystem.

Analysis system (A):This is the system where the custom objects areevaluated for the impact of the change on SAP Objects.

Reference system (R):The upgrade or other change whose impact you want toevaluate must be implemented in this system. During theAnalysis phase of a UCIA project, the SAP Objects in theanalysis system are compared with their correspondingversions in this system.

Upgrade/Change Impact Analysis –Landscape

Knowledge Base:If the user has chosen to use theKnowledge Base instead of the ReferenceSystem option, then Control System andAnalysis System with roles C and A asindicated above are involved in theupgrade/change impact analysis Project.The Reference System is maintained emptyto indicate the usage of Knowledge Base.

Upgrade/Change Impact Analysis –Preparation

For a concrete UCIA project, thepreparatory steps are as follows:

Setting up the system landscapeConsidering the relevant SAP NotesMaintaining project-specific adjustmenttimes (if required).

Upgrade/Change Impact Analysis –Analysis Results

A green traffic lightmeans that no adaptation of the object is requiredin connection with the planned upgrade or change.

A yellow traffic lightmeans that adaptation of the object is probablyrequired.

A red traffic light meansthat there is a very high probability that the objectmust be adapted to ensure its correct functioningafter the upgrade or change.

Upgrade/Change Impact Analysis –Analysis Results – Detailed View

Upgrade/Change Impact Analysis –Analysis Results – Severity Levels

Upgrade/Change Impact Analysis –Analysis Results – Report

CDMC – Additional Functions

TADIR InconsistenciesThis activity obtains the list of objects fromTADIR, checks the existence of the objectsin the system and provides the status.

CDMC – Additional Functions

Unicode CheckThis activity can be executed only on higher versionsof SAP R/3, and is used to check a program set for syntaxerrors in a Unicode environment.This activity runs the ABAP Unicode Scan Tool UCCHECKThe transaction UCCHECK is used to examine a Unicodeprogram set for syntax errors without having to set theprogram attribute "Unicode checks active" for everyindividual program. From the list of Unicode syntax errors,you can go directly to the affected programs and removethe errors. It is also possible to automatically createtransport requests and set the Unicode program attribute fora program set.

CDMC – Additional Functions

Determine Active User ExitsThis activity gives the active user exits forthe selected development classes.The purpose of this activity is to obtain thelist of active user exits (Function Exits) forthe selected development classes.

CDMC – Additional Functions

Delete Mod. Logs of Deleted ObjectsThis activity provides an option to view the list ofdeleted objects and to delete the modification logs ofthe deleted objects in the selected remote system.This activity submits the ReportRS_SMODILOG_FIND_DEL_OBJ in the selecteddestination system. The reportRS_SMODILOG_FIND_DEL_OBJ displays thedeleted sub objects (LIMU) and the higher-levelcomplete objects with a separate object catalog(R3TR), for which only the modification logs exist.These objects were modified by the customer anddeleted during an upgrade or the import of a SupportPackage.

CDMC – Additional Functions

Check tables for Client Transport against Target SystemThis activity is run in the selected remote system and isused to check the structure of tables for client transportagainst the target system.This activity submits the report RSCLICHK in the selectedremote system.This program will give information about the missingdefinitions from the data dictionary in the target. Afterexecuting this program and getting successful results wecan ensure that the client copy will have no problems. Incase some tables are different; you can use SE11 tocompare and adjust the table structure in both the systembefore the client copy. A remote test client copy also can beexecuted to know the differences between source client andtarget client.

CDMC - Lessons Learnt

TimelineDecisions to use CDMC comes to late toassist in upgrades/patch implementationsNo time to analyze reports

Knowledge to use CDMC is limitedOutdated software and prerequisitesOutdated performance data

Performance data to analyze statistics isnot “old” enough – check and adapt ST03Nsettings

Thank You

Questions ?