I am currently experiencing the following phenomenon: I have carried out an automation of SAP in a test environment (here called Q61).
The basic procedure is to first select the SAP sub-application in SAP Logon 770, then perform a login (see screen SAP_3 for login windows test environment and production. It looks identical for both.) and then enter the business process. I have already set the classic settings for GUI automation with regard to scripting in the options for automation in the test environment and this has also worked.
Now I would like to transfer the bot from the test environment Q61 to the productive environment P61. UiPath recognizes all GUI elements on the Q61 and enables automation without any problems. However, if I open P61 from SAP Logon 770 (see figure SAP_3), which at least visually appears completely identical and also takes place within the same software environment, no more GUI elements are recognized in the lower section. Strangely enough, however, it still recognizes the upper GUI element next to “Neues Kennwort” (translated “news password”), but nothing below it. Even after logging into P61, automation of the lower body is not possible.
Has anyone had similar experiences? Are there any administrative settings that need to be requested from IT?
yeah I tried this one but it doesn’t make any difference.
I’m aware of the logon function, but I don’t think it solves the problem that UiPath doesn’t recognize the GUI elements even after logon so that’s why I didn’t try it yet.
the scaling was a good try. I scaled down back to 100% but it didn’t work. TBH didn’t expect it to because I’d expect UiPath to fail on the test environment as well.
But I’ll definetly check out the setting option. This looks like something that might apply here. Thx!
Yeah the SAP scripting options are 2-fold. You need to enable it server side and client side.
When you switch environments, like you did from Q61 → P61 the scripting options need to be verified and set there as well. Most likely the server side setting has not been done.
And again, when you plan to eventually run the automation in an unattended mode, be sure to check the installed client on the runtime environment(s) as well. Else you’ll encounter the same issue again.