Known Issues - Web-based SAP
General
We recommend using the UFT One SAP Solutions Add-in only when no other Web-based add-ins are loaded.
The SAP Solutions Add-in modifies Web configuration settings that may affect other add-ins or applications.
Object Identification
Multiple browser windows |
In some cases, when more than one browser is open during the test run, UFT One is unable to correctly identify certain objects. Workaround: Clear the Enable Smart Identification check box for the Browser test objects in the Object Repository window. You may 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 may not be recognized correctly. |
SAP Enterprise Portal frames |
In some cases, a frame in SAP Enterprise Portal may 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 an appropriate regular expression so that UFT One will be able to recognize 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, UFT One may recognize the object 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. |
Active Screen |
|
Recording
Tables |
When recording and running steps on a table control, only the table content that is visible on the client is actually available. |
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. |
Dragging scroll bars |
Dragging the SAP GUI for HTML table scroll bar is not recorded. Workaround: You can record scrolling in SAP GUI for HTML 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. |
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 |
When recording an SAPList object, you need to click the input part of the list, not its button part in order to enable UFT One to recognize the object. |
SAPTable objects in S/4 HANA applications |
When recording on Internet Explorer, UFT One does not record a step when you press Enter in an SAPTable cell in an S/4 HANA application. Workaround: To instruct UFT One to record 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 |
|
SAPDropDownMenu objects |
UFT One may not be able to record on SAPDropDownMenu objects inside an SAP CRM or WDA application on Chrome or Internet Explorer. Workaround: UFT One 15.0.1 and later: 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/4 HANA |
Duplicate steps may be added 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. |
Activate method of SAPTreeView |
The Activate method of SAPTreeView object cannot be recorded in Chrome. Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test. |
Running tests on SAP applications
Fiori applications
Using a Set method in two consecutive steps
When working with Fiori applications, errors may 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, UFT One adds many extra objects.
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
SAPUI5-specific limitations
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 may be unable to:
|
Disabled controls |
When working with mobile SAPUI5 applications, UFT One cannot use the Object 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. |
SAPWDJ-specific limitations
Load your Add-in |
If you try to record objects in an SAP WDJ application without the SAPWDJ add-in loaded, UFT One records only some of the objects correctly. Workaround: Restart UFT One and load the SAP WDJ Add-in. |
Performance |
During a run session, the response time of the SAP platform running an SAP Web Dynpro Java (WDJ) application may be slower than the time it takes for UFT One to run the corresponding step. Workaround: Add a Wait statement prior to the relevant step or set the Delay each step execution option in the Test Runs pane of the Options dialog box (Tools > Options > GUI Testing tab > Test Runs node) to the necessary wait period (in milliseconds) |
Unsupported features |
The following functionalities are not supported for SAP WDJ applications:
|
SelectCell method |
When recording steps on an SAPWDJTable object, the SelectCell method is not always recorded if you are selecting non-editable cells. |
Links that open popup windows |
If your table contains links that open a popup window, when using the SAPWDJTable.SelectItemInCell method to click the link, UFT One does not run the .SelectItemInCell properly. Workaround: Associate the linkFuncLibr function library with your test. This function library is found at <UFT One installation folder>\dat\Extensibility\Web\Toolkits\SAPWDJ\FunctionLibraries\linkFuncLibr.qfl. |
SAP Business Networks applications
SAPWebExt List |
Spying or adding checkpoints on an SAPWebExt List objects in SAP FieldGlass is not supported. The SAPWebExtList.Select method may 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 WebDynpro ABAP applications
SAPButton.Click methods |
Recording an SAPButton.Click method on WebDynpro ABAP sites may cause browser delays. Workaround: Do one of the following:
|
SAPTable objects |
|
SAPTable.OpenPossibleEntries |
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 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. |
Dynamic displays
If your WebDynpro ABAP or EP app is configured with dynamic display features when scrolling, you may 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: