cancel
Showing results for 
Search instead for 
Did you mean: 

script

Former Member
0 Kudos

can any ane help me to find out this question.

Q. why sap script is client dependant.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

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.

Regards,

Priyanka.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

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.

Regards,

Sankar