You are on page 1of 39


What is CDMC?
Prerequisites for CDMC.
Components of CDMC
Clearing analysis (CA)
Upgrade/change impact analysis (UCIA)
Additional functions of CDMC
Lessons Learnt

The Custom Development

Management Cockpit is a tool
included in SAP Solution Manager
which is a central point for managing
“custom-developed objects” and
“customer-specific objects”.
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.
Prerequisites for SAP
SAP Solution Manager Enterprise
Latest available ST-PI
ST-SER 2008_2 (SP01 recommended)
Prerequisites for SAP
CDMC cont.
Prerequisite support packages;
SAP_BASIS 46C Support Package 20
SAP_ABA 46C Support Package 20
SAP_BASIS 620 Support Package 20
SAP_ABA 620 Support Package 20
SAP_BASIS 640 Support Package 11
SAP_ABA 640 Support Package 11
SAP_BASIS 700 Support Package 05
SAP_ABA 700 Support Package 05
SAP_BASIS 710 Support Package 00
SAP_ABA 710 Support Package 00
Additional Notes for CDMC
considerations for CDMC.

Decide which system is “collector

system” and which is the “control centre”
Recommended to use SAP Solution
Manager as “control centre”
Additional User
Requirements for CDMC
The following user roles are available in CDMC:
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).
Components of CDMC.

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)

Upgrade/change impact analysis (UCIA)
HowTo use CDMC.

Start transaction CNV_CDMC

The initial screen is the main cockpit
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-click
Clearing Analysis Projects or Upgrade / Change Impact Analysis Projects, and
choose Create. Enter a five-digit project ID and a description of the project and
choose Execute.
Open Project
To open a project, select a project and choose Execute. You can then view the tree
structure that lists the various activities for the project.
Delete Project
To 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 a
project, select the project and choose Delete.
Ad Hoc Analysis
This option is only available for Clearing Analysis. You can execute some Clearing
Analysis activities without creating a project. You execute these activities in the
analysis system; they do not require statistics collection.
Analysis Preparation

You need to make sure that you have the required statistics
information available.
For 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
releases) to store the statistics in CDMC-specific tables in
the statistics system(s) and make them usable for your CA
Clearing Analysis
Clearing Analysis
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 a
CDMC database table.
The analysis system is typically a QA system, which should be a
fresh copy of the production system.
The control system (system with role ‘C’),
the control center for all CDMC projects is located in the control
All activities in systems with other system roles are triggered from
here via RFC
The control system should be the central solution manager system
Clearing Analysis - Additional
Clearing Analysis –
Clearing Analysis – Overview of
Clearing Activities
Clearing Analysis results –
Detailed View
Clearing Objects – SAP Guidelines

Adhering to the SAP clearing guidelines ensures the

You minimize the risk of accidentally deleting valid
You maximize the ability to recover objects that you
may delete accidentally.
The clearing guidelines apply to a 1-1-1 system
landscape. This system landscape involves one
development system, one quality assurance system,
and one productive system.
Clearing Objects – SAP Guidelines
The initial stage of the clearing process involves deciding whether to
delete an object or not.
You can use the CDMC application to determine the custom
objects that have not been used for a certain time period (obsolete
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 have
not been used since this date.
For all objects that have been used at some point between the
specified date and the current date, the system compares the
version of the objects in the three systems. Only consider deleting
the 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 is
currently in under development or that is has been transported from
a remote system outside the normal transport chain.
Clearing Objects – SAP Guidelines
The next stage involves deciding whether to archive any objects. In this
context, archiving means saving the object versions (for example the
source code and technical object settings) externally, for example on a
compact disc. There are different archiving options, for example:
Saving the transport files of the transport request of copies. To do
this, create a transport request of copies to which all the objects that
you want to delete are assigned. Releasing the transport request of
copies creates a transport file with the current active version of the
objects. In a next step, you create a workbench transport request
that 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 active
version of the object to the presentation server so that you can store
it on a compact disc.
All archiving tools face one common issue. As the length of time since
deleting the object increases, re-importing the object becomes
increasingly difficult. This is because related standard SAP objects may
be changed, or even deleted, because of a support package
implementation or a system upgrade.
Upgrade/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.
Upgrade/Change Impact Analysis –

Check for success

Upgrade/Change Impact Analysis –
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
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.
Upgrade/Change Impact Analysis –

Knowledge Base:
If the user has chosen to use the
Knowledge 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 Knowledge Base.
Upgrade/Change Impact Analysis –

For a concrete UCIA project, the

preparatory steps are as follows:
Setting up the system landscape
Considering the relevant SAP Notes
Maintaining project-specific adjustment
times (if required).
Upgrade/Change Impact Analysis –
Analysis Results

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
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.
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 Inconsistencies
This activity obtains the list of objects from
TADIR, checks the existence of the objects
in the system and provides the status.
CDMC – Additional Functions

Unicode Check
This activity can be executed only on higher versions
of SAP R/3, and is used to check a program set for syntax
errors in a Unicode environment.
This activity runs the ABAP Unicode Scan Tool UCCHECK
The transaction UCCHECK is used to examine a Unicode
program set for syntax errors without having to set the
program attribute "Unicode checks active" for every
individual program. From the list of Unicode syntax errors,
you can go directly to the affected programs and remove
the errors. It is also possible to automatically create
transport requests and set the Unicode program attribute for
a program set.
CDMC – Additional Functions

Determine Active User Exits

This activity gives the active user exits for
the selected development classes.
The purpose of this activity is to obtain the
list of active user exits (Function Exits) for
the selected development classes.
CDMC – Additional Functions

Delete Mod. Logs of Deleted Objects

This activity provides an option to view the list of
deleted objects and to delete the modification logs of
the deleted objects in the selected remote system.
This activity submits the Report
RS_SMODILOG_FIND_DEL_OBJ in the selected
destination system. The report
deleted sub objects (LIMU) and the higher-level
complete objects with a separate object catalog
(R3TR), for which only the modification logs exist.
These objects were modified by the customer and
deleted during an upgrade or the import of a Support
CDMC – Additional Functions

Check tables for Client Transport against Target System

This activity is run in the selected remote system and is
used to check the structure of tables for client transport
against the target system.
This activity submits the report RSCLICHK in the selected
remote system.
This program will give information about the missing
definitions from the data dictionary in the target. After
executing this program and getting successful results we
can ensure that the client copy will have no problems. In
case some tables are different; you can use SE11 to
compare and adjust the table structure in both the system
before the client copy. A remote test client copy also can be
executed to know the differences between source client and
target client.
CDMC - Lessons Learnt

Decisions to use CDMC comes to late to
assist in upgrades/patch implementations
No time to analyze reports
Knowledge to use CDMC is limited
Outdated software and prerequisites
Outdated performance data
Performance data to analyze statistics is
not “old” enough – check and adapt ST03N
Thank You

Questions ?