Skip to end of metadata
Go to start of metadata

Introduction

This document describes the use of Configuration Validation in the context of Software level validation. The Configuration and Change database (setup via RCA setup) collects for each technical system of type ABAP the currently implemented software components and their release.  A Config Store called ABAP_COMP_SPLEVEL contains the recorded info on implemented software components. The example uses a Solution Manager 7.10 where a development System (SD7 as DEV) and an integration system (SI7 as PROD) are connected to as managed systems.

Where can I find Configuration Validation?

Configuration Validation can be found in the Workcenter Change Management in Related Links. You can start Solution Manager Workcenter either via direct URL link or via the transaction SM_WORKCENTER from the SAP GUI


Which Config Stores are relevant for Software compliance and where can I find them?

You can see the content of Config Stores in the Change Reporting application. Navigate in the SAP Solution Manager to the Root Cause Analysis work center à System Analysis. Then select a required system and start Change Reporting via the button .


From the displayed tree select the group ABAP_SOFTWARE. In this group you will find the Config Stores relevant for Software validation. As soon as you click on the name of store you would see the content of store


ABAP_COMP_SPLEVEL

The Config Store ABAP_COMP_SPLEVEL contains information on the applied components and release level. Let us have a look at the examples of software level validation using this Store.

Validation of the current Software Level of an existing System

It is possible to compare the current Software Level of several systems directly using an existing System as a reference. And it is not necessary to create a target system to get this information.

In our example we are going to validate the current software level of the development system SD7 against the production system SI7.

Selecting Reference and Comparison System

To start validation for an existing system we navigate to the Tab “Report Execution” in the main window of Configuration Validation application. In the left part of the section “Reference System and comparison systems” we type in the input field SD7 and deselect option “Only Target Systems” to display existing systems.


In the right part we are selecting Comparison List S7_LINE that includes both SD7 and SI7. If no comparison lists are defined yet, skip this step and select the comparison system in the variable screen afterwards.


Choose a validation template

In the next step we select a corresponding report for validation. The report 0TPL_OSMD_VCA2_NCOMPL_CI_REF provides an initial drilldown for “non-compliant items only” and all the non compliant items relevant for the software level will be displayed in the initial drilldown.


After the validation template is selected the validation could be started via the link

.

You will be prompted to check the input data. It is necessary to insert ABAP_COMP_SPLEVEL into the input field Config Store to restrict validation only for Software Level.


Click the button to start validation.

Output




The initial view displays only the configuration items (COMPONENT + RELEASE) that exist both in the reference and comparison systems but having different value for the field EXTRELEASE, because the default setting for Compliance is ‘No’. In our example there are no entries that meet this restriction.

To display also missing or additional items you need open Navigation Block at the left side and click on the Compliance filter:


From the displayed Pop-up window you should select option “Item not found” and “Additional in Comparison System”. And click the button “Transfer” at the bottom left part of the window.


The displayed list now includes both the configuration items that do not exist in the comparison systems (In the column “Compliance” they have the value “Item not found”) and the configuration items that exist only in the Comparison System (In the column “Compliance” they have the value “Additional in Comparison System”).


It is possible to see the validation details for the entries which are valuated with Compliance ‘Yes’ or ‘No’ . Perform right mouse click on any entry. Select from the context menu ‘Goto > Config. Validation - Items - Validation Details’


In the displayed table you will find the detailed information for the validation of the selected entry. From this table you can see that the Component AOFTOOLS with the release 400_620_09 is valuated as not compliant because is not found in the comparison system .


Validation based on customer defined Configuration Baseline

In some cases the configuration of existing systems cannot be used as the reference system and it is easier to define a software level manually and compare systems against this predefined configuration baseline. In this case we will create a Target System and modify its content in accordance to configuration baseline requirements.

Creating Target System for Software Validation

To adjust values and parameters for validation example we would create a Target System with a copy of Stores for Software Validation

Navigate to Configuration Validation > “Target System Maintenance” > “Create” and display the system SD7 (type SD7 in the field System ID in the Detailed Selection and click the button ). Filter the stores from the group ABAP_SOFTWARE (use the first line of the table).


Select all the filtered Stores via the button and click the button to create Target System with these Stores. In the Displayed pop-up provide Target System Name and description for the Target System.




Result: The Target System S7SOFTWA is created and the content of Config Stores is copied from CCDB into this Target System.

Edit Target System

After the Target System is created you can edit the Store ABAP_COMP_SPLEVEL and add or remove the validated components and release level.

Navigate to the Configuration Validation > “Target System Maintenance” > “Edit” and display the created Target System S7SOWTWA (type the Target System name in the field Long SID in the Detailed Selection and click enter button or ). The selected Target System will be displayed at the left side. At the right side the corresponding Stores will be displayed. Select the store ABAP_COMP_SPLEVEL to edit its content.


The current content of this store will be displayed in the table below:


We are going to restrict the validated configuration items and apply operators. For that we select only some of the components and delete other via the button to delete unselected items. Finally we have the following list of configuration items to be validated:


In the next step we would quickly change operators for all the entries via the button so that the current values of the configuration items reflect the minimum software level for compliance.

In the displayed popup select the row for EXTRELEASE and choose the operator greater then (>=) and click the button to apply operators for the selected entry.


The content of the store is refreshed to display the applied operators


(You can click on the button to display some examples of using operators):


Click the button to save the changes in the Config Store.

Select your target system and the validation report

You can preselect the reference system with the current Target System for Configuration Validation via the button in the top menu.


This starts the Report Execution tab and the Target System would be selected as the reference system. Select the list of the systems to be compared (in our case it is FIX_ABAP). The report 0TPL_0SMD_VCA2_NCOMPL_CI_REF provides only non compliant items in the initial result


Click the link to executed validation report.

In the displayed pop-up the target system S7SOFTWA is used as the reference. For ‘comparison systems’ the systems from the comparison list are used.

Select the Config Store ABAP_COMP_SPLEVEL to validate only software level from this store and click the button execute.


Output

In the displayed table four items are displayed as non compliant.


The details report that you get via the context menu (right mouse click on the note number) by selecting ‘Goto’à Config.Validation – Items – Validation Details may help to understand why the comparison system is not compliant related to the selected configuration item.


For example:


This screen shot shows that the Component ST-PI with the release 2008_1_700 does exist in the comparison system Q7P but the EXTRELEASE 0002 does not fit the conditions >= 0003 as it is defined in the Target System.

Find all Systems with a specific Software Component

We can use Configuration Validation application to quickly find all the systems with a specific software component. For example it could be done as a preparation for an upgrade project to define potential candidates for upgrade.

Prepare dynamic comparison list providing all ABAP systems

We are going to find all the ABAP systems with the Software component SAP_BASIS equal to 702. For that we would use a comparison list that dynamically provides all the systems of type ABAP.

You can create such a dynamic comparison list via the link in the “Report Execution” tab (alternatively you can navigate directly to the tab “Comparison List Maintenance”).


You will be navigated to the tab “Comparison List Maintenance”. In this tab click the button to create a new comparison list.


In the displayed popup window provide list name and description and type ABAP in the field “System Type”. Save the list via the button .


Return back to the Reporting tab via the link (or navigate directly to the “Report Execution” tab):


Select the created comparison list in the right table.


Now we have the reference system and the list of the systems to be compared selected.

Use of Configuration Reporting

In case reporting you are not interested in a validation it is easier to use Configuration reporting.

In this example we would use Configuration Reporting to display all the systems having a particular level of the software component SAP_BASIS without validation. For Configuration Reporting no Target System is required since we are not comparing systems but displaying data from the Configuration Change Database (CCDB).

Choose a configuration report

Navigate to the tab “Reporting Execution” of the “Configuration Validation” application and select dynamic comparison list created in the previous example (reference system is not required for configuration reporting):


Select the operator validation template 0TPL_0SMD_VCA2_CITEMS_REF that shows all the configuration items and start validation via the link


We know that the configuration data on the software component SAP_BASIS stored in the Config Store with the name “ABAP_COMP_SPLEVEL” Provide this info in the corresponding input fields of the pop-up window. For the Configuration Item use the F4 Help to find the correct value:




Type in the input field “SAP_BASIS” and click the button “Find” to find in the list of the available configuration items only those that could be relevant to SAP_BASIS. Select the item COMPONENT:SAP_BASIS;RELEASE:702; and click the button “Transfer”


In the Variable screen click the button “Execute”


In the displayed table all the systems from the comparison list that have the SAP Basis component equal to 7.02 will be displayed.


This page is part of the Application Operations Wiki. Notice that Application Operations itself is a use-case of SAP Solution Manager

  • No labels