ATA DICTIONARY

Type of a table or structure

The table type determines how the logical table description defined in the ABAP/4 Dictionary is
reproduced on the database. There are the following table types:
1. transparent table
. structure
!. append structure
"or internal purposes# such as storing control data or update te$ts# there are in addition the
following table types:
1. pooled table
. cluster table
!. generated %iew structure
Transparent table There is a physical table on the database for each transparent table. The
names of the physical tables and the logical table definition in the ABAP/4 Dictionary
correspond. All business data and application data are stored in transparent tables.
Structure &o data records e$ist in the database for a structure. 'tructures are used for the
interface definition between programs or between screens and programs.
Append structure An append structure defines a set of fields which belong to another table or
structure but which are treated in the correction administration as its own ob(ect. Append
structures are used to support modifications.
Pooled table Pooled tables can be used to store control data )e.g. screen se*uences# program
parameters or temporary data+. 'e%eral pooled tables can be combined to form a table pool. The
table pool corresponds to a physical table on the database in which all the records of the
allocated pooled tables are stored.
Cluster table ,luster tables contain continuous te$t# for e$ample# documentation. 'e%eral cluster
tables can be combined to form a table cluster. 'e%eral logical lines of different tables are
combined to form a physical record in this table type. This permits ob(ect-by-ob(ect storage or
ob(ect-by-ob(ect access. .n order to combine tables in clusters# at least parts of the /eys must
agree. 'e%eral cluster tables are stored in one corresponding table on the database.
Generated view structure .n acti%ation a structure is generated for a %iew. This structure ser%es
as interface for the runtime en%ironment. .t does not generally appear in the ABAP/4 Dictionary.
!at is a Data Class"
The Data class determines in which tablespace the table is stored when it is created in the
database. 0hat is a 'i1e ,ategory2 The 'i1e category describes the probable space re*uirement
of the table in the database. 3ow 4any types of si1e categories and data classes are there2 There
are fi%e si1e categories )5-4+ and 11 data classes# only three of which are appropriate for
application tables:
- APP65 - 4aster data )data fre*uently accessed but rarely updated+
- APP61 - Transaction data )data that is changed fre*unetly+
- APP6 - 7rganisational data )customi1ing data that is entered when system is
configured and then rarely changed+
!at are control tables"
The %alues specified for the si1e category and data class are mapped to database-specific %alues
%ia control tables.
!at is t!e function of t!e transport syste# and wor$benc! or%aniser"
The function of the transport system and the 0or/bench 7rgani1er is to manage any changes
made to ob(ects of the ABAP/4 De%elopment 0or/bench and to transport these changes between
different 'AP systems.
!at is a table pool"
A table pool )or pool+ is used to combine se%eral logical tables in the ABAP/4 Dictionary. The
definition of a pool consists of at least two /ey fields and a long argument field )8A9DATA+.
!at are pooled tables"
These are logical tables which must be assigned to a table pool when they are defined. Pooled
tables can be used to store control data )such as screen se*uences or program parameters+.
!at is a table cluster"
A table cluster combines se%eral logical tables in the ABAP/4 Dictionary. 'e%eral logical rows
from different cluster tables are brought together in a single physical record. The records from
the cluster tables assigned to a cluster are thus stored in a single common table in the database.
!ic! ob&ects are independent transport ob&ects"
Domains# Data elements# Tables# Technical settings for tables# 'econdary inde$es for transparent
tables#
'tructures# 8iews#
4atchcode ob(ects# 4atchcode .Ds# 6oc/ ob(ects.
!at are t!e Data types of t!e e'ternal layer"
A,,P# ,3A9# ,6&T# ,:;<#,:99# DAT'# D=,# "6TP# .&T1#.&T# .&T4# 6A&>#
6,39#69A0# &:4,# P9=,# ?:A&#9A0 #T.4'# :&.T# 8A9,.
!at are t!e Data types of t!e A(AP)* layer"
Possible ABAP/4 data types: ,: ,haracter. D: Date# format <<<<44DD. ": "loating-point
number in D7:B6= P9=,.'.7& )@ bytes+. .: .nteger. &: &umerical character string of arbitrary
length. P: Amount or counter field )pac/edA implementation depends on hardware platform+. ':
Time stamp <<<<44DD3344''. T: Time of day 3344''. 8: ,haracter string of %ariable
length# length is gi%en in the first two bytes. B: 3e$adecimal )binary+ storage.
+ow can we set t!e tablespaces and e'tent si,es "
<ou can specify the e$tent si1es and the tablespace )physical storage
area in the database+ in which a transparent table is to be stored by setting the si1e category and
data class.
!at is a data dictionary "
Data dictionary is a central source of data in a data management system. .ts main function is to
support the ..t has details about
- !at data is contained "
- !at are t!e attributes of t!e data "
- !at is t!e relations!ip e'istin% between t!e various data ele#ents "
!at functions does a data dictionary perfor# "
.n a data management system# the principal functions performed by the data dictionary are
- 4anagement of data definitions
- Pro%ision of information for e%aluation
- 'upport for software de%elopment
- 'upport form documentation
- =nsuring that the data definitions are fle$ible and up-to-date.
A field containing currency amounts )data type ,:99+ must be assigned to a reference table and
a reference field. =$plain.
As a reference table# a system table containing all the %alid currencies is assigned or any other
table which contains a field with the currency /ey format. This field is called as reference field.
The assignment of the field containing currency amounts to the reference field is made at
runtime. The %alue in the reference field determines the currency of the amount.
!at is t!e si%nificance of Tec!nical settin%s .specified w!ile creatin% a table in t!e data
dictionary/ "
By specifying technical settings we can control how database tables are created in the database.
The technical settings allows us to - optimi1e storage space re*uiremnets
- table access beha%iour
- buffering re*uired
- changes to entries logged
!at is t!e si%nificance of Delivery Class "
- The deli%ery class controls the degree to which the 'AP or the customer is responsible for table
maintenance
- whether 'AP pro%ides the table with or without contents.
- determines the table type. - determines how the table beha%es when it is first installed# at
upgrade# when it is transported# and when a client copy is performed.
!at is t!e #a'i#u# nu#ber of structures t!at can be included in a table or structure
- &ine.
!at are t!e two #et!ods of #odifyin% Sap standard tables "
- Append 'tructures and
- ,ustomi1ing .ncludes.
!at is t!e difference between a Substructure and an Append Structure "
- .n case of a substructure# the reference originates in the table itself# in the forma of a
statement .include... . - .n case of an append structure# the table itself remains unchanged and the
refrence originates in the append structure.
!at are t!e two ways for restrictin% t!e value ran%e for a do#ain"
- By specifying fi$ed %alues.
- By stipulating a %alue table.
!at is a 0atc! Code "
4atch ,ode is a tool to help us to search for data records in the system. 4atch codes are an
efficient and user-friendly search aid where /ey of a record is un/nown. 0hat are the two le%els
in defining a 4atch ,ode 2
- 4atch ,ode ob(ect
- 4atch ,ode .d.
!at is t!e #a'i#u# nu#ber of #atc! code Id1s t!at can be defined for one 0atc! code
ob&ect "
- !C. A match code .d is a one character .D which can be a letter or a number.
Can we define our own 0atc! Code ID1s for SAP 0atc!codes "
<es# the numbers 5 to D are reser%ed for us to create our own 4atch ,ode .Ds for a 'AP defined
4atchcode ob(ect.
!at is an 2pdate type wit! reference to a 0atc! code ID"
.f the data in one of the base tables of a matchcode .D changes# the matchcode data has to be
updated. The update type stipulates when the matchcode is to be updated and how it is to be
done. The update type also specifies which method is to be used for Building matchcodes . <ou
must specify the update type when you define a matchcode .D.
!at are conversion routines "
- &on standard con%ersions from display format to sap internal format and %ice-%ersa are
implemented with so called con%ersion routines.
Aggregated 7b(ects 8iews# matchcodes# and loc/ ob(ects are also called aggregate ob(ects
because they are formed from se%eral related tables.
!at is a 3iew "
- A %iew is a logical %iew on one or more tables. A %iew on one or more tables i.e# the data from
a %iew is not actually physically stored instead being deri%ed from one or more tables. A %iew
can be used to summari1e data which is distributed among se%eral tables
+ow #any types of 3iews are t!ere "
- Database 3iew .S455/
Database %iews are implement an inner (oin# that is# only records of the primary table )selected
%ia the (oin operation+ for which the corresponding records of the secondary tables also e$ist are
fetched. .nconsistencies between primary and secondary table could# therefore# lead to a reduced
selection set. .n database %iews# the (oin conditions can be formulated using e*uality
relationships between any base fields. .n the other types of %iew# they must be ta/en from
e$isting foreign /eys. That is# tables can only be collected in a maintenance or help %iew if they
are lin/ed to one another %ia foreign /eys.
- +elp 3iew . S46*/
3elp %iews are used to output additional information when the online help system is called.
0hen the "4 button is pressed for a screen field# a chec/ is first made on whether a matchcode is
defined for this field. .f this is not the case# the help %iew is displayed in which the chec/ table of
the field is the primary table. Thus# for each table no more than one help %iew can be created#
that is# a table can only be primary table in at most one help %iew.
- Pro&ection 3iew
Pro(ection %iews are used to suppress or mas/ certain fields in a table )pro(ection+# thus
minimi1ing the number of interfaces. This means that only the data that is actually re*uired is
e$changed when the database is accessed. A pro(ection %iew can draw upon only one table.
'election conditions cannot be specified for pro(ection %iews.
0aintenance 3iew . S46* /
4aintenance %iews enable a business-oriented approach to loo/ing at data# while at the same
time# ma/ing it possible to maintain the data in%ol%ed. Data from se%eral tables can be
summari1ed in a maintenance %iew and maintained collecti%ely %ia this %iew. That is# the data is
entered %ia the %iew and then distributed to the underlying tables by the system.
!at is 7oc$in% "
0hen two users simultaneously attempt to access the same data record# this is synchronised by a
loc/ mechanism.
0hen dialog transactions are programmed# loc/s are set and released by calling certain function
modules. These function modules are generated automatically from the definition of so-called
loc/ ob(ects in the ABAP/4 Dictionary. To synchroni1e the access to a table by setting and
remo%ing loc/s# a 6oc/ ob(ect has to be defined in the ABAP/4 Dictionary. Acti%ating the loc/
ob(ect automatically creates Efunction modules for setting and remo%ing loc/s. These function
modules must be included when programming interacti%e transactions.
7oc$ 0ec!anis# 8 To set loc/s# a loc/ ob(ect must be defined in the ABAP/4 Dictionary. .n this
loc/ ob(ect# those tables in which data records are to be loc/ed by calling a loc/ are determined.
All tables included in a loc/ ob(ect must be connected to each other %ia foreign /eys. The /ey
fields of the tables in a loc/ ob(ect form the 6oc/ arguments for the tables. The loc/ arguments
are the basis for formulating the logical condition for identifying the records to be loc/ed. 0hen
acti%ating this loc/ ob(ect# two function modulesB with the names =&?:=:=F and
D=?:=:=F are generated.
4'a#ple 8
Problem : <ou wish to pre%ent a user from being able to change the name of a course or the name
of the professor with responsibility for the course at a time when another user is editing the
course description )which contains this information+.
Solution 8 The problem described abo%e can be sol%ed by defining a loc/ ob(ect =F:;:9'.
This is done by defining primary and secondary tables in the loc/ ob(ect. Table :;:9' is chec/
table of table :;9'B# so :;:9' should be selected as primary table and :;9'B as secondary
table of the loc/ ob(ect. The 6oc/ argument in this case is the field combination "AB&9#
;9'&9# and 'P9A' )i.e Primary ;ey ,ombination+. The 6oc/ mode 'hared is to be selected
here. This allows se%eral users to access the data simultaneously in display mode. The loc/ mode
in the generated function modules for setting )=&?:=:=F=F:;:9'+ and releasing
)D=?:=:=F=F:;:9'+ loc/s is therefore set to shared as default# but can be o%erridden by
calling the function modules. .f the function module =&?:=:=F=F:;:9' is called with
"AB&9 G H1H and ;9'&9 G H!H# the record for course ! in faculty 1 is loc/ed in table :;:9'.
"urthermore# all the course descriptions for this course are loc/ed in table :;9'B since field
'P9A' was not specified when the function module was called. .n such cases# the loc/ is made
generically for a field which is not defined. .f the function module D=?:=:=F=F:;:9' is
now called with "AB&9 G H1H# ;9'&9 G H!H and 'P9A' G HDH# the >erman course description is
unloc/ed. All other course descriptions remain loc/ed.
!at is database utility "
Database utility is the interface between the ABAP/4 Dictionary and the underlying the 'AP
system. The database utility is the interface between the ABAP/4 Dictionary and the relational
database underlying the 'AP system. <ou can call the database utility from the initial screen of
the ABAP/4 Dictionary with :tilities I Database utility. The database utility allows you to
create# delete and con%ert ob(ects from the ABAP/4 Dictionary in the database.
0OD27ARI9ATION
!at is 0odulari,ation and its benefits"
.f the program contains the same or similar bloc/s of statements or it is re*uired to process the
same function se%eral times# we can a%oid redundancy by using modulari1ation techni*ues. By
modulari1ing the ABAP/4 programs we ma/e them easy to read and impro%e their structure.
4odulari1ed programs are also easier to maintain and to update.
+ow can we create callable #odules of pro%ra# code wit!in one A(AP)* Pro%ra#"
A. By defining macros. B. By creating include programs in the library.
!at are subroutines"
'ubroutines are program modules which can be called from other ABAP/4 programs or within
the same program.
!at are t!e types of Subroutines"
A: Internal Subroutines8 The source code of the internal subroutines will be in the same
ABAP/4 program as the calling procedure )internal call+.
(: 4'ternal Subroutines8 The source code of the e$ternal subroutines will be in an ABAP/4
program other than the calling procedure.
!at are t!e different types of para#eters"
"ormal parameters: Parameters which are defined during the definition of subroutine with the
"794 statement. Actual parameters: Parameters which are specified during the call of a
subroutine with the P=9"794 statement.
+ow can one distin%uis! between different $inds of para#eters"
A. .nput parameters are used to pass data to subroutines. B. 7utput parameters are used to pass
data from subroutines.
!at are t!e different #et!ods of passin% data"
A: Callin% by reference8 During a subroutine call# only the address of the actual parameter is
transferred to the formal parameters. The formal parameter has no memory of its own# and we
wor/ with the field of the calling program within the subroutine. .f we change the formal
parameter# the field contents in the calling program also change.
(: Callin% by value8 During a subroutine call# the formal parameters are created as copies of the
actual parameters. The formal parameters ha%e memory of their own. ,hanges to the formal
parameters ha%e no effect on the actual parameters.
C: Callin% by value and result8 During a subroutine call# the formal parameters are created as
copies of the actual parameters. The formal parameters ha%e their own memory space. ,hanges
to the formal parameters are copied to the actual parameters at the end of the subroutine.
The method by which internal tables are passed is By 9eference.
!at is t!e difference between t!e function #odule and a nor#al A(AP)* subroutine"
.n contrast to normal subroutines function modules ha%e uni*uely defined interface. 'ub routines
do not return %alues.
'ub routines do not return e$ceptions. 'ub routines cannot be tested independently. Declaring
data as common parts is not possible for function modules. "unction modules are stored in a
central library. 0hat is a function group2 A function group is a collection of logically related
modules that share global data with each other. All the modules in the group are included in the
same main program. 0hen an ABAP/4 program contains a ,A66 ":&,T.7& statement# the
system loads the entire function group in with the program code at runtime. =%ery function
module belongs to a function group.
!at is t!e difference between internal tables and e'tract datasets"
A. The lines of an internal table always ha%e the same structure. By using e$tract datasets# you
can handle groups of data with different structure and get statistical figures from the grouped
data.
B. <ou ha%e to define the structure of the internal table at the begining. <ou need not define the
structure of the e$tract dataset.
,. .n contrast to internal tables# the system partly compresses e$tract datasets when storing them.
This reduces the storage space re*uired.
D. .nternal tables re*uire special wor/ area for interface whereas e$tract datasets do not need a
special wor/ area for interface.
Delivery class in A(AP data dictionary and
related interview ;uestions
By admin J 7ctober C# 51 J ABAP Basics# All# Data Dictionary# .nter%iew ?uestions# 'AP
Basics
</ !ere is delivery class defined"
Ans: .n '=11# while creation of table# under KDeli%ery L 4aintenanceM tab.
</ !at is t!e si%nificance of a delivery class"
Ans: The deli%ery class attribute allows managing the transport of table data when installing or
upgrading in a client copy and when transporting between customer systems. .t is also used in
the e$tended table maintenance.
</ !at are t!e types of delivery classes"
Ans: There are N different types of deli%ery classes:
A: Application tableO:sed to store master data and transaction data.
,: ,ustomer tableO:sed to store the data of customers only.
6: :sed to store temporary data.
>: ,ustomer tableO.n this table# 'AP may insert new data records but may not o%erwrite
or delete e$isting data records. The customer namespace must be defined in table
T9=',.
=: 'ystem tableOThis table has its own namespaces for customer entries. The customer
namespace must be defined in table T9=',.
': 'ystem tableOThis table has the same status of data changes as program changes.
0: 'ystem tableOA table of the de%elopment en%ironment. Data of this table are
transported with its own transport ob(ects.
The deli%ery class of a maintenance %iew is used in the 4'tended Table 0aintenance .S0=>/.
.f a maintenance interface is generated for the maintenance %iew# the following information is
analy1ed when %iew data is entered for this interface:
"or maintenance %iews ha%ing deli%ery class = or ># there is a chec/ if the entered data
satisfies the namespace defined in table T9=', for the %iew.
There is a chec/ if the transport connection built into the generated table maintenance
ma/es sense. "or e$ample# there is no transport for maintenance %iews with deli%ery
classes 6 and 0.
The deli%ery class of the corresponding base table of the %iew alone defines how the data entered
in a base table of the %iew is handled during an upgrade and during transport between customer
systems.
The PData classP %alue in Technical settings has nothing about table maintenance# it only
determines which table space should the table reside in.
<ou should chec/ the PDeli%ery classP in Attributes screen. .f it is P, - ,ustomi1ing tableP# itHs
considered as customi1ing data and automatically lin/ed to the transport management system.
And to change data in table# the client you are wor/ing should be in P,hanges to 9epository and
cross-client ,ustomi1ing allowedP mode )Trans. ',,4+. .f deli%ery class is PA - Application
tableP# you can still maintain data using '4!5# but there is no lin/ to transport management
)though you can transport manually if you want+# and the client settings are not considered.
<ou can use P&o# or user# recording routineP setting to brea/ a ,ustomi1ing table apart from
transport system. .t has no effect on an Application table.
T!is error can only occur if t!e delivery class of t!e #aintenance view on a G or 4 table is
not #aintained? in ot!er words is initial: To c!ec$ t!is? %o to transaction S455 and c!ec$
t!e content of t!e field 1Delivery class1 on t!e title ele#ent 10aintenance status1:
A program correction is necessary. After you import this correction the deli%ery class of the
primary table is based on the primary table for the running of the %iewHs maintenance dialog in
the case of an initial deli%ery class of the %iew.
Create @ 0aintain Table .S455/
This wi/i guides you how to create and maintain tables.
ABAP Dictionary: Initial Screen
>o to ABAP Dictionary Tools > ABAP Workbench > Development > ABAP Dictionary
Type the name of the table in Database Table te$t bo$.
,hoose Display# Change or Create.
Dictionary: Maintain Table Screen
,lic/ on the deli%ery class.
The deli%ery class controls the transport of table data when installing or upgrading# in a client
copy and when transporting between customer systems.
There are the following deli%ery classes:
A : Application table (master and transaction data).
C : Customer table, data is maintained by the customer only.
L : Table for storing temporary data.
G : Customer table, SA may insert ne! data records, but may not o"er!rite or delete
e#isting data records. The customer namespace must be defined in table T$%SC.
% : System table !ith its o!n namespaces for customer entries. The customer
namespace must be defined in table T$%SC.
S : System table, data changes ha"e the same status as program changes.
& : System table (e.g. table of the de"elopment en"ironment) !hose data is transported
!ith its o!n transport ob'ects.
<ou can choose the option Customized table
7n Object Directory Entry dialog# select the pac/age to sa%e.
>o to Technical Settings
Dictionary : Maintain Technical Settings
The technical settings define how the table is created on the database.
'et the 6ocal 'torage Parameters:
,hoose APP7A from the Data Class dropdown bo$.
'elect the 'i1e Category )5-4+.
,lic/ Save and Active button.
3i#

The data class determines the tablespace in which a table is created. The database administrator
uses tablespaces to organi1e and maintain the database. ,hoosing the proper tablespace ma/es
database administration easier# increases system performance# and to some e$tent e%en increases
system a%ailability because the database is usually ta/en offline for reorgani1ations.

The deli%ery class controls the transport of table data when installing or upgrading# in a client
copy and when transporting between customer systems. The deli%ery class is also used in the
e$tended table maintenance.

There are the following deli%ery classes:

A: Application table )master and transaction data+.
,: ,ustomer table# data is maintained by the customer only.
6: Table for storing temporary data.
>: ,ustomer table# 'AP may insert new data records# but may not o%erwrite or delete e$isting
data records. The customer namespace must be defined in table T9=',. ):se 9eport
9DD;79Q4 here+.
=: 'ystem table with its own namespaces for customer entries. The customer namespace must be
defined in table T9=',. ):se 9eport 9DD;79Q4 here.+
': 'ystem table# data changes ha%e the same status as program changes.
0: 'ystem table )e.g. table of the de%elopment en%ironment+ whose data is transported with its
own transport ob(ects )e.g. 9!T9 P97># 9!T9 TAB6# etc.+.
hi

in a simple way

data class : is the place in the database where the table is stored...

deli%ery class : it describes the owner of the class....i.e the one who maintains the data in the
table

in a elaborate manner


The data class determines the tablespace in which a table is created. The database administrator
uses tablespaces to organi1e and maintain the database. ,hoosing the proper tablespace ma/es
database administration easier# increases system performance# and to some e$tent e%en increases
system a%ailability because the database is usually ta/en offline for reorgani1ations.

The deli%ery class controls the transport of table data when installing or upgrading# in a client
copy and when transporting between customer systems. The deli%ery class is also used in the
e$tended table maintenance.

regards
prasanth
R i#

The data class determines the tablespace in which a table is created. The database administrator
uses tablespaces to organi1e and maintain the database. ,hoosing the proper tablespace ma/es
database administration easier# increases system performance# and to some e$tent e%en increases
system a%ailability because the database is usually ta/en offline for reorgani1ations.

The deli%ery class controls the transport of table data when installing or upgrading# in a client
copy and when transporting between customer systems. The deli%ery class is also used in the
e$tended table maintenance.

There are the following deli%ery classes:

A: Application table )master and transaction data+.
,: ,ustomer table# data is maintained by the customer only.
6: Table for storing temporary data.
>: ,ustomer table# 'AP may insert new data records# but may not o%erwrite or delete e$isting
data records. The customer namespace must be defined in table T9=',. ):se 9eport
9DD;79Q4 here+.
=: 'ystem table with its own namespaces for customer entries. The customer namespace must be
defined in table T9=',. ):se 9eport 9DD;79Q4 here.+
': 'ystem table# data changes ha%e the same status as program changes.
0: 'ystem table )e.g. table of the de%elopment en%ironment+ whose data is transported with its
own transport ob(ects )e.g. 9!T9 P97># 9!T9 TAB6# etc.+.
$eport Abuse
Li(e ())
Re: Data class vs delivery class
Prasanth Kasturi Apr **, *))+ *:,- . (in response to se(har manda)
hi

in a simple way

data class : is the place in the database where the table is stored...

deli%ery class : it describes the owner of the class....i.e the one who maintains the data in the
table

in a elaborate manner


The data class determines the tablespace in which a table is created. The database administrator
uses tablespaces to organi1e and maintain the database. ,hoosing the proper tablespace ma/es
database administration easier# increases system performance# and to some e$tent e%en increases
system a%ailability because the database is usually ta/en offline for reorgani1ations.

The deli%ery class controls the transport of table data when installing or upgrading# in a client
copy and when transporting between customer systems. The deli%ery class is also used in the
e$tended table maintenance.

regards
prasanth
$eport Abuse
Li(e ())
Re: Data class vs delivery class
Naresh !andi "en#ata Apr **, *))+ *:,/ . (in response to se(har manda)
3i#
Data ,lass

.f you choose the data class correctly# your table is automatically assigned to the correct area
)tablespace or DBspace+ of the database when it is created. =ach data class corresponds to a
physical area in which all the tables assigned to this data class are stored. There are the following
data classes:

APP65 )master data+: Data which is seldomly changed. An e$ample of master data is the data
contained in an address file# such as the name# address and telephone number.
APP61 )transaction data+: Data that is fre*uently changed. An e$ample of transaction data is the
goods in a warehouse# which change after each purchase order.
APP6 )organi1ational data+: ,ustomi1ing data that is defined when the system is installed and
seldomly changed. An e$ample is the table with country codes.
Two further data classes# :'9 and :'91# are pro%ided for the customer. These are for user
de%elopments. The tables assigned to these data classes are stored in a tablespace for user
de%elopments.

Deli%ery ,lass

The deli%ery class controls the transport of table data for installation# upgrade# client copy and
when transporting between customer systems. The deli%ery class is also used in the e$tended
table maintenance.

There are the following de%elopment classes:

A: Application table )master and transaction data+.
,: ,ustomer table# data is only maintained by the customer.
6: Table for storing temporary data.
>: ,ustomer table# 'AP may insert new data records but may not o%erwrite or delete e$isting
ones. The customer namespace must be defined in table T9=',. To define the customer
namespace use report 9DD;79Q4. <ou can start it directly from the table maintenance by
choosing ,ustomer namespace definition on the Attributes tab.
=: 'ystem table with its own namespace for customer entries. The customer namespace must be
defined in table T9=',. To define the customer namespace use report 9DD;79Q4. <ou can
start it directly from the table maintenance by choosing ,ustomer namespace definition on the
Attributes tab.
': 'ystem table# data changes ha%e the status of program changes.
0: 'ystem table )e.g. table of the de%elopment en%ironment+ whose data is transported with its
own transport ob(ects )e.g. 9!T9 P97># 9!T9 TAB6# etc.+.
$eport Abuse
Li(e ())
Re: Data class vs delivery class
Bri$esh Patel Apr **, *))+ *:,- . (in response to se(har manda)
hi #

%isit below lin/ to /now about deli%ery class..
Shttp://help.sap.com/saphelpFnwN5/helpdata/en/4!/4Q@C5NN4bN11dDQDN55a5cDDb!c!/content.
htmT

and for Data class
Shttp://help.sap.com/saphelpFnwN5/helpdata/en/cf/1eacQ44C511d1@DN55555e@!d55/content.h
tmT

after reading the document of both lin/ you will understand the difference...

9egards #
Bri(esh
$eport Abuse
Li(e ())
Re: Data class vs delivery class
Runal Singh Apr **, *))+ 0:11 . (in response to se(har manda)
hi#

Data class in technical settings
The data class defines the physical area of the database )for 79A,6= the TAB6='PA,=+ in
which your table is logically stored. .f you choose a data class correctly# your table will
automatically be assigned to the correct area when it is created on the database.

The most important data classes are )other than the system data+:

APP65 4aster data
APP61 Transaction data
APP6 7rgani1ational and customi1ing data4aster data is data which is fre*uently read# but
rarely updated. Transaction data is data which is fre*uently updated. 7rgani1ational und
customi1ing data is data which is defined when the system is initiali1ed and then rarely changed.

There are two more data classes a%ailable# :'9 and :'91. These are reser%ed for user
de%elopments. The tables assigned to these data classes are stored in a tablespace for user
de%elopments.

&ote:The data class only has an effect on table storage for the database systems 79A,6= and
.&"794.B


Deli%ery class
The deli%ery class controls the transport of table data when installing or upgrading# in a client
copy and when transporting between customer systems. The deli%ery class is also used in the
e$tended table maintenance.

There are the following deli%ery classes:

A: Application table )master and transaction data+.
,: ,ustomer table# data is maintained by the customer only.
6: Table for storing temporary data.
>: ,ustomer table# 'AP may insert new data records# but may not o%erwrite or delete e$isting
data records. The customer namespace must be defined in table T9=',. ):se 9eport
9DD;79Q4 here+.
=: 'ystem table with its own namespaces for customer entries. The customer namespace must be
defined in table T9=',. ):se 9eport 9DD;79Q4 here.+
': 'ystem table# data changes ha%e the same status as program changes.
0: 'ystem table )e.g. table of the de%elopment en%ironment+ whose data is transported with its
own transport ob(ects )e.g. 9!T9 P97># 9!T9 TAB6# etc.+.
Beha%ior during client copy
7nly the data of client-specific tables is copied.

,lasses ,# ># =# ': The data records of the table are copied to the target client.
,lasses 0# 6: The data records of the table are not copied to the target client.
,lass A: Data records are only copied to the target client if e$plicitly re*uested )parameter
option+. &ormally it does not ma/e sense to transport such data# but is supported to permit you to
copy an entire client en%ironment.
Beha%ior during installation# upgrade and language import
The beha%ior differs here for client-specific and cross-client tables.

,lient-specific tables
,lasses A and ,: Data is only imported into client 555. =$isting data records are o%erwritten.
,lasses =# ' and 0: Data is imported into all clients. =$isting data records are o%erwritten.
,lass >: =$isting data records are o%erwritten in client 555. .n all other clients# new data records
are inserted# but e$isting data records are not o%erwritten.
,lass 6: &o data is imported.
,ross-client tables
,lasses A# 6 and ,: &o data is imported.
,lasses =# '# and 0: Data is imported. =$isitng data records with the same /ey are o%erwritten.
,lasse >: Data records that do not e$ist are inserted# but e$isting data records are not
o%erwritten.
Beha%ior during transport between customer systems
Data records of tables of deli%ery class 6 are not imported into the target system. Data records of
tables of deli%ery classes A# ,# =# ># ' and 0 are imported into the target system )this is done for
the target client specified in the transport for client-specific tables+.

:se of the deli%ery class in the e$tended table maintenance
The deli%ery class is also analy1ed in the e$tended table maintenance )'4!5+. The maintenance
interface generated for a table ma/es the following chec/s:

<ou cannot transport the entered data with the transport lin/ of the generated maintenance
interface for tables of deli%ery classes 0 and 6.
0hen you enter data# there is a chec/ if this data %iolates the namespace defined for the table in
table T9=',. .f the data %iolates the namespace# the input is re(ected.

BR40O34D (Y 0OD4RATORC

=dited by: Al%aro Te(ada >alindo on Apr # 55@ !:QQ P4
The deli"ery class controls the transport of table data for installation, upgrade, client copy and
!hen transporting bet!een customer systems. The deli"ery class is also used in the e#tended
table maintenance.
.f you choose the data class correctly# your table is automatically assigned to the correct area
)tablespace or DBspace+ of the database when it is created. =ach data class corresponds to a
physical area in which all the tables assigned to this data class are stored.

hi

Data ,lass

.f you choose the data class correctly# your table is automatically assigned to the correct area
)tablespace or DBspace+ of the database when it is created. =ach data class corresponds to a
physical area in which all the tables assigned to this data class are stored. There are the following
data classes:

APP65 )master data+: Data which is seldomly changed. An e$ample of master data is the data
contained in an address file# such as the name# address and telephone number.
APP61 )transaction data+: Data that is fre*uently changed. An e$ample of transaction data is the
goods in a warehouse# which change after each purchase order.
APP6 )organi1ational data+: ,ustomi1ing data that is defined when the system is installed and
seldomly changed. An e$ample is the table with country codes.
Two further data classes# :'9 and :'91# are pro%ided for the customer. These are for user
de%elopments. The tables assigned to these data classes are stored in a tablespace for user
de%elopments.

http://help.sap.com/saphelpFnw554s/helpdata/en/fc/5Q4d!cec4c51e15555555a1145@4/conten
t.htm

Deli%ery ,lass

The deli%ery class controls the transport of table data for installation# upgrade# client copy and
when transporting between customer systems. The deli%ery class is also used in the e$tended
table maintenance.

There are the following de%elopment classes:

A: Application table )master and transaction data+.
,: ,ustomer table# data is only maintained by the customer.
6: Table for storing temporary data.
>: ,ustomer table# 'AP may insert new data records but may not o%erwrite or delete e$isting
ones. The customer namespace must be defined in table T9=',. To define the customer
namespace use report 9DD;79Q4. <ou can start it directly from the table maintenance by
choosing ,ustomer namespace definition on the Attributes tab.
=: 'ystem table with its own namespace for customer entries. The customer namespace must be
defined in table T9=',. To define the customer namespace use report 9DD;79Q4. <ou can
start it directly from the table maintenance by choosing ,ustomer namespace definition on the
Attributes tab.
': 'ystem table# data changes ha%e the status of program changes.
0: 'ystem table )e.g. table of the de%elopment en%ironment+ whose data is transported with its
own transport ob(ects )e.g. 9!T9 P97># 9!T9 TAB6# etc.+.

http://help.sap.com/saphelpFnw54/helpdata/en/4!/4Q@C5NN4bN11dDQDN55a5cDDb!c!/content.h
tm

http://help.sap.com/saphelpFnw54/helpdata/en/@5/@5@bQae1Q11dDQf!55a5cDDb!c!/content.ht
m

UbVr=0A9D ." :'=":66U/bV
Data Class
The data class determines the physical area of the database (tablespace) in which the table is created.
You set the data class in the technical settings for the table.
There are 5 data classes only three of which are appropriate for application tables:
APPL0- Master data (data frequently accessed but rarely updated).
APPL1- Transaction data (data that is changed frequently).
APPL2- Organizational data (customizing data that is entered when system is configured and then
rarely changed).
The other two types are:
!" # $ustomer %ata class
!"& ' $ustomer data class # (ntended for customer)s own de*elopments.
Deliery Class
The deli*ery class controls the degree to !hich the "AP or the c#sto$er is responsible for table
$aintenance%
+hether !,- pro*ides the table with or without contents.
Deter$ines the table type%
%etermines ho! the table behaes !hen it is first installed& at #pgrade& !hen it is transported& and
when a client copy is performed.
There are the following de*elopment classes: A&"&C&L
. A: ,pplication table (master and transaction data).
. C: $ustomer table/ data is only maintained by the customer.
. L: Table for storing temporary data.
. 0: $ustomer table/ !,- may insert new data records but may not o*erwrite or delete e1isting ones. The
customer namespace must be defined in table T"2!$. To define the customer namespace use report
"%%34"55. You can start it directly from the table maintenance by choosing $ustomer namespace
definition on the ,ttributes tab.
. 2: !ystem table with its own namespace for customer entries. The customer namespace must be
defined in table T"2!$. To define the customer namespace use report "%%34"55. You can start it
directly from the table maintenance by choosing $ustomer namespace definition on the ,ttributes tab.
. "' !ystem table/ data changes ha*e the status of program changes.
. +: !ystem table (e.g. table of the de*elopment en*ironment) whose data is transported with its own
transport ob6ects (e.g. "7T" -"40/ "7T" T,89/ etc.)