Show TOC

SUP.01 What Information should be Included in a Problem Ticket Locate this document in the navigation structure

 

When opening a problem ticket, include as much detail as possible. The more information you give us the easier and speedier we will be able to resolve the issue for you.

What are the more interesting details that we require?

Checklist

System:

Name / Client / Language

The system data, especially the name of the system, the client in the system, and the logon language.

Type of System:

ABAP/Portal

If possible, specify whether it is a direct connection to an ABAP system or a portal connection.

URL:

http(s)://...

Always include the URL that is used to access the system.

Authentication:

User/Password

Provide a user name and password if at all possible. The reason is that nearly in all cases problems are related to the roles that have been assigned to the specific user. We do not require (nor request) your personal user. We need just a separate test user that has exactly the same set of roles assigned.

Shell:

NWBC for Desktop / NWBC for HTML (if important)

Most problems are the same in both flavors of NWBC. However, specifically if the problem is more related to the shell, please include information to indicate whether NWBC for Desktop or NWBC for HTML is being used.

Image(s) or Video:

To navigate exactly to the problem

Include at least one screen shot that shows the complete navigation path to the error. If the error is in a separate window, move the window so that we can see the complete shell, we need to know which work center was selected, and within the work center the exactly navigation path to the error location. Draw on the image if needed. Alternatively, create a low-resolution video.

QM:

SAP internal tickets: Provide the name of your QM, as he is the first person that can help us get any stones out of the way to reproduce an error.

Attachments:

Support report (if NWBC for Desktop is used)

NWBC for Desktop: Always include a support report (see FAQ SUP.04) by using a control-click on the help menu.

Text:

Do write some text to explain the problem as best as possible.

If possible, include a description of the click stream to the error, of the observed behavior and, where applicable, also the expected behavior. Important for us is to understand what the real problem is.