topic Re: Regarding warning messages in Application Development and Automation Discussions

Regarding warning messages

Former Member — Wed, 16 May 2007 06:39:33 GMT

Hi ,

Iam using call transaction(tcode ff67).

In this iam getting warning in foreground where as in background it is not showing the

warning message. In background the record is being saved.

If there is any warning message in background how to handle the situation.

Re: Regarding warning messages

Former Member — Wed, 16 May 2007 06:53:21 GMT

Hi Vijay,

As continously, we were discussing about same point again and again.

<b>See, only in foreground , we can see all types of messages.But in background, we cannot see any messages. If you want to see or capture all those messages.

Write tour call transaction like this

CALL TRANSACTION 'Your tcode' USING tbl_bdcdata

MODE 'N'

UPDATE 'S'

MESSAGES INTO tbl_bdc_msg.

IF sy-subrc NE 0.

MOVE sy-subrc TO w_subrc.

ENDIF.

*Moving the error message into a table.

LOOP AT tbl_bdc_msg.

IF tbl_bdc_msg-msgtyp = 'E'. here you can keep 'W' for warnings.

PERFORM get_text_message.

MOVE tbl_string-w_mstring TO tbl_bdc_error-w_bdc_error.

MOVE tbl_bdc_msg-msgid TO tbl_bdc_error-msgid.

MOVE tbl_bdc_msg-msgnr TO tbl_bdc_error-msgnr.

APPEND tbl_bdc_error.

CLEAR tbl_bdc_error.

ENDIF.

ENDLOOP.

</b>

Thanks

Manju.

Re: Regarding warning messages

Former Member — Wed, 16 May 2007 06:54:14 GMT

Hi,

If you are getting warning messages then no need to handle them in background.

they will be automatically ignored.

Regards,

Atish

Re: Regarding warning messages

Former Member — Wed, 16 May 2007 06:56:39 GMT

warning message is a type of message where the user can still go ahead in processing the transaction.

say for example a person is getting warning message in foreground. if he hits ENTER, he can proceed further. whereas in background, the warning messages occured are overtaken and the processing is done further similar way.

warning message is not error message, it is just like information. so no need to interrupt the process in case of such messages.

you can read the warning message in call transaction method using the internal table with structure BDCMSGCOLL.


DATA: it_bdcmsgcoll like bdcmsgcoll occurs 0 with header line.
CALL TRANSACTION 'XYZ' - -- -- -- - messages into IT_BDCMSGCOLL.

in that structure you have a parameter MSGTYP. you can read the internal table with key MSGTYP = 'W'.

hope this info helps you

thx

pavan