client

[Former Member]

What is siginificance of client field in tables.?

What is the difference between client-dependent and client-independent

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

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.

[Former Member]

Hi

tables which can be access by all user are client independent (no mandt field in table)

tables which can be access by some specific user are client dependent (use mandt field in table)

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.

[Former Member]

Hi Sandeep,

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

Hope this helps a bit..

Reward if useful ..

Cheers

Kripa Rangachari.

[ak_upadhyay]

Hi,

when we add a field MANDT of type MANDT then our table is client dependent and is visible to only that client. But if this Field is not added to the table then we can access the table using any client number.

or

tables which can be access by all user are client independent (no mandt field in table)

tables which can be access by some specific user are client dependent (use mandt field in table)

or

client dependent tables have a mandatory field MANDT field.

Reward points if useful....

Regards

AK

[Former Member]

Hi,

CLIENT is the highest heriarchial unit in any Module in SAP.

In the development business SAP landscape will be divided into 3 systems namely DEVELOPMENT, Testing or Quality and Production.

These are 3 sepearate servers(boxes). they may exist seperately (in 3 system landscape)or sometimes both the DEV and TEST systems together and PRD sepearte(2 type landscape).

This is purely a basis work.

Again coming to each System, there may be different clients in DEV system, as we need diffferent systems to work, one for customizing work, and other for sandbox work and other for Development work(transports), based on the requirements we can define any number of clients.

in PRD there won't be different clients.

Somes times in Quality may exits 2 or 3 clients.

So the requests will be created in DEV in one client and they are released and sent to other systems like QUALITY and PRD once they are perfect.

A single R/3 System can manage the application data for several separate areas of a business (for example, branches). Each of these commercially separate areas in the R/3 System is called a client, and has a number. When a user logs onto an R/3 System, 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.

Reading data

Client Handling

As already mentioned, you can switch off the automatic client handling in Open SQL statements using a special addition. In the SELECT statement, the addition comes after the options in the FROM clause:

SELECT... FROM <tables> CLIENT SPECIFIED. ..

If you use this addition, you can then address the client fields in the individual clauses of the SELECT statement

these links helps u

http://help.sap.com/saphelp_46c/helpdata/en/90/174b6e5733d1118b3f0060b03ca329/frameset.htm

http://help.sap.com/saphelp_46c/helpdata/en/42/0a8a885c2811d2b414006094b9ea64/frameset.htm

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 All dictionary Objects data and Repository objects data like Programs, Fun modules, tables etc

Cheers,

vasavi.

kindly reward if helpful.

[former_member202957]

Hi Sandeep,

Significance of clietns shows that the table is client dependent or independent.

Client dependent.: Nothing but the tables have Field MANDT and you can maintain data differnt depending on client.

eX: client 301 may have differnt data and client 501 may have differnt data for the same table.

Client Independent.: This table dosent have MANDT field and the data in all the clients remain same.

<b>reward if useful</b>

Regards,

sunil kairam.