Catch error messages after submit and return.

[Former Member]

Hello,

I am using the following statement in my report

Submit **** eporting list to memory " **** is the standard report RSFTP002

with ....

with ....

AND RETURN.

CALL FUNCTION 'LIST_FROM_MEMORY'

TABLES

listobject = LOBJECT.

CALL FUNCTION 'LIST_TO_ASCI'

TABLES

LISTASCI = LASCI

LISTOBJECT = LOBJECT.

I am able to catch the output into LASCI.But when there is some message information or error messages then I am not able to catch them. Could you please suggest how to capture the error messages from the standard report which i am submittin in my report. Is there any way to handle this without making changes to standard report.

Thanks in advance

[Former Member]

Hello,

I am using the following statement in my report

Submit **** eporting list to memory " **** is the standard report RSFTP002

with ....

with ....

AND RETURN.

CALL FUNCTION 'LIST_FROM_MEMORY'

TABLES

listobject = LOBJECT.

CALL FUNCTION 'LIST_TO_ASCI'

TABLES

LISTASCI = LASCI

LISTOBJECT = LOBJECT.

I am able to catch the output into LASCI.But when there is some message information or error messages then I am not able to catch them. Could you please suggest how to capture the error messages from the standard report which i am submittin in my report. Is there any way to handle this without making changes to standard report.

Thanks in advance

[praveen_hannu]

why cant you try to use the standard exceptions from FM which it is having. are you talking about the error message from the function module.

[Former Member]

Not the error messages from FM.

Error messages that are thrown by report RSFTP002.

Report 1

;

;

;

Submit RSFTP002 exporting list to memory

with ....

with ....

AND RETURN.

CALL FUNCTION 'LIST_TO_ASCI'

TABLES

LISTASCI = LASCI

LISTOBJECT = LOBJECT.

I am able to catch the output.But when there is some message information or error messages then I am not able to catch them. Could you please suggest how to capture the error messages from the standard report which i am submittin in my report. Is there any way to handle this without making changes to standard report.

[Former Member]

First of all see if there is any data coming from the ABAP memory.

Try catching the exception in FM "LIST_FROM_MEMORY".

Next there are 2 exceptions in FM "LIST_TO_ASCI"

Try catching them. Then you can come to a conclusion if there is any output messages of the report submitted.

Let us know the status thereafter.

Regards,

Srinivas

[Former Member]

Yes As I mentioned in my first mail , I AM ABLE TO CATCH THE OUTPUT INTO LASCI but not error messages which thrown from the report RSFTP002. How should one catch the error messages from the Submit and return statement.

[venkat_o]

Hi, <li>You get the error message from RSFTP002, we can not find as it is standard program. If errors are gathered and displayed on RSFTP002 output, we can at least try using LIST_FROM_MEMORY. <li>There are few possibilities where you can get run time errors. press F1 help on SUBMIT statement you will see the below errors. That too those are non-catchable. You need to take not happen those runtime errors. Check the runtime error list.

Non-Catchable Exceptions 
Cause: The specified program was not found. 
"Runtime Error: LOAD_PROGRAM_NOT_FOUND 

Cause: You tried to transfer an invalid value to a selection using the addition SIGN. 
"Runtime Error: SUBMIT_WRONG_SIGN 

Cause: The specified program is not a report. 
"Runtime Error: SUBMIT_WRONG_TYPE 

Cause: You tried to transfer more than one value to a report parameter. 
"Runtime Error: SUBMIT_IMPORT_ONLY_PARAMETER 

Cause: You tried to use WITH sel IN itab to transfer a table that does not have the appropriate structure to a selection. 
"Runtime Error: SUBMIT_IN_ITAB_ILL_STRUCTURE 

Cause: You tried to transfer a parameter that cannot be converted to the target field to the selection screen. 
"Runtime Error: SUBMIT_PARAM_NOT_CONVERTIBLE

Thanks Venkat.O

[Former Member]

Try running the program in background. Any messages by the submitted report also, will be written to spool.

Regards,

Srinivas