Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

necessary of having different clients

Former Member
0 Kudos

Hi all,

what is client concept. why we need development client,test client,quality client, production client while implementing sap to an enterprise. can't we implement sap to an enterprise with a single client.

Thanks and Regards,

Anil.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Client Handling

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

reward all help full answers

Message was edited by:

sunil kumar

8 REPLIES 8

Former Member
0 Kudos

Client Handling

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

reward all help full answers

Message was edited by:

sunil kumar

0 Kudos

Thanks Mr.sunil

Former Member

Hi..,

<b> These Development , testing - quality , production are systems not clients..</b>

This client concept has come to differentiate the data processing with respect to a particular organization..

<b>Suppose Take the example of TATA companies..</b>

They have internally so many divisions like TATA Motors, TATA steels, TATA Consultancy services ....etc

They may not want the data to be shared between different divisions .. But they may use same structured items for storing the data ( like Database tables will be same )..

When it comes to store the data the data will be stored in the database Client specifically.. <b>This is called the automatic Client Handling.. i.e The data in one client is not visible to other client users..</b>

Like .. salaries of the employeees and the performances of the employees of one department may not be disposed to all the other departments... So different client for each Department..

U can observe this in your system also..

When u retrieve data ( suppose spfli table data ) fro m the database then by default u will get the data that has client number equal to the client u r currently working with..., but the database contains other records also with different client number ... This data u cannot retrieve with out using CLIENT SPECIFIED option..

We can disable this AUTOMATIC CLIENT HANDLING by using the option CLIENT SPECIFIED..

i hope u understood...

reward if it helps u...

sai ramesh

Former Member
0 Kudos

Hi,

It seems you wants to know about the SAP landscape and their clients:

not the table field MANDT .

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.

reward if useful.

regards,

Anji

Message was edited by:

Anji Reddy Vangala

0 Kudos

Hi Mr.Anji,

U came close to my question. we know that in development server we develop the objects as per client requirements and in test client we will test those object whether they are working correctly are not and production client is the client in the database of the client resides. now, what i want to know is can't we develop the objects and test those objects in client itself. why we have development client, test client and production client in the project landscape.

Thanks and Regards,

Anil.

0 Kudos

Hi,

We are developers and we are developing the objects for particular client. In production server all the company details are present in database. No body will give access that database to other people. So we develop the objects in development server. And it will be tested in Quality server. In quality server the simulation of production server data will be there. so we test the objects in quality server. and after that we will send it to production server.

Hope it will understand to u

Former Member
0 Kudos

Hi Anil,

We can implement with Single Client if we donot require any custom development... I.e you will be using only standard functionality .

More over it seems u r curious about knowing SAP... and want to know more details.

Feel free to ask any questions by posting it here or send me email for any guidance..

Atlast 1 request. Please reward points to answers given by people. That's a good manner to motivate people.

Hope you will close this question after rewarding points.

DARSHAN PATEL

Former Member
0 Kudos

Thanks to Sunil, Sai ramesh,Anji Reddy, Ravi Kanth, Darshan patel for participating in the discussion and for sharing the knowledge.

Thanks and Regards,

Anil.