Hi I want to know the difference between the type of internal tables.

I know the types of internal table but i dont know the difference between them can any one explain me in simple sentence.

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

Similar Messages

Difference between line type and internal table?

Hi..
I wanted to know, what is the difference between Line type and Internal Table?

Hi,
Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure we need to create a Line type for that structure in Se11 and then we can define the internal table like :
DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
Only thing is this table will be a table without header. So for internal table processing we need to define a work area structure of type line of line type . EX:
DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
Hope this helps.
Thanks,
Greetson

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

Want To Know The Name OF Company Table

In Administration -> Choose Company, It gives me the list of all Company Name,Database Name,Version etc .
I Want to know the Table Name which has all information about company name and all.
Regards

The db version is stored in table CINF (Version). Others information gave you members already. If you want have list of all dbs on the server like in login screen, you should use select from information schemas as
select * from information_schema.tables where table_name = 'CINF'
and youll receive all databases, where the CINF table is, then create tmp table (dbname, company, version fields) and in cursor go through all results from select * from information_schema.tables where table_name = 'CINF'
make insert into this tmp table. At the end make select from this tmp table.

How to know the length of internal table...

Hello experts,
How can I know the line size of my internal table since it will be dynamic
and I am just writing my report manually(not ALV) so I will be using sy-uline,
sy-vline, sy-linsz, etc.
So I can declare my sy-ulines according to the total length of my output.
Also, is this possible in ALV:
Header 1               *
      Header 2             *
         -OUTPUT-
Thanks again!

Hi
You can use the DESCRIBE statement to get the number of lines in an internal table:
DATA: num_lines TYPE i.
DESCRIBE TABLE itab LINES num_lines.
num_lines will now hold the number of lines in your table.
I don't believe you can have multiple header rows in ALV you will probably need to group your records or summarise them to achieve a similar result.
Hope this helps
Andy
Message was edited by: Andrew Wright
Sorry, I misunderstood your requirement, using the DESCRIBE TABLE statement will fill the system field sy-tleng with the line size so immediately after doing DESCRIBE... just pass sy-tleng to an integer type variable.
Kind regards
Andy

Problem in uploading the file of internal table into appliaction server

i want to send the data of internal table to application server through selection screen and in selection screen and in selection screen parameter it should show the path of application server and through that path internal table data should go to application server , if possible give the code

Hi,
form download_file_appl_server.
open dataset p_dlf2 for output
          in text mode encoding default .
if sy-subrc ne 0.
    message:i005 with text-415 text-407.
endif.
loop at i_final into wa_final.
    transfer wa_final to p_dlf2.
endloop.
close dataset p_dlf2.
endform.                    " OPENDATA_CLOSE
where p_dlf2 is the seelction screen parameter which give the application server file path
You can use this code for ur purpose.
Reward if useful.
Regards
Shibin

I want to know the difference between Days column and Day1 Column

Hi All,
I used this query:
SELECT to_char(return_date_time,'dd/mon/yyyy hh24:mi:ss') Test,
DECODE ('I', 'I', DECODE (1, NULL, NULL, 0, NULL, SYSDATE + 1)) Days,
DECODE ('I', 'I', SYSDATE + 1) Day1
FROM fm_curr_locn
WHERE patient_id = 'DU00002765'
output:
Test
Days
Day1
26/oct/2013 00:00:00
26-OCT-13
10/26/2013 3:06:59 PM
I want to know the difference between Days column and Day1 column and why the days column didnt show the time
Please anyone help.....
Regards
Shagar M

Pleiadian wrote:
It is the decode statement that is doing this.
The format of decode is:
decode(expression, search1, result1, search2, result2, searchn, resultn, default)
All result fields must be of the same datatype and will be of the datatype of the first result (result1 in this example)
In your example (the decode for the field Days) the first result is a NULL. I suspect (gurus? anyone?) that Oracle will use the varchar2 overload of the decode statement, and the date field will be converted to varchar2 using your NLS_DATE_FORMAT settings.
In the second decode statment (Day1) the first result is of datatype date, so the result of the decode statement will be a date field (and will be parsed as such by your sql development tool)
I agree, as NULL is the first result returned the datatype is undetermined, so Oracle is picking VARCHAR2 over others, and causing an implicit datatype conversion on the resultant date value, whereas the other which is returned as a date will use the local settings of the client tool being used.
I can replicate the 'issue' in Toad, and it's rectified if we cast the first returned value of the decode statement...
SELECT DECODE ('I', 'I', DECODE (1, NULL, CAST(NULL AS DATE), 0, NULL, SYSDATE + 1)) Days,
DECODE ('I', 'I', SYSDATE + 1) Day1
FROM dual

I want to know the difference between iphoto master folder and previews folder

I want to know the difference between iphoto library master folder and previews folder.. my pictures is stored in master but part of them is also copied into previews.. it occupied too much space.. if I can't change anything in iphoto library, any way to save the space for iphoto? 70G for almost 15,000 pictures, is it reasonable?
i use mac book pro, ilife 11..

70GB for 15,000 photos is reasonable, yes, if the photo files are large.
DO NOT meddle with the contents of your iPhoto Library in any other way than using the commands available in the iPhoto application. What appear to be duplicate files stored in different parts of the library are NOT duplicates, and if you attempt to save space by deleting things in the Finder, you will wreck your library and land in a world of trouble.

Want to know the difference among the sap standard schemas TM00/TM01/TM04

hi, experts
i have read the standard courses HR310 and HR311,but i am still confused about the difference among the three standard TM schemas TM00,TM01 and TM04.
i only learn from the book about it as follows:
TM00: Time evaluation with time events
TM01: Time evaluation for work schedule deviations
TM04: Time evaluation for times entered as hours.
i want to know the details about different forms of time data and different strategies in evaluating the time data in the three standard schemas.
thanks in advance

Hi,
TM01: read the actual data, Automatically calculate the overtime with the help of events.
TM04: Negative time evaluation, Get the data from the Work schedules
TM01: Positive/Negative time evaluation: Read the exception of workschedules, get the data from the time events form the 2011IT.
TM01:
Schema TM01 can be used for time evaluation if you only record
exceptions to the work schedule, and not all times that count as working
time (actual times).
You can use schema TM01 to import and process time data that has been
recorded online.
The schema forms time balances, time wage types, and time quotas, and is
processed using the time evaluation driver, RPTIME00.
The valuation basis for time evaluation forms a planned pair, which is
generated according to the planned specifications in the employee's
personal work schedule.
The planned pairs generally correspond to the time worked. Only
attendances from infotype 2002 and absences from infotype 2001 result in
a difference between planned and actual.
Schema TM01 automatically generates overtime for all attendance times
recorded over and above the planned specifications in the personal work
schedule. If overtime is recorded in infotype 2005, it can be approved
systematically taking account of overtime breaks.
TM00:
Schema TM00 processes time events that have been recorded at a time
recording terminal, or the time pairs formed from the time events in
pair formation. Attendances and absences are also imported.
Schema TM00 is based on positive recording of time data, that is,
recording all times that count as working time (actual times).
Schema TM00 only evaluates time data with clock times (or full-day
records). The main task of schema TM00 is to classify the actual times
by comparing them to the planned specifications in the daily work
schedule (start and end of planned working time, core times, breaks, and
so on).
TM04:
The time worked by the employee is recorded in the Attendances infotype
(2002), and not as clock-in and clock-out times. When processing
clock-in/out times, the emphasis is on the length of time between the
postings and not on the times at which the postings were made.
You can use schema TM04 to process attendances and absences that specify
a number of hours only, rather than concrete start and end times.
The times stipulated in the daily work schedule are not relevant. Only
specifications such as planned hours and minimum daily working time are
evaluated from the daily work schedule.
TM04 caters both for negative time recording (recording of exceptions to
the work schedule) and positive time recording (recording all
attendances or actual times).
If negative recording is used, the planned hours are generated on the
basis of the daily work schedule. Recorded absences and some attendance
times are deducted (see schema TP01.)
The "Time Management status" indicator in the Planned Working Time
infotype (0007) shows whether all actual times are recorded for an
employee, or only exceptions to the planned specifications.
Regards:
Devi.

Im using a pci-6221 daq-card.I want to know the difference(use)of a line output and a port output.

Im using a pci-6221 daq-card.I want to know the difference(use)of a line output and a port output.

Hello Hellraiser24,
This question has actually been discussed in another thread here:
http://forums.ni.com/ni/board/message?board.id=170&message.id=95895&requireLogin=False
I hope this helps,
E.Lee
Eric
DE For Life!

I want to know the relation between Retiremen in assets and AR

i want to know the relation between Retiremen in assets and AR
whene selleing asset in FA and retire it in AR

Hello.
how can i achieve this entry in AR You will have to create it manually. The system does not create it automatically.
and is their any report in FA to identify the sold assetsThe Asset Retirement Report
Octavio

I want to know the versions in SCM and the latest versions

Hi everyone
I want to know the difference between last 2 SCM version. Actually i am an abaper and doent know much about scm , I am want to know about it . Please help .
Thanks
Bharathi.

Hi,
See this links,
http://www.scmexpertonline.com/archive_index.cfm?session=&volume=Volume_03_(2005)
http://www-03.ibm.com/systems/storage/solutions/sap/pdf/hot_standby.pdf
Regards,
Jagadish

Tables r occupying around 12GB.i want to know the space occupied by indexes

Tables r occupying around 12GB.i want to know the space occupied by indexes.
Is there any relation between data tablespace and index tablespace.??

well, in _segments you have all the segments, just filter on the type (index) and SUM that. That's what I would do anyway.

What is the difference between standard,sorted and hash table

can anyone say what is the difference between standard,sorted and hash tabl

Hi,
Standard 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 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 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.
Regards,
Ferry Lianto

What is the difference between message type and element

hi,
When we create a new variable in BPEL we get the option to create 'simple', 'message type', 'element'
I would like to know what is the difference between message type and element.
thanks
Yatan

A message is part of the service and is usually assigned to one of the operations in the wsdl. For example getPhoneNumer() operation may have an input message of personInput and output of phoneNum. These messages would have a type...maybe of string or decimal or a complex type with multiple values.
An element is typically a complex type that could be defined in an xsd file.
When you create a variable in the bpel, you can declare it as a message or a simple type or an element. As I understand it, the simple types are pre-defined in the schema namespace such as string, decimal, date, etc.
The elements are defined in the xsd files or wsdls and can be a combination of strings, dates, etc or other stuff as well.
The messages are defined in the wsdl as part of the input/output but they are typically assigned a type just like other variables you create.

Hi I want to know the difference between the type of internal tables.

Similar Messages

Maybe you are looking for