on 11-14-2006 1:25 PM
Hi,
We are using the portal in our application. For dispalying the error messages we have gone to the BADI and implemented the same. We have created a message class and assigned this to the exception class which we are then raising. The syntax is :
RAISE EXCEPTION TYPE ZCX_ZKPS_XRPM_ERRORS
exporting textid = ZCX_ZKPS_XRPM_ERRORS=>ZCX_ERROR2.
However the problem here is that the length is restrictive. We also tried out with assigning the long text explicitly in the text of the message class, but in such a case, the exception was being raised without the message being displayed. I dont want any restrictions on the length of the message text. Would be nice if somebody could help out urgently in such a situation.
Regards,
Jaydeep.
Which BADI are you referring to?
From an xRPM perspective there is a class <i>
cl_rpm_message_services
</i> that is being used to handle the messages. When I look at the comments in the <i>
message_add
</i> method states that <b>'as the allowed length for the message text is only 200'</b>. If you look at method<i>
MSG_ADD_FREE_TEXT
</i> of the class <i>
cl_cgpl_application_log
</i> which seemed to be used to handle the messages. It calls function <i>
BAL_LOG_MSG_ADD_FREE_TEXT
</i> which declares <i>l_string</i> as only 200 characters long.
I know this does not solve your problem but could point you in the correct direction.
You can also look at the WD4A component <i>WDR_MESSAGE_AREA</i> on more ways on doing this.
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.