Data Dictionary

[Former Member]

Hi ,

I know about Pooled tables & cluster tables .

but i need some tables related to pooled tables & cluster tables.

Regs ,

Murthy

[Former Member]

See BSEG & KONV table they are cluster tables

[Former Member]

table DD02L-> Give TABCLASS as POOL or CLUSTER you will get a list of tables

[Former Member]

Hi Kalpana,

How are you. you remembered me. I am Aman. My mail id is aman.sharma81@gmail.com

For Cluster, Transparent, and Pooled tables, you can go to DD02L and giove tabclass as Pool, Transp, and clust and get the tablenames from TABNAME field.

Regards,

Aman.

[Former Member]

Hi Murthy,

check this

Pooled Tables

A001

A004

A005

A006

A007

A009

A010

A012

A015

A016

A017

A018

A019

A021

A022

Cluster Tables

AUAA

AUAB

AUAO

AUAS

AUAT

AUAV

AUAW

AUAY

BSEC

BSED

BSEG

BSES

BSET

CDPOS

BSEG is a cluster table consisting data from tables

BSID,BSAD,BSIS,BSAS,BSIK,BSAK which all are transperent tables.

[Former Member]

Hi Narayana,

FOr Tables

<b>Pooled Tables, Table Pools, Cluster Tables, and Table Clusters</b>

These types of tables are not transparent in the sense that they are not legible or manageable directly using the underlying database system tools. They are managed from within the R/3 environment from the ABAP dictionary and also at runtime when they are loaded into application memory.Pool and cluster tables are logical tables. Physically, these logical tables are arranged as records of transparent tables. The pool and cluster tables are grouped together in other tables, which are of the transparent type. The tables that group together pool tables are known as table pools, or just pools; similarly, table clusters, or just

clusters, are the tables which group cluster tables.Not all operations that can be performed over transparent tables can be executed over pool or cluster tables.

For instance, you can manage these tables using Open SQL calls from ABAP, but not Native SQL.These tables are meant to be buffered and loaded in memory, because they are commonly used for storing internal control information and other types of data with no external (business) relevance. SAP recommends that tables of pool or cluster type be used exclusively for control information such as

program parameters, documentation, and so on. Transaction and application data should be stored in transparent tables.

<b>Table Pools</b>

From the point of view of the underlying DBMS as from the point of view of the ABAP dictionary, a table pool is a transparent table containing a group of pooled tables which, when created, were assigned to this table pool.

Field Type Description

TABNAME CHAR(10) Table name

VARKEY CHAR(n) Maximum key length n =< 110

DATALN INT2(5) Length of the VARDATA record returned

VARDATA RAW(m) Maximum length of the data varies according to DBMS

<b>Table Clusters</b>

Similarly to pooled tables, cluster tables are logical tables which, when created, are assigned to a table cluster. Therefore, a table cluster, or just cluster, groups together several tables of type clusters.Several 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.A cluster contains a transparent cluster key which must be located at the start of the key of all logical cluster tables to be included in the cluster. As well, a cluster contains a long field (VARDATA), which contains the

data of the cluster tables for this key. If the data does not fit into a field, continuation records are created.

Field Type Description

CLKEY1 CHAR(*) First key fields

CLKEY2 CHAR(*) Second key field

CLKEYN CHAR(*) nth key field

PAGENO INT2(5) Number of the next page

TIMESTMP CHAR(14) Time stamp

PAGELG INT2(5) Length of the VARDATA record returned

VARDATA RAW(*) Maximum length of the data section; varies according to database system

<b>Working with Tables</b>

The dictionary includes many functions for working with tables. There are five basic operations you can perform on tables: display, create, delete, modify, copy. Please do not confuse displaying a table with displaying the table entries (table contents). In order to display a table, it must previously exist; otherwise the system will display an error message in the status bar. For the following example, the table TABNA is used. To display this table, from the main dictionary screen, enter the table name in the Object name

input field with the radio button selected next to Tables. Then, click on the Display button at the bottom of the screen, or press the F7 function key, or, alternatively,

select Dictionary object Display from the menu.

In this screen, you can see table information such as

¨ Table type, shown next to the name of the object. In the example, it is a transparent table.

¨ Short text description.

¨ Name of the user who made the last change, and the date of the change.

¨ Master language.

¨ Table status. On the screen, you can see this table is saved and active.

¨ Development class. For information on development classes, refer to Chap. 6.

Delivery class, which sets the maintenance group for the table. It controls how tables will behave during client copy procedures, upgrades, and so forth.¨

Tab. Maint. Allowed flag, which indicates whether you can generate a screen for maintaining table entries.

¨Then, on the lower part of the screen, you can see the table fields with all associated characteristics such as:

¨ Field name.

¨ Key indicator. When set, this field is the primary key, or part of it.

¨ Data element.

¨ Basic data type.

¨ Length.

¨ Check table.

¨ Short text, describing the field.

Additional information about the table can be displayed by selecting the corresponding functions from the menu or directly from the application toolbar, such as keys, indexes, or technical settings.

Regards,

Balaji

**Rewards for helpful answers