Transaction code MB02 - Issue with Printing and Process overload SM50

[Former Member]

Hello Experts,

We are actually having a problem when trying to print a smartform in tcode MB02. Also, when verifying transaction SM50 for that process then we noticed that there was a timeout after a big data load.

Here is the scenario:

1. Entering a material doc 9999 and Press enter

2.Select and double click a line item for that material doc

3. Click on Messages

3. Select an output type and click on Repeat output

4. Click Save

5. Click Save again.

In a normal case, a screen would appear for printing but this time nothing seems to happen. And then when we go to tcode SM50 and check that process there is 2-3 dumps.

As a newbie programmer I do not understand any of these procedures properly. If anyone can shed any light on this, i would be grateful.

Regards,

Thyaga

[Former Member]

Hello Experts,

We are actually having a problem when trying to print a smartform in tcode MB02. Also, when verifying transaction SM50 for that process then we noticed that there was a timeout after a big data load.

Here is the scenario:

1. Entering a material doc 9999 and Press enter

2.Select and double click a line item for that material doc

3. Click on Messages

3. Select an output type and click on Repeat output

4. Click Save

5. Click Save again.

In a normal case, a screen would appear for printing but this time nothing seems to happen. And then when we go to tcode SM50 and check that process there is 2-3 dumps.

As a newbie programmer I do not understand any of these procedures properly. If anyone can shed any light on this, i would be grateful.

Regards,

Thyaga

[mithun_shetty4]

After Step

3. Select an output type and click on Repeat output

Select the Output which is in yellow and press further Data

Change the processing mode from 4( Send Immediatey) to3 ( Trigger using a Transaction)

Got Program RSNAST0D.

Put Application Object key and Output Type Execute.

Next Start Debugging the Output type to check the point where the processing is taking a lot of time.

[Former Member]

Hi,

Can you post what are the dumps you are getting, so that i can help you

Regards

Ravi

[Former Member]

Hi everybody,

Thanks for your answers. Actually after a lot of time spent on debugger i found that the variable returncode is 999 and then a subroutine is called which in turn calls my program to trigger the smartform.

The problem is throughout my program i do not change the value of the returncode .i.e it remains 999. What i did then is change the returncode 999 before my smartform-program is called then after testing i see that the output is printed without any error.

The program and subroutine i am talking are as follows:

1. Program: RSNAST00

2. Subroutine: programm_aufrufen

3. Line 1297 returncode is 999

4. Line 1318 - my smartform program is called

5. Then at 1324 - on control is done on returncode.

Please advice if these steps are conform/ethical. Also, can you suggest any other steps i can do without the need to modify my own program.

Thank you very much for your replies.

Kind regards,

Thyaga.

[sjeevan]

I don't know why you're using a smartform to print GR/GI slip, but for most movement types you can directly print by configuring values in OMBR and OMB5.

[Former Member]

The problem was with the return code. We had to change the return code in our program if the smartform was processed successfully. Once the SY-SUBRC of the Function Module calling our smartform was successful, we changed the return code from 999.

Thank you for your inputs.

Regards,

Thyaga