cancel
Showing results for 
Search instead for 
Did you mean: 

Vendor e-catalog problem after upgrade to SRM7

Former Member
0 Kudos

Hi all,

We are upgrading from SRM4 to SRM7 and now testing on some existing external web serivces which punch out to vendor e-catalogues. However, we found that one of the vendor e-catalog has problem and the symptom is like this:

- punch out success, vendor e-catalog welcome our logon

- when navigate on vendor e-catalog, it reports error that we have not logon

After debug with vendor IT, it seems that the SRM7 (working with portal) connect a new session for every screen change on vendor e-catalog. Due to the change of session ID, the vendor e-catalog cannot work properly.

Is there any configuration that can be done on SRM7 or portal to solve this problem? If not, what can be update at vendor e-catalog (sorry that I'm not familar with web)? Thanks in advance.

Regards,

Donald

Accepted Solutions (0)

Answers (1)

Answers (1)

jason_boggans
Active Contributor
0 Kudos

Hi Donald,

SRM 7.0 will not intiate a new session for page transition, one sesson is initiated for teh frame you are in while inside the external catalog. If new sessions are generated it must be something that the vendor catalog sends some instruction or data back to SRM with each page transition, only on Catalog checkout should the catalog application return data to SRM_SERVER.

Also make sure you are calling the catlaog with POST method not with GET

Regards,

Jason

Former Member
0 Kudos

Hi Jason,

Thanks for your response. We are calling the catalog with POST method. In SRM7, I found that the e-catalog was wrapped by "Launchpad Start URL". Is that some sort of web iframe and which may affect the session?

Regards,

Donald

Former Member
0 Kudos

The problem was resolved after vendor e-catalog add a Privacy Preferences Project (P3P) compact policy header to their child content web page.

jason_boggans
Active Contributor
0 Kudos

HI Donald,

With regard to the launchpad wrapper, see note [1249323 |https://service.sap.com/sap/support/notes/1249323]for clarification on this entry.

Regards,

Jason