1.

Delivery class: - Technical Settings:

Delivery class is used to control the data transfer in this table while new installation, upgradation, moving to a new system
or moving to a new client or transferring the data between the two customers.

2. Enhancement category:
 Can be enhanced
 Can be enhanced - character type
 Can be enhanced – character type and numeric
 Not classified
 Can be enhanced deep

3. Data browser/Table view editing:

Display -> viewing the contents of the table

Maintenance modifying, adding or deleting the records in the table.

SE11 SE16 SE16N SM30

Display/Maintenance Display Yes Yes Yes Yes
allowed Maintenance Yes Yes Yes Yes
Display/Maintenance not Display No No No No
allowed Maintenance No No No No
Display/Maintenance Display Yes Yes Yes Yes
allowed with restrictions Maintenance No No No No
Only Display allowed Display Yes Yes Yes Yes
Maintenance Yes No No No

4. Table Maintenance Generator: SM30-Ref7

UtilitiesTable Maintenance GeneratorAuthorization Group &NC&-- Means W/O (without) authorization group

Function Group-Give the same name as that of the table.

Maintenance Screens one stepclick on Find Screen No Propose screen no.

 it gives you the screen number of the TMG initial screen.

 Here one screen will appear for the record maintenance

Two Step A small screen will pop up to get the data while adding the records.

Standard Recording Routine  TR will be created when you maintain the table entries. (See in SE10)

No, or user recording routine  TR will not be created.

TMG Events- to be included

1|Page
 5. Primary/Foreign Key:
Primary key(s) of one table is referred in another table as Primary key.

Example: Master Table (Primary key Table)  Primary key must be unique.

Item Table (Foreign key Table/Dependent Table)  But it appeared multiple times in the Item Table.

 It can be combined with other fields to form the primary key (Composite Key).
 And can be set as the foreign key in that table.
 We cannot create new value for this foreign key field which is not in the Master or Header Table

In the foreign key table, select the field foreign key buttongive short descriptionCHECK TABLEgive the name
of the PRIMARY KEY TABLEcheck proposal.

The required key fields will be listed out.

If a screen field is checked against a table, the key entries of the check table are displayed in the input help (F4 help) for
this field.

Cardinality means number of possible dependant records in the foreign key table with respect to the referred records in
the check table. 1N

6. Technical Setting for the Table:

Data Class:
It specifies the area or the region where the data is supposed to be stored in the database.

Size category:
Size category is used to define the expected space required for the table in the database. It defines the amount of the
records that the memory segment can hold. We can choose a size category from 0 to 4 for your table.

When you create a table, the system reserves initial space (an initial extent) in the database. If more space is required at a
later time due to data entries, additional memory is added depending on the selected size category.

2|Page
Buffer:Ref-36
It is a temporary storage in the application layer. In order to improve the performance, the frequently accessed
records are stored in the buffer to fetch them quickly.
Request Request
Presentation Buffer
Database Layer
Layer
Application Layer
Data/Rec Data/Rec

Buffering options:
 Buffering Not Allowed – buffering not permitted
 Buffering activated – buffering allowed
 Buffering allowed but switched off – buffering allowed but switched off, but can be activated later
according to the customer’s requirement.
Buffering types: Ref-40
 Single record buffering – it loads a single record into the buffer. Makes not much difference in the
performance or the access time. AL12
 Full record buffering – all the records are brought to the buffer. The table which is frequently accessed but
changed rarely are suitable for full buffering.
Transaction table are not suitable for full buffering. This reduces the number of database hit, but occupies
more memory
 Generic record buffering – records which are matching the generic key are loaded into the buffer. Mainly used
in language dependant tables.
We need to mention the no. of key fields for the generic area buffering. And this must be lesser than the no. of
primary keys defined.
MANDT to be included in the generic area buffering.

If we want to stop the buffering of the table, use the option ‘Buffering allowed, but switched off’ and not the option
‘Buffering not allowed’.

3|Page
Log Data Changes:
It defines whether the changes to the data records are to be recorded or not. If this check box is checked, then every
change (like update/delete) to the existing records is recorded in the STANDARD DATABASE LOG TABLE (DBTABLOG)

7. Types of SAP database Tables:

There are 3 types of SAP database tables;
1. Transparent Table – one-to-one relationship between the tables in data dictionary to the table in SAP
database.
2. Pooled Table – one-to-many relationship between ABAP dictionary and the database.
3. Cluster Table - one-to-many relationship between ABAP dictionary and the database.

Transparent Table Pooled Table Cluster Table

Used to store Master data Used to store custom of Used to store system data
system data
1-1 relationship with database N-1 relationship with database N-1 relationship with database
tables tables. tables.
It contains single table Contains larger number of Contains fewer number of
small tables. large tables.
Primary-foreign key Primary-foreign key
relationship is not required. relationship is required.
The database table has same The database table has The database table has
name, same number of fields different name, different different name, different
and fields’ name. number of fields and fields’ number of fields and fields’
name. name.
For each transparent table, Pooled tables are stored with Pooled tables are stored with
there is an associated table in other pooled tables in a single other pooled tables in a single
the database. table called table pool, in the table called table pool, in the
database. database.

Pooled and Cluster tables are done in order to have better memory management. We always create TRANSPARENT
tables only.

4|Page
 8. Structures:-Ref19
Structure is the collection of fields of same or different data type. We cannot keep data in the structure. It can hold data
only at the run time only. For that we need to include the structure into the table.

There are 2 ways of including structure in the table.

1. Include structure – reusable structures. (able to include in S4/HANA)

2. Append structure – Not reusable. Applicable to SAP standard tables or custom tables.

Include structure Append structure

This can be used in Customizing tables This can be used with Standard tables or custom
tables.
It can be reused in multiple tables Not reusable
Give FIELD name as ‘.Include’ and DATA ELEMENT as Click APPEND STRUCTURE button to create structure
Structure name and add to the table.

As many as 9 INCLUDE structures can be allowed inside the table.

There are three types of structures:

 Flat structures:
A flat structure only references elementary types.
 Nested structures:
A nested structure references at least one further structure, but not a table type.
 Deep structures:
A deep structure references at least one table type ( Internal Table).

9. Views:- Ref23.
 View is a virtual table with no data in it.
 It brings the data from the table.
 It is used to view the data from same or one or more table.

Types of views:
1. Database view – view is created by extracting the data from 2 or more tables. Tables must have relationship
between them. It is used for READ ONLY purpose.
Give the table name under Tablesclick on Relationsselect the dependent table from the list
Now the required tables are added to the list along with the JOINT conditions on the right side.
Select the table and click on VIEW FIELDS tab to select the required fields.
When database view is created using single table, we can UPDATE the data in it. (Similar to Projection View)
5|Page
 2. Projection view – this view is created by extracting the data from the same table.
Give the name of the table in BASE TABLE. And specify the TABLE FIELDS.
This is used for READ ONLY and READ and CHANGE (Adding the data) purpose.
3. Maintenance view – to maintain 1 or mote tables. Tables must be related.
If we want to maintain 4 or 5 tables, we normally generate TMG for those tables individually and do the
maintenance separately.
But through Maintenance view, those tables can be taken together to do the maintenance. Meaning, READ,
CHANGE, DELETE and INSERT are possible.
Note: MANDT field has to be included on the Maintenance view. And the relationship between the tables must
be 1 to 1.
4. Help view – it is used in search helps. Tables must be related. Similar to Maintenance view, the relationship
between the tables must be 1 to 1. The contents tab will not be displayed in HELP VIEW. This is done for READ
ONLY purpose.

View Tables Operations Relation

Database view 1, 2 or more tables Read only 1N (Inner Join)
Projection view Single table Read/update
Maintenance view 2 or more tables Read/maintenance 11
Help view 2 or more tables Read only 11 (Outer Join)

10. Search Help: Ref-https://youtu.be/WlImWd9g6zU?feature=shared

This is used to give the list of possible values to the input field. There are 2 types in that;
1. Elementary search help –
 Create the search help in SE11 and you can use it in SE38 using the addition MATCH CODE
OBJECT in PARAMETERS.
 Create a DOMAIN & DATAELEMENT and attach the search help to it. And give this data element
name as TYPE in the PARAMETERS.
2. Collective search help
 It can be created by combining elementary search helps.
 Give the name of the search helps one by one. These search helps are added as tabs in the F4
help in the program.

Hot Key- used to access the different tabs by using the HOT KEY. For example, if the 1st search help has the
HOT KEY value as A and the 2nd as B and so on. Meaning, the HOT KEY is used to prioritize the displaying of
the TAB ORDER.

Typing =B in the PARAMETERS field in the program will show the 2 nd TAB directly.

6|Page
 https://youtu.be/m4YIshj3MRE?feature=shared

11. Indexes:
12. Lock Object:
If the same data is accessed by multiple users at the same time, we need to lock the data in order to maintain
synchronization.
For example, if 2 users trying to access the same record/data, who has got the access first, the lock is done for that
user. The other user will get access only after the first user releases the lock.
SM12 is the TCODE to display the lock entries.
The lock objects should start with ‘E’. So the lock object must be of ‘EZ…..’ or ‘EY…..’
There are 3 types of lock modes;
1. Read lock (Shared lock) – Its default value is ‘S’. Read is possible but not Write by other users.
2. Write lock (Exclusive lock) - Its default value is ‘E’. Read and Write not possible by other users. Write
access will be grant to the user who keeps trying to access the record several times when the object is
on LOCK condition.
3. Enhanced write lock (Exclusive but not cumulative) - Its default value is ‘X’. Read and Write not
possible. It prevents the further access from the same transaction.

When we create a lock object, 2 function modules are created by SAP;

1. ENQUEUEENQUEUE_lockobjectname locking the object

2. DEQUEUE DEQUEUE_lockobjectname release or unlock the object

Lock Other name Default value Read Write

Read lock Shared lock S Yes No
Write lock Exclusive lock E No No
Enhanced write Exclusive but not X No No
lock cumulative

13. Table Type:

14. Type group:
Type group contains the ABAP statements for defining globally visible data types, constants and macros.
TYPE-POOL key word is used in the Type Group.
TYPE-POOLS keyword is used in the program to use the Type Group.

7|Page