on ‎2013 Nov 03 8:30 PM
Hello,
we are using SRM7 with NWBC and I created a URL to get directly to the the shopping cart:
That works fine. But when I jump to our 3rd party catalog provider and transfer the shopping cart back, I get an error without any further information, just "An error has occurred". This URL was called:
When I use the link http://xxx.xxx.com:8001/sap/bc/nwbc/srm/ I have to do one click more ('Shop'), but it works.
Has anybody an idea?
Thanks and regards
Johannes
Request clarification before answering.
Hi Johannes,
I'm sorry to bother you but I was wondering whether you have been able to solve the issue.
From my point of view SAP seems to have programmed SRM in a way that we can't call the webdynpro shopping cart application directly and then use it to import catalog data.
We ran in to the same issue today and found you post. Have you been able to the issue?
Thank you for any inputs and responses. If we manage to find out how we resolved this we'll share it here as well.
Kind regards,
Tim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Tim,
I could not solve this issue. I was in contact with SAP. The current design does not allow that, using an external catalogue. Now we go the mainpage and are using the standard "way". This is one click more than a direct link.
If you find another solution, please let me know.
Regards
Johannes
Hi Johannes,
could you please show, how have you defined SC-App in the role.
I'll try to reproduce it in our system.
Regards
Konstantin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Johannes,
how do you jump to catalog? From sholling cart or directly from NWBC?
Regards
Konstantin
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Konstantin,
I jump from Shopping Cart (standard). Just the link to the shopping cart is created manually.
Here you find the config of the external webservice:
| 0 | https://xxx.xxx.com/catalog/login!submitLogin.action 0 URL |
1 VIEW_ID xxx 2 Festwert
2 VIEW_PASSWD xxx 2 Festwert
3 USER_ID sy-uname 1 SAP-Feld
4 BRANDING search5 2 Festwert
5 EASYORDER 1 2 Festwert
6 LANGUAGE DE 2 Festwert
7 COUNTRY DE 2 Festwert
8 ~Target _top 2 Festwert
9 OCI_VERSION 4.0 2 Festwert
52 ~OkCode ADDI 2 Festwert
54 ~caller CTLG 2 Festwert
| 55 HOOK_URL | 4 Rücksprung-URL | |
| ___ ____________________ ____________________________________________________________________________________________________________________________________ |
Hello Konstantin,
yes the hook-url is different. See below.
Any idea how to solve this problem?
Thanks and regards
Johannes
This is working:
%2fsrm
%2f%3fsap-nwbc-has_post_params%3dX%26sap-client%3d001%26sap-language%3dDE%26sap-nwbc-node%3dapp_window_body%26sap-nwbc-action_url%3d
%252fsap%252fbc%252fwebdynpro%252fsapsrm%252fwda_l_fpm_gaf%253bsap-ext-sid%253d6Aa5FqI47jEHgHxs3qhVpG--6Aa5FqI47jEHgHxs3qh_pG--%253fsap-ep-tstamp%253d20131104130224%2526sap-wd-tstamp%253d20131104130224%
26NavigationTarget%3dportal_content%2fnwbc_back%3fsap-nwbc-context%3d
03HA33B030D633D533D233B23434D00F760C080EF2D577F50DF0F18F7475353032373080CB1B1819181B1818181717E51A180738817986060600
%26NavMode%3d3%26UsePost%3dTrue%26SAPSRM_RESUME_ID%3dSAPSRM_OCI
This is not working:
%2f%3fsap-nwbc-has_post_params%3dX%26sap-client%3d001%26sap-language%3dDE%26sap-nwbc-node%3dapp_window_body%26sap-nwbc-action_url%3d
%26NavigationTarget%3dportal_content%2fnwbc_back%3fsap-nwbc-context%3d
03HM33B030D633D533D233B234000104CFC8C0182C621CE004661A1A180000
%26NavMode%3d3%26UsePost%3dTrue%26SAPSRM_RESUME_ID%3dSAPSRM_OCI
Hi Johannes,
have you checked following notes?
https://service.sap.com/sap/support/notes/1603168
http://service.sap.com/sap/support/notes/1865170
Regards
Konstantin
Hi,
the hook-url generated in this class is equal in both scenarios. I took a look at the outbound handler. Here the http-request reads with a system call the parameters. Here it is different. So I think the difference is somewhere between the call of the class you mentioned and the call of the outbound handler.
Regards
Johannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.