on 02-07-2008 5:29 AM
Hello All,
We have installed and configured ESS MSS Business package. Under ESS when I click on Change own data, and if I enter the values like say Extension, Building Number, Room Number, etc. and click on review and save then I am getting following error message:
An exception occurred that was not caught., error key: RFC_ERROR_SYSTEM_FAILURE:
Then I checked the dump in ECC system. It is as below:
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_HRPA_INVALID_SUBTYPE
Date and Time 02/04/2008 07:28:51
----
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_HRPA_INVALID_SUBTYPE' 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_HRPA_READ_TIMECONSTRAINT===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 that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_SUBTYPE', was not
caught in
procedure "HRXSS_COD_SAVE_PERSONAL_DATA" "(FUNCTION)", nor was it propagated by
a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Subtype 0005 Not Permitted for Infotype 0105 &TCLAS&
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_HRPA_INVALID_SUBTYPE"
"CL_HRPA_READ_TIMECONSTRAINT===CP" or "CL_HRPA_READ_TIMECONSTRAINT===CM002"
"IF_HRPA_READ_TIMECONSTRAINT~COMPUTE_TIMECONSTRAINT"
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.
The exception must either be prevented, caught within proedure
"HRXSS_COD_SAVE_PERSONAL_DATA" "(FUNCTION)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
Please suggest the solution.
Hi,
The problem was the result, because we identified that the infotype 105 subtypes within the source code are "hard" standard service "change own data". Some of these subtypes were modified by the customer definition, a situation that generated the error, therefore, we proceeded to carry back the standard server tables 000 to 100. Fixed issue.
I hope it helps someone
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
10 | |
9 | |
9 | |
9 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.