topic Re: Script problem in Application Development and Automation Discussions

Script problem

Former Member — Mon, 10 Jul 2006 11:59:31 GMT

I have designed zscript form and it was assigned to TWO Standard print programs by my functional consultant.

One is for domestic purpose and one for foreign payments.

I used text elements of my standard print program in my Script editor(se71) and it is working fine for the first std print program .

But while executing , another standard print program, it is giving error as

"WRITE_FORM is invalid, START_FORM is missing".

I did not modify any of these std driver programs. Simply designed Script and copied/used text elements in Se71 script editor.

Experts please suggest me, how to rectify this error. from 5days I am trying. please suggest me.

Ur help is highly appreciated.

Re: Script problem

Former Member — Mon, 10 Jul 2006 12:05:27 GMT

Hello,

This is may due to the COntrol_FORM in ur second print program.

Check for any control form in ur report.

In some point u may be calling the second page explicity when some conditiion is satisfied.

Check for this.

If useful Reward points.

Regards,

Vasanth

Re: Script problem

Former Member — Mon, 10 Jul 2006 12:11:28 GMT

hi,

It's basically a print program error.

You must be calling start-form conditonally in an if statement or something. Just debug the print program and you'll realise at some point that your write-form is getting called even before start-form.

Re: Script problem

Former Member — Mon, 10 Jul 2006 13:32:06 GMT

Hi Sam,

could u let us know wat u r trying to print and wat r the std programs u r using for the same..

Re: Script problem

srinivas_akiri — Mon, 10 Jul 2006 14:10:03 GMT

Hi Sam,

Before calling function module WRITE_FORM, we must have to call one START_FORM or OPEN_FORM function module in the driver program.

In your case in the first driver program would call this START_FORM, but the second program may not call this functional module because of some conditional check.

You can check it in debugging by putting the break points at CALL FUNTION statement.

you need to to change the 2nd driver program by make a copy of it.