© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
1.0 Known problems and workaroundsWhile recording against SAP applications, sometimes SAP scripting framework internally throws some ABAP errors and recording stops. The problem will not get fixed unless SAP fixes it in their scripting framework.
Workaround: Disable modal search help on the system for the user that runs the script. You can do this in the Preferences dialog in the SAP GUI, from the help menu. If this solution does not work, you may have to restart your SAP application.
The IBM Rational Functional Tester SAP implementation records user interactions with SAP controls only when the SAP client performs a server transaction (For example, on pressing the enter key or execute button or on saving the document). Even though you might have set a value in a text box or changed the state of a checkbox control, you are not able to see the event in the recording monitor immediately. This event is generated only when the SAP client performs a server transaction. If you add a verification point or a data driven command before the server transaction, the script will include the event (verification point or the data driven command) before the previous user interactions, thus causing a change in the order in which you have performed the interactions. The change in order may result in a playback failure.
Example: If you have selected an item from a combo box or set some value in a text control and then added a verification point on these controls before the SAP client has performed the server transaction, the verification point will fail during playback.
Workaround: Perform any of the following:
- Press Enter after you type/select the value in the text/combo box and then invoke the Data Verification Point wizard.
- Or, cut and paste the set method of the text/combo box before the set verification point method in the script.
You may have closed the calendar control after recording a data-driven script and hence a close() event is generated in the script. The script will look like:
dialog_calendar().close();
Since the setDate() method sets the focused date and also closes the calendar control the script will fail during playback while trying to close the calendar control.Workaround: Delete the calendar close method that was generated in the script.
IBM Rational Functional Tester records the entered password as it appears in the password field and is not able to read the encrypted value.
Workaround: Before playing back the script replace the recorded password with the actual password in the script.
Sometimes you may not be able to record actions performed on SAP applications. This happens when the SAP server is not enabled for scripting.
Workaround: Enable the SAP server for scripting. You need SAP system administrator privileges to perform this task.
Sometimes security check alert messages are displayed while recording against SAP applications. For example: "A script is trying to attach to the GUI".
Workaround: Before you start recording, perform the following to disable the securty check notification:
- In the SAP application window, click Customizing of Local Layout toolbar button > Options.
- In the Options window, select the Scripting tab.
- In the User Setting group box, uncheck Notify When a Script Attaches to a Running GUI and Notify When a Script Opens a Connection.
- Click OK.
SAP Logon is not added to the application list in the Start Application wizard by default . To start the SAP Logon from the recorder, you have to first add the saplogon.exe to the application list.
Workaround: To add the SAP Logon executable to the application list in the Start Application wizard, perform the following steps:
- Bring up the Application Configuration Tool wizard by selecting Configure->Configure Applications for Testing from the Functional Tester perspective.
- Click the Add button In the Application Configuration Tool wizard.
- Select the Excecutable or Batch File radio button in the Add Application window and click Next.
- Click on the Browse button to select the saplogon.exe, which is available in the SAP installation location.
- If you are using SAPGUI 6.4, saplogon.exe will be available from C:\Program Files\sappc\SAPGui.
- If you are using SAPGUI6.2 , saplogon.exe will be available from C:\Program Files\SAP\FrontEnd\SAPGui.
- Click Finish. SAP Logon appears in the applications in the Application Configuration tool.
- Click either Finish to save the changes.