on 2019 Sep 13 2:01 PM
Hi all,
I have a custom built webshop that supports OCI, currently we have a dozen or so clients using the punchout without issue but.. I have one client, on checking out from the webshop the system fails. They are using SAP and posting in the hook_url sapevent:post.
I believe sapevent:post is for the SAP HTML browser and that it is not part of the OCI standard, correct me if I'm wrong.
How do I instruct the client on how to turn off submitting the hook_url as a sapevent:post but instead to generate a full qualified url?
Thanks.
Request clarification before answering.
Hello Martin,
do not understand you problem. You tell us "we have a dozen or so clients using the punchout without issue".
So for them, first and blank parameter for URL catalog provider is populated with Type parameter being 'URL'.
And for your customer with issue, you tell us "The only other difference I can see from the wiki compared to the clients call structure is the parameter name for the URL (Type) is set to URL, would this effect the call structure?".
I let you deduce the conclusion.
Regards.
Laurent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Laurent,
Thank you for your comment, sadly this didn't work. I've asked the client to configure the call structure to the bare minimum, URL, username, password, HOOK_URL, ~OkCode, ~caller and ~target. The same issue is present, the HOOK_URL contains sapevent:post and on checkout the site freezes.
Any help you could provide would be greatly appeciated.
Kind regards,
Martyn
Hi,
The HOOK_URL parameter has to be saved in SAP as blank and should be filled during the catalog call. You can also check this wiki page about the necessary call structure parameters in SAP:
https://wiki.scn.sap.com/wiki/x/GYM8Fg
I hope this helps.
Regards,
Timea
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Timea,
Thanks for the reply, their HOOK_URL parameter is blank and the issue is still persisting. The only other difference I can see from the wiki compared to the clients call structure is the parameter name for the URL (Type) is set to URL, would this effect the call structure? Could it be anything else?
Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.