on 10-27-2015 3:39 PM
Hello all,
we used to display messages for wrong user entries by using exit variables in exit EXIT_SAPLRRS0_001 and this function module:
CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
EXPORTING
i_class = 'ZCO05'
i_type = 'E'
i_number = '102'
i_msgv1 = l_d_yearmonth_to
i_msgv2 = l_d_yearmonth_tvarvc.
RAISE wrong_value.
But this isn't working anymore with the new exit BAdI RSROA_VARIABLES_EXIT_BADI. The replacement
RAISE EXCEPTION TYPE cx_rs_error.
for
RAISE wrong value.
only prevents the output of the report but doesn't displays the above message. I also tried CX_RS_ERROR_WITH_MESSAGE and CX_RSB_GUI_ERROR_WITH_MESSAGE - with no luck!
Is there a solution for this issue?
Best regards, Martin
Message was edited by: Martin Lehmann:
I have one interest observation to add: when I use only
CALL FUNCTION 'RRMS_MESSAGE_HANDLING'
EXPORTING i_class = 'ZCOVS'
i_type = 'E'
i_number = '1'
i_msgv1 = ie_year_to
i_msgv2 = sy-datum(4)
EXCEPTIONS dummy = 1
OTHERS = 2.
without raising any error class, the error message will be displayed in BEx - BUT: then the BEx report is displayed too!
Therefore this is not a solution that leads to the desired results (display of the error message AND prevention of the BEx output)...
One additional information:
We use BW on Netweaver Version 7.31.
Message was edited by: Martin Lehmann
Hallo , the problem is solved - the solution was the identification of a missing CX_RS_ERROR as exception Parameter.
Best regards, Martin Lehmann
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
10 | |
10 | |
9 | |
9 | |
7 | |
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.