Defining Systems and Scheduling Data Collectors 
To extract data for Custom Code Management, you need to set up and schedule data collection jobs.
You define whether the data collectors collect local objects. Local objects are all objects created in development class $TMP. You do not usually collect local objects in a development system because they can interfere with developer tests. Local objects are never transported to a production system. However, if an object is developed directly in a production system, we recommend collecting this information to ensure transparency.
You can schedule the following data collectors for each system:
SM_CCL: OBJECTS_<SID>_<installation number>: Collects the custom objects and extracts data about custom code objects from managed systems. Switches to transaction SM37. Make sure that you schedule this job so that the system collects the data periodically.
SM_CCL: QUALITY_<SID>_<installation number>: Collects data from the Code Inspector. Provides details about level of quality based on Code Inspector results from the managed systems.
SM_CCL: STATM_<SID>_<installation number>: Collects the monthly workload data from transaction ST03N only. Provides monthly usage information based on EarlyWatch Alert (EWA) data directly in SAP Solution Manager.
SM_CCL: STATW_<SID>_<installation number>: Collects the weekly workload data from transaction ST03N only. Provides weekly usage information based on EWA data directly in SAP Solution Manager.
SM_CCL: UPL_<SID>_<installation number>: Collects the daily usage based on SAP NetWeaver Usage Procedure Logging (UPL), including dynamically called custom objects.
SM_CCL: SIMILARITY_<SID>_<installation number>: Collects information about custom code objects that are copies of SAP standard objects (clones) based on SAP Clone Finder.
SM_CCL: ATTRIBS_<SID>_<installation number>: Collects information about customer-specific attribute values. For this job, you have to create a customer-specific development to collect the information.
Prerequisites
There is at least one solution with logical components and systems
EarlyWatch Alert (EWA) is configured for the systems. The data collectors read the usage statistics from the EWA download
A library definition is created as the active library during the technical implementation
Usage and Procedure Logging (UPL) is activated in your systems
More Information
You define systems and schedule data collection jobs in the Custom Code Management (CCM) scenario in SAP Solution Manager Configuration (transaction SOLMAN_SETUP). For more information, see the help texts in corresponding guided procedure.