on 03-28-2011 3:05 PM
Hi Experts
I am experiencing "UNCAUGHT_EXCEPTION" "CX_WDR_RT_EXCEPTION error when testing Internal Candidate Profile on E-recruiting via transaction se80. We are running EREC 604 and on SP0008. Does somebody knows how to rectify this? There is no log in transaction SLG1 but only Analysis from ST22.
Many Thanks.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_WDR_RT_EXCEPTION
Date and Time 22.03.2011 17:07:46
-
-
Short text |
An exception occurred that was not caught. |
-
-
What happened? |
The exception 'CX_WDR_RT_EXCEPTION' was raised, but it was not caught anywhere |
along |
the call hierarchy. |
Since exceptions represent error situations and this error was not |
adequately responded to, the running ABAP program |
'CL_WDR_COMPONENT==============CP' has to be |
terminated. |
-
-
What can you do? |
Note down which actions and inputs caused the error. |
To process the problem further, contact you SAP system |
administrator. |
Using Transaction ST22 for ABAP Dump Analysis, you can look |
at and manage termination messages, and you can also |
keep them for a long time. |
-
-
Error analysis |
An exception occurred which is explained in detail below. |
The exception, which is assigned to class 'CX_WDR_RT_EXCEPTION', was not caught |
and |
therefore caused a runtime error. |
The reason for the exception is: |
Controller for View, Window, Interface, and Configuration Cannot Be Created |
-
-
How to correct the error |
If the error occures in a non-modified SAP program, you may be able to |
find an interim solution in an SAP Note. |
If you have access to SAP Notes, carry out a search with the following |
keywords: |
"UNCAUGHT_EXCEPTION" "CX_WDR_RT_EXCEPTION" |
"CL_WDR_COMPONENT==============CP" or "CL_WDR_COMPONENT==============CM002" |
"GET_CONTROLLER" |
If you cannot solve the problem yourself and want to send an error |
notification to SAP, include the following information: |
1. The description of the current problem (short dump) |
To save the description, choose "System->List->Save->Local File |
(Unconverted)". |
2. Corresponding system log |
Display the system log by calling transaction SM21. |
Restrict the time interval to 10 minutes before and five minutes |
after the short dump. Then choose "System->List->Save->Local File |
(Unconverted)". |
3. If the problem occurs in a problem of your own or a modified SAP |
program: The source code of the program |
In the editor, choose "Utilities->More |
Utilities->Upload/Download->Download". |
4. Details about the conditions under which the error occurred or which |
actions and input led to the error. |
|
Hi,
actually this error says, that the application did not receive required URL parameters.
In order to run e-recruiting correctly you need to use the portal integration, because the candidate profile is just meant to be called from a list context. Either from search results of the quick search or the list of candidacies.
Please try to use portal.
If you want to try without portal you need to call the workcenter web dynpro or the quick search in order to call the canidate profile.
Best regards
Sebastian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi there,
actually you did also post this error at linkedin, didn't you?
I first thought you might call the candidate profile from the recruiter page. In the thread at linked in I saw, you are using the candidate's view on the candidate profile.
Can you please provide the link you are calling?
Best regards
Sebastian
Hi
Yes, I have placed the same on both:-)
But I really appreciate your assistance, and maybe we can just use SDN as one point of contact for this query?
Okay, you said that I should create a candidate object for the user and check if ICF nodes has been activated. I have done that and still the error exist on the Candidate profile.
I am accessing the candidate profile using the Dev Portal start page(as per your suggestion), then when you click on My Profile the Candidate Profile is supposed to then be displayed for a candidate to maintain the profile. Instead it's where the error occurs.
There are no logs created in SLG1, only the Runtime error is displayed on ST22. The error that I posted on the original post.
Many Thanks
Puleng
Hi Sebastian
The error has been resolved! I updated Table V_T77RCF_COM_CHN and it resolved the error on the Candidate profile. So, the resolution to this error on my side was the URL parameters and Commnunication Channels.
Thank you so much for your efforts, all appreciated:-)
Many thanks
Puleng
Hopefully I won't have errors on other applications as well:-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
105 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.