Problem in SAP SCRIPT OUTPUT

[Former Member]

Hi All,

I have a problem in <b>SAP SCRIPTS</b>.

While we are using <b>IW22</b> to view print preview

we are getting error to our inbox as follows :

<i>Update was terminated

System ID.... D5S

Client....... 900

User..... F80006

Transaction.. IW22

Update key... 4309D2BCC9C605E7E10000000A1EB818

Generated.... 22.08.2005, 10:14:14

Completed.... 22.08.2005, 10:14:14

Error info... 00 671:

ABAP/4 processor: GETWA_NOT_ASSIGNED </i>

And so we were not able to print the output.

Can anybody tell me how to solve this issue, Can any body provide us with the solution.

Thanks in advance.

Thanks & Regards,

Rayeezuddin.

[Former Member]

Hi Shaik,

I think there is a problem in the program that will print your form. To be sure: check transaction SM13 to view the update error and to find out in which program the error occurs.

Regards,

John.

[Former Member]

Hi,

We are not authorised to SM13 (or) SM13T.

So we can't really know in which program error is coming.

But when we put a break point in our <b>Print Program</b> it is not going into <b>P.Program</b>.So problem might not be in <b>Print Program</b>.

So please give us a solution where by we can rectify that problem.

Thanks & Regards,

Rayeezuddin.

[Former Member]

Hi Shaik,

You say that your problem might not be in the print program. Since the print program is called in update task, it is quiet tricky to get to the breakpoint. Did you switch on Update debugging?

Regards.

John.

[Former Member]

Hi John,

In case of viewing of Print Preview we are able to get into Print Program in Debug mode. But when we are sending print to <b>Printer/Fax</b> we are not able to get into print program while debugging.

If any other way we can solve this problem, Please provide the solution.

Thanks & Regards,

Rayeezuddin.

[Former Member]

Hi Shaik,

As John said, it's because when you are sending it to <b>Printer/Fax</b> it is being executed in update task. So in order to debug the program you need to enable update debugging. While executing the transaction you can put the program in debug mode by using command '/h', once in debug mode you can choose settings and set 'update debugging'. The result of this would be after you have completed the transaction a new window will open and stop in debug mode for the update task.

Cheers,

Sanjeev