Document Version: 1.

0 – 2016-11-07 CUSTOMER

Troubleshooting Reports for Note Assistant

Typographic Conventions

Type Style Description

Example Words or characters quoted from the screen. These include field names, screen titles,
pushbuttons labels, menu names, menu paths, and menu options.
Textual cross-references to other documents.

Example Emphasized words or expressions.

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, table names, and key concepts of a programming language when they
are surrounded by body text, for example, SELECT and INCLUDE.

Example Output on the screen. This includes file and directory names and their paths, messages,
names of variables and parameters, source text, and names of installation, upgrade, and
database tools.

Example Exact user entry. These are words or characters that you enter in the system exactly as
they appear in the documentation.

<Example> Variable user entry. Angle brackets indicate that you replace these words and characters
with appropriate entries to make entries in the system.

EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .

CUSTOMER Troubleshooting Reports for Note Assistant

2 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Typographic Conventions
Document History

Version Date Change

1.0 2016-11-07 Version 1.0

Troubleshooting Reports for Note Assistant CUSTOMER

Document History © 2016 SAP SE or an SAP affiliate company. All rights reserved. 3
Contents

1 Troubleshooting Reports for Note Assistant ............................................................................ 5

1.1 Identifying Dependent SAP Notes ....................................................................................................... 6
1.2 Identifying Prerequisite SAP Notes ..................................................................................................... 7
1.3 Identifying Objects Affected by an SAP Note ..................................................................................... 9

CUSTOMER Troubleshooting Reports for Note Assistant

4 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Contents
1 Troubleshooting Reports for Note
Assistant

Introduction

While trying to implement or reset an SAP Note (target SAP Note), there are several objects, prerequisite SAP
Notes, or dependent SAP Notes that are affected. It is important that you are aware of the impact of the process
of implementing or resetting an SAP Note. Therefore, there is a need to check for the following:
 Relevance of the SAP Note.
The corrections of the SAP Note being implemented or reset are valid to your system.
 Objects affected by the SAP Note.
The status of the object is active or inactive.
 Required prerequisites SAP Notes
The status of prerequisite SAP Notes is completely implemented, partially implemented, or not implemented.
 Required dependent SAP Notes
The status of the dependent SAP Notes is completely implemented, partially implemented, or not
implemented.
The inconsistent status of the affected objects, prerequisite or dependent SAP Notes can lead to further
inconsistencies of the target SAP Note. It is also tedious and time consuming to check manually all the objects,
prerequisite SAP Notes, or dependent SAP Notes embedded in nested layers. You can use the available reports
to troubleshoot some of the issues. The main objective of these reports is as follows:
 Identify the root cause and troubleshoot issues that hamper implementing or resetting of SAP Notes using
transaction S N O T E .
 Locate the SAP Note that is causing an issue more accurately and quickly.
 Avoid manual checks that is time consuming and tedious.
Following are the reports that are available and their purposes:

Reports Purposes

SCWN_NOTES_SUCCESSORS_CALC Identify the dependent SAP Notes getting affected

during resetting of any SAP Note.
For more information, see Identifying Dependent SAP
Notes.

SCWN_PREREQUISITE_CALC_SWI Identify the prerequisite SAP Notes that are nested in

several layers during implementation of a particular
SAP Note.
For more information, see Identifying Prerequisite
SAP Notes.

SCWN_OBJECT_LIST_CALC_SWI Identify the objects affected by an SAP Note and their

statuses during implementation of that SAP Note.

CUSTOMER
Troubleshooting Reports for Note Assistant © 2016 SAP SE or an SAP affiliate company. All rights reserved. 5
 For more information, see Identifying Objects
Affected by an SAP Note.

Note
The system displays the output of the report in an ALV tree view. The output in the ALV tree includes the SAP
Notes that are valid for your system but does not include all the dependencies maintained in the SAP Note. The
output also depends on your system release and support package.

1.1 Identifying Dependent SAP Notes

Whenever you try to reset an SAP Note, you encounter notifications indicating that the SAP Note that you are
trying to reset is required by another SAP Note, and so on. To reset an SAP Note, first you reset the dependent
SAP Notes.

The SCWN_NOTES_SUCCESSORS_CALC report quickly fetches the dependent SAP Notes that are affected and
nested in several layers. Using this information, you can analyze the effort required to reset an SAP Note.

Note
o For SAP NetWeaver release 702 and below, you reset the dependent SAP Note first before resetting the
target SAP Note.
o For SAP NetWeaver release 730 and above, the system resets all the dependent SAP Notes available in
nested layers.

Prerequisites

You have implemented the SAP Note 2258238.

Procedure

1. Go to transaction SE38
2. Run the report SCWN_NOTES_SUCCESSORS_CALC. The report requires an SAP Note as the input parameter
and this SAP Note is known as the target SAP Note. On execution, the system displays the output in an ALV
tree view with the following details:
o SAP Notes - Input parameter or the target SAP Note and dependent SAP Notes, hierarchy of the SAP
Note
o Correction Instructions (CI)
o Version implemented or downloaded
o Status of the SAP Note
o Level of dependency

CUSTOMER Troubleshooting Reports for Note Assistant

6 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Troubleshooting Reports for Note Assistant
 The level of dependency is based on the level of the correction instruction but not on the SAP Note level.
The highest level of dependency indicates the first SAP Note to be reset.

The figure describes the various levels and their description.

Figure 1: Level of Dependency for Dependent SAP Notes

Based on the results of these levels, you can analyze, which successor or dependent SAP Note has to be
reset.
o Date of the last action performed on that SAP Note
o SNOTE latest log details
o Transport request in which the correction instructions are locked.

1.2 Identifying Prerequisite SAP Notes

You use the SCWN_PREREQUISITE_CALC_SWI report to determine all the prerequisite SAP Notes and even the
level of its dependencies when you are implementing an SAP Note. This report easily identifies the prerequisite
SAP Notes that are not implemented correctly.

Prerequisites

You have implemented the SAP Note 2258238.

Procedure

1. Go to transaction SE38

CUSTOMER
Troubleshooting Reports for Note Assistant © 2016 SAP SE or an SAP affiliate company. All rights reserved. 7
2. Run the report SCWN_PREREQUISITE_CALC_SWI. The report requires an SAP Note as the input parameter
and this SAP Note is known as the target SAP Note. On execution, the system displays a list of prerequisite
SAP Notes in an ALV tree view with the following details:
o SAP Note - Input parameter or the target SAP Note, hierarchy of the SAP Notes
o Required or prerequisite SAP Notes
o Correction Instructions
o Level of dependency
The level of dependency is on the correction instruction level but not on the SAP Note level. The highest
level of dependency indicates the first SAP Note to be implemented.
The figure describes the various levels and their description.

Figure 2: Levels of dependency for prerequisite SAP Notes

Based on the results of these levels, you can analyze, which prerequisite SAP Note has not been implemented
properly.
o Version implemented or downloaded
o Status of the SAP Note (overall)
o Date of the last action performed on that SAP Note
o SNOTE latest log details
o Transport request in which the correction instructions are locked.

CUSTOMER Troubleshooting Reports for Note Assistant

8 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Troubleshooting Reports for Note Assistant
1.3 Identifying Objects Affected by an SAP Note

There are times when you implement an SAP Note and some of the objects touched by the SAP Note are inactive.
You use the SCWN_OBJECT_LIST_CALC_SWI report to check all the objects touched by the target SAP Note and
its prerequisites during implementation of the SAP Note.

Prerequisites

You have implemented the SAP Note 2258238.

Procedure

1. Go to transaction SE38
2. Run the report SCWN_OBJECT_LIST_CALC_SWI. The report requires an SAP Note as the input parameter and
this SAP Note is known as the target SAP Note. On execution, the system displays a list of objects in an ALV
tree view with the following details:

Figure 3: List of objects with statuses

o SAP Note - Input parameter or the target SAP Note
o Objects touched by the SAP Note
o Object type - Report, methods, classes, and so on
o Object status - Active or inactive
o Object modification date - If the object is inactive, the last modified date is displayed.
o Version implemented or downloaded
o Status of the SAP Note (overall)
o Date of the last action performed on that SAP Note
o SNOTE latest log details

CUSTOMER
Troubleshooting Reports for Note Assistant © 2016 SAP SE or an SAP affiliate company. All rights reserved. 9
 o Transport request in which the correction instructions are locked

Note

Manual correction instructions do not have any status.

CUSTOMER Troubleshooting Reports for Note Assistant

10 © 2016 SAP SE or an SAP affiliate company. All rights reserved. Troubleshooting Reports for Note Assistant
[Link]/contactsap

© 2016 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of
SAP SE (or an SAP affiliate company) in Germany and other
countries. All other product and service names mentioned are the
trademarks of their respective companies. Please see [Link]
[Link]/corporate-en/legal/copyright/[Link]#trademark for
additional trademark information and notices.

Material Number: