Pooled tables m_vmvlb and m_vmvla in ECC6.0

Hi,
We are upgrading system from 4.6C to ECC6.0. But in ECC6.0 pooled tables m_vmvlb and m_vmvla have been deleted. Now these tables have been used in a customize program. So do we need to create the tables with similar structure or there is any OSS note that need to be implemented ??
Please reply as soon as possible. Our deadlines are near.
Regards
Puneet.

just transport the table from the development server to production server or viseversa.
see if you are upgrading the server PRD then Tranport it from the DEV.orelse
if You are upgrading the server DEV then Tranport it from the PRD .
Girish

Similar Messages

Statistical table, pool table, structure, and ordinary table

请教在ABAP引用表时，不同类型的表的区别：
statistical table
pool table
structure,
ordinary table
其它 table (请列出)
谢谢!

>
leopard123456 wrote:
> 请教在ABAP引用表时，不同类型的表的区别：
> statistical table
> pool table
> structure,
> ordinary table
> 其它 table (请列出)
>
> 谢谢!
对上面提到的几个term不是很明白（尤其是statistical table和ordinary table），其中structure应该不是表的类型。
请举例。

Select query taking too much time to fetch data from pool table a005

Dear all,
I am using 2 pool table a005 and a006 in my program. I am using select query to fetch data from these table. i.e. example is mentioned below.
select * from a005 into table t_a005 for all entries in it_itab
                   where vkorg in s_vkorg
                   and     matnr in s_matnr
                   and     aplp   in s_aplp
                   and     kmunh = it_itab-kmunh.
here i can't create index also as tables are pool table...If there is any solutions , than please help me for same..
Thanks ,

it would be helpful to know what other fields are in the internal table you are using for the FOR ALL ENTRIES.
In general, you should code the order of your fields in the select in the same order as they appear in the database. If you do not have the top key field, then the entire database is read. If it's large then it's going to take a lot of time. The more key fields from the beginning of the structure that you can supply at faster the retrieval.
Regards,
Brent

Alternative for Pooled table M_VMVLA in ECC 5 version

Hi,
Pooled table M_VMVLA in version 3.1i does not exist
in ECC 5.Can anyone tell me the alternative for this?
Pool/cluster M_VMVL in 3.1i version
Helpful answers will be rewarded
Thanks
Kiran

Hai Kiran
Check the following Code in program 'RVV50L21'.
the following Code is present in ECC 5.0
select * from shp_idx_gdsi where wadat in i_datum "470
 and vstel in i_vstel
 and route in i_route
 and vbeln eq vttp-vbeln.
simillar code in 3.1 version is
select * from m_vmvla where wadat in i_datum
 and vstel in i_vstel
 and route in i_route
 and vbeln eq vttp-vbeln.
Replacent table for m_vmvla is shp_idx_gdsi
Regards
Sreeni

How can I get data in flat file from Pool table and cluster table ?

Hi,
I am working in one Achiving project. My requirement is to get data into flat file from Cluster table and pool table.
Is there any tool avilable to download data into flat file from pool table and cluster table ?
if table name given in the selection screen then data will be downloaded into flat file.
waiting for quick response.
Best Regards,
Bansidhar

Data cannot be retrived directly form the cluster table
as the Cluster results are stored in Cluster Key say for example PCLkey
and form that Key we need to fetch the data
these clustes are not the part of PNP or PNPCE tables
for ur info kindly check

Inforation on Pool tables and cluster tables required.

I want to know about the pool tables and cluster tables like how to create them and how to look the tables associated with the given tables. Like for the table BSEG we have other tables linked BSID etc. I'm new to this concept please guide me.

Pooled Table:
A pooled table in R/3 has a many-to-one relationship with a table in the database (see Figures 3.1 and 3.2). For one table in the database, there are many tables in the R/3 Data Dictionary. The table in the database has a different name than the tables in the DDIC, it has a different number of fields, and the fields have different names as well. Pooled tables are an SAP proprietary construct.
When you look at a pooled table in R/3, you see a description of a table. However, in the database, it is stored along with other pooled tables in a single table called a table pool. A table pool is a database table with a special structure that enables the data of many R/3 tables to be stored within it. It can only hold pooled tables.
R/3 uses table pools to hold a large number (tens to thousands) of very small tables (about 10 to 100 rows each). Table pools reduce the amount of database resources needed when many small tables have to be open at the same time. SAP uses them for system data. You might create a table pool if you need to create hundreds of small tables that each hold only a few rows of data. To implement these small tables as pooled tables, you first create the definition of a table pool in R/3 to hold them all. When activated, an associated single table (the table pool) will be created in the database. You can then define pooled tables within R/3 and assign them all to your table pool.
Pooled tables are primarily used by SAP to hold customizing data.
Cluster Table:
A cluster table is similar to a pooled table. It has a many-to-one relationship with a table in the database. Many cluster tables are stored in a single table in the database called a table cluster.
A table cluster is similar to a table pool. It holds many tables within it. The tables it holds are all cluster tables.
Like pooled tables, cluster tables are another proprietary SAP construct. They are used to hold data from a few (approximately 2 to 10) very large tables. They would be used when these tables have a part of their primary keys in common, and if the data in these tables are all accessed simultaneously.
Table clusters contain fewer tables than table pools and, unlike table pools, the primary key of each table within the table cluster begins with the same field or fields. 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. Thus, when a row is read from any one of the tables in the cluster, all related rows in all cluster tables are also retrieved, but only a single I/O is needed.
A cluster is advantageous in the case where data is accessed from multiple tables simultaneously and those tables have at least one of their primary key fields in common. Cluster tables reduce the number of database reads and thereby improve performance.
Restrictions on Pooled and Cluster Tables
1. Pooled and cluster tables are usually used only by SAP and not used by customers, probably because of the proprietary format of these tables within the database and because of technical restrictions placed upon their use within ABAP/4 programs. On a pooled or cluster table:
2. Secondary indexes cannot be created.
3. You cannot use the ABAP/4 constructs select distinct or group by.
4.You cannot use native SQL.
5.You cannot specify field names after the order by clause. order by primary key is the only permitted variation.
For creation of pooled /cluster table, have a look at below link.
http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
For creation of table pool /cluster, have a look at below link.
http://help.sap.com/saphelp_erp2004/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
Have a look at below link.
http://www.sap-img.com/abap/the-different-types-of-sap-tables.htm
Best Regards,
Vibha
*Please mark all the helpful answers

Cluster and pooled tables

when we will use cluster table , pooled table and transparent tables...

FOr Tables
http://www.erpgenie.com/abap/tables.htm
For Tables
Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
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.
Table Pools
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
Table Clusters
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
Working with Tables
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

Cluster and pool tables

I make a join with a pool table the compiler writes
Für Pool-Tabellen, Cluster-Tabellen und Projektions-Views ist JOIN
for pool-Tables, Cluster-Tables and Projections-View is no JOIN allowed.
What can I do to read the data from the table a005 in join.
thanks.
Waseem

>
Ahmad Waseem wrote:
> What can I do to read the data from the table a005 in join.
> thanks.
> Waseem
Hello Waseem,
Ans is DONOT use JOIN. You have to use FOR ALL ENTRIES.
You can JOIN only transperant tables. This is where JOIN scores over FOR ALL ENTRIES
BR,
Suhas

Reg : Cluster and pool tables

Hi All,
I think this has been asked previously.
Have a doubt, i think this area is kind of opaque.
This is the scenario, we have standard business suite systems now i am going to get the data into hana using SLT how do i handle cluster and pool tables. Do i bring in the declustered data?
I am aware that we can get the data from these tables into BW on hana, not sure if that is correct.
What are the best practice approach for these table classes.
How have you implemented these kind of scenarios.
Message was edited by: Tom Flanagan

Hello,
SLT Supports replication of non-Unicode to Unicode systems.
Includes cluster / pool tables, etc. (writes into transparent tables in SAP HANA system).
Regards,
Subbu

Can we join the transparent and pooled tables?

hi friends,
i have a doubt that is when we want to get the data from transparent and pooled tables it is not possible to join the tables.
so should we go with nested select statements or is there any way to get the data? with better performance
if i go with nested select statements it takes a lot time thats y i need a better way
for example i want the data from BKPF and BSEG based on BELNR
please send me how can we get it
regards
jagadish

hi rob
thanks for response
see the below code once
SELECT * FROM bkpf
 WHERE gjahr = p_gjahr
 AND ( monat BETWEEN lv_1st_mth AND gw_prev_monat ).
*- Selection with cost center
 IF gw_kostl NE SPACE.
 s_kostl = s_kostl+3(10).
 SELECT * FROM bseg
 WHERE bukrs = bkpf-bukrs
 AND belnr = bkpf-belnr
 AND gjahr = bkpf-gjahr
 AND kokrs = p_kokrs
 AND kostl IN s_kostl
 AND buzei = '001'
 AND lstar <> ' '.
 MOVE bseg-lstar TO itab2-lstar .
 MOVE bkpf-bukrs TO itab2-bukrs.
 MOVE bkpf-belnr TO itab2-belnr.
 MOVE bkpf-gjahr TO itab2-gjahr.
 MOVE bkpf-monat TO itab2-monat.
 MOVE bkpf-budat TO itab2-budat.
 MOVE bseg-kokrs TO itab2-kokrs.
 MOVE bseg-buzei TO itab2-buzei.
 MOVE bseg-wrbtr TO itab2-wrbtr.
*Changed----
 IF bseg-shkzg = 'H'.
 lv_wrbtrcd = 0 - bseg-wrbtr.
 itab2-wrbtr = lv_wrbtrcd.
 ELSEIF bseg-shkzg = 'S'.
 MOVE bseg-wrbtr TO itab2-wrbtr.
 ENDIF.
 MOVE bseg-fdwbt TO itab2-fdwbt.
 MOVE bseg-sgtxt TO itab2-sgtxt.
 MOVE bseg-kostl TO itab2-kostl.
 APPEND itab2.
 ENDSELECT.
 ELSE.
 s_kostl = p_estat+0(4).
 SELECT * FROM bseg
 WHERE bukrs = bkpf-bukrs
 AND belnr = bkpf-belnr
 AND gjahr = bkpf-gjahr
 AND kokrs = p_kokrs
 AND kostl IN s_kostl
 AND buzei = '001'
 AND lstar <> ' '.
 IF bseg-kostl+0(4) = s_kostl.
 MOVE bseg-lstar TO itab2-lstar.
 MOVE bkpf-bukrs TO itab2-bukrs.
 MOVE bkpf-belnr TO itab2-belnr.
 MOVE bkpf-gjahr TO itab2-gjahr.
 MOVE bkpf-monat TO itab2-monat.
 MOVE bkpf-budat TO itab2-budat.
 MOVE bseg-kokrs TO itab2-kokrs.
 MOVE bseg-buzei TO itab2-buzei.
 MOVE bseg-wrbtr TO itab2-wrbtr.
*Changed----
 IF bseg-shkzg = 'H'.
 lv_wrbtrcd = 0 - bseg-wrbtr.
 itab2-wrbtr = lv_wrbtrcd.
 ELSEIF bseg-shkzg = 'S'.
 MOVE bseg-wrbtr TO itab2-wrbtr.
 ENDIF.
 MOVE bseg-fdwbt TO itab2-fdwbt.
 MOVE bseg-sgtxt TO itab2-sgtxt.
 MOVE bseg-kostl TO itab2-kostl.
 APPEND itab2.
 ENDIF.
 ENDSELECT.
 ENDIF.
 ENDSELECT.
regards
jagadish

Joining transparent and pool tables.

Friends,
I Had to join 7 tables in which 6 are the transparent tables 1 is the pool table. I had declared 3 internal tables one for data from 6 transparent table(JOIN) second for data from pool table third for combining and saving data from both tables into single table. I had written following cide. But its giving errors. I am unable to locate where i made the mistake.
Also is it possible to join two INTERNAL tables?
TABLES: EKKO,EKPO,MAKT,LFA1,MSEG,EKET,KONV.
TYPES: BEGIN OF TAB1,
BUKRS TYPE EKKO-BUKRS,
EKORG TYPE EKKO-EKORG,
BSART TYPE EKKO-BSART,
LIFNR TYPE EKKO-LIFNR,
KNUMV TYPE EKKO-KNUMV,
MATNR TYPE EKPO-MATNR,
MATKL TYPE EKPO-MATKL,
WERKS TYPE EKPO-WERKS,
MENGE TYPE EKPO-MENGE,
KO_PRCTR TYPE EKPO-KO_PRCTR,
EINDT TYPE EKET-EINDT,
MAKTX TYPE MAKT-MAKTX,
NAME1 TYPE LFA1-NAME1,
end of TAB1.
DATA: ITAB1 type table of TAB1,
        WA1 like line of ITAB1.
TYPES:begin of TAB2,
    KNUMV TYPE KONV-KNUMV,
KSCHL TYPE KONV-KSCHL,
KBETR TYPE KONV-KBETR,
END OF TAB2.
DATA:ITAB2 type table of TAB2,
        WA2 like line of ITAB2.
TYPES : BEGIN OF TAB4,
BUKRS TYPE EKKO-BUKRS,
EKORG TYPE EKKO-EKORG,
BSART TYPE EKKO-BSART,
LIFNR TYPE EKKO-LIFNR,
MATNR TYPE EKPO-MATNR,
MATKL TYPE EKPO-MATKL,
WERKS TYPE EKPO-WERKS,
MENGE TYPE EKPO-MENGE,
KO_PRCTR TYPE EKPO-KO_PRCTR,
EINDT TYPE EKET-EINDT,
MAKTX TYPE MAKT-MAKTX,
NAME1 TYPE LFA1-NAME1,
KSCHL TYPE KONV-KSCHL,
KBETR TYPE KONV-KBETR,
END OF TAB4.
DATA: ITAB4 type table of TAB4,
      WA4 LIKE ITAB4.
*select a1-bukrs a1 ekorg a1-bsart a1-lifnr b1-matnr b1-matkl b1-werks b1-menge b1-ko_prctr
c1-eindt d1-maktx e1-name1 f1-menge into corresponding fields of table ITAB up to 50 rows
from(((((( ekko as a1 INNER JOIN ekpo as b1 on a1ebeln = b1ebeln) inner join eket as c1 on
a1ebeln = c1ebeln and b1ebelp = c1ebelp) inner join makt as d1 on b1matnr = d1matnr) inner join LFA1 as e1
on a1lifnr = e1lifnr) inner join mseg as f1 on a1lifnr = f1lifnr and a1ebeln = f1ebeln and b1matnr = f1matnr
and b1werks = f1werks and b1ebelp = f1ebelp) inner join konv as g1 on a1knumv = g1knumv) .
select a1bukrs a1ekorg a1bsart a1lifnr b1matnr b1matkl b1werks b1menge b1~ko_prctr
c1eindt d1maktx e1name1 f1menge into corresponding fields of table ITAB1
from ((((( ekko as a1 INNER JOIN ekpo as b1 on a1ebeln = b1ebeln) inner join eket as c1 on
a1ebeln = c1ebeln and b1ebelp = c1ebelp) inner join makt as d1 on b1matnr = d1matnr)
inner join LFA1 as e1 on a1lifnr = e1lifnr) inner join mseg as f1 on a1lifnr = f1lifnr and a1ebeln = f1ebeln and b1matnr = f1matnr
and b1werks = f1werks and b1ebelp = f1ebelp).
*select * from ITAB1 into WA1.
select KSCHL KBETR KNUMV into TABLE ITAB2
from KONV for all entries in ITAB1 where ITAB1-KNUMV = KNUMV~KNUMV .
select abukrs aekorg absart alifnr amatnr amatkl awerks amenge ako_prctr aeindt
    amaktx aname1 a~menge
    bkschl bkbetr into corresponding fields of table ITAB4
    from ( ITAB1 as a INNER JOIN ITAB2 as b on aKNUMV = bKNUMV ).
LOOP AT ITAB4 INTO WA_ITAB.
WRITE : / WA_ITAB-BUKRS,WA_ITAB-MATNR,WA_ITAB-EINDT,WA_ITAB-MAKTX ,WA_ITAB-NAME1 ,WA_ITAB-KSCHL,
WA_ITAB-KBETR,WA_ITAB-MENGE.
ENDLOOP.

You have too many parentheses in your JOIN condiiton. Your FAE condition is incorrect. And no, you cannot do a JOIN on internal tables.
Please do an F1 on SELECT.
Rob

Pooled table and clustred table

pooled table and clustred table

Hi
Pooled Tables, Table Pools, Cluster Tables, and Table Clusters
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.
Table Pools
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
Table Clusters
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
Working with Tables
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
Standard table:
The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
You should usually access a standard table with index operations.
Sorted table:
The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
Hash table:
The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
Index table:
The table can be a standard table or a sorted table.
Index access is allowed to such an index table. Index tables can be used to define the type of generic parameters of a FORM (subroutine) or a function module.
Just have a look at these links:
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/74/83015785d811d295a800a0c929b3c3/frameset.htm
For creating cluster tables first u have to create table pool ...
create a table and specify the fields and other tecnical settings and
then Goto EXTRAS --> Change Table Category and selct the Pooled table and activate it...
Then Create another table And specify the required fileds and also the settings and then
Goto EXTRAS --> Change Table Category and selct the Cluaster table and in Delivery and
Maintainence Properties mention the Pooled table that u created and activate it...
Regards
Sreeni

Diff Bt Cluser and pool tables?

HI,
Wats the diff between the cluster and pool tables?
Regards,
KK

Hi Kishore,
Pooled and Cluster Tables
Table pools (pools) and table clusters (clusters) are special table types in the ABAP Dictionary. The data from several different tables can be stored together in a table pool or table cluster. Tables assigned to a table pool or table cluster are referred to as pooled tables or cluster tables.
A table pool or table cluster should be used exclusively for storing internal control information (screen sequences, program parameters, temporary data, continuous texts such as documentation). Data of commercial relevance is usually stored in transparent tables.
Table Pools
A table in the database in which all records from the pooled tables assigned to the table pool are stored corresponds to a table pool.
The definition of a pool consists essentially of two key fields (Tabname and Varkey) and a long argument field (Vardata).
Regards,
VKreddy

Can u create cluster and pooled tables in real time

hi
can u create cluster and pooled tables in real time.can u send data base tables name of above one.

Hai Anil
For creating cluster tables first u have to create table pool ...
create a table and specify the fields and other tecnical settings and
then Goto EXTRAS --> Change Table Category and selct the Pooled table and activate it...
Then Create another table And specify the required fileds and also the settings and then
Goto EXTRAS --> Change Table Category and selct the Cluaster table and in Delivery and
Maintainence Properties mention the Pooled table that u created and activate it...
Regards
Sreeni

Doubt on cluster and pooled tables

Dear experts
i kno how to create a cluster and pooled table ..
but in reality how a requirement comes to create a cluster or pooled table....
plz kindly explain in detailed
thanks in advace
somesh

Hello,
Hope the below link gives you an insight into how the pooled/cluster tables behave.
http://help.sap.com/saphelp_46c/helpdata/EN/81/415d363640933fe10000009b38f839/frameset.htm
For better understanding on how and when to create pooled/cluster table, refer to the below examples.
All Condition tables i.e., Annn tables (pricing/discounts etc.,) belong to the table Pool KAPOL (Condition Pool) as the underlying concept is same across different condition tables, but, they have different Key (primary) fields.
Accounting Document Segment (Line Item records) BSEG is a cluster table that belongs to the table cluster RFBLG. Also, other tables such as BSEC, BSED, BSES, BSET also come under the same table cluster as all of them possess the common Key i.e., BUKRS/BELNR/GJAHR.
Please contact for further details. <removed_by_moderator>
With Regards
Vijay Gajavalli
Edited by: Julius Bussche on Sep 4, 2008 8:40 AM

Pooled tables m_vmvlb and m_vmvla in ECC6.0

Similar Messages

Maybe you are looking for