on 05-12-2011 7:30 AM
Hi All,
We are on SRM 7.0 and ECC 6.0.
We have just recently set up our SRM 7.0 system along with the portal. SSO, UWL etc have been configured in the Portal.
Now when the user logs in to create a shopping cart and clicks on the
1. Employee Self Service link, he gets the following error :
The URL http://sapsrmdev:8003/sap/bc/webdynpro/sap/powl/ was not called due to an error.
Note
The following error text was processed in the system ASR : Die URL enthält keine vollständige Domainangabe (sapsrmdev statt sapsrmdev.<domain>.<ext>).
The error occurred on the application server SAPSRMDEV_ASR_03 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: STARTUP_CHECKS of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
PS : The user has the standard employee self service role in the portal and employee role in the backend.
Also the service sap/bc/webdynpro/sap/powl/ is active.
Please provide inputs.
Regards
Edited by: sivakumar lakshminarayanan on May 12, 2011 11:56 AM
I'd follow what the error message is trying to tell you - you need the fully qualified domain name for your URL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jay,
I maintained the FQDN as you mentioned.
Now I am getting a different error when I click on Employee Self Service link.
The URL http://sapsrmdev.patni.com:8003/sap/bc/webdynpro/sap/powl/ was not called due to an error.
Note
The following error text was processed in the system ASR : An exception occurred that was not caught.
The error occurred on the application server SAPSRMDEV_ASR_03 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: GET_LAYOUT of program CL_POWL_PERS_ACCESSOR=========CP
Method: INITIALIZE of program CL_POWL_MODEL=================CP
Method: HANDLEDEFAULT of program /1BCWDY/AFSW3OIPJU90DEGN2AMU==CP
Method: HANDLEDEFAULT of program /1BCWDY/AFSW3OIPJU90DEGN2AMU==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/AFSW3OIPJU90DEGN2AMU==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_IF_VIEW=====CP
Method: DISPLAY_TOPLEVEL_COMPONENT of program CL_WDR_CLIENT_COMPONENT=======CP
Method: INIT of program CL_WDR_CLIENT_APPLICATION=====CP
Method: IF_WDR_RUNTIME~CREATE of program CL_WDR_MAIN_TASK==============CP
Method: HANDLE_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Regards
I can't tell any more what might the problem be. However, I'd suggest that you put an external breakpoint in the method GET_LAYOUT. Go to transaction SE38, enter program name "CL_POWL_PERS_ACCESSOR=========CP" and double click on GET_LAYOUT method. Run the scenario and see where you get the uncaught exception.
Can you please explain what Lisa is trying to say? What do we need to maintain under Personalisation Hierarchy?
I think Lisa might be on to the correct path for you. Follow her first response. If you can't find the exact IMG path (transaction code SPRO), do a search for the branch name and you should find it. Once you are under "Edit Personalisation Hierarchy", you just need to make sure one of those two "Personalization Application" is there. Then you move on to her next steps. But first, as she suggested, you have to debug to find out exactly which application is giving you the dump. So, I'd suggest that you
1) Make an External break point in class CL_POWL_PERS_ACCESSOR, method GET_LAYOUT and run your scenario. When the break point hits, run to line "CALL FUNCTION 'FPB_PERS_READ_FOR_USER'" and check what "l_appid" is.
2) With the l_appid you got from step 1, follow Lisa's response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.