Updating custom infotype with FM 'HR_INFOTYPE_OPERATION' dumps

Question

Hi All,
While updating a custom infotype 9008 with FM 'HR_INFOTYPE_OPERATION', its giving adump.
Except.  CX_HRPA_INVALID_PARAMETER.
I am using DIALOG_MODE as '1'. when I enter a valid field value to that particular field ( mandatory field) on that infotype, it gives dump.
Can you suggest something which will solve this?
Thanks.
Dipti.

Answer 1

Hi,
Here is the dump.
Runtime Errors         UNCAUGHT_EXCEPTION
Except.                CX_HRPA_INVALID_PARAMETER
Date and Time          12.11.2008 07:23:32
Short text
An exception occurred that was not caught.
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
Missing RAISING Clause in Interface
Program                                 SAPFP50P
Include                                 FP50PE10
Row                                     2,152
Module type                             (FORM)
Module Name                             RESOLVE_EXCEPTION
Trigger Location of Exception
Program                                 CL_HRPA_RESOLVE_EXCEPTION=====CP
Include                                 CL_HRPA_RESOLVE_EXCEPTION=====CM001
Row                                     80
Module type                             (METHOD)
Module Name                             RESOLVE
Source Code Extract
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.
Regards,
Dipti.