Skip to Content
Oct 08, 2015 at 09:14 AM

Unsure how to handle eo_message in signature of /BOBF/IF_FRW_ACTION~EXECUTE


Hi community,

I am not happy with the exporting parameter eo_message of the interface method /BOBF/IF_FRW_ACTION~EXECUTE .

It would have been nice if the framework would instantiate this and I need not to think about instantiation.

My question is if it is ok to instantiate it once in the constructor of the class implementing /BOBF/IF_FRW_ACTION for the corresponding BOBF action and to assign this instance to a class member which can be consumed if needed.

My doubt is whether this method is called multiple times resulting in adding errors of former call added to the BOBF log.

But I do not want to add in the error handling code the instantiation again and again.

Please advice.

Regards, Jürgen

Message was edited by: Juergen Ette At the moment I do it this way: METHOD constructor. me->bobf_frw_message = /bobf/cl_frw_factory=>get_message( ). ENDMETHOD. METHOD /bobf/if_frw_action~execute. eo_message = me->bobf_frw_message. .... ENDMETHOD. For AUnit I could drive out this productive instantiation by a local /bobf/if_frw_message implementation.