topic RAISE Statement is giving DUMP. in Application Development and Automation Discussions

RAISE Statement is giving DUMP.

Former Member — Mon, 11 Aug 2008 04:33:09 GMT

hi,

i was created Custom function module there i was reaised Exceptions.In FM it is working fine.

That FM I am using into One method.when I am executing through my transaction it is giving DUMP in RAISE statement.

Please Help me.

regards,

kumar

Re: RAISE Statement is giving DUMP.

Former Member — Mon, 11 Aug 2008 04:36:08 GMT

Hi Kumar,

Can you give the exact message that you are getting.

Regards,

Prashant.

Re: RAISE Statement is giving DUMP.

Former Member — Mon, 11 Aug 2008 04:51:59 GMT

hi kumar,

check the lines before raise statement.

Dump is occuring , before raise statement is encountered.

Regards,

Sabari

Re: RAISE Statement is giving DUMP.

Former Member — Mon, 11 Aug 2008 04:54:42 GMT

Hi,

Thanks for Reply.

Error analysis

A RAISE statement in the program "SAPLZFG_HCM_SURVEY" raised the exception

condition "NO_SET_PICKED".

Since the exception was not intercepted by a superior

program, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use

Transaction SE37 (Function Library). You can take the called

function module from the display of active calls.

Source Code...

module 9000_EXIT input.

CASE OKCODE.

WHEN 'EXT'.

> RAISE NO_SET_PICKED.

SET SCREEN 0.
LEAVE SCREEN.

ENDCASE.

regards,

kumar

Re: RAISE Statement is giving DUMP.

Former Member — Mon, 11 Aug 2008 05:14:23 GMT

Is the Function developed by You. if so why are you raising this here...

module 9000_EXIT input.
CASE OKCODE.
WHEN 'EXT'.
------> RAISE NO_SET_PICKED.


ENDCASE.

Re: RAISE Statement is giving DUMP.

former_member195383 — Mon, 11 Aug 2008 05:23:36 GMT

Hi...

This happens in the following scenario...

suppose u have one program P1, that is calling the FM, in which you are raising the exception....

Now...in the FM the exception is raised...but in program P1, u are not catching that exception...

see in the call FM block wheather u have the exception block there or not...if so then check wheather

that perticular exception is inside the exceptionblock of the call function statement or not...

If not then write the same over thr....like below...

call function 'function1'

Exporting

Tables

EXCEPTIONS

Excep1 = 1

Excep2 = 2

Excep3 = 3.