topic Re: Changing an output type for SmartForms in Application Development and Automation Discussions

Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 18:52:26 GMT

Hi all,

I have a picklist that I changed from SAPScript to SmartForm. I am trying to edit the output type EK00 to use the SmartForm. I am using V/38 to edit EK00 but I can't figure out the right properties. Right now I have the FM name (/1BCDWB/SF00000017) as the Layout Module, the SmartForm name (ZPCC_PICKLST_STD) as the SmartForm. Also, under Pricessing 1, I have the print program (ZRVADEK01), FORM routine as (SMARTFORM_PRINT) and Form as (ZPCC_PICKLST_STD). Is there anything else that I need to change? When I try to use EK00 it is still looking for a SAPScript instead of a SmartForm.

Regards,

Davis

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 19:32:31 GMT

Remove the entry in Layout Module and remove the entry under Form.

All you should need is the Smart Form and then under Processing 1 you need the Program and Form Routine.

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 19:37:02 GMT

Matt, thanks for the reply. I just tried what you posted and it still gives me an error. I get a popup that says "WRITE_FORM is invalid, OPEN_FORM is missing.

Could my problem be that the old SAPScript and the new SmartForm have the same name? Below is the configuration:

Layout Module: nothing there

SmartForm: ZPCC_PICKLST_STD (name of the smartform)

Processing 1:

Program: ZRVADEK01

FORM routine: SMARTFORM_PRINT

Regards,

Davis

EDIT: I do not have any SAPScript functions (open_form, close_form, etc...) in the print program. I took the preconfigured print program for SDPIK_L (preconfigured picklist) and added our custom logic.

Message was edited by:

Davis

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 19:44:43 GMT

When you go to V/38 and double click on EK00 are there any Programs or Form Routines filled in under the General Data tab?

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 19:46:31 GMT

Matt, no there are not.

Regards,

Davis

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 19:48:13 GMT

Hmmm... and your Program ZRVADEK01 has a Form called 'SMARTFORM_PRINT'?

And there is no mention of WRITE_FORM in ZRVADEK01?

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 19:59:44 GMT

Matt, you are correct with both questions. I have SMARTFORM_PRINT in ZRVADEK01 and no mention of WRITE_FORM.

Regards,

Davis

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 20:05:15 GMT

Matt, you pinpointed the problem. When I was copying the code from our old print program to the new one I overwrite most of the SMARTFORM_PRINT code and included WRITE_FORM.

I am going to edit the code and hope that it works.

Thanks for all of your help!

Regards,

Davis

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 20:07:59 GMT

Hi Davis,

Please try this in transaction V/38.

Layout Module: nothing there

SmartForm: ZPCC_PICKLST_STD (name of the smartform)

Processing 1:

Program: ZRVADEK01

FORM routine: ENTRY

Regards,

Ferry Lianto

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 20:09:53 GMT

Ferry, do I use FORM routine: Entry or SMARTFORM_PRINT?

Regards,

Davis

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 20:13:56 GMT

Hi Davis,

You need to use FORM routine: Entry.

This form routine will call form routine SMARTFORM_PRINT at the end after getting all the required data for smartform and perform user exits (if any).

Regards,

Ferry Lianto

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 20:16:45 GMT

Ferry,

His print program is ZRVADEK01 not SMARTFORM_PRINT.

Davis,

It seems like the norm is to use ENTRY for the Form Routine name, but I'm pretty sure you can call it whatever you want to.

Re: Changing an output type for SmartForms

Former Member — Tue, 22 May 2007 20:19:14 GMT

Thanks to all for your help. All of this could have been avoided had I paid attention to my code a little more.

Thanks again for all the help,

Davis