Now you can learn ABAP by watching and listening video classes by experienced consultant.
Read, Surf and Download useful ABAP tips, tutorials, code and download many eBooks and documents free
Get all latest opening for SAP ABAP and related jobs, vaccancies across India and apply for the same.
A client is a logical portion of an SAP R/3 physical database. From a business standpoint, a client can be interpreted as a logical group of companies.
All customizing (configuration) and development (ABAP) work in SAP R/3 is performed in a client. However, the data from both customizing and development work may be stored within an individual client (client dependent data) or among all clients (client independent data) in the system.
The data on each client
may be separate from that of the other clients. There are basically two
types of data in an SAP R/3 System. Client-dependent and
client-independent data.
§ Client-dependent data is defined as
data specific to an individual client. Client-independent data can be defined
as data contained across all clients in the system.
§ Some examples of client-dependent
data include number ranges, ABAP variants, and user masters as well as the data
that is created or updated through SAP R/3 transactions
( transaction data).
( transaction data).
Examples of
client-independent data include data dictionary objects (tables, views),
ABAP source code, screens, and menus.
All data resides in
tables. To determine if a particular table is client-dependent or
client-independent, the table structure needs to be reviewed. The table
structure can be viewed by the data dictionary (SE11). If MANDT (client
in German) is the first key field of the table, then the table is
client-dependent; otherwise, the table is client-independent.
For example, the TSTC
table is client-independent; however, the USR01 table is client-dependent. As
shown in the above diagram, every SAP R/3 system contains the three clients
000, 001, and 066. Let's review these clients and examine what they
contain.
