Explore topic-wise InterviewSolutions in .

A cluster table is similar to a Pooled table. It has a many to one relationship with a table in an underlying database. Many cluster TABLES are stored in a single table in an underlying database called a table cluster.

So table cluster is similar to pooled table pool. A table cluster holds only cluster table within it.

Table clusters store data from several cluster tables based on the PRIMARY KEY fields that they have in common. 

Rows from the cluster tables are combined into a single row in the table cluster. The rows are combined based on the part of the primary key they have in common.

The biggest advantage of cluster table and pooled table is they reduce the number of database reads and thereby improve PERFORMANCE.

Tables CDPOS and CDHDR are Cluster tables in SAP ABAP Dictionary and CDCLS is the table cluster that exist in the underlying database. CDCLS table contains or hold data of both tables CDPOS and CDHDR in the underlying database.

A cluster table is similar to a Pooled table. It has a many to one relationship with a table in an underlying database. Many cluster tables are stored in a single table in an underlying database called a table cluster.

So table cluster is similar to pooled table pool. A table cluster holds only cluster table within it.

Table clusters store data from several cluster tables based on the primary key fields that they have in common. 

Rows from the cluster tables are combined into a single row in the table cluster. The rows are combined based on the part of the primary key they have in common.

The biggest advantage of cluster table and pooled table is they reduce the number of database reads and thereby improve performance.

Tables CDPOS and CDHDR are Cluster tables in SAP ABAP Dictionary and CDCLS is the table cluster that exist in the underlying database. CDCLS table contains or hold data of both tables CDPOS and CDHDR in the underlying database.

Tables in Data dictionary which has many to one relationship with an underlying database table is called Pooled table. In simple words, Pooled tables appear as many tables in ABAP dictionary, but the thing is they are stored as a single table in the underlying database.

In ABAP Dictionary, you can see each and every pooled table is assigned to a Table POOL.

As it is understood that for many pooled tables in ABAP dictionary, there is a single table called as Table Pool in an underlying database. A Table Pool is an underlying database table with a special structure that enables the data of many ABAP Dictionary tables to be stored within it.

Tables M_MTVMA, M_MTVMB, M_MTVMC, M_MTVMD and M_MTVME can be SEEN in ABAP Dictionary. These all mentioned tables are Pooled Tables. All these tables have been assigned to one Table Pool i.e. M_MTVM, which will be present in the underlying database and storing data of all the five mentioned tables of ABAP Dictionary.

Pooled tables are basically used by SAP to store temporary data or customizing data. Pooled tables can also be used to store control data (such as screen sequences or program parameters).

Generally as a developer, we will NEVER CREATE a Pooled table or Table Pool. It does not mean that we cannot create them. SAP has given the OPTION to create Pooled tables through SE80 transaction and Table pool via ABAP Dictionary.

Tables in Data dictionary which has many to one relationship with an underlying database table is called Pooled table. In simple words, Pooled tables appear as many tables in ABAP dictionary, but the thing is they are stored as a single table in the underlying database.

In ABAP Dictionary, you can see each and every pooled table is assigned to a Table Pool.

As it is understood that for many pooled tables in ABAP dictionary, there is a single table called as Table Pool in an underlying database. A Table Pool is an underlying database table with a special structure that enables the data of many ABAP Dictionary tables to be stored within it.

Tables M_MTVMA, M_MTVMB, M_MTVMC, M_MTVMD and M_MTVME can be seen in ABAP Dictionary. These all mentioned tables are Pooled Tables. All these tables have been assigned to one Table Pool i.e. M_MTVM, which will be present in the underlying database and storing data of all the five mentioned tables of ABAP Dictionary.

Pooled tables are basically used by SAP to store temporary data or customizing data. Pooled tables can also be used to store control data (such as screen sequences or program parameters).

Generally as a developer, we will never create a Pooled table or Table Pool. It does not mean that we cannot create them. SAP has given the option to create Pooled tables through SE80 transaction and Table pool via ABAP Dictionary.

Whenever a table is created and defined through ABAP Dictionary, then it is CALLED a transparent table. When the table is ACTIVATED in ABAP Dictionary, a table AUTOMATICALLY gets created in the underlying database with the same name as was defined in ABAP Dictionary. 

So generally we say, transparent tables has one to one relationship with underlying database which means there will be only one physical table on the database for each transparent table created and defined through ABAP Dictionary. 

The names of the table and fields in underlying database will CORRESPOND or have the same names as the logical table definition in the ABAP Dictionary.

Transparent tables can be used to store APPLICATION data which include master data as well as transaction data. Transparent tables are probably the only type of table that you will ever create as a developer.

Whenever a table is created and defined through ABAP Dictionary, then it is called a transparent table. When the table is activated in ABAP Dictionary, a table automatically gets created in the underlying database with the same name as was defined in ABAP Dictionary. 

So generally we say, transparent tables has one to one relationship with underlying database which means there will be only one physical table on the database for each transparent table created and defined through ABAP Dictionary. 

The names of the table and fields in underlying database will correspond or have the same names as the logical table definition in the ABAP Dictionary.

Transparent tables can be used to store application data which include master data as well as transaction data. Transparent tables are probably the only type of table that you will ever create as a developer.

There are 3 TYPES of tables in SAP DICTIONARY (DDIC). They are:

• Transparent Table
• Pooled Table
• CLUSTER Table

There are 3 types of tables in SAP Dictionary (DDIC). They are:

The basic objects of the ABAP Dictionary are TABLES, data ELEMENTS and domains. Objects that can be created in the ABAP Dictionary or via SE11 transaction are:

• Tables
• Data Elements
• STRUCTURES
• Table Types
• Type Groups
• Domains
• Views
• SEARCH Helps
• Lock Objects

The basic objects of the ABAP Dictionary are tables, data elements and domains. Objects that can be created in the ABAP Dictionary or via SE11 transaction are:

A data dictionary is a centralized storage location for information about the data that is STORED in a database. It is basically an interface which HELPS us to understand like what kind of data is stored in database, what are the properties and attributes of the data and the RELATION between different data objects available in database.

SAP’s data dictionary is called the ABAP Dictionary. ABAP Dictionary is accessed via transaction CODE SE11.

A data dictionary is a centralized storage location for information about the data that is stored in a database. It is basically an interface which helps us to understand like what kind of data is stored in database, what are the properties and attributes of the data and the relation between different data objects available in database.

SAP’s data dictionary is called the ABAP Dictionary. ABAP Dictionary is accessed via transaction code SE11.

There are two types of SQL being used in SAP ABAP programming language. They are

• Native SQL
• Open SQL

Open SQL allows to ACCESS the database tables declared in the ABAP dictionary REGARDLESS of the database platform that the SAP R/3 system is using.

Native SQL allows to use database-specific SQL statements in a SAP ABAP program. This means that one can use database tables that are not administered by ABAP dictionary, and therefore integrate data that is not PART of the SAP R/3 system.

Open SQL is not confined to any particular type of database while a Native SQL is confined to a particular type. 

ABAP PROGRAMS that uses only Open SQL statements will work in any R/3 system, regardless of the database system in use. Open SQL statements can only work with database tables that have been created in the ABAP dictionary.

There are two types of SQL being used in SAP ABAP programming language. They are

Open SQL allows to access the database tables declared in the ABAP dictionary regardless of the database platform that the SAP R/3 system is using.

Native SQL allows to use database-specific SQL statements in a SAP ABAP program. This means that one can use database tables that are not administered by ABAP dictionary, and therefore integrate data that is not part of the SAP R/3 system.

Open SQL is not confined to any particular type of database while a Native SQL is confined to a particular type. 

ABAP programs that uses only Open SQL statements will work in any R/3 system, regardless of the database system in use. Open SQL statements can only work with database tables that have been created in the ABAP dictionary.