cancel
Showing results for 
Search instead for 
Did you mean: 

HOOK_URL in punch-out catalogue

Former Member
0 Kudos

Hi all,

I try to make a connection with a punch-out catalog but can't get it to work propperly.

The suplier says the HOOK_URL has to be maintained by a url provided by us, but when I read the documentation the HOOK_URL isn't mandatory and is filled automaticly.

Is it possible that the HOOK_URL has to be filled and how do I get the wright url?

Kind regards,

Jorgen

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi again, just had another thought. Has the supplier not worked with punch out before?

If they have ask them how they find the hook URL for other customers.

I have worked with several suppliers setting up punch out catalogues and none of them have never asked me about the hook URL, they seem to know how to find it themselves without asking.

Regards,

Dave.

Former Member
0 Kudos

Hi David,

Thank you for your clear answer.

What I understand is that the field of the hook_url in the call structure is always blank.

The strange thing is, when I put the logon data and hook_url in the url in the first field in the call structure, the catalogue is called correctly (but return an error when ordering to SRM).

E.g. http://www.supplier.nl/bestellen/oci/oci.html?USERNAME:<uname>&PASSWORD:<pword>&HOOK_URL=&;

And when I devide those vallues in separate fields in the call structure the catalogue is called different and an extra logon at catalogue side is required and there is no option toextract the SC from the catalogue to SRM.

e.g.

10. url

20. username

30. pasword

40 hook_url

Is there something I'm doing wrong?

This is the first SAP Punnch-out connection from the supplier.

Regards,

Jorgen

Former Member
0 Kudos

Hi. SRM automatically adds those fields on.

You should just put them in the catalogue call structure and it should sort itself out.

The URL in the call structure should just be the basic URL that the supplier gives you, user name, password and hook URL will be added by SRM.

That must be how the supplier gets the hook URL actually, SRM will add it on to the URL that it calls. Can the supplier not pick it up from there?

If it is asking you for a user name and password that would indicate that the user name or password in the call structure config is wrong. Check it again with the supplier and watch the case. Also check that you are using the correct URL.

Regards,

Dave.

masa_139
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

HOOK_URL is filled by application. You can check the http post parameter in httpWatch tool.

If system is SRM 7.0, HOOL_URL value is like this.

https://<host>:<port>/sap/sapsrm/inbound_hdlr?TARGET_URL=https%3a%2f%2fp<host>%3a<port>%2firj%2fport...

Regards,

Masa

robin_janke
Contributor
0 Kudos

Hi Jorgen,

in the call URL I hope the parameters are passed as "USERNAME=<uname>&PASSWORD=<pwd>" (notice the = instead off :).

Otherwise it doesn't work using the separate fields, then you would have to use the single URL way. So in your call structure you would have:

10 URL http://www.supplier.nl/bestellen/oci/oci.html?USERNAME:<uname>&PASSWORD:<pword>;

20 HOOK_URL

If that doesn't work:

Open the login page then rightclick->view source in your browser and check out the fieldnames of the form for username and password.

It might be that those names are case sensitive.

As David said, HOOK_URL is generated automatically by SRM.

The way back to SRM is another matter. Just before the data should be transferred view the source of the page that sends the data back (rightclick->view source),

the ACTION parameter of the form should be the generated HOOK_URL.

As this is the first punchout implementation of the vendor, there might be some issues there.

Regards,

Robin

Former Member
0 Kudos

Hi. The hook URL is generated every time you open a catalogue and is unique to that session, so that if 2 users are using the catalogue at the same time the correct data is returned.

When SAP calls the catalogue it should pass the hook URL as a field that the catalogue can read and then post the catalogue data to when returning to SRM, so that SRM knows where to pick the data up from.

When you open a catalogue you can see a large string across the top of the internet explorer window before the name of the catalogue is shown, this long string is the hook URL.

That is all I know I'm afraid, I am not too sure how the supplier can read the hook URL in, but it should be passed over from SRM as standard, as long as you have the blank field in the call structure.

Regards,

Dave.