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.

Minimized or collapsed iViews might not be recognized correctly.

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.

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.

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.

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.

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.

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: 

• In the object repository, update the objects' descriptions using the Update from Application button . For details, see Update description properties.

• Learn the object again by spying on it and adding it to the object repository. Then update the test steps to use the new object.

• Delete the relevant steps and recreate them by recording.

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.

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.

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: 

• Press Tab to submit the value and move to the next cell.
• Press Enter to submit the value before clicking a location that is outside the table cell.

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.

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

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.

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.

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.

• The Activate method of SAPTreeView object cannot be recorded in Chrome, Edge, and Firefox.

  Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test.

• The Select operation on a node of the SAPTreeView object might fail to be recorded if you click the node once.

  Workaround:

  • Click the node twice while recording. If the issue still persists, try the second method.

  • Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test.

The OpenContextMenu() operation on SAPTreeView objects in SAP Enterprise Portal might fail to be recorded.

Workaround: Do one of the following:

• Perform the following steps to load the event configuration file, and then record the operation again.

  1. In OpenText Functional Testing, select Record > Web Event Recording Configuration.

  2. In the Web Event Recording Configuration dialog box, click Custom Settings.

  3. In the Custom Web Event Recording Configuration dialog box, select File > Load Configuration.

  4. Select the SapEventConfiguration.xml file in C:\Program Files (x86)\OpenText\UFT One\dat.

• Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test.

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:

• Record the steps in Chrome and run them in Internet Explorer.

• Use the Spy to learn the SAPUI objects and add them to the object repository. Then manually add necessary steps to the test.

In some cases, recording on SAP SuccessFactors applications records nothing when you click the x icon in the edit field to clear its contents.

Workaround: Manually add the SAPUITextEdit.Clear to clear the field.

When recording on a CRM S/4HANA system in Firefox 78.14.0 ESR, you might encounter the following errors:

• OpenText UFT Agent is slowing down the browser

• OpenText Functional Testing performs slowly or does not respond

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.

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.

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).

During a run session, the SAP platform response time might be slower than the time it takes for the corresponding step to run.

Workaround: Add a Wait statement prior to the relevant step.

In some cases, when running tests on SAPEdit, SAPNavigationBar, or SAPPortal, you might receive a Cannot find object error. 

Workaround: Do one of the following:

• Ensure that the object properties are unique and correct.

• Modify the registry as specified below:

  For 32-bit computers: In the HKEY_LOCAL_MACHINE\Software\Mercury Interactive\QuickTestProfessional\MicTest\AbortIfHangInSendData key, set the value of DWORD to 0.

  For 64-bit computers: In the HKEY_LOCAL_MACHINE\Software\Wow6432Node\Mercury Interactive\QuickTestProfessional\MicTest\AbortIfHangInSendData key, set the value of DWORD to 0.

  Note: Some registry keys intentionally include previous company branding, due to backward compatibility considerations.

When running a test on an ITS frame in an SAP Enterprise Portal iView, the ITS menu sometimes fails to operate properly.

Workaround: Enlarge the iView size and/or increase the Object Synchronization Timeout and then run the test again.

Use CRM system test mode:

When test Web-based CRM systems, make sure that the CRM system is in test mode. You can do this by adding "?sap-testmode=X" to the URL.

CRM 7.02 and 7.03:

When testing applications developed using CRM 7.02 or 7.03, the SAPList.Select method might generate parameter errors.

If this occurs, add a Click step before your Select step to avoid future errors.

When testing web-based CRM and NWBC S/4HANA systems, the Highlight and CaptureBitmap methods are not supported for SAPRadioGroup and SAPTabStrip objects.

On some SAPTable objects, only the table content that is visible on the client is actually available.

Some methods, such as FindRowByCellContent, ExtendSelectRow, and ExtensDeSelectRow do not work correctly if the row to find or select is not visible in the table.

Workaround: Add steps to scroll the relevant rows into view.

The following issue occurs on Fiori, SAP UI5 Web Components, and SAP SuccessFactors applications.

On some SAPUITable objects with scroll bars, IsRowVisible and MakeRowVisible methods might not work correctly.

Workaroud: Before the steps that operate on the table content, write steps that expand the table to make the relevant rows visible.

For example:

Set DeviceReplay=CreateObject("Mercury.DeviceReplay")

x=Browser("MyApp").Page("MyApp").Frame("Frame").SAPUITable("SAPUITable").GetROProperty("abs_x")

y=Browser("MyApp").Page("MyApp").Frame("Frame").SAPUITable("SAPUITable").GetROProperty("abs_y")

DeviceReplay.MouseClick x+1055,y+180,LEFT_MOUSE_BUTTON

SAPTable multi-row-selection methods

On some multi-row-selection SAPTable objects, the ExtendSelectRow and ExtendDeSelectRow methods do not select the rows.

Workaround: Try using SelectCell or SelectCellData methods to select the checkboxes in the row headers (column one).

On some S/4HANA systems, running an SAPList().Select method on a list contained in a table cell does not select from the list.

Workaround: Add a step to select the table cell before the step that selects from the list inside the cell.

Example:

SAPTable("MyTable").SelectCell X,Y

SAPList("MyList").Select

SAPDropDownMenu objects in SAP NWBC, WDA, or EP applications might not be identified during runtime.

Workarounds:

• Add the Logical name and innertext description properties to the object in the object repository, and run your test again. If the innertext property does not provide a unique identification, use the index property instead.
• If the above workarounds do not resolve the issue, perform the following: In Object Identification, add the 'html id' property to the SAPDropDownMenu object's Mandatory Properties.

SAPDropDownMenu objects with sub-menus

If you had selected an item in a sub-menu of an SAPDropDownMenu object while recording, the object recorded will be the sub-menu instead of the parent. This might cause your test run to fail.

Workaround: To avoid errors, before running your test, manually change the description properties in the object repository to match the parent menu instead of the sub-menu.

In Internet Explorer, SAPButton.Click operations that were recorded in Chrome might fail to run.

Workaround: In the object repository, replace the assistive property html tag with html id.

When you run a SAPNWBC.DetailedNavigation step that navigates to a menu item under a folder in the left navigation tree in Chrome, an error occurs.

Workaround: Add a step to navigate to the parent folder first and then run the step that navigates to the child menu item.

If you add a checkpoint for an SAPFrame object that contains an image whose name ends with "." in Chrome, thecheckpoint might fail to run in Internet Explorer.

Workaround: Remove the check for the image from the checkpoint.

In Internet Explorer,SAPTreeView.SelectMenuItem steps that were manually added to the test 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.

SAPRadioGroup objects recorded in Chrome might contain an extra description property sap groupbox name. If you run test steps you recorded in Chrome on SAPRadioGroup objects in Internet Explorer, the test steps might fail.

Workaround: Delete the description property sap groupbox name of SAPRadioGroup objects in the object repository and run the test steps in Internet Explorer.

A pop-up window opens when you run the Highlight method on an SAP object in Chrome or Edge. As a result, the method does not work properly.

Workaround: To solve the issue, perform the following steps:

1. Right-click the browser desktop shortcut and select Properties from the context menu.

   If your browser does not have a shortcut on the desktop, find the program from the startup menu and open the file location.

2. On the Shortcut tab of the Google Chrome Properties / Microsoft Edge Properties dialog box, append the following line to the existing value of the Target field.

   ' --silent-debugger-extension-api'

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.

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:

• Make sure your test does not contain steps that need to be performed on the Alert message.

• Add an If statement to your test for the object that triggers the alert to check if the Alert exists.

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.

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:

• Add the menu object to the repository on Firefox and Chrome browsers with the Add Object to the Repository button

• Record the object on Chrome browsers.

• Add checkpoint or output value steps in Firefox and Chrome browsers

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.

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.

Using the ChildObjects method on some objects returns a different result between browsers.

The SAPUIFacetFilter.Open method might fail when opening multiple filters.

Workaround: Use DeviceReplay to blur the mouse focus before opening the second filter.

Example:

x=Browser("SAPUI5 SDK - Demo Kit").Page("SAPUI5 SDK - Demo Kit").SAPUIFacetFilter("SAPUIFacetFilter").GetROProperty("abs_x")

y=Browser("SAPUI5 SDK - Demo Kit").Page("SAPUI5 SDK - Demo Kit").SAPUIFacetFilter("SAPUIFacetFilter").GetROProperty("abs_y")

Set obj=CreateObject("Mercury.DeviceReplay")

obj.MouseMove x,y

obj.MouseClick x-5, y-5, 0

If you use the WebUtil.LaunchBrowser method to open your application from Internet Explorer or Chrome, subsequent SAPUIFacetFilter.Open steps might fail.

Workaround:

• Use Record & Run Settings to open the browser.

• Use DeviceReplay to move the focus out of the navigation bar.

Example:

x=Browser("SAPUI5 SDK - Demo Kit").Page("SAPUI5 SDK - Demo Kit").SAPUIFacetFilter("SAPUIFacetFilter").GetROProperty("abs_x")

y=Browser("SAPUI5 SDK - Demo Kit").Page("SAPUI5 SDK - Demo Kit").SAPUIFacetFilter("SAPUIFacetFilter").GetROProperty("abs_y")

Set obj=CreateObject("Mercury.DeviceReplay")

obj.MouseMove x,y

obj.MouseClick x-5, y-5, 0

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:

1. Directly click the button to expand the SAPUIList object.

2. Check if the option you want to select exists in the currently displayed list.

3. If yes, use WebElement.Click to click the option. Otherwise, use DeviceReplay to scroll down the expanded list until the target option appears and then use Webelement.Click.

Example

Browser("SuccessFactors: People").Page("SuccessFactors: People").WebButton("Select Options").Click

wait 10

Set objWshShell = CreateObject("WScript.shell")

For Iterator = 1 To 20 Step 1

If Browser("SuccessFactors: People").Page("SuccessFactors: People").WebElement("Position Title:Engineering").Exist(1) Then

Browser("SuccessFactors: People").Page("SuccessFactors: People").WebElement("Position Title:Engineering").Click

Exit For

ElseIf Iterator < 20 Then

objWshShell.SendKeys "{DOWN}"

objWshShell.SendKeys "{DOWN}"

objWshShell.SendKeys "{DOWN}"

print(Iterator)

wait 1

End If

Next

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.

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.

The SetCellData method might fail to set the cell value of SAPUITable objects.

Workaround: Use an SAPUITextEdit.Set method instead.

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.

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:

Browser("Performance-Potential_2").Page("Performance-Potential").WebButton("__xmlview0--userSearchInput-ar").Click

wait 5

Browser("Performance-Potential_2").Page("Performance-Potential").SAPUITable("SAPUITable").SelectCell 16,"#1"

• Recording or running steps on some SAPUICalendar objects might fail.

  Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test.

• For the same SAPUICalendar object, the value of the innertext property captured in Internet Explorer might be different from that captured in Chrome.

  Workaround: Change the value of the innertext property to a regular expression in the Object Repository for compatibility requirements.

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.

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.

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

Browser("SuccessFactors: Admin").Page("SuccessFactors: Admin").SAPUITextEdit("SAPUITextEdit").Set "ac"

Wait 3

Browser("SuccessFactors: Admin").Page("SuccessFactors: Admin").SAPUITable("SAPUITable").SelectCell 6,"#1"

Alternatively, use DeviceReplay to select the edit box value or the SAPUITextEdt.Set step directly to set the edit box value.

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:

• Use DeviceReplay.

  Example

  x=Browser("SuccessFactors: Administer").Page("SuccessFactors: Administer").SAPUIButton("Upload").GetROProperty("abs_x")

  y=Browser("SuccessFactors: Administer").Page("SuccessFactors: Administer").SAPUIButton("Upload").GetROProperty("abs_y")

  Set obj=CreateObject("Mercury.DeviceReplay")

  obj.MouseMove x,y

  obj.MouseClick x+5, y+5, 0

• Use the WebFile.Submit method to submit and upload a file.

  Example

  Browser("SuccessFactors: Administer").Page("SuccessFactors: Administer").WebFile("fileData1").Submit

  Browser("SuccessFactors: Administer").Page("SuccessFactors: Administer").WebFile("fileData1").Set "C:\Temp\SAPUILandscape.xml"

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.

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: Setting.WebPackage("ReplayType") = 2

We recommend returning the replay type to the default (Run by Events) setting after the step: Setting.WebPackage("ReplayType") = 1

SAPUITextEdit.Set

The following issues might occur when you spy or record on a dynamic search box:

• Sometimes, in a recording session, no SAPUITextEdit.Set step is recorded when you select a dynamic search result for the text box.

  Workaround: Use the Spy to learn the object and add it to the object repository. Then manually add the necessary step to the test. If a WebEdit.Set step is recorded, delete that step.

• Sometimes, two different steps are recorded (a WebEdit.Set step and an SAPUITextEdit.Set step) when recording a Set operation on an SAPUITextEdit object.

  Workaround: Delete the WebEdit.Set step and keep the SAPUITextEdit.Set step.

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.

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.

When spying or recording, controls might be identified as Web objects instead of, for example: SAPUIButton, SAPUIToggleButton, SAPUITextEdit, SAPUIToolBar, or SAPUIList test objects.

Workarounds: 

• To identify these objects as SAPUI test objects, click slightly below the object.

  To find the exact location to click, move your mouse around below the object until the Spy highlights the SAPUI test object.

• To identify an SAPUIDialog test object, click in the footer of the dialog box.

• Record an operation that successfully identifies the SAPUI test object, then adjust the operation as needed.

• For Checkpoint or Output Value steps, create a step with the correct test object type, then hover over that step and create a Checkpoint or Output Value for that object. For details, see Insert a checkpoint step while editing and Insert a new output value from the editor.

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.

Checkpoints on SAPWebExtTable objects are not supported.

Workaround: Do one of the following:

• Restart OpenText Functional Testing, clear the SAPWebExt addin, and then add a checkpoint on a WebTable object.

• Use the .GetCellData method

• Add a checkpoint on the child WebTable of an SAPWebExtTable object.

Recording an SAPButton.Click method on Web Dynpro ABAP sites might cause browser delays.

Workaround: Do one of the following:

• Wait for the browser to respond
• Pause recording and click again
• Refresh the browser and try again

• A Click operation on an SAPTable object in WDA applications is not recorded.

  Workaround: Manually add the object as a WebElement and add a WebElement.Click step to your test.

• A Click operation on a Link object inside an SAP web table cell in WDA applications or WDA applications in SAP S/4HANA might be recorded incorrectly as an SAPTable.SelectCell operation.

  Workaround: Use the Spy to learn the Link object and add it to the object repository. Then manually add the necessary step to your test.

• An unspecified error might occur when adding checkpoints for SAPTable objects in WDA applications.

  Workaround: Add a registry AbortIfHangInSendData with a default value of 0 in HKEY_LOCAL_MACHINE\Software\Wow6432Node\Mercury Interactive\QuickTest Professional\MicTest.

  Note that this might cause issues when running on the other SAP technologies, such as Fiori and SAPUI5.

  Note: Some registry keys intentionally include previous company branding, due to backward compatibility considerations.

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.

When using the SelectCell method on SAPTable objects in SAP WDA 7.5 applications:

• If the table cell is located in a popup dialog window that closes immediately after clicking, the action cannot be recorded.

• You might need to click twice on the table cell for the action to be recorded.

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.

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.