Did you submit an SR to get assistance from Ariba Support to troubleshoot the issue?
Ariba Exchange Community Manager
I was getting ready to submit a message to the SAP marketplace, but our implementation partners are seeing the same error in their ECC box as well, my guess is the call structure is bad.
Since I'm new with Ariba functionality - where do you submit the service request for Ariba support? would that be the Ariba connect website?
Yes, you can submit an SR from Ariba Connect
thought I would follow up with this to see if you knew anything about this...
SAP replied back and said I needed to upgrade my SAPGUI to 7.4 patch 4 hotfix 1, (currently on 730 patch 9) so we got a test machine and upgraded the gui on it and it seems to work as expected.
Do you know of any KBA's out there that reference the compatibility issues between the two gui versions? Is this a known issue?
We will probably move forward with the 7.4 installation but our basis administrator is not sure this is the core solution.
In regards of this issue is there a core solution for it? Because after several months I upgraded to SAPGui 740, apparently this is not the core solution if any OSS notes implemented for Ariba in ECC.
So I wonder is there a solid way to solve this issue actually?
Hope for your reply.
I have tried to upgrade to SAPGui 7.4 patch 5 hotfix 1 and indeed it temporary solved the problem of the script popping up. But after certain OSS notes implemented / changes made to the system, the script error message again now pop-out in SAPGui 740 environment.
I'm sincerely asking is there any core solution for this as we really need this to be fixed as soon as possible.
I see that you are getting an error when doing a punchout to APC from SAP ECC.
Please try the below given steps:
-Start Internet Explorer.
-On the Tools menu, click Internet Options.
-On the Security tab, click Trusted sites, and then click Sites.
-In the Add this Web site to the zone box, type the URL of the Web site that is affected, and then click Add.
Now restart the browser and try again. If the error persists then please check with your local IT team. They should be able to help you. In case they are not able to resolve, then you will have to check with Ariba support by logging a ticket using connect.ariba.com. Ariba team will further try to diagnose it by enabling the logging on their side to see where exactly the issue is happening and help you further in resolving this.