Calrification of structure and table type

hai experts,
what is the difference between STRUCTURE AND TABLE TYPE?

Refer this for TABLE TYPE
http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm
STRUCTURE
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb2d74358411d1829f0000e829fbfe/content.htm
SE11, In structre u <b>cant maintain any values</b>. Its just used as a refernce.
In tables u can maintain values.

Similar Messages

Difference between Table and Table Type

Hi
Can you please let me know the
Difference between Table and Table Type and
Difference between Structure and Table Type?
Regards,
Sree

hi,
table is a data dictionary object in sap. table is of different types
1. transparent tables
2. pool tables
3. cluster tables
table type gives option for u to select different types of internal tables. they r
1. standard table
2. sorted table
3. hash table
Structures :
-Defined like a table and can then be addressed from ABAP programs.
-Structures contain data only during the runtime of a program.
-Just like user-defined data type.
- they are not present in database server and only on application server.
if helpful reward some points.
with regards,
Suresh Aluri.

Differrences between structure and table in data dictionary in ABAP?

What is the differrences between structure and table in data dictionary in ABAP?
are they same?

Tables :
1. The place where the data is stored so that you can retrieve at any time.
2. There can be more than one record stored
Structures :
1. The data / info stays only during the runtime of the application and will not get stored at all during the run time ....
2. Only one record can be stored at the runtime .....
A structure forms the skeleton of the table.
A structure comprises components i.e., fields. Types are defined for the components A component can refer to an elementary type (via a data element or by directly specifying the data type and length in the structure definition), another structure or a table type. A structure can therefore be nested to any depth
Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined with their (database-independent) data types and lengths.
When the table is activated, a physical table definition is created in the database for the table definition stored in the ABAP Dictionary. The table definition is translated from the ABAP Dictionary to a definition of the particular database.

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
                        "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
                        types : begin of ts_reclist,
mso-bidi-        style='mso-tab-count:2'>                            receiver type somlreci1-receiver,
mso-bidi-        style='mso-tab-count:2'>                 style='mso-tab-count: 1'>             rec_type type somlreci1-rec_type,
mso-bidi-         style='mso-tab-count:2'>                            end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal">                         types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
                       data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]>   <![endif]>                         data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
                        s_reclist-receiver = '[email protected]'.   "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi-                         s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
                        append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1">           style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                        EXPORTING
style='mso-tab-count:2'>                                    document_data = docdata
style='mso-tab-count:2'>                                    DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'>                                    PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'>                                    COMMIT_WORK = 'X' "used from rel.6.10
                        TABLES
mso-bidi-font-size: style='mso-tab-count:2'>                                    receivers = t_reclist
class="style1"> <![if !supportEmptyParas]>   <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

Calling Oracle Stored proc with record type and table Type

I have a oracle SP which takes record type and table Type which are used for order management.
Is there anay way to populate parameters with these datatypes and call the stored procedure using ODP.NET?
Please help.
Thanks in advance

Hi,
ODP supports associative arrays and REF Cursors. There is no support for PLSQL table of records.
Jenny

How does a record type and table type works

Hi,
How a record type and table type work for the ref cursor,
below i m giving an example but its giving me errors
can any one help me for this?
declare
type empcurtyp is ref cursor;
type rectype is record (veid t.emp_id%type, vename t.ename%type);
TYPE tabtype IS TABLE OF rectype;
empcv empcurtyp;
vtab tabtype;
begin
open empcv for select emp_id,ename from t;
loop
fetch empcv into vtab;
exit when empcv%notfound;
dbms_output.put_line(vtab.vename||vtab.veid);
end loop;
close empcv;
end;
here we hav table t and i m taking only two fields of the table t which r emp_id and ename.

Hi,
What errors are you getting with this? From experience you don't need a loop to put the records into the ref cursor its usually done on block.
HTHS
L :-)

Extractor andExtract structure and table Relation

Hi All,
Is there any system table which provides the Datasource/Extractor/ Extract
structure and table Relation Information.
For ex:
Data source 2LIS_02_ITM uses following tables for data
EKKO
EKPO

Hi Murali,
I'm not really sure if there exists a table to give the information that you've asked for...
Let me to tell you something to find out the tables referred in a datasource.
Execute your datasource in RSA3 in Debug mode. This will give you the details of the tables used by that datasource.
assign points if useful ***
Thanks,
Raj

How can we use IMPORT-EXPORT as structure and TABLES parameters?

Hello Sir,
I have used SAPRFC with single IMPORT and EXPORT parameter.
Could anybody give me an example in I can use IMPORT/EXPORT as structure and TABLE parameter as input?
of course from/to PHP.
Regards,
RH

Thanks

Definitions of record and table type

Im confused with the definition of record and table type. Below is my understanding, Please correct me if anything wrong. Thanks in advance!
Record type can only hold one record with multiple fields.
Table type is an array (multiple records) with only one field
Table type defined with %rowtype (table of records) is an array of multiple records with multiple fields.

I am not sure that I understand what you are asking. I have not heard the term table type before.
However, I think a record type is more closely aligned to the %rowtype declaration. Maybe a collection is what you are looking for with the term table type.
From the Oracle 10g documentation:
%ROWTYPE
In PL/SQL, records are used to group data. A record consists of a number of related fields in which data values can be stored. The %ROWTYPE attribute provides a record type that represents a row in a table. The record can store an entire row of data selected from the table or fetched from a cursor or cursor variable.
Columns in a row and corresponding fields in a record have the same names and datatypes. In the example below, you declare a record named dept_rec. Its fields have the same names and datatypes as the columns in the dept table.
DECLARE
dept_rec dept%ROWTYPE; -- declare record variable

How could I retrieve metadata about Array Type and Table Type?

I use DatabaseMetaData.getUDTs() method for obtain metadata about Object Types, but this method doesn't work with Array Type and Table Type.

JJ,
Go into the diagrams of the DBTools List Columns and DBTools Get Properties respectively. When you inspect this diagram, you will see the raw ActiveX properties and methods called to get the size information. The value of -1 means the requested recordset is already closed. This is the sort of thing that is controled by the driver (ODBC, OLE DB, Jet, etc) you are using. Notice that you can right click on the property and invoke nodes and get more information about these specific items directly from the ADO online help.
Crystal

Defining Record and Table Types

Is there a good tutorial out there somewhere that provides good examples on how to define and work with Record and Table Types? How to define and work with an entire record or table as opposed to just a variable?
For instance- I'd like to create a cursor of records from a table, loop through each record to examine variable values, and in some instances insert those entire records into another table.
Thanks in advance for any suggestions.

Oracle documentation is excellent (Lots of live examples that can be cutNpaste) place to start.
http://download.oracle.com/docs/cd/B10501_01/appdev.920/a96624/05_colls.htm
Is there any thing specific you are looking for?
vr,
Sudhakar B.

Difference between Info structure and Table

Hi Friends
I need to know difference between info structure and table (updating a table using a scheduled program),Which one of this is better and why?
Please help me to get the Pros and Cons of the two available approach.
Thanks
Mitesh

Hi,
No different, these are just transparent tables like any other. You can select data from them the same as any other transparent table.
Refer
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=1424611
https://forums.sdn.sap.com/click.jspa?searchID=4342729&messageID=3609095
Regards

Structure or Table Type ??

Hi Epxerts,
Can someone give me an idea of passing multiple records in the parameter it_prxkna1 which of type structure as in code below :
I am working on this to pass it to XI.
Note : it_prxkna1 contains a 3 more nested structures and not an internal table.
Should it_prxkna1 be a table type or structure to hold multiple records?
TRY.
Assign row
    it_prxkna1-MT_KNA1-record-row = wa_zcaap. --> one record of a customer
loop at t_zcaap into wa_zcaap.
    CALL METHOD kna1_prxy->execute_asynchronous
      EXPORTING
        output = it_prxkna1.
    COMMIT WORK.
endloop.
CATCH cx_ai_system_fault .
    DATA fault TYPE REF TO cx_ai_system_fault .
    CREATE OBJECT fault.
    WRITE :/ fault->errortext.
ENDTRY.
Please suggest.
Thanks
Dany
Edited by: Dan on Apr 11, 2008 9:42 AM

You can append even if it is structure.
check the code below,
REPORT ZTEMPB_TEST7.
types: begin of st1,
       s1 type c,
       s2 type c,
       end of st1.
types: st2 type st1 occurs 1.
data: begin of itab,
      f1 type c,
      f2 type st2,
      end of itab.
data: wa_f2 type st1.
wa_f2-s1 = '1'.
wa_f2-s2 = '2'.
append wa_f2 to itab-f2.
Here ST1 is the structure with 2 fields.
ST2 is table type with the structure ST1.
f2 is the structure in the structure jtab with table type ST2.
But ST2 must be internal table.
Regards,
Bhanu
Edited by: Bhanu P on Apr 11, 2008 4:23 PM

Define structure with table type fields using keyword "TYPES"

Hi Gurus,
Using keyword "TYPES", I want to define a structure in which there is a field must be table type. It seems not allowed. For example:
    TYPES tt_items TYPE TABLE OF sflight.
    TYPES: BEGIN OF str,
      field1 TYPE i,
      field_tabl TYPE tt_items.
    TYPES: END OF str.
Then I got a syntax error:
"TT_ITEMS" is a generic type. Use of this type is only possible for     typing field symbols and formal parameters. -
What should I do if I want to have a table type field in it?
Thanks a lot.

include type EKKO includes the whole strucutre of EKKO.
if you see the structure in debug mode, it_ekko contains the fields of EKKO as well as the field CHK of type C.
In your case you can do this
TYPES: BEGIN OF str.
INCLUDE TYPE sflight. " includes whole structure of SFLIGHT
TYPES : field1 TYPE i. " include the field1 of type I
TYPES: END OF str.
DATA : it_str TYPE TABLE OF str, " internal table
       is_str TYPE str.          " work area
Regards
Gopi

Purpose of Row type, line type and Table Type..

Hi All,
Just Im started working with OOABAP. Whenever I open some structures, most of the components in the structures have the below three words. What is the exact difference b/w the below words. What is purpose those?
Row type, line type
Table type:
Please let me know.

hi,
Line Type
The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
Table type
The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.
Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional 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. When you define the table, you must specify whether the key is to be UNIQUE or NON-UNIQUE. Standard tables and sorted tables are known generically as index tables.
Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.
The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
At tables with structured row type, the standard key is formed from all character-type columns of the internal table. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty. At tables with non-structured row type, the standard key consists of the entire row. If the row type is also a table, an empty key is defined.
The user-defined key can contain any columns of the internal table that are no internal table themselves, and do not contain internal tables. References are allowed as table keys. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.
Internal tables are always completely specified regarding row type, key and access type
Hope this helps.

Calrification of structure and table type

Similar Messages

Maybe you are looking for