Known Issues - Web-based SAP
This topic contains troubleshooting and limitation information about testing web-based SAP applications.
General
We recommend using the SAP Solutions Add-in only when no other Web-based add-ins are loaded.
The SAP Solutions Add-in modifies Web configuration settings that might affect other add-ins or applications.
Testing web-based SAP applications on Chrome
You might experience unexpected behavior if you are using the latest extension available in the Chrome store or in the <Installdir>\Installations\Chrome\v3 folder.
How can I tell if I am using the relevant extension: Navigate to the chrome://extensions/ page and click Details on the extension you installed. The Inspect views of the extension are service worker.
Workaround: Uninstall the existing extension, follow the installation instructions in Manually install the extension and install a different Chrome extension from <Installdir>\Installations\Chrome\v2.
Testing web-based SAP applications on Edge
Testing SAP Business Networks Web applications on Edge browsers is not supported. Similarly, SAPWebExt test object steps cannot be recorded or run on Edge browsers.
Object Identification
This section describes known issues that relate to object identification.
Affected product area | Known issues |
---|---|
Multiple browser windows |
In some cases, when more than one browser is open during the test run, certain objects are not identified correctly. Workaround: Clear the Enable Smart Identification checkbox for the Browser test objects in the Object Repository window. You might also want to disable the Enable Smart Identification option for Browser test objects in the Object Identification Dialog Box for future test recording. |
iViews |
Minimized or collapsed iViews might not be recognized correctly. |
SAP Enterprise Portal frames |
In some cases, a frame in SAP Enterprise Portal might be recognized as a Web Frame object instead of an iView object. In some of these, the frame name is generated dynamically. Because the Web Frame object uses the name property to identify the object, you must modify the recorded name value to use a regular expression that will enable recognizing it during the test run. |
SAP Web table cells |
When using the Object Spy or creating a checkpoint on an object inside an SAP Web table cell, the object might be recognized as a WebElement (and not as the appropriate SAP Web object), if a click has not yet been performed on the object. Workaround: Click on the object inside the SAP Web table cell before using the Object Spy or creating a checkpoint on it. |
Web table cells in SAP NWBC S/4HANA systems |
When you use the Object Spy to spy on or create a checkpoint on an object inside an SAP Web table cell in SAP NWBC S/4HANA systems in Internet Explorer, duplicate table names and cell values might be captured. |
SAPList objects in SAP NWBC S/4HANA systems |
When you spy or record on SAPList objects in SAP NWBC S/4HANA systems in Internet Explorer, the values of some captured properties might be wrong. |
Active Screen |
Avoid using an Active Screen that was captured when a pop-up dialog was open to add an object from the main window to the object repository. Doing this results in an incorrect object hierarchy in the object repository. |
SAP SuccessFactors tests from versions earlier than 24.2 |
In 24.2, SAP SuccessFactors object identification was modified. If you run tests created in versions earlier than 24.2, some SAP or Web objects might not be identified. In this case, update your tests by doing one of the following:
|
Recording
This section describes known issues you might encounter when recording steps on your application.
Affected product area | Known issues |
---|---|
Dragging scroll bars |
Dragging table scroll bars is not recorded. Workaround: You can record scrolling in tables by clicking the scroll button. Alternatively, use the Step Generator or Editor to insert an SAPTable.Object.DoScroll("up") or SAPTable.Object.DoScroll("down") statement in your test. |
iView option menu / SAP Enterprise Portal title bar |
Operations on the iView option menu and on objects within the page title bar of SAP Enterprise Portal are recorded as Web operations on the Frame object, and not as SAP operations on the iView object. |
SetCellData method |
On some tables in SAP GUI for HTML, the SetCellData method is not recorded properly. Workaround: When recording, do one of the following after editing a text value in a table cell:
|
SAPList objects |
To enable a SAPList object to be identified during a recording session, you need to click the input part of the list, not its button part. |
SAPTable objects on S/4HANA systems |
When recording on Internet Explorer, no step is recorded when you press Enter in an SAPTable cell in an S/4HANA system. Workaround: To enable recording an SAPTable.Submit step when Enter is pressed, create the following registry key and set its value to 1: Computer\HKEY_CURRENT_USER\Software\Mercury Interactive\QuickTest Professional\MicTest\Packages\SAPPackage\Settings\RecordSubmitForTableNavigateEvent |
Active Screen |
The Active Screen might not display the entire HTML page captured while recording your test. Workaround: Resize the Active Screen so that it best fits the HTML page size. |
SAPDropDownMenu objects |
You might not be able to record on SAPDropDownMenu objects inside an SAP CRM or WDA application on Chrome or Internet Explorer. Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test. |
SAPTabStrip().Select operations on CRM S/4HANA systems |
Redundant steps are sometimes recorded when recording SAPTabStrip().Select operations on Internet Explorer. Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test. |
SAPTreeView objects |
|
SAPTreeView objects in SAP Enterprise Portal |
The OpenContextMenu() operation on SAPTreeView objects in SAP Enterprise Portal might fail to be recorded. Workaround: Do one of the following:
|
SAPUI5 or SAP SuccessFactors in Internet Explorer |
In some cases, recording on SAPUI objects in SAPUI5 or SAP SuccessFactors applications in Internet Explorer does not record any steps. Workaround: Do one of the following:
|
SAPUITextEdit.Clear method |
In some cases, recording on SAP SuccessFactors applications records nothing when you click the x icon in the edit field. Clicking this x is the application clears the edit field. Workaround: Manually add the SAPUITextEdit.Clear to clear the field. |
Recording on CRM S/4HANA systems in Firefox |
When recording on a CRM S/4HANA system in Firefox 78.14.0 ESR, you might encounter the following errors:
Workaround: In Firefox extensions settings, click the dot button next to OpenText UFT Agent and select Options. Then set Default Frame Communication Mode to extension in the Options tab. |
SAPRadioGroup.Select |
When recording a Select operation on an SAPRadioGroup object in an SAP NWBC S/4HANA 2020 system on Internet Explorer, the operation might not be recorded, or it might be recorded incorrectly as a MouseDown event. Workaround: Manually add or change the recorded step to the SAPRadioGroup.Select step. |
SAPButton object |
When recording a SelectMenuItem operation on an SAP dropdown button in SAP Enterprise Portal, an additional SAPDropDownMenu.Select step might be recorded. Workaround: Delete the additional SAPDropDownMenu.Select step. |
SAPTable multi-row-selection methods |
On some multi-row-selection SAPTable objects, ExtendSelectRow and ExtendDeSelectRow methods are not recorded. Workaround: Spy on the table and add it to the object repository. Then add multi-row-selection steps to the test manually. If the ExtendSelectRow and ExtendDeSelectRow methods don't select the rows, try using SelectCell or SelectCellData methods to select the checkboxes in the row headers (column one). |
Running tests on SAP applications
This section describes known issues you might encounter when running tests on SAP applications.
Fiori applications
This section describes known issues you might encounter when testing Fiori applications.
Using a Set method in two consecutive steps
When working with Fiori applications, errors might occur when running a test with the sapUIObject value set to a variable in your script, where a Set method is used twice in a row.
For example:
set sapObject=Browser("DatePicker - sap.m").Page("DatePicker - sap.m").SAPUICalendar("DP1-describedby") sapObject.SetDate "20150114" sapObject.SetDate "000000"
Update your script using one of the following methods:
For example:
set sapObject=Browser("DatePicker - sap.m").Page("DatePicker - sap.m").SAPUICalendar("DP1-describedby") sapObject.SetDate "20150114" sapObject.RefreshObject sapObject.SetDate "000000"
For example:
Browser("DatePicker - sap.m").Page("DatePicker - sap.m").SAPUICalendar("DP1-describedby").SetDate "20150114" Browser("DatePicker - sap.m").Page("DatePicker - sap.m").SAPUICalendar("DP1-describedby").SetDate "000000"
Extra objects in Chrome
When working in Chrome, when you add certain objects to the object repository, many extra objects are added.
Workaround: Use a different browser (IE or Firefox) or manually remove the unwanted objects from the repository.
Recording a SetDate step on an SAPUICalendar
When working with Fiori applications, SetDate on a Calendar object with a Time picker does not properly record and run the Time part.
Workaround: Add a WebEdit.Set step to your test manually.
For example:
WebEdit.Set "Jan 23, 2019, 11:46:00 AM"
Recording a SetDateTime step on an SAPUIDateTimeInput
When recording on Fiori applications, SAPUIDateTimeInput.SetDateTime are not recorded.
Workaround: While recording, before selecting a date in the SAPUIDateTimeInput object, click the text box to bring the SAPUIDateTimeInput object into focus.
Browser refreshes when using Submit method
When both WEB and SAP add-ins are enabled, the browser will refresh If you use a Submit method in Firefox/Chrome after using webUtil.
Workarounds:
- Use systemUtil instead of webUtil.
-
Use DeviceReplay to move the focus point from URL-Textbox to the one you want to submit, before the submit method. For example:
WebUtil.LaunchBrowser "FIREFOX" Browser("micclass:=browser").Navigate "https://sapui5.hana.ondemand.com/1.44.27/test-resources/sap/m/Dialog.html" Browser("micclass:=browser").Page("micclass:=page").SAPUIButton("name:=Simple Dialog").Click Set dr = CreateObject("Mercury.DeviceReplay") ax = Browser("micclass:=browser").Page("micclass:=page").SAPUIDialog("name:=Simple Dialog").GetROProperty("abs_x") ay = Browser("micclass:=browser").Page("micclass:=page").SAPUIDialog("name:=Simple Dialog").GetROProperty("abs_y") dr.MouseClick ax,ay,LEFT_MOUSE_BUTTON Browser("micclass:=browser").Page("micclass:=page").SAPUIDialog("name:=Simple Dialog").Submit
Recording SAPUIMenu.Select operations on Chrome
Redundant steps are sometimes recorded when recording SAPUIMenu().Select operations in Fiori version 1.91 and later on Chrome.
Workaround:
-
Manually remove the duplicate steps from your test.
-
Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test.
SAPUI5-specific limitations
This section describes known issues you might encounter when testing SAPUI5 applications.
Affected product area | Known issues |
---|---|
Desktop/mobile |
Because the SAPUI5 add-in supports both desktop and mobile applications, not all methods for all objects are supported for both desktop and mobile applications. |
Application alert messages |
When running a test or component on SAPUI5 test objects, application Alert messages for some objects are not displayed. Workaround: Do one of the following:
|
Nested table objects |
If your SAPUI5 application contains nested table objects, inserting a checkpoint on the nested table object shows only the parent SAPUITable object. Workaround: Select the nested WebTable objects and create checkpoints for the WebTable object instead of the parent SAPUITable object. |
SAPUIMenu objects |
When using the Object Spy to view an SAPUIMenu object or recording an SAPUIMenu object which is hidden in closed status, you might be unable to:
|
Disabled controls |
When working with mobile SAPUI5 applications, Object Spy cannot spy on some disabled controls (like the SAPUIButton and SAPUITextEdit) due to the application object properties. |
Internet Explorer 11 |
When working in Internet Explorer 11, if your application requires you to scroll down to perform a button click, the SAPUIButton.Click method does not click the button. Workaround: Use an SAPUIButton.Submit method instead. |
ChildObjects method |
Using the ChildObjects method on some objects returns a different result between browsers. |
SAPUIFacetFilter.Open method |
The SAPUIFacetFilter.Open method might fail when opening multiple filters. Workaround: Use DeviceReplay to blur the mouse focus before opening the second filter. Example:
|
SAPUIList.SetItemData method | To record on an input field in a list in Mozilla Firefox, click the field twice during recording before entering text. |
WebUtil.LaunchBrowser method |
If you use the WebUtil.LaunchBrowser method to open your application from Internet Explorer or Chrome, subsequent SAPUIFacetFilter.Open steps might fail. Workaround:
Example:
|
SAPUI5 and SuccessFactors applications
This section describes known issues you might encounter when testing SAPUI5 and SuccessFactors applications.
Affected product area | Known issues |
---|---|
SAPUIList.Select method |
The SAPUIList.Select method fails to select an option if the operation involves scrolling down to find the option in the SAPUIList object. Workaround 1: Run the SAPUIList.Select step twice. Workaround 2:
Example
|
SAPUIList.Select method |
If indexes are used to represent the items to select in your script, the SAPUIList.Select method might fail to run the operation. Workaround: Use above-mentioned workaround 2. |
SAPUIList objects |
If multiple similar SAPUIList objects exist on the same page, they might not be correctly identified during runtime. Workaround: Change the object property in the object repository to create a unique description of the object. For example, add a property ID and remove extra index values. |
SAPUITable.SetCellData method |
The SetCellData method might fail to set the cell value of SAPUITable objects. Workaround: Use an SAPUITextEdit.Set method instead. |
SAPUITable.SelectItemInCell method |
In Internet Explorer, a recorded SAPUITable.SelectItemInCell operation might fail to run. Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test. |
SAPUIList objects that contain SAPUITable objects |
An SAPUIList object might be incorrectly recorded as an SAPUITextEdit object or SAPUITable object. In this case, running the recorded SAPUITextEdit.Set or SAPUITable.SelectCell steps might fail. Workaround: Add a WebButton.Click step and a Wait step before SAPUITextEdit.Set or SAPUITable.SelectCell steps. Example:
|
SAPUICalendar objects |
|
SAPUIDateTimeInput objects |
When recording a SAPUIDateTimeInput.SetDateTime operation, additional steps might be recorded. For example, redundant SAPUICalendar.SetDate, SAPUIDatePicker.SelectDate, and SAPUIDateTimeInput.SetDateTime steps might be recorded. Workaround: Before running the test, remove the unnecessary steps. |
SAPUI objects inside a table |
Recording steps on SAPUI objects inside a table might fail. Workaround: Use the Spy to learn the objects and add it to the object repository. Then manually add the necessary step to the test. |
Dynamic search triggered by SAPUITextEdit.Set |
An SAPUITextEdt.Set operation might record or run incorrectly if it triggers dynamic search. Workaround: Add a Wait statement and then a SAPUITable.SelectCell step. Example
Alternatively, use DeviceReplay to select the edit box value or the SAPUITextEdt.Set step directly to set the edit box value. |
SAPUIButton.Click |
In some applications, you might not be able to record or run a SAPUIButton.Click operation that opens a window for uploading a file. Workaround: Use one of the following solutions:
|
SAPUIDateTimeInput.SetDateTime method |
If the date and time format does not meet the format expected by the application, the step might run successfully, but the date and time are not updated. Workaround: To determine the format expected by the application, record a SAPUIDateTimeInput.SetDateTime step and check the date and time format in the recorded step. Use this format in the SetDateTime steps you write. |
SAPUIToggleButton objects |
On SAPUIToggleButton objects, steps with methods such as Click, DoubleClick, FireEvent, MiddleClick, RightClick, and Submit might run successfully but not perform the operation. Workaround: Perform these steps using mouse replay. Change the replay type before the step to Run by mouse operations using: We recommend returning the replay type to the default (Run by Events) setting after the step: |
SAPUITextEdit.Set |
The following issues might occur when you spy or record on a dynamic search box:
|
SAPUIButton objects |
Sometimes, two different steps are recorded (a WebButton.Click step and an SAPUIButton.Click step or two SAPUIButton.Click steps), when recording a Click operation on an SAPUIButton object. Workaround: Delete one step and keep the SAPUIButton.Click step. |
SAPUIList.ExtendSelect and SAPUIList.ExtendDeselect methods |
After successfully recording an ExtendSelect or ExtendDeselect operation on an SAPUIList, subsequent ExtendSelect or ExtendDeselect operations might fail to be recorded. Workaround: After the first ExtendSelect or ExtendDeselect operation is successfully recorded, click the dropdown button to re-open the dropdown list and then continue recording. |
SAP UI controls identified as Web test objects |
When spying or recording, controls might be identified as Web objects instead of, for example: SAPUIButton, SAPUIToggleButton, SAPUITextEdit, SAPUIToolBar, or SAPUIList test objects. Workarounds:
|
SAP Business Networks applications
This section describes known issues you might encounter when testing SAP Business Networks applications.
Affected product area | Known issues |
---|---|
SAPWebExt List |
Spying or adding checkpoints on an SAPWebExt List objects in SAP FieldGlass is not supported. The SAPWebExtList.Select method might fail when testing SAP FieldGlass. If this occurs, use the WebEdit.Set method instead. |
SAPWebExtTable objects |
Checkpoints on SAPWebExtTable objects are not supported. Workaround: Do one of the following:
|
SAP WDA applications / SAP WDA applications in S/4 HANA
This section describes known issues you might encounter when working with Web Dynpro ABAP (WDA) applications or WDA applications in SAP S/4 HANA.
Affected product area | Known issues |
---|---|
SAPButton.Click methods |
Recording an SAPButton.Click method on Web Dynpro ABAP sites might cause browser delays. Workaround: Do one of the following:
|
SAPTable objects |
|
SAPTable.OpenPossibleEntries in SAP WDA applications |
On some applications, the SAPTable.OpenPossibleEntries operation is not recorded on IE or Chrome. Workaround: Click the cell first, then click the icon beside cell to record OpenPossibleEntries. Remove any extra SetCellData steps that are recorded. |
SAPTable.SelectCell method: General recording |
When using the SelectCell method on SAPTable objects in SAP WDA 7.5 applications:
|
SAPTable.SelectCell method: Recording table objects that disappear in your application |
If a table object disappears in the SAP WDA application immediately after a select operation is performed, SelectCell methods are not recorded on the table object. Workaround: Manually add the SAPTable.SelectCell method after recording. |
SAPEdit objects |
When recording on SAPEdit objects in some WDA applications in SAP S/4HANA on Chrome or Egde, an incorrect object name might be recorded. Workaround: Use the Spy to learn the SAPEdit object and add it to the object repository. Then manually add the necessary step to your test. |
Dynamic displays
If your Web Dynpro ABAP or EP app is configured with dynamic display features when scrolling, you might have issues retrieving cell or list data that is currently invisible.
To prevent this, ensure that all your data is fully loaded before running your step, spying, or highlighting.
For example:
Workaround for tables:
Before your SAPTable.GetCellData method, add steps to scroll down and display all row data.
Then, use the GetCellData method with the current row value.
For example:
'get value in row 1
print Browser("WDR_TEST_C_TABLE [Web").Page("Web Dynpro Test Suite").SAPTable("[Demo Table Part 1]").GetCellData (2,4)
For Iterator = 1 To 4 Step 1
wait 1
Browser("WDR_TEST_C_TABLE [Web").Page("Web Dynpro Test Suite").SAPButton("SAPButton_2").Click
Next
'get value in row 7 which is shown in line 4 after scroll
print Browser("WDR_TEST_C_TABLE [Web").Page("Web Dynpro Test Suite").SAPTable("[Demo Table Part 1]").GetCellData (4,4)
Workaround for lists:
Activate the SAPList object before using the GetItem method or spying.
For example, first select or click the list, or use the Select or Click method in your test.
See also: