SAP Basis Tech Supports

Symptom

The Web Dynpro ABAP checklist is used for creating problem messages.

Reason and Prerequisites

The Web Dynpro ABAP processing team requires the following information to be able to process messages.
Solution

To avoid possible delays and to speed up message processing by the Web Dynpro ABAP team, review the following checklist before submitting the problem.
SUMMARY
Use the following checklist when you create a customer message regarding Web Dynpro ABAP (component BC-WB-ABA*).
Contact information: Name and telephone number of the reporterLanguage: EnglishSystem information: SAP NetWeaver Release (SAP_BASIS) and Support Package numberProblem description: Name of the Web Dynpro application, URL, step-by-step instructions, screenshots, dumps, and tracesSystem access: Opening of the system, maintain customer logon data

CONTACT INFORMATION
Check that your contact information (name and telephone number) is correct.
We receive many messages that are written by the service user of a colleague. This is fine. However, sign the message with your name and surname so that we know who our (correct) contact person is.
You must also specify a telephone number that we can contact you with, especially if you are not using your own service user.

LANGUAGE
We recommend that you create the message in English.
Both SAP and SAP’s customers (mostly) operate on an international scale. If frequently happens that the same problem is handled by native speakers of different languages. Due to this, we prefer to use only English for all problem handling. (In exceptional cases, we can have texts translated where required.)

SYSTEM INFORMATION
The SAP NetWeaver release and correct Support Package level are import pieces of information for processing the problem.
To determine these, choose “System” -> Status…”. Choose the magnifying glass button (”Component information”) beneath “SAP System Data”. The relevant information is alongside the “SAP_BASIS” entry.
The kernel level is the next relevant item of information. Using transaction SM51, select the application server, and then choose “Release Notes”. The creation date and Support Package details are sufficient.
If you use reverse proxies or Web dispatchers or if you have set up other complex connections, describe briefly how they are configured and connected with the SAP Web application server.

PROBLEM DESCRIPTION
Describe how to reproduce the problem in as much detail as possible.
Enter the name of the Web Dynpro application, the names of the Web Dynpro components and the URL for starting the application.
The best method to use is freestyle text to describe all the necessary steps.
Example:
- Start with URL “http://url…”
- Enter the text “abc” in the input field “klm”
- Choose button “xyz”
and so on.
An important part of the description is what you expected to happen and what you saw/experienced. Keep in mind that we can not always reproduce the error correctly. Your description of what you expected versus what actually happened will help us a lot during troubleshooting.
Attach as many screenshots as possible with a short description. (To save space, we recommend that you save the screenshots as JPG files.) Preferably, combine all screenshots and texts in one document. Then zip and upload the complete document.
If you start the application with a configuration, specify the relevant configuration ID.
Tell us whether the application is personalized using administrator personalization or user personalization.
If you are running your Web Dynpro application in the portal or on a NetWeaver Business Client, check to see whether you can reproduce the problem by calling it directly in a “standalone” environment (for example, when starting it from transaction SE80). If so, tell us the URL of the standalone Web Dynpro application.
We can often read a lot of information from the HTTP trace. This is usually the key to correcting the problem. We recommend that you use an “HTTP sniffer” to trace the customer’s HTTP traffic directly. We use “HttpWatch”
(http://www.simtec.ltd.uk) and can read and analyze trace files directly in this program. Alternatively, you can use “fiddler tools”. These tools have options for saving trace files in text files. Zip these files before you attach them to them to the message.
In addition, always create a trace with WD_TRACE_TOOL (see Note 884424).

SYSTEM ACCESS
1. Service connection
It rarely happens that we can just read the problem message and immediately know the correct answer. In general, we go directly to the system to reproduce and isolate the problem. For this purpose, we require access to the system. Therefore, having your system open helps us a lot when we try to reproduce the problem to minimize processing time.
Web Dynpro ABAP has a lot to do with Web programming. For most problems, we require an HTTP service connection to the system (see Note 592085). If we can access your system directly over the Internet, an HTTP service connection is not required. In this case, we only need the external URL with which we can perform the tests. If problems occur during the HTTP configuration, you can forward the problem to our network specialists (component XX-SER-NET-HTL).
In addition, we require SAP GUI access to be able to set breakpoints and debug the source code.
As an alternative to HTTP and SAP GUI service connections, you can provide us access by setting up a Windows Terminal Server. If you choose this option, you should install SAG GUI and, if possible, a desktop link to the relevant portal on this server. Make sure that a JavaScript debugger and HTTP sniffer (”HttpWatch” or “Fiddlertool”) are installed on this server. Also check again to see whether you can reproduce the problem on the Windows Terminal Server.
If you have a problem with the SAP Interactive Forms by Adobe” solution, a Windows Terminal Server connection is essential.
2. Logon data for all connections
For each connection, we require a user name, password, and client number. Store this information in the “customer logon data” area (Note 508140).
If the problem affects the portal, we also need the relevant user data for the portal service.
In addition, if you have set up a terminal server, we need the logon data for this connection.
To be able to troubleshoot in the R/3 system, we require at least one dialog user with some basic rights and authority. We recommend that this user be authorized to run the following transactions:
SE03+SE09 Transport systemSM04 See sessions listSM50 List processes (relevant long-term problems)SM51 Check kernel versionST22 List dumps and rabaxesSMICM ICM access (HTTP tracing, logging, settings)SICF Check handler configuration for HTTP requestsSE80 Development workbenchWD_TRACE_TOOL (see also Note 884424)DEBUG rights are also required.