script

[Former Member]

Why script is a client-dependent and smart form is client-independent?

[Former Member]

Hai Balu,

When you activate the Smart Form, the system generates a function module that encapsulates all attributes of the Smart Form. As soon as the application program calls the function module, the Smart Form uses the modules interface (which corresponds to the form interface) to transfer any table data previously selected and to print the form according to the form description.

As we are making use of the generated function module, Smartforms are client independent.

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 ...

<b>Refer these links :</b>

http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci1190925,00.html?NextURL=http%3A//...

regds,

Rama.Pammi

[Former Member]

Hi Balu,

For information on the difference between SAPscript & smarform, kindly check the following links:

http://www.sap-img.com/smartforms/smartform-sapscripts.htm

Hope this resolves your query.

Reward all the helpful answers.

Regards

[Former Member]

hi

balu

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.

regards

praveen

[Former Member]

Hai Balu,

When you activate the Smart Form, the system generates a function module that encapsulates all attributes of the Smart Form. As soon as the application program calls the function module, the Smart Form uses the modules interface (which corresponds to the form interface) to transfer any table data previously selected and to print the form according to the form description.

As we are making use of the generated function module, Smartforms are client independent.

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 ...

Refer these links :

http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci1190925,00.html?NextURL=http%3A//...

<b>Reward points if it helps you.</b>

Regds,

Rama chary.Pammi

[Former Member]

Hi Balu,

Script is client Dependent ( For Example if u want to test the script u need to move the script to the testing client , for that u need to use programs rstxr3tr ,rstxscrp or SCC1(Tcode) ,

SmartForms as client independent as soon as u activate a smartform it generates a function module , generally Function Modules are Client Independen so u can say that answer , again smartforms are version dependent , during the time of upgradation , u have todevelop the smartforms from Scratch....

in smartForms Drag and drop Operations are ,so ucan say smartforms are user friendly ...., u can create a back ground picture for a page , here u can maintain one page in portrait and other page in Landscape which is not possible in scripts..

Thanks & Regards

Bhaskar Rao.M

[Former Member]

Hi BAlu,

Sap script is client dependent but the cooresponding program is client indepedent.

Thecorresponding programs are stored in a table.

All the predefined and user defined programs are stored in 'TRDIR'.

Table is client independent.

But the smartforms are client indepedent because when ur execute the smartform it generate the 'Function Module'.

Function module is a client indepedent.if u create the function module once we can access this function module in any client.

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.

Dont forget rewords points.

Regards,

P.Nag