Standard tables hashed tables

in SORT we will not use sorted tables like where we will not use STANDARD TABLES and HASDED TABLES ........CAN U EXPLAIN IN DETAIL .......

Standard Internal Tables
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Internal Tables
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Internal Tables
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
Index Tables
Index table is only used to specify the type of generic parameters in a FORM or FUNCTION. That means that you can't create a table of type INDEX.
Internal tables are not DB tables. Standard and Sorted tables in combined are basically called as Index tables and there nothing else. Here is the hierarchy
 ANY TABLE
 |
 | |
 Index Tables Hashed Table
 |
 | |
Standard Table Sorted Table
Reward points if it is usefull .....
Girish

Similar Messages

Creation of Sorted and Standard and Hashed Internal Tables ..

Hi ..
Pls specify me.. how to create .. sorted ,Standard and Hashed Internal Tables...
pls give me the full code regarding ...this ..
Thnks

Standard tables
This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.
Sorted tables
This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.
Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
Special Features of Standard Tables
Unlike sorted tables, hashed tables, and key access to internal tables, which were only introduced in Release 4.0, standard tables already existed several releases previously. Defining a line type, table type, and tables without a header line have only been possible since Release 3.0. For this reason, there are certain features of standard tables that still exist for compatibility reasons.
Standard Tables Before Release 3.0
Before Release 3.0, internal tables all had header lines and a flat-structured line type. There were no independent table types. You could only create a table object using the OCCURS addition in the DATA statement, followed by a declaration of a flat structure:
DATA: BEGIN OF <itab> OCCURS <n>,
<fi> ...
END OF <itab>.
This statement declared an internal table <itab> with the line type defined following the OCCURS addition. Furthermore, all internal tables had header lines.
The number <n> in the OCCURS addition had the same meaning as in the INITIAL SIZE addition from Release 4.0. Entering 0 had the same effect as omitting the INITIAL SIZE addition. In this case, the initial size of the table is determined by the system.
The above statement is still possible in Release 4.0, and has roughly the same function as the following statements:
TYPES: BEGIN OF <itab>,
<fi> ...,
END OF <itab>.
DATA <itab> TYPE STANDARD TABLE OF <itab>
WITH NON-UNIQUE DEFAULT KEY
INITIAL SIZE <n>
WITH HEADER LINE.
In the original statement, no independent data type <itab> is created. Instead, the line type only exists as an attribute of the data object <itab>.
Standard Tables From Release 3.0
Since Release 3.0, it has been possible to create table types using
TYPES <t> TYPE|LIKE <linetype> OCCURS <n>.
and table objects using
DATA <itab> TYPE|LIKE <linetype> OCCURS <n> WITH HEADER LINE.
The effect of the OCCURS addition is to construct a standard table with the data type <linetype>. The line type can be any data type. The number <n> in the OCCURS addition has the same meaning as before Release 3.0. Before Release 4.0, the key of an internal table was always the default key, that is, all non-numeric fields that were not themselves internal tables.
The above statements are still possible in Release 4.0, and have the same function as the following statements:
TYPES|DATA <itab> TYPE|LIKE STANDARD TABLE OF <linetype>
WITH NON-UNIQUE DEFAULT KEY
INITIAL SIZE <n>
WITH HEADER LINE.
They can also be replaced by the following statements:
Standard Tables From Release 4.0
When you create a standard table, you can use the following forms of the TYPES and DATA statements. The addition INITIAL SIZE is also possible in all of the statements. The addition WITH HEADER LINE is possible in the DATA statement.
Standard Table Types
Generic Standard Table Type:
TYPES <itab> TYPE|LIKE STANDARD TABLE OF <linetype>.
The table key is not defined.
Fully-Specified Standard Table Type:
TYPES <itab> TYPE|LIKE STANDARD TABLE OF <linetype>
WITH NON-UNIQUE <key>.
The key of a fully-specified standard table is always non-unique.
Standard Table Objects
Short Forms of the DATA Statement :
DATA <itab> TYPE|LIKE STANDARD TABLE OF <linetype>.
DATA <itab> TYPE|LIKE STANDARD TABLE OF <linetype>
WITH DEFAULT KEY.
Both of these DATA statements are automatically completed by the system as follows:
DATA <itab> TYPE|LIKE STANDARD TABLE OF <linetype>
WITH NON-UNIQUE DEFAULT KEY.
The purpose of the shortened forms of the DATA statement is to keep the declaration of standard tables, which are compatible with internal tables from previous releases, as simple as possible. When you declare a standard table with reference to the above type, the system automatically adopts the default key as the table key.
Fully-Specified Standard Tables:
DATA <itab> TYPE|LIKE STANDARD TABLE OF <linetype>
WITH NON-UNIQUE <key>.
The key of a standard table is always non-unique.
Internal table objects
Internal tables are dynamic variable data objects. Like all variables, you declare them using the DATA statement. You can also declare static internal tables in procedures using the STATICS statement, and static internal tables in classes using the CLASS-DATA statement. This description is restricted to the DATA statement. However, it applies equally to the STATICS and CLASS-DATA statements.
Reference to Declared Internal Table Types
Like all other data objects, you can declare internal table objects using the LIKE or TYPE addition of the DATA statement.
DATA <itab> TYPE <type>|LIKE <obj> WITH HEADER LINE.
Here, the LIKE addition refers to an existing table object in the same program. The TYPE addition can refer to an internal type in the program declared using the TYPES statement, or a table type in the ABAP Dictionary.
You must ensure that you only refer to tables that are fully typed. Referring to generic table types (ANY TABLE, INDEX TABLE) or not specifying the key fully is not allowed (for exceptions, refer to Special Features of Standard Tables).
The optional addition WITH HEADER line declares an extra data object with the same name and line type as the internal table. This data object is known as the header line of the internal table. You use it as a work area when working with the internal table (see Using the Header Line as a Work Area). When you use internal tables with header lines, you must remember that the header line and the body of the table have the same name. If you have an internal table with header line and you want to address the body of the table, you must indicate this by placing brackets after the table name (<itab>[]). Otherwise, ABAP interprets the name as the name of the header line and not of the body of the table. You can avoid this potential confusion by using internal tables without header lines. In particular, internal tables nested in structures or other internal tables must not have a header line, since this can lead to ambiguous expressions.
TYPES VECTOR TYPE SORTED TABLE OF I WITH UNIQUE KEY TABLE LINE.
DATA: ITAB TYPE VECTOR,
JTAB LIKE ITAB WITH HEADER LINE.
MOVE ITAB TO JTAB. <- Syntax error!
MOVE ITAB TO JTAB[].
The table object ITAB is created with reference to the table type VECTOR. The table object JTAB has the same data type as ITAB. JTAB also has a header line. In the first MOVE statement, JTAB addresses the header line. Since this has the data type I, and the table type of ITAB cannot be converted into an elementary type, the MOVE statement causes a syntax error. The second MOVE statement is correct, since both operands are table objects.
plz reward if useful

How to,Pass HASHED table data to STANDARD table

i have itab1 as Hashed.
when i pass this as out put table for
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
it gives me error,saying hashed type cannot be used..
please suggest the remedy..

IT_DEV2[ ] = IT_DEV[ ].
seems to be right..it works fine in this code....but if the selected records are huge it gives irrelevant values
REPORT ZMONTHLY_STOCK .
DATA : IT_DEV TYPE ZBIW_MNTH_STK_L .
DATA : IT_DEV2 LIKE STANDARD TABLE OF ZBIW_MNTH_STK.
*Selection-Screen
Parameters : LFMON type LFMON obligatory,
 LFGJA type LFGJA obligatory,
 BWKEY type BWKEY.
START-OF-SELECTION.
 SELECT e~MATNR e~BWKEY e~LFGJA e~LFMON e~LBKUM e~SALK3 l~MTART
l~MATKL l~MEINS f~WAERS FROM
 MBEWH AS e INNER JOIN
 MARA AS l ON e~MATNR = l~MATNR
INNER JOIN
 T001K AS n ON e~BWKEY = n~BWKEY
INNER JOIN
 T001 AS f ON n~BUKRS = f~BUKRS
 INTO CORRESPONDING
 FIELDS OF TABLE it_dev
 WHERE
 e~LFGJA EQ LFGJA AND e~LFMON EQ LFMON.
IF SY-SUBRC = 0.
IT_DEV2[] = IT_DEV[].
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
 I_CALLBACK_PROGRAM = SY-CPROG
 I_STRUCTURE_NAME = 'ZBIW_MNTH_STK'
 TABLES
 T_OUTTAB = IT_DEV2.
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDIF.

Internal Table Types (Standard, Sorted, Hashed)

Hi all,
I wonder about using internal table types. I always work with standard table type. I don't know when i have to use the standard, sorted or hashed itab type. Is there limits for line counts of types, like over 200.000 lines use hashed table type etc. ? I need performance improvements for itabs.
Thx,

the terminology of internal tables is unfortunately quite confusing:
internal tables use 'index' for the row number of the line in the table, if you know then you can access it directly. It is actually the sy-tabix variable which you have to know.
Things which are called index on the database are called keys, i.e. the sorted primary key of a SORTED table or the hashed primary key of a HASHED table (the technical realization is actually called index).
With the newest basis release (7.02 or 7.20) there are also secondary keys possible on internal tables, for all 3 types.
Siegfried

Generic standard table type

Anybody please resolve my doubt
types tb_std_type type table of sflight.
-->this i understand as not a generic table type.'NON-UNIQUE" and DEFAULT KEYS are implicity defined .
data it_std type tb_std.-->Since i could declare an internal table of tb_std_type,i strongly belive tb_std_type is not a genric table type.
But when i try to declare another type of same table type tb_std_type ie
types tb2_type type tb_std_type.
This is giving me an error saying\
tb_std_type has a generic type.Use of this type is only possible for typing field symbols and formal parameters.
If thats true then how was i able to create a internal table out of it...
In case of sorted and hashed tables it behaves as exactly as it is defined.(Like if generic,can only be used for typing formal params.field symbold..and if non generic--internal tables declaration and normal typing is possible)
Please resolve this
*Would be great if could avoid a copy paste from std.help..because i have been through it..

Hello Teenu,
Query#1
types tb2_type type tb_std_type.
This is giving me an error saying\
tb_std_type has a generic type.Use of this type is only possible for typing field symbols and formal parameters.
Why is the table generic? An excerpt from SAP documentation clearly states that:
An internal table that has no table key or an incomplete table key is generic with respect to the table key. A table type of this nature can be used only for typing formal parameters or field symbols.
Query#2
If thats true then how was i able to create a internal table out of it...
SAP says:
A standard table type with a generic primary table key can only be specified after TYPE when DATA is used.
Source: [http://help.sap.com/abapdocu_70/en/ABAPTYPES_KEYDEF.htm|http://help.sap.com/abapdocu_70/en/ABAPTYPES_KEYDEF.htm]
BR,
Suhas

Size Category of a standard table - - Urgent

Guys,
Suppose the data in the table exceeds the size category of the table defined, will there be any problem??
Is there any possibility of changing the size category of the standard table??
Regards
Jiku

Hi,
Internal tables
Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and
formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects. A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
Internal Tables as Dynamic Data Objects
Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2
gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.
Regards,
Bhaskar

Can we insert data directly in standard table

hi
how can we insert data in standard table directly.
pls reply urgently.

Hi sapna yes u can insert data to the SAP tables, as shown below...
use the table mara in the place of m
REPORT ZTEST_INSERT.
TABLES: <m>.
DATA: wa_m TYPE <m>.
wa_m-ernam = 'ZTEST'.
insert into <m> VALUES wa_m.
if sy-subrc = 0.
WRITE / 'Records inserted Successfully'.
ENDIF.
reward if usefull,
Vishnu. R
Edited by: vishnu ramanathan on Sep 18, 2008 2:17 PM

Can we enter data in any standard table directly through custom form??

Dear All,
Can we enter data in any standard table directly through custom form??
I have create custom form in R.12. I want to insert data in quality standard table directly through custom form. Need experts guideline.
Awaiting regards,

Hi,
Can we enter data in any standard table directly through custom form??
I have create custom form in R.12. I want to insert data in quality standard table directly through custom form. Need experts guideline.
Awaiting regards,
I would not recommend touching the standard tables at all unless you are being guided by the SR. For a record to be in the standard table it should go through series of validations based on the what operation you are performing and some times datas are dependent upon the other tables, and also some times the same records are hit to so many other tables simultaneously.
Therefore I would not recommend this brother.
Thanks &
Best Regards,

Standard table for finding query where used list

Are there any standard tables available to find the list of web templates, bex reports and views using a particular query?
i.e if i have the query name i should be able to find out where all it is being used.
Thanks,
Archna

Hello,
You have to join multiple tables to achieve this, here we go
FOR QUERY Related Information
RSRREPDIR - Directory of all reports (Query GENUNIID)
Choose Type of a reporting component -> REP
Tips :
Choose Type of a reporting component -> QVW for query view
SE11 -> RSZ* -> F4 gives you all tables related to queries
For WORKBOOK Related Information
Use the FM RRMX_WORKBOOK_QUERIES_GET to get the queries in a workbook by selecting the workbook ID from table RSRWORKBOOK
Tips :
SE11 -> RSRWB* -> F4 gives you all tables related to workbooks
SE37 ->RRMX_WORKBOOKS* -> F4 gives you all the FM related to workbooks
For Webtemplate Related Information
Choose the dataprovider for query / view ID.
SE11 -> RSZWOBJXREF - Structure of the BW Objects in a Template
Also see,
SE11 - > RSZWTEMPLATE - Header Table for BW HTML Templates
Thanks
Chandran

How do I read this "standard" table in my Function Module?

I have a remote-enable Function Module (RFC). I am receiving two tables as part of the parameters. Table "A" is header information, and Table "B" is detail information. So for every 1 "A" header record, I may have 1 to many "B" detail records. I have a field we'll call "vendor_number" that is the common link between the two tables.
Here's what I want to do: I want to loop through table "A", and for each record, I want to do a READ on table "B", using the "ref_doc_no" from "A" as my key, to get the position of the first matching record. I hold onto the value of the table index and then start looping table "B", adding 1 to the saved table index each time to process all of the detail records.
Here's the problem: This worked great as an ABAP program. I had my "B" table declared with "ref_doc_no" as a non-unique key. But when I ported my code over to the RFC, it told me that the RFC could only deal with standard tables. I had to remove the "ref_doc_no" key declaration. So now when I try to activate, I get an error similar to this:
The declaration for the key field "another_field" is incomplete; however, "another_field" is contained in the key of table "B" and must be filled.
I don't understand that. I've not declared any keys for table "B". I don't understand why it's thinking I need to populate "another_field" (I don't even know what the value would be). My code to read the table (i.e. the line getting the error) is this:
Priming read on table (sets the initial sy-tabix index value)
    READ TABLE it_incoming_invoice_line_item "table 'B'
      WITH TABLE KEY ref_doc_no =
                     wa_incoming_invoice_header-ref_doc_no
                INTO wa_incoming_invoice_line_item.
Is it possible for me to do some sort of direct read on a table in an RFC? The only alternative I can think of would be to have to loop through table "B" until I find the first occurrence of a match. Is that what I need to do?
Thanks everyone. Points, as always, awarded for helpful answers.

Dave,
1. You can fire SELECTS in an RFC as well, but in your case the data exists in SYSTEM A and the RFC is in System B, so you can't do that. You can fire SELECTS on tables in the same system.
2. Quick example of two table loops - EKKO (HEADER) EKPO (ITEM).
LOOP AT EKKO.
LOOP AT EKPO WHERE EBELN = EKKO-EBELN.
ENDLOOP.
ENDLOOP.
I hope this is clear now.
Regards,
Ravi

Changing field length of a standard field in standard table VBEP

Hi,
Please advice the possibility and the possible repercussions of changing field lengths in a standard table. Table in concern is VBEP.
Thanks & Rgds,
Pradeep

No you cannot change the field length
thanks
G. Lakshmipathi

Maintenance view on the standard table

Hi,
We need to have a maintenance view on the standard XYZ table .
Since it is a std table. we would not be able to create a maintenance view since we need an access key.
So we have to :
1. Copy the table XYZ into a Z_table. (just the structure alone).
2. Create a table maintenance generator on this table.
3. When the data is being saved in the maintenance view, update the record in the XYZ.
How we can populate the XYZ when the Z_table is populated with data?
Can anyone help in this regard.
Thanks and regards,
Kapil

Hi Rich,
Thanks for your reply.
I am referring to standard table "comc_settyp_attr" in SAP-CRM system . I have copied it and created a z_table. But its not allowing me to create a maintainance view. Its giving an error :
GUID in table key (Field name CUSTINFO) not supported.
But when i create the z_table without the GUID(char 32) as key field, it generates table maintenance. But the key field is required.
Can you help me in this regard.
Regards,
Kapil

Regarding creation of a standard table

Hi,
In my landscape, somebody deleted a standard table in one of my systems. when i am trying to access this table it is throwing an error message stating that table does not exist. check name.
Now i want to know how to create this standard table and how to get the structure of that table.
kindly help me regarding this issue.
thanks & regards,
eeswar

Hi
Well the solution you are thinking for this problem, doesn't seem to be a right way to me. Although recreation is no where possible for standard table, you can carry out transport.
As the table is standdard one, and deleted you should rather think of restoring your backup. Because even if you transport it from one system to other, the data missing from your active server cannot be recovered and system can become inconsistent.
So think about it once. Before applying transport.
Regards
Rahul

What are the standard tables for plant maintenance in r/3

I need the list of standard tables for plant maintenance in r/3. and also
is there any way we can find the field name and table which it belongs to in r/3, based on the description of the field.

I NEED THE FIELD NAMES FOR FOLLOWING FIELDS AND CORRESPONDING TABLE NAMES
Equipment status
registration number
insurance type
insurance type description
registration date
expiry date
insurance companies
expiry date
policy number
amount insured
premium paid
created by ..so ..on
for our report in PM .. insurance data report
THANKS

How to change the lenth of existing field in sap standard table

Hi all,
can anybody help,my requirement is, how to change the length of existing field in sap standard table....
thanks in advance..

Which field are you thinking of in particular? Are you wanting to increase or decrease the length?
Some fields are used so extensively that a change to their length will mean adjusting many tables, some of them potentially very large, and hence taking a long time to adjust.
Some standard SAP programs expect certain fields to be of specific lengths and won't work if the length is changed.
Some screens could cease to work.
If you decrease length, then you could lose data.
matt

Standard tables hashed tables

Similar Messages

Maybe you are looking for