Show TOC

Procedure documentationDefining Systems and Scheduling Data Collectors in the Settings View Locate this document in the navigation structure

 

In the Settings view, you select a solution for Custom Code Lifecycle Management. You set up and schedule data collection jobs to extract data for Custom Code Management.

The Systems screen area lists all the systems that are assigned to the selected solution, along with basic information about the systems.

You define whether the selected system is a lead system, that is, the system in which the object is created, normally the development system.

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 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.

The Status column indicates the status of each system or data collector. The following statuses are available:

Green LED indicator (Green LED indicator)

All data collectors are scheduled and there are no errors

Yellow LED indicator (Yellow LED indicator)

At least one data collector is not yet scheduled

Red LED indicator (Red LED indicator)

At least one data collector was terminated

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 is activated in your systems

Procedure

Defining the Scope for Data Collection Jobs

  1. In the Systems screen area, in the Solutions dropdown list, select a solution. The systems that are assigned to the selected solution are displayed.

  2. Select a system.

  3. Define the scope for the data collection. You can specify which objects the system collects using the following settings:

    • To collect all data, choose Maintain Lead System to select the Lead System checkbox.

    • To only collect new custom objects and changes to existing custom objects, choose Maintain Lead System to deselect the Lead System checkbox.

    • To include local objects ($TMP), choose Local Objects to select the Local Objects checkbox.

    • To exclude local objects from the collection, choose Local Objects to deselect the Local Objects checkbox.

Scheduling Data Collection Jobs

  1. In the System screen area, select a system and define the scope for the data collection. The data collectors for this system are displayed in the Details of System screen area, along with basic information about the data collectors.

  2. In the Details of System screen area, select a data collector.

  3. Choose Schedule Job.

The data collector is scheduled automatically for the next possible date.

Note Note

To cancel a scheduled job, choose the job name of a data collector to call transaction SM37. In this transaction, you can cancel jobs or make changes to the job schedule.

End of the note.
Scheduling Data Collection Jobs for a Specific Time

You may sometimes need to set a specific time for a data collection job, for example, to prevent conflicts with other scheduled jobs or to avoid overloading the system by running too many jobs simultaneously.

Proceed as follows:

  1. In the Details of System screen area, choose the job name of a data collector to call transaction SM37.

  2. In this transaction, schedule the job to start either at a specific time or after an event is completed, for example, SAP_ARCHIVING_DELETE_FINISHED.

  3. Confirm your selection.