Differnce between client dependentand client independent config

Hi guys,
Could some one please clarify me the difference between client dependent and client independent configuration and give me full details
regards
Murali

Hi
There are two types of objects in SAP, client dependent and client independent.
configuration effect client tables called depedent.configuration not effect tables called independent
u can distinguish as follows
Objects used in several clients are called client independent while objects used in a specific client is called client dependent. To identify if a table is client dependent, one can use tcodes SE11 or SE12. In the table field attributes, if the MANDT field is present that table is client dependent.
A client-dependent table has the field MANDT of data type CLNT, which indicates Client id.
A client-independent table does not have this field.
Data which can be access by all user are client independent (no mandt field in table). Data which can be access by some specific user are client dependent (use mandt field in table)
Hope ths Helps
Please reward points
Sunil

Similar Messages

  • 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

  • Basic differnce between 000 and 001 clients.

    what is the basic differnce between 000 and 001 clients?
    why do we use client 000 as source client while client copy?

    Hi Kumar
    The basic difference between Client 000 and Client 001 is that Client 000 is client independent instace while Client 001 is Client dependent.
    Client 000 is SAP source client while Client 001 doesn't exits for every installation.
    Regards
    Shashank

  • 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

  • Distinguish client dependent & client independent

    Hi
          what is the difference between client dependent and client independent;
    can any one explain on it.
    thanks in advance
    sameer

    Hi,
    Whatever the configuration we do in IMG- will be store in certain tabels .
    if u observe tables in
    Tcode:SE11- enter table name
    if first field is CLNT- MANDT means
    its client dependant .
    this config is specific to the client.
    the rest will be client independent like number ranges.
    eg: Factory Calender-
    once maintained will be available in all clients in the same server.
    Table:TFACD
    ( check in SE11)
    whichsnt client specific (no CLNT - MANDT field)
    Edited by: RMD on Apr 11, 2008 6:42 PM

  • Questions on scripts, tables & transfer objects between clients.

    1. In script, how to use the same print program for two different layouts? with procedure.!
    2. Why cant sapscripts be client independent.?
    3. Want to maintain a table in dev server and if i update the data, it should simultanously update in Quality and Production servers. How? please explain in details.
    4. How to transfer object between clients.? explain.
    Points will be promptly rewarded for HELPFULL answers.!

    Hi!
    3. With SE01, you can create a transport request for all table entries.
    SE01 - Create button - Workbench request - Give description and save
    Select the created request and click on Display object list.
    Click on Display - Change button
    Insert line button
    ProgID: R3TR
    Object: TABU
    Object name: Z_YOUR_TABLE
    Double click on the table name
    Insert line
    Key: *
    Save everything
    Release the transport in SE10 transaction and transport with STMS transaction.
    Regards
    Tamá

  • Client dependent and client independent in ALE

    I am going through pdf learning of an ALE scenario,i couldnot get wat is meant by client Independent and client dependent.
    How can i conclude
    Create message type (WE81){color:green} Client independent {color}
    To create a new message type, follow these next few steps:
    u2022 Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
    u2022 Choose Create logical message type by double clicking on it
    u2022 Click on change icon to enter change mode
    u2022 Click on New entries to add a new type
    u2022 Enter the required message type, in our case it is ZINVRV and an appropriate description
    u2022 Save and exit.
    Your message type has now been created. The next step will be to link it to the IDoc.
    2.2.1. Link message to IDoc type (WE82 & BD69) {color:green} Client independent {color}
    To link the message type to the IDoc type follow these next few steps:
    u2022 Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
    u2022 Click on change icon to enter change mode
    u2022 Click on New entries to create the link
    u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
    u2022 Save and exit
    u2022 Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
    u2022 Click on change icon to enter change mode
    u2022 Click on New entries to create the link
    u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
    u2022 Save and exit
    Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
    2.2.2. Maintain object type for message type (BD59) Client independent
    The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
    For our own message type and IDoc you must maintain object types for the links.
    If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
    To add an object type to our message type, follow these next few steps:
    u2022 Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
    DOC NAME: ALE_SCENARIO_DEVELOPMENT_PROCEDURE
    Version 1 Page 6 of 16
    ALE Scenario Development Guide
    u2022 Type in your message type ZINVRV and press enter
    u2022 Click on New entries
    u2022 Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
    u2022 Save and exit.
    You have now created an object that weu2019ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
    We now need to add our new message type to the distribution model.
    2.3. Configuring the Distribution Model
    This task is performed on your ALE reference client.
    2.3.1. Manual Configuration (BD64) {color:green}  Client dependent {color}
    To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
    u2022 Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
    u2022 Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
    u2022 Choose the receiving systems to which the sending system must forward message type ZINVRV to.
    u2022 For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
    u2022 Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
    u2022 Save the entries.
    Refer my query within color:green
    Edited by: aditya  sharma on Jul 14, 2010 12:57 PM
    Edited by: aditya  sharma on Jul 14, 2010 1:01 PM

    A client is an independent business unit within an R/3 System, Data in the R/3 are classified as cleint-Dependent and client-independent.
    Client-independent data such as ABAP Programs, R/3 repository objects throught the entire system. Other data is client-dependent. meaning, it can be viewed from one client. Cleint-dependent data includes customizing application and user data.
    Eg.
    Scripts are client dependent, means the changes done to SAP scripts in particular client will not be reflected in other client.
    Smartforms are client independent, means changes done in one client will be reflected in all the clients.
    Server : ECC6
    Client : 100 , 200 , 300 , 400
    Now suppose you have developed report in DV server client 100.
    Then you will be able to see that in all clients.
    Hence this is called as client independent. You can change anywhere and changes will be reflected to all ...
    Now suppose you have developed a script in DV client 100.
    You will not be able to see that in client 200 or 300 or 400 unless ytou copy that from client since it is client dependent.

  • Which are client independent and dependent objects in SAP ABAP

    which are client independent and dependent objects in SAP ABAP

    Hello Jagrut
    A special kind of objects are client-<u>dependent </u>repository objects. These objects have to be treated specially in the way that they have to be imported into their specific target client. In contrast, client-independent repository objects can be imported into any client.
    The following list shows the client-dependent repository objects:
    LIMU     FSEL     Field Selection
    LIMU     VARI     Report Program System Variant
    R3TR     COC1     CO: Cost Centers
    R3TR     COC2     CO: Activity Types
    R3TR     FORM     SAPscript form
    R3TR     LODS     HRDSYS: Logical information object client-dep. table E SYST
    R3TR     PCYS     HR: Transport standard personnel calculation rules
    R3TR     PHDS     HRDSYS: physical information object client-dep. table E SYST
    R3TR     SBNL     Logical Information Object for BDS
    R3TR     SBNP     Logical Information Object for BDS
    R3TR     SBNR     BDS: Relationship Between Information Objects
    R3TR     SBPL     Logical Information Object for BDS: Bid Invitation
    R3TR     SBPP     Physical Information Object for BDS
    R3TR     SBPR     BDS: Relationship Between Information Objects
    R3TR     SBRL     Logical Information Object for BDS
    R3TR     SBRP     Physical Information Object
    R3TR     SBRR     BDS: Relationship Between Information Objects
    R3TR     SBSL     Logical Information Object for BDS
    R3TR     SBSP     Physical Information Object
    R3TR     SBSR     BDS: Relationship Between Information Objects
    R3TR     SBTL     Logical Information Object for BDS
    R3TR     SBTP     Physical Information Object
    R3TR     SBTR     BDS: Relationship Between Information Objects
    R3TR     SBWL     Logical information object for BDS
    R3TR     SBWP     Logical information object for BDS
    R3TR     SBWR     BDS: Relationship between information objects
    R3TR     SRHL     SRM: Hierarchical Lists
    R3TR     SRLD     Language-Dependent Client-Specific Retrieval Index Objekt
    R3TR     STYL     SAPscript Style
    Regards
      Uwe

  • Difference Between "Client Level & Company Code Level"

    Hello
    Can any explain me the difference between client level and company code level?
    What is the configuration that we do on client level and company code level?

    Message: Dear,
    Client : Unit within SAP system, self-contained, separate master data with independent set of tables. It represent corporate group.
    Company Code : Smallest organizational unit of external account for which a complete, self-contained bookkeeping system can be replicated.
    e.g, company within a corporate group
    Note: You will do the configuration at company code level by logging into the client for master tables etc..

  • Client Independent tables

    Hello,
    I have a following situation.
    We have two clients in development server. Table TAB1 has client as primary key so we have say 100 records in client 1 & 200 records in client 2.
    I would like to remove client field & make table TAB1 as client independent.
    What will happen with data when I will adjust the database table, if i select KEEP data option?
    How many records TAB1 will have ?
    300 records (100 + 200)
       OR
    100 + delta between 100 & 200
    Any help would be appriciated
    Regards,
    Sunil Joyous

    hi Sunil,
    you have to run Database Uitlity (SE14) and it will clean up your data acc. to the new table key. This means, if there is any duplication between the two clients, the duplicate entries will be deleted automtically (i. e. reduced to one entry).
    Just give it a try!
    hope this helps
    ec

  • Difference between clients.

    Hello all,
    I have a basic question here.
    What is the difference between clients in a system.
    For example we are having 120, 600 and 700 clients in DEV
    What type of data is stored in those clients. Will the data be different. Since programs are client independent can I do modifications to my programs in 600 and 700 clients.
    Why the name SILVER and GOLD to the clients??
    Please explain.

    Hi Naren,
    Client strategies vary from place to place. But one thing to understand is that a client is SAP's way of logically seperating data. In the underlying database, though, it will be just one table holding all the data for all the clients within the same server.
    There are repository objects and some configuration tables that are cross-client or client-independent. In the basis configuration, there is a setting where they configure each client to be modifiable, non-modifiable and if modifiable, whether client-dependent modification are allowed or client-independent modifications are allowed.
    So, if they allow it, you can do your programs anywhere. But one more factor to consider is the transport layer. This is again configuration dependent on client. So if you are making changes in client that is not on the transport path, then you will have tough time getting it into higher systems.
    GOLD, SILVER etc are typically terminology used for representing the importance of the client. Typically Golden client is one which is like a vault, where you move all your tested configuration and client-dependent activities and leave it there. This will only be used if there is a need for restore or creating a brand new client. All other clients in development system will either be constantly changing or refreshed periodically. There will be lot test data also. So you need a client that is clean from all this garbage and that is your golden client. I have to admit that I didn't hear SILVER being used anywhere, but it may be on similar lines.
    Clients are dedicated to development, configuration, crash-and-burn, unit testing and golden client. It is not necessary to have all these, but most often they use this landscape in development systems.
    In production systems, different clients are used to seggregate access and data.
    Hope this helps,
    Srinivas

  • 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

  • Diff client depandent and client independent

    HI,
    what is different between client dependent and client independent.Please explain...
    gaurav mittal

    client dependent is when u make some configuration which will effect all the clients.. i mean changes are reflected in all clients
       for eg access sequence,
    client independent is when u make any changes in some client it will reflect in particular client in which u r working

  • Can we share the same Business Action between clients?

    Hi All,
    I have a scenario wherein we have two Remote Trading Partners (say Remote1 and Remote2). Both these clients send EDI-850 documents and expect EDI-997.
    So,
    1. I first go to the Protocols Tab.
    2. Create a Business Action (Process_850) and Follow the Wizard for the details.
    In the process i create
    a. Process Protocol
    b. Document Protocol
    c. Exchange Protocol
    Now for the second client also sends us the EDI-850 document. So can I reuse all the above created objects and just have two Agreements one with Remote1 using the same Business Action (Process_850) but different Delivery Channels
    Or should i be creating different Business Actions for the different Clients?
    If i indeed have to create diff business actions then can i reuse the Document Protocol between clients? It does allow you to select and existing one.
    Finally, If i understand this correct, We create a Business Action and hence the Document Protocol. We set the default values of the Document Protocol Parameters in here and when we create Trading Partners we override these (Application Sender Code, etc.). In a way we are saying that Process_850 is a business action that is processing 850 documents. 850 being a template and the document parameters are the replacements done on 850 when it is sent by Sender we have say Acme and when it is receiver we have GlobalChips.

    If it is for two diffrent trading partner you can share the same business action.

  • What's the difference between client combo and server combo? Also, what would happen if I install both?

    what's the difference between client combo and server combo? Also, what would happen if I install both?

    One is for the base version of the Mac OS, the other is for the Server version. You can only install the one that matches your system.

Maybe you are looking for