Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

clnt dependent & independent

Former Member
0 Kudos
101

hi all,

what makes script client dependent and what makes smartform client independent?

1 ACCEPTED SOLUTION

Former Member
0 Kudos
68

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

There should be no logic in making scripts Client dependent..coz thier successors smartforms are client independent...Why scripts are client dependent....they must be stored in client dependent data tables ex STXH is a table which has MANDT as the first field.

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

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,

Santosh

Edited by: Santosh Kumar Patha on May 26, 2008 7:32 PM

6 REPLIES 6

Former Member
0 Kudos
69

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

There should be no logic in making scripts Client dependent..coz thier successors smartforms are client independent...Why scripts are client dependent....they must be stored in client dependent data tables ex STXH is a table which has MANDT as the first field.

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

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,

Santosh

Edited by: Santosh Kumar Patha on May 26, 2008 7:32 PM

0 Kudos
68

hi santhosh..its seems complicated to understand ur answer?

can u explain in simple way..

thank u

sunny

Former Member
0 Kudos
68

Hi,

One of the differences.

For the Forms, when we say client dependent,

example we have 2 clients.

700 and 710.

When it is client dependent like SAPSCIRPT, if you create a form in client 700, it will not be seen in 710. Therefore, you need to run a tcode to transport the form to different clients.

If it is client independent like SMARTFORMS, if you created a form in client 700, you can see it under client 710.

Hope this helps.

Benedict

Former Member
0 Kudos
68

for additional Info... it is tcode SCC1.

Former Member
0 Kudos
68

i hope the scripts are not dynamic but smartforms are dynamic..the smartforms can generate the dynamic function modules automatically by the system ...if u do any change on the smart form it will be updated automatically by the system once u activated the smart form ....this makes the smartform client dependent...but script is not the dynamic one..

regards,

venkat

Former Member
0 Kudos
68

Hi,

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.

Refer

https://forums.sdn.sap.com/click.jspa?searchID=12188282&messageID=4282569

Regards

Kiran Sure