Configuration validation determines whether the systems in your landscape are configured consistently and in accordance with your company’s requirements. You validate the current configuration of a system in your SAP landscape by comparing it with a target state (system) or an existing system. Examples of questions that can be answered by configuration validation include:

  • Have all transports from the development system arrived in the production system?
  • How long did a transport take to move from development to production after release?
  • Are the client settings consistent across the SAP estate?
  • Is the kernel patch level consistent in the landscape?
  • Are the company standard security settings consistent across the landscape?

The main components that make up Configuration Validation are:

  • Comparison Lists
  • Target Systems
  • Configuration Stores

Understand these components and how they interact and you’ll soon crack Configuration Validation. So what are they?

Comparison Lists

Comparison lists define the systems to be compared to reference systems on a regular basis. These lists contain the comparison systems not the reference system. Typically, a comparison list will contain systems in the same landscape (e.g. ECC) or of the same type (e.g. production systems). They are referenced in reporting so that you no longer need to select individual named systems each time you verify a configuration.

Target Systems & Configuration Stores

Target Systems and Configuration Stores work together to define which systems and parameters will be used when running comparison reports. Hence, they are discussed together in this section.

The reference system contains the target configuration data that is to be compared with actual configuration data. A reference system can be a user-defined target system or an existing system. The reference system becomes the target system for the comparison, hence the term Target System.

Once you have created the target system you have to assign one or more configuration stores to it, which forms the basis of the configuration objects being validated.

If you’re concerned about consistency across your SAP estate, like the idea of being able to validate this configuration using Solution Manager but need additional guidance, get in touch with no obligation mailto:info@aliterconsulting.co.uk