Unable to Spy SAP Table Elements in UiPath

Help Studio
,
1

Hello Team,

I need help extracting table data from SAP using UiPath. I am unable to spy the table elements correctly, as the selector is identifying a different area instead of the required table element.

image
image1619×837 245 KB

I have attached a screenshot for reference. Could you please review it and let me know what might be causing this issue?

I have tried different spying methods, but none of them are working as expected.

Has anyone faced a similar issue while automating SAP? If so, please share your suggestions or any possible solutions.

Thank you.

2

This can often be caused by zoom settings in SAP. If you google around that you should be able to find lots of existing resources on it and how to solve it.

3

Hi @QRPABOT
This issue usually occurs when UiPath detects the SAP container instead of the actual table control. Verify that SAP scripting and the UiPath SAP extension are enabled. Use UI Explorer to identify the table as GuiGridView/GuiTableControl and try alternate frameworks (F4) or Computer Vision. If the table is a custom SAP control, SAP-specific activities or AA selectors often work better than standard spying methods.

4

I have already tried using Computer Vision (CV) activities, but I am still facing the same issue that I encountered earlier. The table control in SAP is of type GuiTableControl, and none of the spying methods are working correctly.

Could you please let me know if there are any alternative approaches to click the Purchase Order value in the table? If anyone has faced a similar issue, please share your suggestions or possible solutions.

Thank you.

5

Hi @QRPABOT,

You can refer this, this might help in your case.

Also, there is some reusable activity available from UiPath Marketplace. This is to get data using BAPI from SAP Tables.
Extract SAP Table with BAPI | UiPath Marketplace

Cheers!

6

Hi @QRPABOT

You can try the following steps:

  1. First, check whether SAP Scripting is enabled.
  2. Open UiPath UI Explorer and try to indicate the table again.
  3. Check whether UiPath identifies the control as GuiGridView or GuiTableControl.
  4. If the table is not identified correctly, try changing the UI Framework (for example, AA/UIA).
  5. You can also try Computer Vision if the table is a custom SAP control.
  6. If it is still not working, check whether an SAP-specific activity or selector can be used for that table.

In my experience, changing the UI framework and checking the selector in UI Explorer usually helps identify the actual SAP table control.

7

Hi @QRPABOT,

Can you check whether SAP GUI Scripting is enabled on both the server and client sides? This is a common prerequisite for SAP automation in UiPath.

You can follow the configuration steps here:

Thanks!

8

Hi @QRPABOT

on top of what Prashanth flagged about DPI/multi monitor scaling, wich is worth checking first since it explains CV failing too, not just the selector, theres a second thing specific to GuiTableControl

that control type behaves differently from GuiGridView, individual cells often arent spyable as separate elements the normal way, wich is exactly the “selector grabs a different area” symptom you’re seeing. For GuiTableControl the reliable approach is addressing cells through the SAP scripting row/column pattern instead of trying to click-indicate each one

check the selector UiPath generated for the table container itself (not a cell), it should have something like row=“0” col=“0” as attributes if it correctly saw a GuiTableControl. If so, you can build the click dynamically by looping the rows and swapping those row/col values in the selector at runtime with a variable instead of indicating each cell by hand, that sidesteps the whole spying problem

also worth trying the Get/Set Sap Value activities if you have the SAP activities package, those talk to the table through the SAP scripting api directly using row and column index rather than relying on visual spying at all, more reliable for GuiTableControl specifically

fix the DPI thing first though since Prashanth’s link matches your case closely (WinGUI 7.70 + table controls), might solve both problems at once.

hope this gets you unblocked :slight_smile: