Skip to end of metadata
Go to start of metadata

Introduction

This document describes the use of the Report Directory of the Configuration Validation to explore Configuration Items, e.g. ABAP transport requests. The Configuration and Change database (setup via RCA setup) collects for each technical system of type ABAP the import history of transports starting with the setup day. A config store called ABAP_TRANSPORTS contains the recorded transports. 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.

Use Cases:
The QM team needs the information about the production backlog of the transports requests or about failed imports. With the help of the report directory these information is provided quickly.

The security team has created a target system for security related items. For the Security notes an ABAP_NOTES config store is filled. After the patch day SAP has provided additional security notes. An update of the content of the config store ABAP_NOTES of the target system has to be done. This document describes how to use the current SAP security notes without changing the before created target system.

Where can I find Configuration Validation?

Configuration Validation application can be found:

Ÿ SAP Solution Manager 7.0 EhP1 / 7.10 

 - In Work Center Change Management in Related Links

 - Via SAP Easy Access

Ÿ SAP Solution Manager 7.10 SP05

 - In Work Center Change Management in Related Links

 - In Work Center Root Cause Analysis

 - Via SAP Easy Access


Where can I find the used config stores and have a look at the data?

Work Center Root Cause Analysis (RCA) > System Analysis > Change Reporting

The extraction of the data is scheduled as soon as a “Root Cause Analysis Set Up” has been performed for a system.



Preparation

To demonstrate the functionality of the Reporting Directory we will use the Target System S7PRDBLG that have been created for the section “ABAP transport reporting with 710” for the “Prod backlog” example. This Target System is created from the store with the name ABAP_TRANSPORTS of the source system SD7. The content of this Target Store has been restricted to the transport request which are created in the system SD7 and having TRSTATUS not equal to “D”.

Reporting Directory: store input data

For each execution of a Validation Report it is necessary to provide several input data: Reference and Comparison Systems, Validation Template, startup parameters as well as a restriction on the Date Range for Transports and the Config Stores to be validated (see the picture below).


To avoid these efforts for regular execution of the same Validation Report it is possible to store all the input data in the Report Directory and reuse them each time, when the Report is executed (see the picture below).
To display Report Directory please navigate to the tab "Report Execution" in the section "Report Directory". In the picture below you can see the User Interface of Report Directory. 

Advantages of  Report Directory

Customer reports

  • ŸAll input parameters required for Configuration Validation reporting are stored for one click execution or a further maintenance. Ÿ
  • Reports for different use cases could be organized via customer defined groups.
  • Custom operations for reports. ŸIt‘s possible to add certain content dynamically to an existing target system. For example replace the ABAP_NOTES store with the latest list of SAP security notes from the online recommendations

Predefined SAP reports

ŸFor typical use cases such as Production Backlog reporting, validation of security relevant SAP Notes, finding failed transport requests, etc. SAP provides automated reports. For these reports a Target System is dynamically created and filled with the corresponding data to minimize manual efforts.

After a previously saved report is selected from the list it’s just a click on the button “Start Report”.

How to create a new report in the Report Directory

For our example we would create a new report to display the “Prod Backlog” described in the chapter “ABAP transport reporting with 710”. For this report the Target System S7PRDBLG has been used and the compared system was SI7.

To create a report, please navigate to the Report Directory that you can find in the “Report Execution” Tab:


You will see the list of all available reports. Click the button to create a new report.

Provide all the necessary data in the displayed form. To provide the validation template click the button at the right side. In the displayed pop-up window select the corresponding validation template and click the button .



You can enter any text in the field “Report Group”. For our example we use ‘Transports’. This field is used to group the reports in accordance with customer own requirements.

At the next step you need to provide a Reference System. Please use the button at the right side.

In the popup window you can select the reference system. It could be either a Target System or an existing system. In our case the system “S7PRDBLG” is used.


After the Reference System is selected the corresponding entry is filled:


You can also restrict the validated stores. Click the button at the right side and select the stores to be validated. In our case there is only one config store in the Target System, so there is no need to select and restrict the config stores.

At the next step provide the systems to be compared. In the popup window you can select either the comparison list or the single systems.


To select the single systems from the list please select the comparison list


At the tab “Single Systems” click the button to display single systems from the list.


Optionally you can provide a date range for the Transport Requests to be validated. By default the last seven days are proposed for the date range.


You can also provide the startup options and filter values for the validation report.


Click the button to save the report in the Report Directory.

Execution of validation report via Report Directory

At the top menu of Report Directory there are the buttons for a quick filter of the displayed reports. To display reports created by your user click the button .


Select the required report from the list and click the button at the bottom part of the screen. The variable screen will be displayed except the option ‘Suppress query variable pop-up’ had been selected.


Click the button “Execute” to get the validation results:


How to create a new report in the reporting application

Another variant to create a new report in the Report Directory is to use the option “Save selection” in the area Reports. Provide the name for the report and click the button


The reference system as well as the comparison list and validation template will be stored in the Report Directory. For editing or providing further input data please navigate to the “Report Directory” Tab.

Dynamic Custom Operations of reports

Optionally you can add dynamic Custom Operations that will be executed before starting the report. These operations can be added to you report via the button . In the pop-up window you would find dynamic operations to:

*Add the highest SAP Kernel from the online recommendations (SAP Security list).
*Add latest released ABAP Support Package
*Add SAP Notes from the online recommendations (SAP Security list)


The goal of custom operation is to add content to the reference system dynamically before the report execution is done. For that a new Target System will be created containing both the dynamically generated content and the content from the original reference system. This Target System will be used for validation instead of the original Reference system. The name of this Target System can be seen in the initial screen after any Custom Operation is selected:


Note: The generated Target System is available only at the time of report execution. After you select another report all unused generated Target Systems will be deleted.

For the mentioned use case that a target system for security had been defined and the actual SAP Notes from the security list should be used without touching the target system the Custom Operation “Add SAP Notes from the security list” offers the solution:


If a Reference System is provided in the corresponding field (in our case it is SI7), then only the SAP Notes relevant for this system will be inserted (that are the SAP Notes matching ABAP Component and Kernel Release of the Reference System).

If the checkbox “Replace Original” is selected then the content of the store ABAP_NOTES will be replaced with the generated one. In case this checkbox is not selected the generated content and the existing one will be merged together.

Predefined SAP Reports

SAP delivers with the Report Directory some predefined reports for typical operations. These reports can be displayed via the quick filter button .


All these reports are generating a Target System with the corresponding content.

Note: The generated Target System is available only at the time of report execution. After you select another report all unused generated Target Systems will be deleted.

0SECNOTE - Validation of SAP Notes using online recommendations

For the validation of SAP Notes we use only notes that are available in the online recommendations and that are automatically checked in Early Watch Alert. You can find them also in SAP service market place https://service.sap.com/securitynotes. These notes have an X for ‘Automatic check in EWA (*)’:


The complete list of these notes will be used in the Configuration Validation. Select the predefined report 0SECNOTE from the list:


To display the detailed information on the predefined report click the button . The detailed description will be displayed in the pop-up window:


After the report is selected you need to provide some information for validation report.

To provide the systems to be validated click the button . In the displayed pop-up select either a comparison list or the single systems.


In our case the systems from the comparison list “FIX_S*” will be selected for validation.


After you are provided the comparison systems you can execute the report via the button . The Target System 0GNRT001 will be generated and used for validation.


The output displays 10 notes per page of overall 42 notes with Compliance ‘No’:


Optionally you can select in the report directory whether the SAP Notes of the online recommendation available for all kernel releases and software components or only SAP Notes that relevant for one of the systems are validated:

No restrictions - SAP Notes for all the kernel releases and application components will be added


The generated ABAP_NOTES config Store of the target system will contain all notes for this option.


Restrict as per Reference System – only those SAP notes will be added which are matching kernel release and application components of the reference system (in this case SD7).



Restrict as per Component and / or Release – only those SAP notes will be added which are matching related to the kernel release and application components provided in the input fields



0PRDBLG Reporting of Production Backlog

To validate the production backlog select the 0PRDBLG report from the list:


To display detailed description for this report click the button . A dialog screen will pop-up:


In the selection screen provide a development and a production system for validation. In our case they are the system SD7 (DEV) and the system SI7 (PROD)


Click the button to execute the report. This will create the target system 0GNRT001 with the ABAP transport requests of the development system and date range.


The Validation report will display all transport requests of the development system that are not found (Compliance ‘Item not found’) in the production system


0BADTRAN Finding failed transports

To find the transports which are failed (RETCOD > 4) select the report 0BADTRAN from the list.


In the displayed form provide the systems to be validated.


Click the button to execute the report.

The Target System 0GNRT001 will be generated for validation:


This definition means that all transport requests with return code 4 or less are fine. All others are valuated as non compliant in the report:


In our example two transport requests had been found.

0SPLVCHK Validation of Support Package level using the latest release


The goal of this report is to find the differences between the Support Package Levels of the compared systems and the latest released Support Package.

For this purpose a Target System will be generated and filled with the data of the latest released Support Package Level.

To execute the report please provide the systems to be compared from the list of the existing systems. This list is displayed when you click the button at the right side of the corresponding field.


After the system is provided click the button to start report. At this point a new Target System will be generated and filled with the data.


Output:


Detailed results for the BI_CONT component


Note: You have the possibility to restrict the validated components. Additionally you can define the difference between that latest released and the accepted Support Package Level of the compared systems.

To provide these restrictions you need to select first the compared systems and then click the button at the right hand side of the option "Components & differences to the latest released SP level". In the displayed pop-up window select the components to be validated and the accepted difference.

By default all the ABAP and Java components will be provided with the current release:


In this dialog you can filter the components, e.g. to all ABAP components starting with SAP*. For these you can define the ‘Allowed difference’, e.g. to2, which means that not the actual SP level is used for the validation, but “latest – 2”.


The generated Target System which is used for the validation will be generated according this definition:


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

  • No labels