Capture errors in standard Function Module

[aidan_mulcahy]

Hi,

I am using WS_DELIVERY_UPDATE, but question relevant for any similar FM really.

Sometimes, this FM will fail deep inside its code and outputs a hard 'E'rror and kills the process.

Previously, for other FM's, I have used:

call function '...'

IMPORTING...

EXPORTING...

EXCEPTIONS

OTHERS = 99.

to capture these errors. But WS_DELIVERY_UPDATE does not have any EXCEPTIONS (just a PROT table).

Any way of catching the errors so I can log the data in a better way in my own code rather than just crashing out?

Thanks.

[arseni_gallardo]

Use:

  EXCEPTIONS

      error_message = 1.

It is documented,

[aidan_mulcahy]

Bahh!!!

Thanks Arseni. Where was it documented? Couldn't find it.

I've always used OTHERS = 99 and that normally works.

ERROR_MESSAGE = 1 worked perfectly.

Thanks again.

[arseni_gallardo]

Take a look here http://help.sap.com/saphelp_nw04/helpdata/en/9f/db98ef35c111d1829f0000e829fbfe/frameset.htm

Calling Function Modules in ABAP

To call a function module, use the CALL FUNCTION statement:

CALL FUNCTION <module>
     [EXPORTING  f₁ = a ₁.... f _n = a _n]
     [IMPORTING  f₁ = a ₁.... f _n = a _n]
     [CHANGING   f₁ = a ₁.... f _n = a _n]
     [TABLES     f₁ = a ₁.... f _n = a _n]
     [EXCEPTIONS e₁ = r ₁.... e _n = r _n [ERROR_MESSAGE = r _E]
                                     [OTHERS = r_o]].

[former_member213851]

Hi ,

You can create Z FM 'ZWS_DELIVERY_UPDATE' by copying existing WS_DELIVERY_UPDATE nad then inside Exceptions tab you can add your own Exceptions via SE37.