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

Similar Messages

To fetch 2 fileds of table TRFCQIN (abap schema table ) through OPEN SQL

Hi Experts,
My basis team wants me to write a OPEN sql statement in DB2 . T
The Open SQL statement for reading data from database tables is:
SELECT      <result>
INTO      <target>
FROM      <source>
[WHERE    <condition>]
[GROUP BY <fields>]
[HAVING   <cond>]
[ORDER BY <fields>].
I want to fetch 2 fileds of table TRFCQIN (abap schema table ) through OPEN SQL in report RSORADJV in PI .
As per PI basis comment : To use u201CRSORADJVu201D you need write the code in open SQL. If the code had been written in open SQL in the first place you wouldnu2019t be having to translate this from MS SQL.
Can you pls help in writing open sql with above syntax .
Initially when I wrote as
QL statement : select * from SAPDBSR3.XI_AF_MSG, I got the error messege as
Error : insufficient priviliage to access specified table.
Again basis suggested to write this code in OPen SQL statement .
Please suggest., I dont know open SQL for the same.
Regards,
Arnab.

Hi,
Well I don't know why you have duplicates, this is a functionnal issue. But you get the dump due the the message number 864 that triggers the abend... Changing the message type to 'E', 'S' or 'I' will prevent the dump but I guess this message has a good reason to be
Kr,
Manu.

Diference b/w normal tables and pl/sql tables

what is the diference b/w normal tables and pl/sql tables.
already we have tables then what is the purpose of pl/sql tables.
what are the advantages of pl/sql tables compare nor mal tables.

user10447332 wrote:
what is the diference b/w normal tables and pl/sql tables.As BluShadow pointed out "PL/SQL tbles" are now called collections. They are memory structures that store data and go away when your program stops running - essentially arrays or "tables" in other programming languages. "normal" ("heap") tables are stored on disk and are persistant - they store data permanently.
already we have tables then what is the purpose of pl/sql tables.Collections are used to store data temporarily in memory, when it will be accessed shortly or repeatedly for fast access. This works best with smaller data sets because if you store too much data in a collection you can run out of memory to use
what are the advantages of pl/sql tables compare nor mal tables.Collections give you faster access to data you need to read more than once during the same application. They work well for fast lookups and for smaller data sets can improve program performance slightly with the use of the bulk collect and forall PL/SQL operators under the right conditions.

How to get different field in two are more different table using open sql

Dear all,
          This SenthilMani am very new into sap abap am having doubt in reports how get the different fields from different tables like mara,marc,mard using open sql and native sql program give me some tips to get the data .
with regards,
senthil

HI ,
1) If u want to select data from more the two table then u can use FOR ALL ENTRIES.
         EX ..Open sql
                   select matnr from mara into table t_mara.
                  select matnr werks from marc into table t_marc for all entries in t_mara where matnr = t_mara-matnr.
2) U can join more than one table.
           ex:
               select mara~matnr
                          marc~werks
                from mara join marc into table t_maramarc
                 on maramatnr = marcmatnr
3) Using native sql ...only u can use JOIN statement

Update VBKD table using open sql

HI
when i use BAPI_SALESORDER_CREATEFROMDAT2 to create SO!
but some field i can't fill in BAPI_SALESORDER_CREATEFROMDAT2 of parameter. so i want update it using open SQL.
so i want to use BAPI_SALESORDER_CREATEFROMDAT2 first. and next using
open sql to update VBKD of field! VBKD-TRATY(Means-of-Transport Type)
abap code:
   CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
SALESDOCUMENTIN               =
        ORDER_HEADER_IN               = header
        ORDER_HEADER_INX              = headerx
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
     IMPORTING
       SALESDOCUMENT                 = saledocument
      TABLES
       RETURN                        = return
       ORDER_ITEMS_IN                = item
       ORDER_ITEMS_INX               = itemx
        ORDER_PARTNERS                = partner
ORDER_SCHEDULES_IN            =
ORDER_SCHEDULES_INX           =
       ORDER_CONDITIONS_IN           = condition
       ORDER_CONDITIONS_INX          = conditionx
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
if sy-subrc = 0.
update vbkd
set TRATY = in_data-TRATY
where vbeln = saledocument.
if sy-subrc = 0.
commit work.
endif.
endif.
but i don't what affect if i use open sql to update sap VBKD table.
who can help me to explain it!
thank you!

Hi,
   Try like thais
*&      Form SUB_READ_UPDATE_BSEG
      text
FORM sub_read_update_bseg.
IF NOT it_final[] IS INITIAL.
    LOOP AT it_final INTO wa_final.
      UPDATE bseg SET zuonr = wa_final-ccnum
                  WHERE bukrs EQ wa_final-bukrs
                  AND   belnr EQ wa_final-vbeln
                  AND   rfzei EQ wa_final-rfzei
                  AND   saknr NE ' '.
    ENDLOOP.
*--Message data updated successfully
    MESSAGE i888 WITH text-002.
    LEAVE LIST-PROCESSING.
ELSE.
*--Message No data found
    MESSAGE i888 WITH text-003.
    LEAVE LIST-PROCESSING.
ENDIF.
ENDFORM.                    " SUB_READ_UPDATE_BSEG
Regards,
Prashant

How to Extract data from Cluster table and transperant table

Hello BW Experts ,
I want to extract the data from cluster table BSEG and a transperant table BKPF .
The primary fields are BELNR , GJHAR and BUKRS.
the fields of table BKPF to extarct is BUDAT and fields of BSEG table is HKONT , BSCHL , ZUONR and POSID.
I can not create a view over these two tables as BSEG is a Cluster table.
Please guide me.
Regadrs ,
Amol.

hi Amol,
take a look Sigg's weblog
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
you can use RSAX_BIW_GET_DATA_SIMPLE as sample, there specified import parameters
FUNCTION RSAX_BIW_GET_DATA_SIMPLE.
""Lokale Schnittstelle:
*" IMPORTING
*" VALUE(I_REQUNR) TYPE SRSC_S_IF_SIMPLE-REQUNR
*" VALUE(I_DSOURCE) TYPE SRSC_S_IF_SIMPLE-DSOURCE OPTIONAL
*" VALUE(I_MAXSIZE) TYPE SRSC_S_IF_SIMPLE-MAXSIZE OPTIONAL
*" VALUE(I_INITFLAG) TYPE SRSC_S_IF_SIMPLE-INITFLAG OPTIONAL
*" VALUE(I_READ_ONLY) TYPE SRSC_S_IF_SIMPLE-READONLY OPTIONAL
*" TABLES
*" I_T_SELECT TYPE SRSC_S_IF_SIMPLE-T_SELECT OPTIONAL
*" I_T_FIELDS TYPE SRSC_S_IF_SIMPLE-T_FIELDS OPTIONAL
*" E_T_DATA STRUCTURE SFLIGHT OPTIONAL
*" EXCEPTIONS
*" NO_MORE_DATA
*" ERROR_PASSED_TO_MESS_HANDLER

Native and open sql - oracle

hi all,
<dynamic > = SELECT matnr FROM mara .
EXEC SQL.
OPEN c1 FOR <dynamic >ENDEXEC.
ENDEXEC.
can i use dynamic native sql in open sql-oracle .
cheers
senthil

EXEC SQL doesn't allow for dynamic constructs. In order to get native SQL features dynamically you can use the JDBC-like classes CL_SQL_STATEMENT, CL_SQL_CONNECTION, and so on.
Best regards
Ulrich

How to create a cluster table and cluster view?

Hi,
Can anyone guide me in creation of cluster table in general and also creation of cluster view?

Hi,
check this links.
http://help.sap.com/saphelp_nw04/helpdata/en/cf/21f0b7446011d189700000e8322d00/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/d0/999246b2aa11d1a5700000e82deaaa/content.htm
Regard's
SHAIK.

Cluster table and views

1. can i use cluster tables in my report
2. what are the views in xd01,xk01 and mm01

try to avoid using cluster tables as much as possible while coding...it takes up time and even has a performance issues....
Views of XD01
Address
Contact persons
Control data
Account Management
Partners functions
Views of XK01
Address
Control
Payment Transactions
Accounting Info
Correspondence
Withholding Tax
Purchasing data
partner functions
Views of MM01
Basic Data 1
Basic Data 2
Classification
Sales Org: Data 1
Sales Org: Data 2
General/Plant data
Foreign trade: export data
sales text
purchasing
Foreign trade: import data
purchase order text
MRP 1
MRP 2
MRP 3
MRP 4
ForecastingAccounting 1
Work Scheduling
Production Resources/Tools
General plant Data/Storage 1
General plant Data/Storage 2
Warehouse Management 1
Warehouse Management 2
Quality Management
Accounting 1
Accounting 2
Cost Estimate 1
Costing 2
Plant Stock
Storage Location Stock
Award Points...............
Message was edited by:
Ramesh Babu Chirumamilla

What are the Cluster tables and pooled tables

pls give some examples for the above table
Thankyou
ravi

Hi
<b>Pooled Table</b>
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.
<b>Cluster Table</b>
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

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

To Select the data from two table one is transp table and onther is cluster

Hi All,
I want to select the data from two tables
Here i am giving with an example.
Fileds: kunnr belnr from bseg. table bseg
fields: adrnr from kna1     table: kna1.
Know i want to put these into one internal table based on kunnr and belnr.
Thanks in advance.
Ramesh

Hi,
   U cant use joins on cluster table and BSEG is a cluster table so use FOR ALL ENTRIES for taht
refer this code
*&      Form sub_read_bsak
      text
--> p1        text
<-- p2        text
FORM sub_read_bsak.
*--Select data from BSAK Table
SELECT lifnr
         augdt
         augbl
         gjahr
         belnr
         xblnr
         blart
         dmbtr
         mwskz
         mwsts
         sgtxt
         FROM bsak
         INTO CORRESPONDING FIELDS OF TABLE it_bsak
         WHERE belnr IN s_belnr
         AND   augdt IN s_augdt.
IF sy-subrc EQ 0.
*--Sort table by accounting document and vendor number
    SORT it_bsak BY belnr lifnr.
ENDIF.
ENDFORM.                    " sub_read_bsak
*&      Form sub_read_bseg
      text
--> p1        text
<-- p2        text
FORM sub_read_bseg.
IF NOT it_bsak[] IS INITIAL.
*--Select data from BSEG table
    SELECT belnr
           gjahr
           shkzg
           kostl
           hkont
           ebeln
           ebelp
           FROM bseg
           INTO CORRESPONDING FIELDS OF TABLE it_bseg
           FOR ALL ENTRIES IN it_bsak
           WHERE belnr EQ it_bsak-belnr
           AND   gjahr EQ it_bsak-gjahr
           AND   shkzg EQ 'S'.
    IF sy-subrc EQ 0.
*--Sort table by accounting document
      SORT it_bseg BY belnr.
    ENDIF.
ENDIF.
ENDFORM.                    " sub_read_bseg

I need some working examples with pl/sql records and pl/sql tables.

i am new to pl/sql tables and pl/sql records. i need some working examples on pl/sql records and pl/sql tables from basics to hoghlevel.how to use then procedures and functions and packages.

i am new to pl/sql tables and pl/sql records. i need some working examples on pl/sql records and pl/sql tables from basics to hoghlevelThere is no such thing as PL/SQL "+tables+". This is a misnomer and creates the perception that a PL/SQL "table" is somewhat like a SQL table. Nothing can be further from the truth. The correct term is "+collection+" or "+associative array+". Compared to SQL tables, these are very primitive structures, very rigid structures, cannot scale, and can be quite expensive memory wise.
That is not to say do not use an associative array or collection. These are very useful tools.. but only when applied correctly. Like using a collection for a bulk fetch to transfer more rows between the PL and SQL engines and thus decrease context switching.
Unfortunately, quite often we see the row-by-row and slow-by-slow approach - where the developer uses SQL as an I/O only layer, pulls rows into expensive PL engine memory into record structures and arrays, and then process the rows there.
So before looking at working example (even the wrong approach's code will compile and run and work in practice), make sure that you know the fundamentals of correctly using the PL engine and correctly using the SQL engine. And these fundamentals can be summed up into a very basic rule:
Maximize SQL. Minimize PL/SQL+
Get this rule right, and you will have a sound foundation for writing performant and scalable Oracle applications.

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

Wat is the exact differences between clustered table and pooled table

hi,
can you tell me ravi...wat is the exact differences between clustered table and pooled table
with regards//
anilreddyg

Hi Anil Reddy
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
Regards
Sreeni

Cluster Tables and Open SQL

Similar Messages

Maybe you are looking for