Hi Hari,here is the enrire dump...
Category ABAP Programming Error
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_HRPA_INVALID_PARAMETER
ABAP Program SAPFP50P
Application Component PA-PA
Date and Time 05.12.2013 08:54:41
What happened?
The exception 'CX_HRPA_INVALID_PARAMETER' 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_RESOLVE_EXCEPTION=====CP' has to be terminated.
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_HRPA_INVALID_PARAMETER', was not caught in
procedure "RESOLVE_EXCEPTION" "(FORM)", 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:
Invalid parameter EXCEPTION, value
The occurrence of the exception is closely related to the occurrence of
a previous exception "CX_HRPA_VIOLATED_PRECONDITION", which was raised in the
program "CL_HRPA_MASTERDATA_FACTORY====CP",
specifically in line 6 of the (include) program "CL_HRPA_MASTERDATA_FACTORY====CM004".
The cause of the exception was:
Precondition Violated
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_PARAMETER"
"CL_HRPA_RESOLVE_EXCEPTION=====CP" or "CL_HRPA_RESOLVE_EXCEPTION=====CM001"
"RESOLVE"
User and Transaction
Client.............. 121
User................ "BHAGUDIAN"
Language key........ "E"
Transaction......... " "
Transaction ID...... "26da25d4623311e3bc0e000000dcaa6e"
EPP Whole Context ID.... "26DA25D4623311E3BC0E000000DCAA6E"
EPP Connection ID....... "09B39DE0623211E3B3BDF13F0A0AF656"
EPP Caller Counter...... 298
Program............. "CL_HRPA_RESOLVE_EXCEPTION=====CP"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Debugger Active..... "none"
Chain of Exception Objects
Attrib. Name Value
Level 1 Class CX_HRPA_INVALID_PARAMETER
Program CL_HRPA_RESOLVE_EXCEPTION=====CP Include CL_HRPA_RESOLVE_EXCEPTION=====CM001 Row 80
Short Te Invalid parameter EXCEPTION, value
Long Tex
IS_RESUMABLE
KERNEL_ERRID
PARAMETER EXCEPTION
VALUE
Level 2 Class CX_HRPA_VIOLATED_PRECONDITION
Program CL_HRPA_MASTERDATA_FACTORY====CP Include CL_HRPA_MASTERDATA_FACTORY====CM004 Row 6
Short Te Precondition Violated
Long Tex
IS_RESUMABLE
KERNEL_ERRID
Information on where terminated
Termination occurred in the ABAP program "CL_HRPA_RESOLVE_EXCEPTION=====CP" -
in "RESOLVE".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 80
of the (Include) program "CL_HRPA_RESOLVE_EXCEPTION=====CM001".
The termination is caused because exception "CX_HRPA_INVALID_PARAMETER"
occurred in
procedure "RESOLVE_EXCEPTION" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPFP50P "; its source code begins in line
2139 of the (Include program "FP50PE10 ".
Source Code Extract (Source code has changed)
Line SourceCde
50 message_handler = message_handler.
51 return.
52
53 catch cx_sy_move_cast_error.
54 endtry.
55 END-OF-DEFINITION.
56
57
58 try_to resolve_missing_infty_data cx_hrpa_missing_infty_data.
59 try_to resolve_missing_authorization cx_hrpa_missing_authorization.
60 try_to resolve_invalid_feature cx_hrpa_invalid_feature.
61 try_to resolve_unexpected_message cx_hrpa_unexpected_message.
62 try_to resolve_missing_personid cx_hrpa_missing_personid.
63 try_to resolve_invalid_infotype_db cx_hrpa_invalid_infotype_db.
64 try_to resolve_invalid_customization cx_hrpa_invalid_customization.
65 try_to resolve_inconsistent_database cx_hrpa_inconsistent_database.
66
67
68 * Just to ensure the macro can be used nowhere else.
69 DEFINE try_to.
70 END-OF-DEFINITION.
71
72 * If we can not remap we would like to just re-raise the
73 * exception like below like "RAISE EXCEPTION exception.".
74 * Unfortunately the kernel will then forget about the
75 * original source position.
76
77 * So this is the fallback strategy. Calling this method
78 * is only allowed if the exception can be resolved. Since
79 * this is not the case we indicate a parameter violation.
>>>>> RAISE EXCEPTION TYPE cx_hrpa_invalid_parameter
81 EXPORTING
82 previous = exception
83 parameter = 'EXCEPTION'.
84
85 ENDMETHOD.
Thanks
Arun
Willkommen jedenfalls 
