topic Re: Error message in ABAP class in Application Development and Automation Discussions

Error message in ABAP class

Former Member — Thu, 02 Aug 2012 05:32:18 GMT

Hello ,

I have standard class, in this class there is a bapi used . In this bapi a error messaged is raised.

How can i capture this error message in my z FM.

Please note that there is no expection in the standard class and error message is raised by the bapi.

ZFM ---> standard class ----> Bapi.

Re: Error message in ABAP class

Former Member — Thu, 02 Aug 2012 13:51:51 GMT

Please call the ZFM within TRY...CATCH..ENDTRY block.

In CATCH, you can catch exception into a reference variable (for example CX_ROOT) and get the message from GET_TEXT method.

Re: Error message in ABAP class

alex_campbell — Thu, 02 Aug 2012 19:24:22 GMT

According to OP, standard class does not raise any exception, so TRY...CATCH... has nothing to catch.

Re: Error message in ABAP class

alex_campbell — Thu, 02 Aug 2012 19:24:39 GMT

If the standard class doesn't expose the error to you, there's nothing you can do about it. Check to see if the class has any error parameters, or sets any attributes, with the error data. That's the point of classes, give the calling program (in your case, ZFM) access to what it needs, and hide from it everything else.

If you post which class you are using, and how you're calling it, someone with experience with that class may be able to be helpful

Re: Error message in ABAP class

Former Member — Fri, 03 Aug 2012 19:56:22 GMT

Hello Alex,

thanks for ur help.

FM : /SAPRCX/SHPPLC

Class :

CALL METHOD g_shp_appl->place_railcar.

I am calling the above fm in another z fm.

thanks

amit

Re: Error message in ABAP class

bharat_rathod2 — Sun, 05 Aug 2012 06:33:24 GMT

Dear Amit,

please give class name which u r using and how u r using it.

if you want to capture error message which is raised in bapi then create z class and modify it.

Re: Error message in ABAP class

matt — Thu, 09 Aug 2012 14:16:48 GMT

Don't catch CX_ROOT. You should only catch exceptions you're expecting to have raised, and react to those accordingly. If you get an unexpected error and use CX_ROOT, it can be a pain to find the cause of the error - as those who use BW will know...