Skip to Content
0
Former Member
Mar 29, 2010 at 07:56 AM

External Catalogs of SRM 5.0 not working in SRM 7.0

211 Views

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