Physical table list against Cluster Table CDPOS and PCDPOS

Hello experts,
For function customized requirement, we need to know the physical table
list against Cluster Table CDPOS and PCDPOS and EDID4, just like
Cluster Table BSEG contain with six physical tables
BSAD/BSID/BSAS/BSIS/BSAK/BSIK. Also we want to know if there is any
general way to find out the physical table list for any cluster table.
My question is:
1. How can I find all the transparent table for Cluster Table CDPOS?
just like Cluster Table BSEG has transparent tables of
BSAD/BSID/BSAS/BSIS/BSAK/BSIK.
2. How can I find all the transparent table for Cluster Table PCDPOS?
3. How can I find all the transparent table for Cluster Table EDID4?
4. Additionally,I want to know if there is any
general way to find out all the transparent tables for an specific
cluster table.
Many thanks.

Hello,
simply look in transaction SE11.
Example:
1. SE11 -> Table CDPOS - Display. On Tab 'Delivery and Maintenance' you'll find Pool/Cluster 'CDCLS'.
2. SE11 -> Table CDCLS -> Display. On next screen position on CDCLS-> Where-used-list -> Tables -> you'll find tables CDPOS and PCDPOS.
Same thing with EDID4 -> EDI40 ...
Regards Wolfgang

Similar Messages

Tables related to cluster tables..

Dear all,
i know the concept of cluster tables, how data is stored in cluster tables and related to small tables.
i want to know what are all the tables to related to a cluster table.
Say for BSEG is a cluster table, and BSIK, BSAK and other tables are related to BSEG.
how can we know what other tables are related to BSEG?
Thanks in advance.

BSIK and BSAK are index tables for BSEG, but are transparent tables and not part of the cluster.
To see what other tables are part of the cluster:
Go to SE11 and press the "delivery and maintenance" tab. You will see that cluster is RFBLG. double click on it. It will display RFBLG.
Take the menu path
Utilities -> where used list
then select tables.
You'll see the tables in the cluster.
Rob

Access ODBC link table list ONLY one table

Hi all,
I try to link Oracle tables from Microsoft Access via Link Table. The return list show ONLY one table, which by right it should show ALL tables in my Database.
What is the problem here? Anyone encounter this same problem before.
My database is very large, over 10,000 tables. Can it be because of resources issues?
Pls help

Are they all real tables are or some of them perhspa VIEWS, SYNONYMS or the like? The default list is for just tables. I have seen cases where a really large list would make Access puke, but this generally results in getting nothing listed.

How can i join pool table to a cluster tables ?

Hi Experts,
is it possible to join bseg to bkpf table if possible then please do help me with the required query for the same purpose.
Thanks
Aditya Rajput.

Hi Aditya,
There is nice blog on create joins for BSEG and BKPF.
Refer to the link below
Query Report Tips Part 3 - Efficient Data selection with BSEG Joining BKPF
Hope this helps.
Regards,
Deepak Kori

Writing select from multiple tables, listed in another table

Hi there.
I need to write a select which is a little complex for me. Here is conditions,
All tables have the same column names, but i want to use staff_no.
All table names written in MASTER_TB table (15 table name).
is there a shortcut to write a sql like i am joining them?
(NO select * from staff t1, emp t2 ,company t3 .....etc....)
THANKS

you will have to write each tables just the same as writing a simple query. this is the part where you will have to write each tables in your FROM clause and any other column in the SELECT statement plus those condition expressions in your WHERE clause as to what you might be needing to arrive in the results that you needed.

How to append table T184 , Pool / Cluster table

Hi,
Has any one appended Pool table like T184 to add more z fields.
thxs,
Pavan

Hello,
I think that table is not able to append new structures, if you check on tcode se11 the append structures button isnt activated. What u r looking for seems to not be possible
bye
gabriel P

Does Pool & Cluster tables has the same structure in both Dictionary and Db

------------ Exists with the same structure both in dictionary as well as in database exactly with the same data and fields
a. Pool Table
b. Cluster Table
c. Transparent Table
d. All the above
To my knowledge, I know transparent table has the same structure in both Dictionary and database.
Can anyone tel me the answer for the above question.. whether it is
c. Transparent table
or
d. All the above

Transparent Table:
A physical table definition in the database for the table definition which is stored in the ABAP Dictionary for transparent tables when the
table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.
A transparent table in the dictionary has one to one relationship with a table in the database.
For each transparent table in the data dictionary there is one associated table in the database.The database table has the same name, the same number of fields and fields have same names as the transparent table definition. Transparent tables are used to hold application data. Application data is master data or transaction data used by an application.
e.g. master data - table of customers
Transaction data - order placed by the customers.
Pooled tables:
Pooled tables can be used to store control data (e.g. screen sequences,program parameters or temporary data). Several 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 pooledtables are stored.
Pooled table in R/3 has a many to one relationship with a table in the database. For one table in the database there are many tables in the R/3 data dictionary.R/3 uses pooled tables to hold large number of very small tables. You might create a table pool if yoou need to create hundreds of small tables that each hold only a few rows of data.
Cluster tables :
Cluster tables contain continuous text, for example, documentation.Several cluster tables can be combined to form a table cluster. Severallogical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or
object-by-object access. In order to combine tables in clusters, atleast parts of the keys must agree. Several cluster tables are stored in
one corresponding table on the database.
A cluster table is similar to pool table . It has many to one relationship with the table in the database.
They are used to hold the data from a few(approximatelly 2 to 10) very large tables. They would be used when these tables have a part of their primary keys in common and if data in these tables are all accessed simultaneously.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 table reduce number of database reads and thereby improves performance.

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

Can we create secondary index for a cluster table

hi
can we create secondary index for a cluster table

Jyothsna,
There seems to be some kind of misunderstanding here. You cannot create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).
Hope this clarifies things,
Mark

Tables in Cluster table

Hi,
Please can any one tell me that how can we find transperent tables in the Cluster table.
Eg: KONV is cluster of which all tables.
Thanks
Sameer

Hi Vikash,
Follow the steps.
<li>SE11->KONV->Display
<li>Click on Delivery and Maintenance tab
<li>Double click on Table Cluster KOCLU.
<li> Place cursor on KOCLU and use Where-Used List. You will find list of Cluster tables attached to Table Cluster. In your case only one entry is found.
<li>You can follow same procedure for BSEG,
Small correction:Logically related cluster tables can be stored together in Table cluster(Not Cluster pool).
Regards,
Venkat.O

How many SECONDARY INDEXES are created for CLUSTER TABLES?

how many SECONDARY INDEXES are created for CLUSTER TABLES?
please explain.

There seems to be some kind of misunderstanding here. You cannot create a secondary index on a cluster table. A cluster table does not exist as a separate physical table in the database; it is part of a "physical cluster". In the case of BSEG for instance, the physical cluster is RFBLG. The only fields of the cluster table that also exist as fields of the physical cluster are the leading fields of the primary key. Taking again BSEG as the example, the primary key includes the fields MANDT, BUKRS, BELNR, GJAHR, BUZEI. If you look at the structure of the RFBLG table, you will see that it has primary key fields MANDT, BUKRS, BELNR, GJAHR, PAGENO. The first four fields are those that all cluster tables inside BSEG have in common. The fifth field, PAGENO, is a "technical" field giving the sequence number of the current record in the series of cluster records sharing the same primary key.
All the "functional" fields of the cluster table (for BSEG this is field BUZEI and everything beyond that) exist only inside a raw binary object. The database does not know about these fields, it only sees the raw object (the field VARDATA of the physical cluster). Since the field does not exist in the database, it is impossible to create a secondary index on it. If you try to create a secondary index on a cluster table in transaction SE11, you will therefore rightly get the error "Index maintenance only possible for transparent tables".
Theoretically you could get around this by converting the cluster table to a transparent table. You can do this in the SAP dictionary. However, in practice this is almost never a good solution. The table becomes much larger (clusters are compressed) and you lose the advantage that related records are stored close to each other (the main reason for having cluster tables in the first place). Apart from the performance and disk space hit, converting a big cluster table like BSEG to transparent would take extremely long.
In cases where "indexing" of fields of a cluster table is worthwhile, SAP has constructed "indexing tables" around the cluster. For example, around BSEG there are transparent tables like BSIS, BSAS, etc. Other clusters normally do not have this, but that simply means there is no reason for having it. I have worked with the SAP dictionary for over 12 years and I have never met a single case where it was necessary to convert a cluster to transparent.
If you try to select on specific values of a non-transparent field in a cluster without also specifying selections for the primary key, then the database will have to do a serial read of the whole physical cluster (and the ABAP DB interface will have to decompress every single record to extract the fields). The performance of that is monstrous -- maybe that was the reason of your question. However, the solution then is (in the case of BSEG) to query via one of the index tables (where you are free to create secondary indexes since those tables are transparent).

Cluster table RFBLG

I have come accross cluster table RFBLG. How it is used. I can see that it is a cluster of multiple tables i.e. BSEG. and how does it improve the performance of the ABAP report.
Thanks in advance.
Faiq

hi
good
The famous BSEG table is a cluster table.
It is as was correctly stated part of the Accounting Document Segment. It is part of the Pool cluster RFBLG and lives in the package: FBAS (Financial accounting 'Basis').
You can't read a cluster table exactly the way you read a database (old speak, transparent table).
You can use a program to read called RFPPWF05
Note 435694: Display BSEG item by calling FB09D (modified FB09)
Other possiblity: Other possibility: CALL DIALOG 'RF_ZEILEN_ANZEIGE', but since this is a dialog I don't think this would work.
In any event go to FBAS Package (development class) to see your business objects, class library and functions.
thanks
mrutyun

Cluster tables

tell me some cluster tables

Example for Cluster tables.
BSEG - Accounting Document Segment
PCDCLS - Cluster structure for change documents
RFBLG - Cluster for accounting document
Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to strore control data. They can also be used to store temporary data or texts, such as documentation.
A cluster table have many to 1 relationship. Cluster table are much more complex and you cannot display the data of a cluster table directly. Cluster table have be read and display via your ABAP program.
Table cluster is a special table type in ABAP dictionary. The data from different tables can be stored in a table cluster.
A table cluster should be used exclusively for storing internal control information (screen sequences, program parameters, temporary data, continuous text such as documentation).
Check this link for creating cluster tables.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f0b7446011d189700000e8322d00/content.htm

By passing Cluster Table BSEG ?

What is the science of using Cluster tables? I mean why are cluster tables used for ? + HOW CAN I BY PASS CLUSTER TABLER to get the data quickly ??

Hi,
The famous BSEG table is a cluster table.
It is as was correctly stated part of the Accounting Document Segment. It is part of the Pool cluster RFBLG and lives in the package: FBAS (Financial accounting 'Basis').
You can't read a cluster table exactly the way you read a database (old speak, transparent table).
You can use a program to read called RFPPWF05
Note 435694: Display BSEG item by calling FB09D (modified FB09)
Other possiblity: Other possibility: CALL DIALOG 'RF_ZEILEN_ANZEIGE', but since this is a dialog I don't think this would work.
In any event go to FBAS Package (development class) to see your business objects, class library and functions.
you must use keyfields bukrs , belnr, gjahr
(so 1st select table bkpf) to select bseg.
or use secondary index tables:
bsas, bsis, bsik, bsak, bsid, bsad
Cluster Table : Cluster tables are logical tables that must be assigned to a table cluster when they are defined. Cluster tables can be used to strore control data. They can also be used to store temporary data or texts, such as documentation.
A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.
One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in Abap are limited as well.
But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool.
All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data.
For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.
Regards,
Raj.

Regarding cluster table

hi experts,
I have an requirement about PR. I've to fetch all txgrp, buzei, kschl and hwste from bset table according to belnr and gjahr.
but at the of fetching, only one txgrp, buzei, kschl and hwste are fetched. BSET table is a cluster table.
Pls tell me how can I solve this problem.
thanks in advance.
Goutam

Hi sachin,
PR means perchase register.
and I've fetch from bset table. I've no option.
now what I've to do.
thanks,
Goutam.

Physical table list against Cluster Table CDPOS and PCDPOS

Similar Messages

Maybe you are looking for