External Catalogs of SRM 5.0 not working in SRM 7.0

[Former Member]

Hi all,

Iu2019m in the process of converting all SRM 5.0 punchout catalogs to SRM 7.0.

All catalogs are working fine in SRM 5.0 but not in SRM 7.0.

For one I got a problem autologgin into the vendor catalog page.

In SRM 5.0 we are using ITS (no portal). For SRM 7.0 we are using SAP-Portal.

Iu2019ve traced SRM 5.0 punchout and SRM 7.0 punchout:

SRM50:

strUserName=XXXXX&strUserPwd=XXXXX&strLiefNr=XXXXX&HOOK_URL=https%3A%2F%2FXXXXX.XXX.ads%3A8002%2Fsap%28cz1TSUQlM2FBTk9OJTNhYWJhaGFjaGlfU1JEXzAwJTNhZjF2UUpGTlZWa1FFUFZrcDRXcDk5eDEwdDBBSUNnSE01V3pXQkY5Sy1BVFQ%3D%29%2Fbc%2Fgui%2Fsap%2Fits%2Fbbpsc03%2F%3F%7EOkCode%3DADDI%26%7Etarget%3D_top%26%7Ecaller%3DCTLG%26%7Eclient%3D100%26%7Elanguage%3DDE%26%7EHTTP_CONTENT_CHARSET%3Dutf-8&OCI_VERSION=4.0&OPI_VERSION=1.0&returntarget=_top

SRM70:

sap-client=100&sap-language=D&strUserName=XXXXX&strUserPwd=XXXXX&strLiefNr=XXXXX&OCI_VERSION=4.0&OPI_VERSION=1.0&returntarget=_top&HOOK_URL=http%3A%2F%2FXXXXX.XXX.ads%3A8000%2Fsap%2Fsapsrm%2Finbound_hdlr%3FTARGET_URL%3Dhttp%253a%252f%252fvangogh%252eafg%252eads%253a50000%252firj%252fportal%253fNavigationTarget%253dpcd%253aportal_content%252fcom%252esap%252epct%252fspecialist%252fcom%252esap%252epct%252esrm%252esrm70%252fcom%252esap%252epct%252esrm%252ecore%252efl_core%252fcom%252esap%252epct%252esrm%252ecore%252efl_roles%252fcom%252esap%252epct%252esrm%252ecore%252ero_employeeselfservice%252ffl_goshopping%252fcom%252esap%252epct%252esrm%252ecore%252eiv_shop%2526NavMode%253d3%2526UsePost%253dTrue%2526SAPSRM_RESUME_ID%253dSAPSRM_OCI&CATALOG_URL=http%3A%2F%2Fshop.xxxdaten.de%2Fcommerceportal%2Focisrm_autologin.asp

I guess the differences in the punchout call is the reason for the failure in the autologin.

I thought OCI u2013 interface is standardized. Both punchouts are with OCI-Version 4.0, but the call is different!

Have I missed some settings? Is it possible to customize the punchout call e.g. to exclude the system added parameter "sap-client=100" because this is not used ins SRM50 punchout?

Or is it the task of the vendor to customize his system to the SRM 7.0 punchout logic?

Thanks for all of your inputs

Regards

Stefan

[Former Member · Accepted solution]

Hello Stefan,

Did you read this recent post: [;

He resolved his punchout problems via OSS message: implementing an internal note. He didn't post the exact note though.. Maybe you can put a post there asking for the note he implemented.

Kind regards,

Tim

[Former Member · Accepted solution]

Stefan,

I see you have the main parameters userid, password etc on the call structure that should have got you to the autologin page of the Supplier.

The best way is to check with the Supplier and see what they check for Autologon in URL parameters. Here are couple of variations I noticed in SRM 5.0 and 7.0 calls from your machine. You may want to try these first before approaching the Supplier.

You are missing ~HTTP_CONTENT_CHARSET=utf-8 parameter in SRM 7.0. Can you try adding UTF-8 as CODEPAGE on the External Webservice definition?

Another parameter that is missing or not being sent is the "~language=DE" in SRM 7.0. Try adding that to call structure as well.

SG

[Former Member · Accepted solution]

Have tried the parameters and entered the codepage in the webservice but it doesn't work.

[Former Member]

Hi all,

I've contacted my suppliers and we have found the why the catalog call wasn't working.

One catalog Url contains two ? and the SAP-system truncates the part of the URL after the "?" and browser

displays an HTTP error (400) "The webpage cannot be found".

I've sent a message to SAP to resolve this issue.

The second catalog call was working but the login failed.

It was a problem of Internet Explorer authority.

I had to set the vendor web-shop-site as trustable.

Thanks for all your input!!

Stefan

[Former Member]

All,

We seem into run into similar issues once we upgraded from SRM 5.0 to SRM 7.0 Our catalog punchouts to ARIBA On-deman catalogs are not working. We have opened an OSS message with SAP so far none of the suggested options are working for us. ARIBA is also unable to help us.

We suspect our issue is failing within SAP and OCI is not writing any application logs (SLG1) etc, So it has been difficult to troubleshoot.

From the SRM Portal side, when we try to launch CATALOGS page in SRM 7.0, it fails right away with the following error

"Error connecting to Catalog; contact your System Administrator "

There are no errors anywhere on SRM box to investigate.

We are on SRM 7.0 Support pack level 6. So Note 1429685 - Empty importing parameter in BADI BBP_CAT_CALL_ENRICH is part of support pack 6.

We have also applied the note 1405908 - Issues with 3rd Party catalog integration with SRM 7.0 as per SAP, still no resolution.

Any suggestions !

[Former Member]

Hi all,

We have an issue where the punch-out is not wokring because the supplier validates that the HOOK URL is not more than 400 chars, which is failing in SRM 7.0 now.

Does OSS note 1405908 fix this? The note is not available any more - can send provide the fix details if so?

We will ask our supplier to change their validation on thieir side but this is going to take a long time and we would like to be able to go-live soon, so wondered if there is a quick fix to shorten the HOOK URL.

Best regards,

Nicjk

[Former Member]

Stefan,

You might need to consult your catalog vendor/provider. We had similar problems when going from SRM 2 - SRM 6. One big difference which has already been noted is the much longer HOOK_URL. Validate your vendor is not expecting a GET method instead of POST. You and your vendor might need to switch to a POST method. Your new punchout URL might also be sending new information that the vendor is not interpreting hence causing the error. In any case, you will most likely need to work with your vendors catalog support team to trace the incoming traffic in order to resolve this.

[Former Member]

Implement

Note 1429685 - Empty importing parameter in BADI BBP_CAT_CALL_ENRICH

[masa_139]

Hi,

What is the exact error message? HTTP 404 etc?

Regards,

Masa

[Former Member]

Hi Masa,

we are using 3 punchout catalogs. All are working fine in SRM 5.0.

SRM 7.0:

- For one (for this one I've posted the punchout call) the vendor page appears - but logon doesn't work

- For one I get response HTTP 400 (Page not found). If I enter the url manually in IE the logon page appears.

- The last one is working fine

Your help will be appreciated.

Regards

Stefan

[Former Member]

Stefan,

Did you try with HTTP GET setting in Catalog definition? Also, try moving HOOK_URL parameter to the bottom of call structure. I have noticed that some vendor sites are not able to extract query string correctly for some parameters below HOOK_URL

SG

[Former Member]

Hello - I had the same problem, and I found OSS Note 1405908. There is a work around for this, however the soluction should be to reach out to your catalog host and have them change config on their end. The Hook URL generated by SRM 7.0 is 600+ characters, much larger than SRM 5.0's Hook URL. Most companies will truncate the long URL and the item will never transfer back in to SRM.

-Eric