What makes scripts client dependent

Hi all can anyone clarify me on waht makes scripts client dependent smart forms client independent.
Is the graphic that we do in in SE78 client independent or client dependent.
please reply..
Thanks &  Regards,
Saroja.

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...
if u feel its a worthy answer then dont forget to reward with points...
with regards,
madhuri.

Similar Messages

  • Why  SAP Script  client-dependent  but  Smartform is client  independent

    Hi  All,
        What   are  the  fundamental  reasons   for  justifying  that  SAP Script  is  client-dependent  but  Smartform is client  independent  ???
    Regards
    jaman

    hi,
    why script is client dependent?
    the reason is:
    in script, to display some table data, we use text elements, where the text elements access the dictionary tables data. there the table from which we are fetching data, that may be a client dependent table, so first the text elements became client dependent. as script use text elements, script also became client dependent.
    hope u got the point. to b simple, the text elements r client dependent, there fore scripts also became client dependent.
    smartforms are client independent. bcoz it doesnt use any text elements. it will be executed through a function module, as you know function modules are client independent, the smartform also became client independent.
    hope ur clear, if any doubts, plz post them back.
    reward if helpful.

  • Urgent:Why Script is cliend dependant and smartform is not client dependant

    Hi all,
    Can any one pls tell me why script is client dependent and smartform is not client dependant.
    <b>Please give some real time examples in brief</b>
    regards
    tapu

    Hi
    DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:
    1. script is client dependent one while smartform is client independent.
    2. In scripts we have to write print program while in smart forms it is not necessary.
    3. In scripts we can print background logo while in smartforms we cant print background logo
    4. In scripts we have 99 main windows while in smartforms we have only 1 main window.
    5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .
    6. In scripts we can print the text in only two character formats.
    while in smartforms we can do with more.
    7. In scripts we dont have line types while in smartforms we have linetypes.
    8.Multiple page formats are possible in smartforms which is not the case in SAPScripts
    9.It is possible to have a smartform without a main window .
    10.Labels cannot be created in smartforms.
    11.Routines can be written in smartforms tool.
    12.Smartforms generates a function module when activated.
    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
    difference between smartforms and scripts
    Diff betwen Scripts & smartforms
    advantages of smartforms over scripts
    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.
    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).
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Client dependent & client independent objects

    Hi All,
    What is meant by client independent & client dependent ?
    I know that sapscripts are client dependent while smartfiorms are client independent. Also reports & FMs are client independent.
    Want to have a better idea on this concept....
    Thanks in advance..
    Sweta

    If you create a table in 010 client in DEV server with CLNT as its first fields type, then you will find that table structure in all clients in DEV server. (i.e client independent)
    example: function module, abap program, smart form.
    If you create a record in that table in 010 client, you will not find that record in other clients. (i.e client dependent)
    Example: script.
    Sap script was developed a long back.
    smartform is developed to avoid these type of some restrictions
    Also:
    Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
    Like SAP SCRIPTS and STD texts data
    where as Client Independent means the data if you create in one client that is available in that as well as in other clients
    Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
    There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
    As for SAP -- 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.
    MANDT is the field which differenciates the table from Client Dependent and Client Independent Tables.
    All the Scripts are Client Dependent Objects
    Smart Forms, Function Modules are Client Independent Objects.

  • Client dependent n client independent?????????/

    hi this is vinod,
    please explain the concept behind of script client dependent and smartforms r client independent pleaseee its urgent????????????

    Hi,
    Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
    Like SAP SCRIPTS and STD texts data
    where as Client Independent means the data if you create in one client that is available in that as well as in other clients
    Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
    There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
    As for SAP -- 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.
    rewards if useful,
    regards,
    nazeer

  • Difference between client dependent table and client independent table

    hi all,
                  i m new in sap pls tell me the difference between client dependent table and client independent table.
    tell me in detail.
    thanks and regards
      vikas saini

    HI
    Client dependent Means if you create that data in one client is limited to that client only and it is not accessable in other clients
    Like SAP SCRIPTS and STD texts data
    where as Client Independent means the data if you create in one client that is available in that as well as in other clients
    Like SMARTFORMS, All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc..
    There is no specific reason behind why scripts are client dep[endent and smartforms are client independent!!!
    As for SAP -- 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.
    What is client dependent and Client Independent
    https://www.sdn.sap.com/irj/sdn/forums

  • Why sapscripts are client dependent & smart forms are client independent?

    why sapscripts are client dependent & smart forms are client independent?

    You developed the script in development client , you can't find the same in testing client even though the server is same.
    Where are You developed the smartform in development client , you can find the same in testing client even though the server is same.
    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).
    Check the beloe links for more information
    script and smart forms
    http://www.sap-img.com/smartforms/smartform-sapscripts.htm

  • Why the sapscript called as client dependent? y smartform not?

    why the sapscript called as client dependent? y smartform not?

    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).
    Thanks,
    Santosh

  • . What is the client concept in SAP? What is the meaning of client independ

    hi,
    send me replay

    Hi ,
    since u r maintaining different clients in da same server ,
    so ,
    tables needs to have diff data for diff client.....
    now if u dont make tables client dependent then , same table data will be used by all clients ...
    But all clients have their own diff data ,
    So making a table client depedent , u r using same database table, to store data of different clients.
    for more information:
    A client is a logical division of data within an SAP system. Some things, like application data are mostly client-dependent, meaning that for example, a G/L account defined in client 123 of system ABC is only visible in that client. Therefore if you logon to client 456 of system ABC you will not be seeing the same database entity (if it is defined at all).
    At a technical level, client dependent data simply resides in database tables that have the client number as a key field (typically the first key field).
    Multiple clients within an SAP system are often used in development, testing and training systems - so that individuals can work in the same system (on the same codeset) but in isolation of each other.
    Very rarely will a production system have multiples clients (ignoring the internal SAP clients like 000 and 066).

  • What exactly is the diff between client dependant and client independant te

    Hi gurus,
    What is the diff between client independant and client dependant term.. I initially had a confusion related to client independant and client dependant Transport requests, where else are these words applicable, do they apply to data as well, if so how? any links to help me understand the difference..
    regards,
    kishore

    Hi Kishore,
    Client Independant: These objects are not specific to any client. And it is universal which can be viewed,changed across the clients.
    Client Dependant: These are the objects can be viewed, changed for the client for which it has been assigned. Other clients do not have access on these objects.
    In SAP, all objects are finally stored as tables. "Mandt" is key field which determines whether the object is client dependant or not.
    Client Independant transport requests will make the transported objects available across the clients. and Client dependent transport request make the objects available only for the client mentioned by field "Mandt"
    Regards,
    Dinesh D

  • Why SAP Script is said to  be client dependent

    <b>Hi friends,
    Can you tell me Why SAP Script is said to  be client dependent .
    please let me know it
    Thank you</b>

    Hi,
    Please go through this link,
    http://searchsap.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid21_gci1190925,00.html
    Hope this will give you a clear idea.
    Feel free to revert back.
    --Ragu

  • Why  SAP script is client dependent ?

    why  SAP script is client dependent ?

    Hi,
    By design, SAP script is a word processing tool which displays data on the form with the help of text elements where the logic of those is written in the print program and Forms were designed to be driven from print program, hence are often termed as client dependent. Smart forms are client independent. Bcoz it doesnu2019t use any text elements. It will be executed through a function module. When a print program calls a Smart Form, the form itself takes over to produce output, without any further direction from print program.
    Pelase reward if useful.
    Bye

  • What will be the diff.between Custiomizing(C),Client dependent(E) in BSI System

    HI Experts,Can you just clarify in this two components or table names used how it wil be helpful to us. When we have to use these two in updation of taxation updates(TUB)-Tax Updations Bulletin.
    So, please give me clarity about these two.
    Thanks&Regards
    Rajeshwari

    Hi
    Customizing entries are those which are created by customer himself not delivered via TUBS.If the tables where you have created custom entries are having any new table delivered care must be taken not to import the whole cumulative transport which will then overwrite your custom entries. Custom entries ware not in client 000 they only reside in your development system
    Easiet way to decide if a table is client dependent or client independent is to check if it has client as one of the kep field.If it has then it is  a client dependent else it is client independent
    Hope this makes sense
    Regards
    Ajay

  • What is client dependency

    urgent

    Hi,
    As name itself suggests, the object which you create as client dependent will be pertaining to that client only.
    For ex:  Your create a table with MANDT as first field, which is client dependent(say client is 900 in development system)  here whatever entries you make in this client will be available only for this client.
    In the same development system, for different client( say 950) you will not be finding any table entries for the same table made through client 900.
    Hope you got my point

  • Why SAP Script are Client Dependent, Smartforms are client-independent.

    why  SAP Script are Client Dependent,Smartforms are client-independent.
    Edited by: Srinivasa Reddy Ariga on Oct 27, 2008 12:28 PM
    Edited by: Srinivasa Reddy Ariga on Oct 27, 2008 12:49 PM

    Before you do anything else, read this: Welcome and Rules of Engagement
    Google is your friend.  Try keywords smartforms client dependent   Next time - search first and ask second.
    oh, and it helps to get the correct forum...

Maybe you are looking for