Function documentationConfiguration Validation Locate this document in the navigation structure

 

Configuration validation determines whether the systems in your landscape are configured consistently and in accordance with your requirements. You can validate the current configuration of a system in your landscape by comparing it with a target state (system) or an existing system. You can answer the following questions, for example:

  • Have all transports from the development system arrived in the production system?

  • How long did a transport take to get from the development system to the production system after it was released?

  • Have particular notes been imported into the production system?

  • Have the desired security settings been made in the production system?

Integration

The configuration verification is based Change Reporting. For more information, see Change Reporting.

Prerequisites

For information about the prerequisites for using the configuration verification, see SAP Note 1478974.

Features

  • Defining a reference system

    The reference system contains the target configuration data that is compared with actual data. A reference system can be a user-defined target system or an existing system.

    • Creating a target system: You can use the configuration data from existing systems, which is extracted from the managed systems and stored in the configuration and change database. You augment the target configuration data of the target system with operators, in the configuration verification application. The target system is stored, with its target configuration data, in a separate table. For more information, see Creating a Target System.

      Note Note

      Changes to the original configuration data of the target system are not recorded.

      End of the note.

    • Using an existing system: The saved configuration data of an existing system is used in the reference system.

  • Editing configuration data

    When you create the target system, you can specify the configuration data using operators. You can obtain information about the various operators by clicking the Display Compliance Key button.

  • Defining comparison lists

    If you want to compare reference systems with your existing systems regularly, you can define comparison lists. These contain all comparison systems available for the configuration verification. You do not then need to select systems each time you verifiy a configuration; you can use the list of comparison systems. You can define a new comparison list or modify an existing one.

    For more information, see Creating Comparison Lists.

  • Executing the verification report

    After defining the reference system and (optionally) a comparison list, you can execute the configuration verification report. There are various report options.

    The system compares the configuration elements of the comparison systems with the corresponding elements of the target systems, using the operators defined there. Each configuration element is verified. If the value of the element in the comparison system fulfills the condition of the operator defined in the target system, it is rated compliant.

    If any element in a configuration store is not compliant, the entire configuration store is rated non-compliant. The same applies to a system: If any element in a configuration store is not compliant, the entire system is non-compliant.

    For more information, see Executing the Report.

Activities

You perform the following steps in the configuration verification:

  1. Call the configuration verification in the Change Management work center, under Related Links

  2. Define a reference system

  3. Define a comparison list

  4. Execute the verification report and select a report variant

  5. Adapt the report output to your requirements