Regarding SAP Scripts and Smartforms

[Former Member]

What is the functionality that can be provided by SAP Script and not by the smartform?

[Former Member]

hi Naveen,

SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...

1. script is client dependent one while smartform is client independent.

2. In scripts we have to write print program while in smart forms it is not necessary.

3. In scripts we can print background logo while in smartforms we cant print background logo

4. In scripts we have 99 main windows while in smartforms we have only 1 main window.

5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .

6. In scripts we can print the text in only two character formats.

while in smartforms we can do with more.

7. In scripts we dont have line types while in smartforms we have linetypes.

also refer

the main diffarences between smart form and script form are:

1) smart forms are clinent independent where as scripts are client dependent.

2) smart form require half the time to create and maintain forms compare with

script.

3) smart forms provide multiple page formats where as in script not possible

4) smart forms exisist without main window also where as in script not possible.

5) smart form is entairely graphical user interface comapre with script.

6) labeling is not possible in smart form where as it is possible in script.

7) smart form genarate function module whenver it activate where as script

doesn't genarate.

😎 smart form can easily web publishing using the genarated XML output compare

with script.

9) using smart forms we can design web forms but bot possible with script.

10) we can maintain background graphics in smartform wher as in script not

possible.

11) in smart form we use transaction codes SMARTFORM for designing FORM

and SMARTSTYLES to create differnt styles of text, where as in script we

use SE71 for form painter and SE72 for different styles of text and font.

12) we can migrate script to smart form vice-versa is not possible.

Also,

Multiple page formats are possible in SmartForms which is not the case in SAPScripts

It is possible to have a SmartForm without a main window.

Labels cannot be created in SmartForms.

Routines can be written in SmartForms tool.

SmartForms generates a function module when activated.

SAP Smart Forms is used to create and maintain forms for mass printing in SAP Systems.

As output medium SAP Smart Forms support a printer, a fax, e-mail, or the Internet (by using the generated XML output).

SAP introduced SmartForms in 1998 to overcome the limitations in SAP Scripts.

SmartForms are easier to develop, maintain and transport than SAP Script.

SAP Smart Forms offer the following advantages:

Adapting forms without any programming knowledge due to entirely graphical user interface

Web Publishing using the generated XML output

When activating the smart form the system automatically generates the function module and at the runtime processes it.

To make any changes we have to use the Drag & Drop, Cut & Paste. These actions do not include writing of coding lines or using a script language.

We can insert static and dynamic tables. These include the line feeds in the individual table cells, triggering events for table headings and subtotals and sorting data before output.

The smart forms allow the user to include graphics, which can be displayed as a part of the form or as background graphics. During printout the user can suppress the background graphic as and when necessary.

hope this helps,

cheers,

Hema.

[Nawanandana]

hi

The Following are the differences :-

a) Multiple page formats are possible in smartforms which is not the case in SAPScripts

b) It is possible to have a smartform without a main window .

c) Labels cannot be created in smartforms.

d) Routines can be written in smartforms tool.

e) Smartforms generates a function module when activated.

Contributed by : SAP ABAP/4 Programming, Basis Administration, Configuration Hints and Tips

-

---

f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.

It was said that it was provided in CRM 3.0 version, but not available in R/3. You can download smartforms into Local PC in a XML format. In the same way you can upload this XML format into Smartform. From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment.

In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.

In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.

For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.

g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.

i) The main difference is that SAP script is client-dependant, while smartform is independent. Also there are some advanced and intreractive features available in smartforms.

You can use an External subroutine-call in sapscript editor like:

/: perform <form_name> in program <program_name>

/: using <var1>

/: using <var2>

.

.

/: changing <return1>

/: changing <return2>

/:endperform

regard

nawa

[Former Member]

hI

Hope it will help you.

Pls reward if help,.

DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:

1. script is client dependent one while smartform is client independent.

2. In scripts we have to write print program while in smart forms it is not necessary.

3. In scripts we can print background logo while in smartforms we cant print background logo

4. In scripts we have 99 main windows while in smartforms we have only 1 main window.

5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .

6. In scripts we can print the text in only two character formats.

while in smartforms we can do with more.

7. In scripts we dont have line types while in smartforms we have linetypes.

8.Multiple page formats are possible in smartforms which is not the case in SAPScripts

9.It is possible to have a smartform without a main window .

10.Labels cannot be created in smartforms.

11.Routines can be written in smartforms tool.

12.Smartforms generates a function module when activated.

SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...

also refer

Whenever a smartform is created, a funciton module gets generated. So, we can access the smartform in different clients. But in case of scripts, it is not so.. So, scripts are client dependent.

Smart Forms are implemented using the Function Module SSF*, and all the logic lies in the FM. Function Modules are client independent objects, so Smart forms are also client independent

SAP Scripts are the Layout Forms that you design and there are aviable in the client in which you have created them, for making them available you have to copy across the clients.

Because, Sapscripts are saved in ITF format as text in client dependant tables STXH and STXL. smartforms are not saved in client dependant tables and visible across clients.

SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. As you have noted correctly, client dependence is a fundamental one.

Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports; if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean. Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.

Conversely, a Smart Form is significantly more robust and complex. For instance, it can contain program nodes and nested tables with patterns. When a Smart Form is compiled, it generates an ABAP function module – and these are always client-independent. This is appropriate, given that this form has more in common with an ABAP program than its predecessor. For instance, when a print program calls a Smart Form, the form itself takes over to produce output, without any further direction from the print program. In fact, the join is so seamless that I often find myself using a Smart Form's Initialization section for logic to handle any data gathering not handled by the print program. I would never even think to attempt this with SAPscript.

I suspect several factors figured into SAP's decision to make Smart Forms client-independent, including customer feedback. There are significant advantages to client-independence. For instance, a change made in one development client happens immediately across all development clients. Among other things, this means we don't have to waste time figuring which client contains the most recent version -- they all do! In addition, transporting Smart Forms is easier, since we can safely bundle them together in the same transport as their client-independent print programs (no worry about mixing client-dependent and independent objects).

[Former Member]

We can create labels using Smartforms.

script is client dependent and sf is client independent.

We create Script Styles using SE72 Tcode.