cancel
Showing results for 
Search instead for 
Did you mean: 

SRM 7 OCI issue: Hook_URL always blank, BSP error

Former Member
0 Kudos

I have an OCI 4 compliant punchout catalog application that I am trying to integrate with a client who is using SAP SRM7. Regardless of what the client does in SRM, the punchout requests always have a blank for the hook_URL. I understand that hook_URL is left blank in the set up of the punchout, and that SRM is supposed to fill in the hook_URL at runtime so that the URL contains a unique session key that facilitates write-back of the cart contents. However, the punchout GET posts arrive at the store application with an empty hook_URL. Here is an example of what we log from the punchout requests at the store application end:

We get this error after submitting the cart session from the application:

The OCI config looks like this:

Can anyone offer suggestions about how to debug this?

Kevin

Accepted Solutions (0)

Answers (1)

Answers (1)

0 Kudos

Hello Kevin,

Could you kindly implement below notes and retest the issue.

2295808 - LPD: Missing encoding of special Launchpad parameters

2321292 - Forbidden Catalog Exception will occur during Catalog Transfer

Also, please check if SICF service is activated for ctlg_wrapper.

(Path: sap/bc/bsp/sapsrm)

Regards,

Bhanupriya

Former Member
0 Kudos

Hi. Thank you for the suggestion. It may take 24 hours to run a test. The testing group is +5 hours from us and sometimes they only work in their own time zone. But I will try it!

Former Member
0 Kudos

Hi. No luck with these suggestions. The first one is not compatible with our SAP version and the second one is already implemented.

Can you think of any other reason why the hook_url parameter is not populated by SRM in the punchout request?

I have seen many people suggest that POST should be used. Presently our system is configured to use GET. Could that be the reason?

Kevin

0 Kudos

Hi Kevin,

Could you kindly change the system to use POST and retest the issue?

If issue still persists, kindly upload a HTTPWatch trace for the scenario.

Regards,

Bhanupriya