difference between client dependent table and client independent table

[Former Member]

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

[Former Member]

Very simple: Client dependent tables have field 'MANDT' as the first key field.

Regards,

John.

[Former Member]

Hi,

The main difference is:

A Client dependent table has the first field as client i.e. field with data type as MANDT.

A Client independent table does not have a field for client.

Hence if a server has 3 clients 100, 200 and 300 - then in a client dependent table, each client can have completely different entries.

However in a client independent table, the entries would be cross-client i.e. same.

Cheers,

Aditya

[Former Member]

Hi

client dependent tables have amndt feild. these cannot be used in other clients.

for example if u create a table in 800 client if u delcare it as client dependent,u cannnot use it in 100 client.

client independent tables can be used irrespective of client.

[Former Member]

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.

https://www.sdn.sap.com/irj/sdn/forums

[Former Member]

Hi,

In SAP, highest level of organisation structure is client which you are entering at the time of log-in itself.

In most of the tables are client dependant where first column is client (MANDT) by default and entry in that field is complusory. so that is client dependant table.

There are few tables which are client independents, effect of any change in this table will affect all the clients. In that table client field is not there.

Whenever you making any change in value of such table, system will give you message that "this is client independance, whether you want to change it".

only data i.e the entries in the table are client independent or dependent depending on the field mandt

structures of tables are always client independent if u created one table structure in one client u can see that in all other clients of that server

hope it is clear plzz reward if it is usefull plzz dont forget to reward if it is useful.....

[Former Member]

Client Dependent Table:-

1>They have field called MANDT in this type of table which contains the client no.

2>In this type of table for different client the data set can be different.

Client Independent Table:-

1> They dont have that MANDT field in this type of table

2>This Table is called cross client table means for all the clients they have the same entries in the table.

[Former Member]

Client dependent is data is avilable for only the specified client in the table is MANDT field.

client independent table means the data or records will be avilable to all the clients.

[Former Member]

hi,

There are two types of tables in the R/3 database: client-dependent and client-independent. A table is client-dependent if the first field is of type CLNT. The length will always be 3; and by convention, this field is named mandt. If the first field is not of type CLNT, the table is client independent.

The user master records (containing R/3 user IDs) are client-dependent. Therefore, to gain access to a client, the system administrator must create a new user ID for you within that client

Developers and testers use the logon client mechanism to create and access multiple, independent set of data within a single table.

The average R/3 installation has three systems: development, test, and production. By default, each system comes with three clients installed: 000, 001, and 066. It is common to have from three to six clients in the development and test systems, but rarely will you see more than one client in production.

reward if its useful

[Former Member]

Client dependent tables have field 'MANDT' as the first key field. and this tables in data belongs to that client only, others clients can't view this table in data.

Client independent means its for all clients.

[Former Member]

A table is client-dependent if the first field is of type CLNT. The length will always be 3, and by convention, this field is always named mandt. If the first field is not of type CLNT, the table is client-independent.

If the tables involved are all client-dependent, there can be more than one group of testers working at a time in one test system. Two teams of testers can test divergent functionality in the same set of programs at the same time provided they log on to different logon clients. The updates done by one team will not change the data belonging to the other team.

[Former Member]

Hi,

A single SAP system can manage the application data for several separate areas of a business (for example, branches). Each of these commercially separate areas in the SAP system is called a client, and has a number. When a user logs onto the SAP Web AS ABAP, they specify a client. The first column in the structure of every database table containing application data is the client field (MANDT, from the German word for client). It is also the first field of the table key. Only universal system tables are client-independent, and do not contain a client name.

By default, Open SQL statements use automatic client handling. Statements that access client-dependent application tables only use the data from the current client. You cannot specify a condition for the client field in the WHERE clause of an Open SQL statement. If you do so, the system will either return an error during the syntax check or a runtime error will occur. You cannot overwrite the MANDT field of a database using Open SQL statements. If you specify a different client in a work area, the ABAP runtime environment automatically overwrites it with the current one before processing the Open SQL statement further.

Should you need to specify the client specifically in an Open SQL statement, use the addition

... CLIENT SPECIFIED ....

directly after the name of the database table. This addition disables the automatic client handling and you can use the field MANDT both in the WHERE clause and in a table work area.

Regards,

Renjith Michael.

http://www.sourceveda.com/

[Former Member]

Hi,

Please Close The Thread if u have found the Answer already

Regards

Sandipan