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

Similar Messages

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

How to convert Internal Table to Cluster Table ?

How to convert Internal Table to Cluster Table ?

Use :
EXPORT itab TO DATABASE dbtab(ar) ID key.
EXPORT obj1 ... objn TO DATABASE dbtab(ar) ID key.
Additions:
1. ... = f (for each field you want to export)
2. ... FROM f (for each field you want to export)
3. ... CLIENT g before ID key )
4. ... USING form
5. ... FROM wa (as last addition or after dbtab(ar))
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See Implicit field names not allowed with clusters and Table work areas not allowed.
Effect
Stores a data cluster in database table dbtab. The specified objects obj1 ... objn (fields, structures, or tables) are stored as a single cluster in the database table dbtab.
The specified database table dbtab must have a standard structure.
The database table dbtab is divided into various logically-related sections (ar, two-character name).
You can export a collection of data objects (a data cluster) to a part of the database using a key (field key).
You can import individual data objects from this collection using the IMPORT statement.
Notes
In classes, you must always assign explicit names to the data objects you want to export, that is, you must use either addition 1 or addition 2.
In classes, you must always specify the work area explicitly, that is, addition 5 is obligatory.
The table dbtab that appears after DATABAE must be declared under TABLES (except in addition 5).
You cannot export the header lines of internal tables. If you specify the name of an internal table with header line, the system always exports the body of the table.
You cannot export data, object, or interface references.
The data is stored in the database, and is consequently not actually stored until a database commit occurs (see LUW). Until this point, you can undo all of your changes using a database rollback (see Programming Transactions).
Example
Exporting two fields and an internal table to the database table INDX:
TABLES INDX.
TYPES: BEGIN OF ITAB3_TYPE,
 CONT(4),
 END OF ITAB3_TYPE.
DATA: INDXKEY LIKE INDX-SRTFD VALUE 'KEYVALUE',
 F1(4), F2 TYPE P,
 ITAB3 TYPE STANDARD TABLE OF ITAB3_TYPE WITH NON-UNIQUE
 DEFAULT KEY INITIAL SIZE 2,
 WA_INDX TYPE INDX.
Fill the data fields before CLUSTR
before the actual export
INDX-AEDAT = SY-DATUM.
INDX-USERA = SY-UNAME.
Export der Daten.
EXPORT F1 FROM F1
 F2 FROM F2
 ITAB3 FROM ITAB3
 TO DATABASE INDX(ST) FROM WA_INDX ID INDXKEY.

Regards

Generic extractors on pool table and Cluster tables

Good Afternoon all,
Can we create generic extractors on Cluster or pool Table. If yes Let me know how?
I am trying to create a Generic Extractor on BSEC Table but it is not allowing me to do this. It throws error that"Extraction from pool tables and cluster tables is not permitted"
Kindly guide me on this
Thanks,
Vaishali.

Hi
you cannot do generic extraction directly on pooled or cluster tables.
You can create a function module, then you can create a Generic Data source based on this..
Hope it helps,
Thanks,
Teja
Edited by: Teja badugu on Apr 15, 2008 12:24 PM

How to 'inner join' internal table or cluster table ??

Hi,
when i inner join table BSEG it said is a cluster table can't be inner joined .
i wonder how i can "inner join" bseg with a internal table such as
data: begin of i_bseg_trans,
        bukrs like bseg-bukrs,
        gjahr like bseg-gjahr,
        belnr like bseg-belnr,
        total_runtimes like i_runtimes-total,
        already_runtimes like i_runtimes-already,
        left_runtimes like i_runtimes-left,
      end of i_bseg_trans.
and similar things trouble me when considering several internal tables .
thanks for any help!!

Hi,
but if there's more than 2 tables, for example
data: begin of it_bseg occurs 0,
        bukrs like bseg-bukrs,
        else_1 type i,
     end of it_bseg.
data: begin of t occurs 0,
        bukrs like bseg-bukrs,
      end of t.
data: begin of r occurs 0,
        bukrs like bseg-bukrs,
        else type c,
      end of r.
select bukrs from bkdf into table t.
select bukrs from bkdf into corresponding fields of table it_bseg.
select bseg~bukrs      "else_1
from bseg      "it_bseg
into table r
for all entries in t
where bseg~bukrs = t-bukrs.
      " and it_bseg-bukrs = t-bukrs.
in the select clause i mean whether there's a method similar to the way just drop the " in my code.
now my solution is to use another loop on it_bseg, but i think when table amount is large this is really a boring solution.

SELECT is taking lot of time to fetch data from cluster table BSET

<Modified the subject line>
Hi experts,
I want to fetch data of some fields from bset table but it is taking a lot of time as the table is cluster table.
Can you please suggest me any other process to fetch data from cluster table. I am using native sql to fetch data.
Regards,
SURYA
Edited by: Suhas Saha on Jun 29, 2011 1:51 PM

Hi Subhas,
As per your suggestion I am now using normal SQL statement to select data from BSET but it is still taking much time.
My SQL statement is :
SELECT BELNR
 GJAHR
 BUZEI
 MWSKZ
 HWBAS
 KSCHL
 KNUMH FROM BSET INTO CORRESPONDING FIELDS OF TABLE IT_BSET
 FOR ALL ENTRIES IN IT_BKPF
 WHERE BELNR = IT_BKPF-BELNR
 AND BUKRS = IT_BKPF-BUKRS.
<Added code tags>
Can you suggest me anymore?
Regards,
SURYA
Edited by: Suhas Saha on Jun 29, 2011 4:16 PM

Cluster Tables and Open SQL

Hi,
I am planning to replace several transparent tables with cluster tables.
And this also implies that I have to read from cluster tables.
One of the reason, I did not do this is until now is, that at the moment I am heavily
relying on the possibility to specify the DB name dynamically during runtime.
If I start implementing this scenario in one case, it should be possible to implement this
for all cases.
My question is now, is it possible to use cluster table similar to transparent table?
The following sketches the idea
The typical cluster table looks like
RELID     INDX_RELID
SELKEY
SRTF2     INDX_SRTF2
CLUSTR
CLUSTD
What one could do is, select from the cluster table using the primariy key fields
RELID     INDX_RELID
SELKEY
into an internal table, treating the DB table as an transparent table and after that,
do an import from the internal table to the real internal table.
To generate the value for SELKEY - Fill the structure and move the content of the
structure to a CHAR50.
The question is: Would this work?
I looked across the documentation, but I have found only little.
Trying it out is not useful either, since this technique needs to work independ of OS, DB
and NW Release.
And if it works, I cant be sure, that with a different system setup it still works.
Thanks fro your help.
With kind regards
Uwe Gebhardt
Edited by: Uwe Gebhardt on Apr 28, 2011 9:38 AM

Hello Uwe,
I would not advise you to switch from transparent to cluster tables. Cluster tables give you much less flexibility in terms of different access strategies, usage of indexes, etc.
And I think you can forget about reprogramming SAP DBI functionality of parsing cluster table contents in your program and moving it into a real internal table. There is simply too much you should take care of. And what if SAP decides to make a slight change in the next release. Then the upgrade will ruine your program.
So my advise - stick to the transparent tables.
Regards,
Yuri

HR Cluster Tables

Hi
I need the HR cluster table names. Can you please provide?
Regards
Praveen

hi praveen,
 go through this
Cluster Table
u2022 Cluster tables combine the data from several tables with identical (or almost identical) keys
into one physical record on the database.
. Data is written to a database in compressed form.
u2022 Retrieval of data is very fast if the primary key is known.
u2022 Cluster tables are defined in the data dictionary as transparent tables.
u2022 External programs can NOT interpret the data in a cluster table.
u2022 Special language elements EXPORT TO DATABASE, IMPORT TO DATABASE and DELETE
FROM DATABASE are used to process data in the cluster tables.
PCL1 - Database for HR work area;
PCL2 - Accounting Results (time, travel expense and payroll);
PCL3 - Applicant tracking data;
PCL4 - Documents, Payroll year-end Tax data
Database Tables PCLn
u2022 PCLn database tables are divided into subareas known as data clusters.
u2022 Data Clusters are identified by a two-character code. e.g RU for US payroll result, B2 for
time evaluation result...
u2022 Each HR subarea has its own cluster.
u2022 Each subarea has its own key.
Database Table PCL1
u2022 The database table PCL1 contains the following data areas:
B1 time events/PDC
G1 group incentive wages
L1 individual incentive wages
PC personal calendar
TE travel expenses/payroll results
TS travel expenses/master data
TX infotype texts
ZI PDC interface -> cost account
Database Table PCL2
u2022 The database table PCL2 contains the following data areas:
B2 time accounting results
CD cluster directory of the CD manager
PS generated schemas
PT texts for generated schemas
RX payroll accounting results/international
Rn payroll accounting results/country-specific ( n = HR country indicator )
ZL personal work schedule
Database Table PCL3
u2022 The database table PCL3 contains the following data areas:
AP action log / time schedule
TY texts for applicant data infotypes
Data Management of PCLn
u2022 The ABAP commands IMPORT and EXPORT are used for management of read/write to
database tables PCLn.
u2022 A unique key has to be used when reading data from or writing data to the PCLn.
Field Name KEY Length Text
MANDT X 3 Client
RELID X 2 Relation ID (RU,B2..)
SRTFD X 40 Work Area Key
SRTF2 X 4 Sort key for dup. key
Cluster Definition
u2022 The data definition of a work area for PCLn is specified in separate programs which comply
 with fixed naming conventions.
u2022 They are defined as INCLUDE programs (RPCnxxy0). The following naming convention applies:
 n = 1 or 2 (PCL1 or PCL2)
 xx = Relation ID (e.g. RX)
 y = 0 for international clusters or country indicator (T500L) for different country cluster
Exporting Data (I)
u2022 The EXPORT command causes one or more 'xy' KEY data objects to be written to cluster xy.
u2022 The cluster definition is integrated with the INCLUDE statement.
REPORT ZHREXPRT.
TABLES: PCLn.
INCLUDE: RPCnxxy0. "Cluster definition
* Fill cluster KEY
xy-key-field = <value>.
* Fill data object
* Export record
EXPORT TABLE1 TO DATABASE PCLn(xy) ID xy-KEY.
 IF SY-SUBRC EQ 0.
 WRITE: / 'Update successful'.
 ENDIF.
Exporting Data (II)
. Export data using macro RP-EXP-Cn-xy.
u2022 When data records are exported using macro, they are not written to the database but to a
main memory buffer.
u2022 To save data, use the PREPARE_UPDATE routine with the USING parameter 'V'.
REPORT ZHREXPRT.
*Buffer definition
INCLUDE RPPPXD00. INCLUDE RPPPXM00. "Buffer management
DATA: BEGIN OF COMMON PART 'BUFFER'.
INCLUDE RPPPXD10.
DATA: END OF COMMON PART 'BUFFER'.
RP-EXP-Cn-xy.
IF SY-SUBRC EQ 0.
 PERFORM PREPARE_UPDATE USING 'V'..
ENDIF.
Importing Data (I)
u2022 The IMPORT command causes data objects with the specified key values to be read from
 PCLn.
u2022 If the import is successful, SY-SUBRC is 0; if not, it is 4.
REPORT RPIMPORT.
TABLES: PCLn.
INCLUDE RPCnxxy0. "Cluster definition
* Fill cluster Key
* Import record
IMPORT TABLE1 FROM DATABASE PCLn(xy) ID xy-KEY.
 IF SY-SUBRC EQ 0.
 * Display data object
 ENDIF.
Importing data (II)
u2022 Import data using macro RP-IMP-Cn-xy.
u2022 Check return code SY-SUBRC. If 0, it is successful. If 4, error.
u2022 Need include buffer management routines RPPPXM00
REPORT RPIMPORT.
*Buffer definition
INCLUDE RPPPXD00.
DATA: BEGIN OF COMMON PART 'BUFFER'.
INCLUDE RPPPXD10.
DATA: END OF COMMON PART 'BUFFER'.
*import data to buffer
RP-IMP-Cn-xy.
*Buffer management routines
INCLUDE RPPPXM00.
Cluster Authorization
u2022 Simple EXPORT/IMPORT statement does not check for cluster authorization.
u2022 Use EXPORT/IMPORT via buffer, the buffer management routines check for cluster
authorization.
Payroll Results (I)
u2022 Payroll results are stored in cluster Rn of PCL2 as field string and internal tables.
n - country identifier.
u2022 Standard reports read the results from cluster Rn. Report RPCLSTRn lists all payroll results;
report RPCEDTn0 lists the results on a payroll form.
Payroll Results (II)
u2022 The cluster definition of payroll results is stored in two INLCUDE reports:
include: rpc2rx09. "Definition Cluster Ru (I)
include: rpc2ruu0. "Definition Cluster Ru (II)
The first INCLUDE defines the country-independent part; The second INCLUDE defines the country-specific part (US).
u2022 The cluster key is stored in the field string RX-KEY.
Payroll Results (III)
u2022 All the field string and internal tables stored in PCL2 are defined in the ABAP/4 dictionary. This
allows you to use the same structures in different definitions and nonetheless maintain data
consistency.
u2022 The structures for cluster definition comply with the name convention PCnnn. Unfortunately,
 'nnn' can be any set of alphanumeric characters.
*Key definition
DATA: BEGIN OF RX-KEY.
 INCLUDE STRUCTURE PC200.
DATA: END OF RX-KEY.
*Payroll directory
DATA: BEGIN OF RGDIR OCCURS 100.
 INCLUDE STRUCTURE PC261.
DATA: END OF RGDIR.
Payroll Cluster Directory
u2022 To read payroll results, you need two keys: pernr and seqno
. You can get SEQNO by importing the cluster directory (CD) first.
REPORT ZHRIMPRT.
TABLES: PERNR, PCL1, PCL2.
INLCUDE: rpc2cd09. "definition cluster CD
PARAMETERS: PERSON LIKE PERNR-PERNR.
RP-INIT-BUFFER.
*Import cluster Directory
 CD-KEY-PERNR = PERNR-PERNR.
RP-IMP-C2-CU.
 CHECK SY-SUBRC = 0.
LOOP AT RGDIR.
 RX-KEY-PERNR = PERSON.
 UNPACK RGDIR-SEQNR TO RX-KEY-SEQNO.
 *Import data from PCL2
 RP-IMP-C2-RU.
 INLCUDE: RPPPXM00. "PCL1/PCL2 BUFFER HANDLING
Function Module (I)
CD_EVALUATION_PERIODS
u2022 After importing the payroll directory, which record to read is up to the programmer.
u2022 Each payroll result has a status.
'P' - previous result
'A' - current (actual) result
'O' - old result
u2022 Function module CD_EVALUATION_PERIODS will restore the payroll result status for a period
 when that payroll is initially run. It also will select all the relevant periods to be evaluated.
Function Module (II)
CD_EVALUATION_PERIODS
call function 'CD_EVALUATION_PERIODS'
 exporting
 bonus_date = ref_periods-bondt
 inper_modif = pn-permo
 inper = ref_periods-inper
 pay_type = ref_periods-payty
 pay_ident = ref_periods-payid
 tables
 rgdir = rgdir
 evpdir = evp
 iabkrs = pnpabkrs
 exceptions
 no_record_found = 1.
Authorization Check
 Authorization for Persons
u2022 In the authorization check for persons, the system determines whether the user has the
 authorizations required for the organizational features of the employees selected with
 GET PERNR.
u2022 Employees for which the user has no authorization are skipped and appear in a list at the end
 of the report.
u2022 Authorization object: 'HR: Master data'
Authorization for Data
u2022 In the authorization check for data, the system determines whether the user is authorized to
read the infotypes specified in the report.
u2022 If the authorization for a particular infotype is missing, the evaluation is terminated and an error
message is displayed.
Deactivating the Authorization Check
u2022 In certain reports, it may be useful to deactivate the authorization check in order to improve
performance. (e.g. when running payroll)
u2022 You can store this information in the object 'HR: Reporting'.

Cluster tables in SAP

Hi all,
what are the cluster tables in SAP.
and shall we use inner join statment on cluster tables.
regards,
Suresh

HI,
CLUSTER Tables :-Table clusters (clusters) are special table types in the ABAP Dictionary
The data from several tables is 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.
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.
Can check this link for more clarity
http://help.sap.com/saphelp_47x200/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
We can't use inner join on clustor table.
To Join cluster table with other table its better use
several select statements.
This one sample code to join cluster table with other transperant table.
In this bseg is a cluster table.
Check it out.
TABLES : bkpf,
 bseg.
 INTERNAL TABLE AND WORK AREA FOR THE FIELDS IN BKPF TABLE *
DATA : BEGIN OF itab_bkpf OCCURS 0,
 bukrs LIKE bkpf-bukrs, "Company Code.
 gjahr LIKE bkpf-gjahr, "Fiscal Year.
 budat LIKE bkpf-budat, "Posting Date in the Document.
 belnr LIKE bkpf-belnr, "Accounting document number.
 blart LIKE bkpf-blart, "Document Type.
 END OF itab_bkpf.
DATA : wa_bkpf LIKE LINE OF itab_bkpf.
 INTERNAL TABLE AND WORK AREA FOR THE FIEDLS IN BSEG TABLE *
DATA : BEGIN OF itab_bseg_debit OCCURS 0,
 bukrs LIKE bseg-bukrs, "Company Code.
 gjahr LIKE bseg-gjahr, "Fiscal Year.
 belnr LIKE bseg-belnr, "Accounting Document Number.
 buzei LIKE bseg-buzei, "Line Item.
 hkont LIKE bseg-hkont, "General Leadger Account.
 shkzg LIKE bseg-shkzg, "Credit/Debit Indicator.
 wrbtr LIKE bseg-wrbtr, "Amount in Document Currency.
 pswsl LIKE bseg-pswsl, "Update Currency for Gen.Ledger
 dmbtr LIKE bseg-dmbtr, "Amount in local currency.
 sgtxt LIKE bseg-sgtxt, "Item Text.
 zuonr LIKE bseg-zuonr, "Assignment Number.
 END OF itab_bseg_debit.
DATA : itab_bseg_credit LIKE STANDARD TABLE OF itab_bseg_debit WITH
 HEADER LINE.
 FINAL OUTPUT INTERNAL TABLE *
DATA : BEGIN OF itab_output OCCURS 0,
 belnr(08),
 bukrs(04),
 budat LIKE bkpf-budat,
 buzei(03),
 hkont(07),
 blart(02),
 shkzg(01),
 wrbtr(08),
 pswsl(05),
 dmbtr(10),
 sgtxt(19),
 zuonr(10),
END OF itab_output.
CONSTANTS : c_debit TYPE c VALUE 'S',
 c_credit TYPE c VALUE 'H'.
 SELECT-OPTIONS *
SELECTION-SCREEN BEGIN OF BLOCK input WITH FRAME TITLE text-t01.
SELECT-OPTIONS : s_bukrs FOR bkpf-bukrs.
PARAMETERS : p_year LIKE bkpf-gjahr.
SELECT-OPTIONS : s_budat FOR bkpf-budat,
 s_dbacct FOR bseg-hkont,
 s_cracct FOR bseg-hkont,
 s_amt FOR bseg-dmbtr.
SELECTION-SCREEN END OF BLOCK input.
 SELECTING RECORDS FROM BKPF TABLE BASED ON THE CONDITION *
SELECT bukrs gjahr budat belnr blart
 FROM bkpf INTO TABLE itab_bkpf
 WHERE bukrs IN s_bukrs AND
 gjahr EQ p_year AND
 budat IN s_budat.
 SELECTING DEBIT LINE ITEMITEMS FROM BSEG FOR THE DOCUMENT *
 NUMBER SELECTED FROM BKPF *
IF NOT itab_bkpf[] IS INITIAL.
SELECT bukrs gjahr belnr buzei
 hkont shkzg wrbtr pswsl
 dmbtr sgtxt zuonr
 FROM bseg INTO TABLE itab_bseg_debit
 FOR ALL ENTRIES IN itab_bkpf
 WHERE bukrs EQ itab_bkpf-bukrs AND
 belnr EQ itab_bkpf-belnr AND
 gjahr EQ itab_bkpf-gjahr AND
 hkont IN s_dbacct AND
 shkzg EQ c_debit AND
 dmbtr IN s_amt.
 SELECTING CREDIT LINE ITEMITEMS FROM BSEG FOR THE DOCUMENT *
 NUMBER SELECTED FROM BKPF *
SELECT bukrs gjahr belnr buzei
 hkont shkzg wrbtr pswsl
 dmbtr sgtxt zuonr
 FROM bseg INTO TABLE itab_bseg_credit
 FOR ALL ENTRIES IN itab_bkpf
 WHERE bukrs EQ itab_bkpf-bukrs AND
 belnr EQ itab_bkpf-belnr AND
 gjahr EQ itab_bkpf-gjahr AND
 hkont IN s_cracct AND
 shkzg EQ c_credit AND
 dmbtr IN s_amt.
ENDIF.
SORT itab_bkpf BY bukrs gjahr belnr.
SORT itab_bseg_credit BY bukrs gjahr belnr.
 LOOPING THE DEBIT ENTRIES
LOOP AT itab_bseg_debit.
READING THE CREDIT ENTRIES WHICH MATCHES WITH HE CURRENT DOC. NUMBER
READ TABLE itab_bseg_credit WITH KEY
 bukrs = itab_bseg_debit-bukrs
 gjahr = itab_bseg_debit-gjahr
 belnr = itab_bseg_debit-belnr BINARY SEARCH.
IF sy-subrc EQ 0.
*READING THE POSTING DATE AND DOCUMENT TYPE FOR THE CURRENT DOUCMENT
 AND APPENDING THE DEBIT AND CREDIT ENTRIES
 READ TABLE itab_bkpf INTO wa_bkpf WITH KEY
 bukrs = itab_bseg_debit-bukrs
 gjahr = itab_bseg_debit-gjahr
 belnr = itab_bseg_debit-belnr BINARY SEARCH.
 itab_output-belnr = itab_bseg_debit-belnr.
 itab_output-bukrs = itab_bseg_debit-bukrs.
 itab_output-budat = wa_bkpf-budat.
 itab_output-buzei = itab_bseg_debit-buzei.
 itab_output-hkont = itab_bseg_debit-hkont.
 itab_output-blart = wa_bkpf-blart.
 itab_output-shkzg = itab_bseg_debit-shkzg.
 itab_output-wrbtr = itab_bseg_debit-wrbtr.
 itab_output-pswsl = itab_bseg_debit-pswsl.
 itab_output-dmbtr = itab_bseg_debit-dmbtr.
 itab_output-sgtxt = itab_bseg_debit-sgtxt.
 itab_output-zuonr = itab_bseg_debit-zuonr.
 APPEND itab_output.
 itab_output-belnr = itab_bseg_credit-belnr.
 itab_output-bukrs = itab_bseg_credit-bukrs.
 itab_output-budat = wa_bkpf-budat.
 itab_output-buzei = itab_bseg_credit-buzei.
 itab_output-hkont = itab_bseg_credit-hkont.
 itab_output-blart = wa_bkpf-blart.
 itab_output-shkzg = itab_bseg_credit-shkzg.
 itab_output-wrbtr = itab_bseg_credit-wrbtr.
 itab_output-pswsl = itab_bseg_credit-pswsl.
 itab_output-dmbtr = itab_bseg_credit-dmbtr.
 itab_output-sgtxt = itab_bseg_credit-sgtxt.
 itab_output-zuonr = itab_bseg_credit-zuonr.
 APPEND itab_output.
ENDIF.
ENDLOOP.
Reward if it helps you.
Thanks.

How to find which transparent tables compose cluster tableuFF1AKONV

How to find which transparent tables compose cluster table：KONV

Hi,
Welcome to SDN.
Try doing this ....
1). Goto se12 and display the table BSEG
2). Click on the Delivery & Maintenanace tab
3). Double click on the Pool/Cluster field
4). On the next screen do a where used list
You will find all the related tables.
Regards,
Amit
Reward all helpful replies.

What are the Cluster tables and pooled tables

pls give some examples for the above table
Thankyou
ravi

Hi
Pooled Table
Pooled tables are logical tables that must be assigned to a table pool when they are defined. Pooled tables are used to store control data. Several pooled tables can be cominied in a table pool. The data of these pooled tables are then sorted in a common table in the database.
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.
check this link also
http://help.sap.com/saphelp_47x200/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
Rewards if helpfull
Regards
Pavan

POOL & CLUSTER TABLEs

Hi Experts,
Can you send me some example tables for pool and cluster tables..
And where exactly you use these tables in real time..
Kindly reply me as early as possible
Thanks in advance
Santosh

Hi santosh,
Go to se11
table DD02L-> Give TABCLASS as POOL or CLUSTER you will get a list of tables
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). A pool has the following structure:
Field
Data type
Meaning
Tabname
CHAR(10)
Name of pooled table
Varkey
CHAR (n)
Contains the entries from all key fields of the pooled table record as a string, max. length for n is 110
Dataln
INT2(5)
Length of the string in Vardata
Vardata
RAW (n)
Contains the entries from all data fields of the pooled table record as a string, max. length n depends on the database system used
If a pooled table record is saved, it is stored in the table pool assigned. The name of the pooled table is written to the field Tabname. The contents of all key fields of the pooled table are written as a string to field Varkey and the contents of all data fields as a string to field Vardata. The length of the string stored in Vardata is entered in field Dataln by the database interface.
Due to the structure of a table pool, there are certain restrictions on the pooled tables assigned to it. The name of a pooled table may not exceed 10 characters. Since Varkey is a character field, all key fields of a pooled table must have character data types (for example, CHAR, NUMC, CLNT). The total length of all key fields or all data fields of a pooled table must not exceed the length of the Varkey or Vardata field of the assigned pool.
Table Clusters
Several logical data records from different cluster tables can be stored together in one physical record in a table cluster.
A cluster key consists of a series of freely definable key fields and a field (Pageno) for distinguishing continuation records. A cluster also contains a long field (Vardata) that contains the contents of the data fields of the cluster tables for this key. If the data does not fit into the long field, continuation records are created. Control information on the structure of the data string is still written at the beginning of the Vardata field. A table cluster has the following structure:
Field
Data type
Meaning
CLKEY1
First key field
CLKEY2
Second key field
CLKEYn
nth key field
Pageno
INT2(5)
Number of the continuation record
Timestamp
CHAR(14)
Time stamps
Pagelg
INT2(5)
Length of the string in Vardata
Vardata
RAW (n)
Contains the entries from the data fields of the assigned cluster tables as a string, max. length n depends on the database system used
The records of all cluster tables with the same key are stored under one key in the assigned table cluster. The values of the key fields are stored in the corresponding key fields of the table cluster. The values of all data fields of the assigned cluster tables are written as a string to the Vardata field of the table cluster. Besides the actual data values, the data string contains information on the structure of the data and which table it comes from. If the string exceeds the maximum length of the Vardata field, a continuation record is written with the same key values. The continuation records for a key are distinguished by their value in field Pageno. The actual length of the string in the Vardata field is stored in the Pagelg field by the database interface.
You need the structural information stored in the ABAP Dictionary to read the data from a pooled table or cluster table correctly. These tables can therefore only be processed using Open SQL with the cluster interface, and not with Native SQL directly in the database.
In Repository informatino SE84 goto ABAP Dictonary -> Other Objects -> Pooled and clustered tables -> And then execute. It will give the list of available pooled/clustered tables.
For further reference check the SAP help document...
http://help.sap.com/saphelp_erp2005/helpdata/en/cf/21ea0b446011d189700000e8322d00/frameset.htm
regards,
keerthi

Cluster tables in views???

Hi all!!!
Thanks for all ur replies for my prev query!!!!
Here's my another doubt...
Can we include cluster tables in a datadictionary view?
Thanks,
jyothi D.

Hi Jyothi...
These are the types of SAP tables:
1) Transparent tables
2) Cluster tables
and 3) Pool Tables
The base difference in These tables is:
Cluster and Pool tables can not have Views.
Cluster and Pool tables consist of data from multiple tables. They can not have views.
Thanks and Best regards,
Vikas Bittera.

Cluster table clustd field

hi,
how to read data stored in this field, clustd?
actually how to use this table?
thanks

Hi,
Several logical data records from different cluster tables can be stored together in one physical
record in a table cluster.
A cluster key consists of a series of freely definable key fields and a field (Pageno) for
distinguishing continuation records. A cluster also contains a long field (Vardata) that contains
the contents of the data fields of the cluster tables for this key. If the data does not fit into the long
field, continuation records are created. Control information on the structure of the data string is
still written at the beginning of the Vardata field.
The records of all cluster tables with the same key are stored under one key in the assigned table cluster. The values of the key fields are stored in the corresponding key fields of the table cluster.The values of all data fields of the assigned cluster tables are written as a string to the Vardata field of the table cluster. Besides the actual data values, the data string contains information on the structure of the data and which table it comes from. If the string exceeds the maximum length
of the Vardata field, a continuation record is written with the same key values. The continuation records for a key are distinguished by their value in field Pageno. The actual length of the string in the Vardata field is stored in the Pagelg field by the database interface.
You need the structural information stored in the ABAP Dictionary to read the data from a pooled
table or cluster table correctly. These tables can therefore only be processed using Open SQL
with the cluster interface, and not with Native SQL directly in the database.
refer link.
Re: read data from cluster tables
Regards,
Priyanka.

Tables in Cluster table

Similar Messages

Maybe you are looking for