topic Re: Need to return to the Wrapper program when the called Program dumps in Application Development and Automation Discussions

Need to return to the Wrapper program when the called Program dumps

Former Member — Sun, 06 Feb 2011 04:08:12 GMT

Dear Experts,

We are calling a standard sap report from our Z wrapper program using submit and return statement.

The standard sap report program is dumping because of some issues and the execeptions are not caught by SAP.

Our requirement is we need to return to the wrapper program even if the dump occurs so that we can contunue with the further processing.

Any help on this will be highly appreciated and <promise removed by moderator>

Thanks in advance,

Regards

Edited by: Balwants on Feb 6, 2011 5:10 AM

Edited by: Thomas Zloch on Feb 6, 2011 1:57 PM

Re: Need to return to the Wrapper program when the called Program dumps

Former Member — Sun, 06 Feb 2011 05:22:56 GMT

Hi,

What is the dump details.

Can you please provide the exact submit statement syntax that you are using in your wrapper program.

With these details maybe we can troubleshoot.

Also let me know if the SAP report you are submitting.

Re: Need to return to the Wrapper program when the called Program dumps

Former Member — Sun, 06 Feb 2011 17:29:47 GMT

Hi,

The std program name is RGLE_ECS_DIRECT_INPUT_PP

submit statement is something like this (I am not mentioning the exact code & have replaced the std program by Y program):

SUBMIT YOVERFLOW_TEST_SUCCESS USING SELECTION-SCREEN 1000

WITH p_date = sy-datum

WITH p_sim = 'X'

AND RETURN.

This problem is basically a very general problem and should not be related to a particular dump.

I am looking for a very general solution on this .

Regards

Re: Need to return to the Wrapper program when the called Program dumps

Former Member — Mon, 07 Feb 2011 19:19:45 GMT

Hi Experts,

Please let me know if you were able to get the solution on this.

Thanks in advance,

Balwant

Re: Need to return to the Wrapper program when the called Program dumps

Clemenss — Mon, 07 Feb 2011 20:25:06 GMT

Hi,

did you try

TRY.
submit ...
CATCH CX_ROOT.
WRITE: / 'Severe error in submitted program'.
ENDTRY.

I did not try but I have some hope - though no dump will be created.

If you need to know why and where the error occured, you may have chances with exception object.

Regards,

Clemens

Re: Need to return to the Wrapper program when the called Program dumps

Former Member — Mon, 07 Feb 2011 20:36:40 GMT

I have already tried this it dosent work.

Is there anyother hope to catch an exception like this.

Thanks

Balwant

Re: Need to return to the Wrapper program when the called Program dumps

vikrant_guptarya — Mon, 07 Feb 2011 23:21:35 GMT

Not possible...

Dump is a special situation where the exception is not taken care by the program.

Could you please let me know as to what exactly is your requirement...

Re: Need to return to the Wrapper program when the called Program dumps

Former Member — Tue, 08 Feb 2011 02:33:36 GMT

Hi ,

I faced some dumps when I was using submit some time ago.It was because I was using the slection screen statement

for a report using screens built out of screen painter. This may be a possibility in your case.

Tell me if this is your case.

Thanks

Re: Need to return to the Wrapper program when the called Program dumps

Clemenss — Tue, 08 Feb 2011 16:55:35 GMT

Hi vikranth,

yes, it is true.

TRY .. CATCH is used to catch an exception that would otherwise raise a dump.

But as the submitted program runs in it's own LUW, the exception is not caught.

That means: No way to catch the dump, only make checks before submitting. This is about the same as errors in update task - then you get an express mail.

You couls create and start a Job for any single submit, then you evrything is processed and the errors with dump are in the job log.

Regards,

Clemens

Re: Need to return to the Wrapper program when the called Program dumps

Former Member — Wed, 09 Feb 2011 15:50:14 GMT

Hi All,

There is no problem without a solution;).

We solved it by submitting the report in a wrapper RFC.

RFC will open a new session that is why it will work.

As Clemens mentioned Job spawning ,that was one of the solution too we had figured out intiailly but the std report we were submitting was creating lot of parallel processes so we did not went ahead with this one.

Regards,

Balwant