Cluster table for PD infotypes

Hi,
I've created a custom PD infotype and wish to use IMPORT and EXPORT to database as I have a text box for comments on the screen. Could anyone suggest which cluster table and area would be suited for this operation?
Thanks

Hi Gaurav
As an alternative to your approach, you can try the way SAP uses at infotypes like 1002. The main table HRP1002 containes a reference number (ADATNR as I remember) and with this reference number it holds lines at the table HRT1002.
As far as I know, it is possible to design such infotypes but I do not remember how. It maybe related to some option at PPCI.
Regards
*--Serdar <a href="https://www.sdn.sap.com:443http://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.sdn.businesscard.sdnbusinesscard?u=qbk%2bsag%2bjiw%3d">[ BC ]</a>

Similar Messages

Tables for OM infotype 1000, 1001 and 1002

Hi,
I need to use OM infotypes P1000, P0001 and P1002. But, I don't know the name of the tables for these infotypes.
Could you please provide me the table names for the above infotypes.
Lokman

Sorry ignore my prev post:
refer hrp1000
HRP1002
AND HRP1001
Message was edited by: Ravi Kanth Talagana

Custom Subtype table for custom Infotype

Hi,
How can I have a customer table Z* as subtype for an infotype? In PM01 I can set a Z table and field in infotype settings, but an error occurs when genarating my infotype.
I would like someting similar to IT 2006 in my custom infotype where I would have a specific Z table as subtype (not a generic one like t591a) so that new entries in that Z table appears as new subtype options.
Thanks and regrads.
Sérgio.

Hi,
The Subtype Table doesn't contain the Subtype Field.
For Example: PM01 for IT 2006 has Subtype Table T556A, Subtype Field KTART (which is not part of T556A).
KTART is a field in the IT2006 Structure itself.
Subtype Table is used just for the Values of the subtypes, Texts, Time Constraints and Object IDs.
Can you mention what the Structure of Z table is, and what the Subtype Field is.
Thanks,
Suryakiran D.

Internal tables for OM infotypes when LDB is used

It's pretty much clear that for the infotypes used in a report, when a logical database is used the corresponding structures with pxxxx is created.
Is that limited only for PA infotypes or is that applicable to OM infotypes also? I could identify that it is applicable for OM also with my report usage, but i cant justify how is that done.
If it is applicable to OM infotypes, can you please explain in detail about this?
I have tried this in many forms but in vain.(research has been made before posting)
Edited by: mythrikalam on Jan 20, 2012 11:59 AM

Hi! First I would create a system repair disc. If you still have a problem, restoring back to factory will eliminate software and you can start finding what hardware is causing you this problem. Key Board or Mother Board would be good suspects.
http://www.dummies.com/how-to/content/how-to-use-a-system-repair-disc-to-restore-windows.html
http://forums.toshiba.com/t5/Computer-Troubleshooting/What-can-I-do-if-my-Windows-7-or-Windows-Vista...
PS Strange that it won't turn on with the power button. Are you holding it down for a couple of seconds?
I Love my Satellite L775D-S7222 Laptop. Some days you're the windshield, Some days you're the bug. The Computer world is crazy. If you have answers to computer problems, pass them forward.

How to Extract Data for a Maintenance View, Structure and Cluster Table

I want to develop 3 Reports
1) in First Report
it consists only two Fields.
Table name : V_001_B
Field Name1: BUKRS
Table name : V_001_B
Field Name2: BUTXT
V_001_B is a Maintenance View
For this one I don't Find any Datasource
For this Maintenance View, How to Extract the Data.
2)
For the 2nd Report also it consists Two Fields
Table name : CSKSZ
Field Name1: KOSTL (cost center)
Table name : CSKSZ
Field Name2: KLTXT (Description)
CSKSZ is a Structure
For this one I don't Find any Datasource
For this Structure How to Extract the Data
3)
For the 3rd Report
in this Report all Fields are belonging to a Table BSEG
BSEG is a Cluster Table
For this one also I can't Find any Datasource,
I find very Few Objects in the Datasource.
For this One, How to Extract the Data.
Please provide me step by step procedure.
Thanks
Priya

Hi sachin,
I don't get your point can you Explain me Briefly.
I have two Fields for the 1st Report
BUKRS
BUTXT
In the 2nd Report
KOSTL
KLTXT
If I use 0COSTCENTER_TEXT Data Source
I will get KOSTL Field only
what about KLTXT
Thanks
Priya

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 <i>cannot</i> 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

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).

View on cluster table

hi all,
I am trying to create a view for the tables bkpg and bseg.but am unable to as the error is "bseg is cluster table".
can't we create view for cluster table. if can, how

You cannot create a view because BSEG is in a cluster table
For this reason SAP has provided some "secondary index" tables, look for :
     BSAD     Accounting: Secondary Index for Customers (Cleared Items)
     BSAK     Accounting: Secondary Index for Vendors (Cleared Items)
     BSAS     Accounting: Secondary Index for G/L Accounts (Cleared Items)
     BSID     Accounting: Secondary Index for Customers
     BSIK     Accounting: Secondary Index for Vendors
     BSIM     Secondary Index, Documents for Material
     BSIS     Accounting: Secondary Index for G/L Accounts
Regards

How to select data from cluster table

hi experts,
I have a report which picks data from bseg (cluster table ) for a month report it is taking around 4 minutes to process.I feel it is not good when take the report after some months.
how to select data from these table???how to declare itab for these cluster tables????can we include any search condition or any other kind of internal table???
please advice.
mani

Hi Manikandan,
The following code may be helpful to understand how to select the data from cluster table.
Types: Begin of ty_kna1,
Kunnr type kna1-kunnr,
adrnr type kna1-adrnr,
end of ty_kna1,
begin of ty_bseg,
belnr type bseg-belnr,
kunnr type bseg-kunnr,
end of ty_bseg,
begin of ty_final,
belnr type bseg-belnr,
kunnr type kna1-kunnr,
adrnr type kna1-adrnr,
end of ty_final.
Data: it_kna1 type table of ty_kna1,
wa_kna1 type ty_kna1,
it_bseg type table of ty_bseg,
wa_bseg type ty_bseg,
it_final type table of ty_final,
wa_final type ty_final.
Select kunnr adrnr from kna1 into table it_kna1 where....
if sy-subrc = 0.
select belnr kunnr into table it_bseg for all entries in it_kna1 where kunnr = it_kna1-kunnr.
endif.
sort it_kna1 by kunnr.
Loop at it_bseg into wa_bseg.
move wa_bseg-belnr to wa_final-belnr.
read table it_kna1 into wa_kna1 with kunnr = wa_bseg-kunnr binary search.
if sy-subrc = 0.
move: wa_kna1-kunnr to wa_final-kunnr,
wa_kna1-belnr to wa_final-belnr.
endif.
append wa_final to it_final.
clear wa_final.
endloop.
Loop at it_final into wa_final.
write: / wa_final-belnr, wa_final-kunnr, wa_final-adrnr.
endloop.
Reward if useful.
Thankyou,
Regards.

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 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.

Table for the report RPUAUD00 Logged Changes in Infotype data

Hi
I have a query with the program RPUAUD00 Logged changes in Infotype Data. In which table stores the details of the program RPUAUD00. for example in the 1st period there is a LWP record for the employee. If in the 2nd period the LWP entered in 1st period has deleted, in the log the LWP displays for 1st period new field contents, Action Indicator I. The deleted information displayes in Old field contents with the Action Indicator D. We want to know in which table the LWP insert and LWP delete (d) details are stored.
This information required to create a report for ESI. In the report No of days (payroll processed for) has to mention. To know the no of days need to access the report RPUAUD00. From the RPUAUD00 the details of LWP insert and delete can be known.
Request to help in solving the issue
Thanks & Regards
EKP Yadav

Hello:
Logged changes in Infotype Data are stored in cluster table PCL4 ID LA and SA for employee and LB and SB for applicant. Maybe L is for longterm and S for shorterm
Cheers.
Antoine

How to fetch data for a struture from a cluster table

How can I fetch data for a struture, from a cluster table, based on the name of the structure?

Hi,
In order to read from Cluster DB Table use the following statement:
Syntax
IMPORT <f1> [ TO < g1 > ] <f2> [TO < g2 >] ...
FROM DATABASE <dbtab>(<ar>)
[CLIENT <cli>] ID <key>|MAJOR-ID <maid> [MINOR-ID <miid>].
This statement reads the data objects specified in the list from a cluster in the database <dbtab>.
You must declare <dbtab> using a TABLES statement. If you do not use the TO <gi> option, the
data object <fi> in the database is assigned to the data object in the program with the same
name. If you do use the option, the data object <fi> is read from the database into the field <gi>.
For <ar>, enter the two-character area ID for the cluster in the database. The name <key>
identifies the data in the database. Its maximum length depends on the length of the name field
in <dbtab>.
The CLIENT <cli> option allows you to disable the automatic client handling of a client-specific cluster database, and specify the client yourself. The addition must always come directly after the name of the database.
For Eg:
PROGRAM SAPMZTS3.
TABLES INDX.
DATA: BEGIN OF JTAB OCCURS 100,
COL1 TYPE I,
COL2 TYPE I,
END OF JTAB.
IMPORT ITAB TO JTAB FROM DATABASE INDX(HK) ID 'Table'.
WRITE: / 'AEDAT:', INDX-AEDAT,
/ 'USERA:', INDX-USERA,
/ 'PGMID:', INDX-PGMID.
SKIP.
WRITE 'JTAB:'.
LOOP AT JTAB FROM 1 TO 5.
WRITE: / JTAB-COL1, JTAB-COL2.
ENDLOOP.
Regards,
Neha
Edited by: Neha Shukla on Mar 12, 2009 1:35 PM

Maintaince view creation for a cluster table

Hi friends,
I have created a maintaince view for a cluster table bseg and i have activated it its working fine..
now my problem is i can create maintaince view for mutiple tables if other tables are linked with primary table using foriegn key relationship..
Now can any one tell me is it possible to create maintance view for cluster table with multiple tables as i need a linked table with bseg which iam not able to get... ie : when i click on the relationship tab iam not getting the linked tables for bseg...
now can i create a maintaince view with 2 linked cluster tables..
if so can any one tell me how to create it.
As sap says we can create projection view for cluster and pooled table and we cannot create database view for cluster and pooled tables , but it does not mentioned like that for maintaince view....
I assume we can do it.... as iam trying to create a maintaince view with single cluster table then it shoudl allow me to create for multiple linked cluster tables.... and is it mandatory to maintain TMG for this maintaince view....?
Regards
KUMAR

yes.. ur right inserting values into a cluster table other than standard sap tarnactions is dangerious....
But sap didnot mentioned any where that we cannot maintain data for cluster tables using maintaince view... which it said for database view..that pooled and cluster table cannot be used for database view..
Regards
Kumar

Lock object for KONV table/Cluster table ??

Hi All,
Is it possible to set Lock/Enqueue cluster tables or in my case table:KONV (KNUMV field) ?.
OSS provided some programs without locks so was hoping if I could add before performing data manipulation.
Regards,
Neeth

Hi Nameeth,
you can use generic lock object E_TABLE with function modules ENQUEUE_E_TABLE, DEQUEUE_E_TABLE for locking and unlocking with parameters table name and key field.
Regards,
Satya

Cluster table for PD infotypes

Similar Messages

Maybe you are looking for