Creating and Running Testing Documents
· Running a test on HTML elements embedded in an SAP GUI for Windows application may result in an "Object is disabled" error. This may happen if the HTML control is not ready for the test run.
Workaround: Add a Sync statement such as SAPGuiSession.Sync or a Wait statement to the script in order to run the test successfully.
· By default, the recording and running of steps on HTML elements embedded in an SAP GUI for Windows application is performed using the UFT Web Add-in. In some cases, steps recorded using the Web Add-in are inserted into the script before SAP Add-in steps that use the SAP Scripting API.
Workaround: Use the option of recording HTML elements embedded in SAP GUI application using the SAP Scripting Interface. To do so, stop recording, select the Record HTML elements using SAPGui Scripting interface check box in the SAP pane of the Options dialog box (Tools > Options > GUI Testing tab > SAP > General node). Then close and reopen the test and then begin recording again.
· If inserting a call to an external action or a copy of an action, and that action includes an SAPGuiTable.Input, SAPGuiGrid.Input, or SAPGuiAPOGrid.Input statement, the corresponding input data sheet is not copied to the Data pane with the action.
Workaround: Insert and run Datatable.AddSheet and Datatable.ImportSheet statements to import the sheet referenced by the action’s Input method. Ensure that the name of the data sheet exactly matches the name specified in the corresponding Input statement.
· In the SAP Enterprise Portal environment, occasional synchronization problems may occur during the test run when alternating between SAP Web and SAP Windows environments.
Workaround: Add a WaitProperty or Wait statement between the Web steps and the Windows steps.
· UFT can connect to SAP Logon or SAP Logon Pad application for recording and running tests on SAP GUI for Windows sessions. If using both SAP Logon and SAP Logon Pad processes on the computer, UFT connects to the latest process that was launched.
· Use the SAP tab of the Record and Run Settings dialog box to instruct UFT to open SAP GUI for Windows application. Do not use the Windows Applications tab of the dialog box for this purpose.
Working with Windows-based SAP Controls
· Separate toolbar controls (ones that are not part of a grid or other object) are supported by the SapGuiToolbar test object (GuiComponentType is 202), and the Object Spy recognizes them because they are separate objects.
Note that tree controls do not have associated toolbars. Toolbars displayed on top of tree controls are recognized as separate toolbars, and are therefore supported as described above.
· Toolbars inside grid controls are supported by the SapGuiToolbar test object (GuiComponentType is 204). However, the Object Spy does not recognize these toolbars because they are part of the grid. If not possible to add these toolbars to the object repository using the Add to repository option from the Active Screen or the Add Objects option in the Object Repository window. To add these toolbars to the object repository, record on them.
· Toolbars inside other controls (such as a toolbar within a text area control) are not supported.
· Microsoft Office controls within the SAP window are not supported.
· If recording the step of pressing an F4 key, and that key press results in setting new values for multiple fields, a step is recorded only for the field from which the F4 key was pressed, and therefore, only that field will be populated during the run.
· The SAP Editor control is not supported.
· UFT fails to run steps on SAP tree nodes that contain the ";" character.
· UFT does not automatically record standard Windows dialog boxes used by the SAP GUI for Windows application (such as the Open File and Save As dialog boxes). This is because the SAP scripting API does not support these dialog boxes. This may also occur when using SAP GUI for Windows with GuiXT.
Workaround: Do one of the following:
o Change to Standard Windows Recording mode (select Standard Windows Recording from the Recording Modes drop-down in the Record toolbar) to record on these objects. (Make sure that it is switched to Standard Windows Recording mode before performing the operation that opens the standard Windows control in the SAP application.)
o Use low-level recording to record on these objects.
o Use programmatic descriptions to run steps on these objects.
Checkpoints, Output Values, and the Object Spy
o To ensure that the correct object properties are captured with the checkpoint, always record a step that results in communication with the server (such as pressing Enter) before inserting a checkpoint or output value.
o It cannot be used the Object Spy or created checkpoints for the controls listed below. However successfully can be recorded and run steps on them.
o Toolbar buttons in grid controls.
o Internal controls in tree or table objects.
(For example, a radio button in a table cell or a check box in a tree.)
· Creating checkpoints or using the Object Spy on an object that is located in a currently inactive SAP screen (for example, if the screen is behind an invoked dialog box) is not supported. However, it can be created checkpoints on status bar messages (displayed in an inactive window) using the Record status bar messages option (Tools > Options > GUI Testing tab > SAP node > Record status bar messages).
· When running old 6.20 tests on a 6.40 client, checkpoints on radio buttons, check boxes, edit boxes, or regular buttons may fail due to changes to tooltip property values for these objects in the 6.40 client.
· UFT can estimate the number of rows in a table control, but it cannot retrieve the exact number because only the table content that is visible on the client is actually available. Data from non-visible rows are stored only on the back-end server. Therefore, when inserting or modifying checkpoints for a table control object, the number of rows specified in the Define/Modify Row Range dialog box may not be accurate.
· Do not perform any operations on the SAP GUI window (such as changing the transaction state or navigating to another window) while UFT retrieves the data for a table checkpoint even if it seems to take a long time, as this may cause severe problems.
· When inserting a checkpoint on a table or grid from the Active Screen, the actual table must be open in the SAP Gui for Windows application to extract the correct information from the table or grid.
Test Objects, Methods, and Properties
· When using the SAPGuiTable Input method, check the scrolling mode of the current table. If parameterizing a table with a Data pane sheet that contains more rows in the sheet than are displayed in the table’s current view, UFT tries to scroll down the table while running the test, to insert more rows from the data sheet. UFT supports two ways of scrolling rows in tables—by pressing the Enter key, or by pressing the PageDown key. By default, the Add-in for SAP Solutions tries PageDown if needed. Is available possible to configure the required mode using the second argument of the Input method.
· Right-click operations are not supported for the SAPGuiTextArea object.
· Drag-and-drop operations in the SAP Gui for Windows application are disabled when UFT is open.
Using the Active Screen
· Active Screen images are based on captured screen bitmaps. Therefore, objects that are not visible in the SAP GUI for Windows view are not part of the Active Screen image. Objects cannot be added to the script from the Active Screen if they were not in the captured view.
· Drop-down menus are not captured in the Active Screen. Active Screen technology captures the data after the menu is closed and the menu item is selected.
· While recording, UFT captures one Active Screen image for several steps. UFT records steps only when the SAP GUI for Windows client sends information to the SAP back-end server. When this occurs, all steps that were performed between the previous communication and the current one are added to the script. The last screen that was sent to the server is captured by the Active Screen for all steps recorded during that communication.
· When recording on Web elements inside SAP GUI for Windows applications, HTML images are not captured.
· Adding objects to the object repository (using the View/Add Object option, or creating checkpoint or output value steps) from an Active Screen created from a step recorded on a Web element inside a SAP GUI for Windows application generates an incorrect object hierarchy in the object repository.
SAP Scripting API
· For security reasons, the SAP scripting API prevents the recording of passwords. When recording the operation of inserting a password in a password box, UFT records a Set statement using asterisks (****) as the method argument value.
Workaround: Do one of the following:
o Configure and enable the Auto-logon settings in the SAP tab of the Record and Run Settings dialog box.
o Insert a step using one of the SAPGuiUtil object’s AutoLogon methods.
o Record the password normally during the recording session. After the recording session, modify the password step to use the SetSecure method, and enter the encrypted password value or parameterize the value.