script and smartform

[Former Member]

hi,

one of the diff bt script and smartform is script is client dependent and where as smartform is client independent.what it means exactly........

regards,

srinu

[Former Member]

Let me take one example :

I have one development server and it will have 2 diffrent clients

first client - 100

second client - 200

If you create sap script at 100 client ,then it will not available in 200 Client.

if you create sap smartform at 100 client ,then it will be available in 200 client.

so Script is client dependent

smartform is client independent.

Reward Points if it is helpful

Thanks

Seshu

[ferry_lianto]

Hi,

Smartform will be visible in all development client(s) whereas SAPscript only visible in development client where you created. You need to transport to other development clients in order to make it visible.

Regards,

Ferry Lianto

[Former Member]

Hi,

In SAP-Script we have to give screen number such as 100, 200 etc n these screens such as 100 screen is not visible to 200 n 200 screen is not visible to 300 so it is client dependent where as in Smart Forms its not like that u can view all the screens so it is client independent.

if useful reward with points,

with regards,

madhuri.

[Former Member]

Hi,

Client dependent means the things which are in client 100 will not be available in the client 200.

Client independent means the things which are in client 100 will be available even in client 200.

Note:- The client numbers given here is for your understanding.

The object on which a particular client can make changes are called Client Dependent objects.The object on which all clients can make changes are called Client Independent objects(or Cross Client Applications).

Ex:In Table MARA data is different for different clients.

In table T80I,T80IT data is same for all clients.

Regards,

Padmam.

[Former Member]

hi

good

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

THANKS

MRUTYUN^