Only messages sent with MESSAGE are collected in BDCMSGCOLL (CTU) or logged (BI), except if: • MESSAGE is used with one of these additions (the message is handled internally by the program): • MESSAGE … INTO … • MESSAGE … RAISING … • Those sent inside a function module (and in its called procedures) called with EXCEPTIONS error_message = are also not collected. • or if the message makes the program abort or dump. Situations are explained here: SAP Library – Screen programming – Message Processing • In A and E (and D/H) display mode, messages 00344 (“No batch input data for screen & &”) are not displayed and not returned (except for BI session with expert mode activated). • In BI, messages 00355 are not returned if the BI session is not run with “Detailed log” • There is also the case where the message is returned, but not displayed: when you display the BI session log, messages 00162 and 00368 are not displayed if you didn’t tick the “Details” checkbox A frequent issue is
