Why does the SAP BAPI activity fail to connect when the connection wizard is successful?
Issue Description:
When migrating to SAP S4 from On-prem ECC, it may be possible to authenticate correctly with the SAP BAPI activity , but may find that it does not return a call when executed. Searching for existing BAPIs throws an error. Installing the SAP connector does not seem to correct the issue. It should be possible to connect using the SAP GUI.
The RPA machine runs SAP GUI 7.50, however even if the 3.0.25.0 connector, UiPath Studio still runs 3.0.19.0, which is part of the GUI package.
Resolution:
After removing the SAP GUI 7.50 and installing the SAP connector 3.0.25.0, UiPath Studio works perfectly with S4 BAPIs, communicating with S4D without error.