scripts

[Former Member]

Why scripts are client dependent?

[Former Member]

Hi

Because they should output that particular client data only, not a global data(client independent data)

It was made like that by SAP for scripts and Std texts and Number ranges etc

<b>Reward points for useful Answers</b>

Regards

Anji

[Former Member]

Hi,

Scripts are called client dependent because if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.

Few more reasons why....? Please read below:

SAPscript technology is based on a mainframe product from the 1980s.SAPscript 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.

Regards,

Padmam.

[Former Member]

hi ram,

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

Regards...

Arun.

Reward points if useful.

[Former Member]

Hi,

in scripts we can use graphics but in smartforms we can create color ones also.....n even background is pssible...

in sap scripts multiple layouts is not pssible whereas its possible in smartforms....even we can have more than one main window in smartform but in scripts ...a form can ahve only one main window.....

background is not possible in scripts whereas it is possible in smartforms...

these r things tht makes scripts client dependent...

[Former Member]

Hi Ramanarayana,

When u creat sap script in one client ex 100

U can not see it it in other client,it will not be available in other clients ex 310 thats why it is client dependent.

But this is not the case with smart forms if u create in client 100 still it will be available uin other clients ex 310 so client independent,

Client 000 is mother of all clients all scripts will be available dere and u can copy it from client 000 to other client if want to use it.

>for dat goto se71

> utilities -> copy frrom client -> give souce client 000

and target wat u want

Thanks.

Message was edited by:

Viji

[sreeramkumar_madisetty]

Hi

<b>Scripts are called client dependent because scripts created in one client won't be automatically available in another clients.

Ex: if you create client in say,200 it would be available in that only.If you want to test the script in client 300 then it won't be there,you will have to go to transaction se71 in 300 .Then Utilities-> Copy from client.Give the source as 200 & form name(i.e. script name) & copy.</b>

Regards,

Sree

[Former Member]

Scripts are Client dependent.

Example Standards Scripts are saved in Client 000. If we want to use this we should copy these scipts to out present client.

So scripts are Client dependent.