in scripts and smartforms

[Former Member]

hi

why scripts are called client dependent and smartforms are called client independent

[Former Member]

Scripts are always client dependant and Smart forms are

client independant.

You will be able to see your smartforms in all the clients in the same application server.

For examples in DEV system there might be three clients

100, 300, 500. So you will be able to see ur smartforms in

all the three clients.

But in order to see SapScripts you will have to transport the form from each client to another.

To see the smartform in you QA server which is a different appplication serer you will have to transport objects.

Regards,

[Former Member]

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.

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

REward points if useful.

[Former Member]

Hi Jyothsna,

Requeset you to follow the link

http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1190925,00.html

http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci1194729,00.html

[Former Member]

scripts are client dependent since they won't generate function modules. in case of smartforms it will generate function module it can be run any where.

[Former Member]

Hi

scripts are client dependent...i.e if u create a script in client one client u cannot call or use the script in other client.

smartforms are client independent ....

if u create a smartform in 800 client u can use it in 000 client also.....bcoz smartforms generate a function module when executed and function modules are client independent....smartforms are client independent

[Former Member]

Hi,

Scripts are client dependent objects as they have to be explicitly exported to the required client using the report RSTXCPFS, only then the changes made will be visible in the destination client. Every small change you make in script has to be transferred by executing the above mentioned program.

This is not the case with SmartForms. They need not be exported to different clients explicitly.

I hope this gives you a clear idea.

Regards,

Farheen

[Former Member]

Hi Jyothsna Vankadari ,

Smartforms are client independant beacuse when we execute a smartform, FM gets generated.The function module is client independant.Hence, the smartforms are client independant.

SAP scripts do not generate any FM while execution and hence client dependant.

Regards,

Thasneem