topic difference between line type and table type in Application Development and Automation Discussions

difference between line type and table type

Former Member — Wed, 05 Mar 2008 08:42:54 GMT

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

Re: difference between line type and table type

Former Member — Wed, 05 Mar 2008 08:49:32 GMT

hi,

This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the ABAP Dictionary.

Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.

TYPES type TYPE|LIKE tabkind OF linetype

After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:

tabkind OF linetype

The type constructor defines the table type tabkind, the line type linetype, and the key key of the internal table type.

You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.

Line Type

For the line type linetype, you can specify:

· Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the ABAP Dictionary. If you specify any of the generic elementary types c, n, p and x , any attributes that you fail to specify (field length, number of decimal places) are automatically filled with the default values. You cannot specify any other generic types.

· Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and structures in the ABAP Dictionary (for compatibility reasons).

All of the lines in the internal table have the fully-specified technical attributes of the specified data type.

Hope this helps, Do reward.

Re: difference between line type and table type

Former Member — Wed, 05 Mar 2008 08:53:39 GMT

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 = 'user@company.com'. "<-- 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.

Re: difference between line type and table type

sreelatha_gullapalli — Wed, 05 Mar 2008 08:56:45 GMT

for line type

http://help.sap.com/saphelp_nw2004s/helpdata/en/68/b0e7418192c717e10000000a155106/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/fc/eb366d358411d1829f0000e829fbfe/content.htm

for table type

http://help.sap.com/saphelp_nw70/helpdata/en/90/8d72fbb1af11d194f600a0c929b3c3/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm

hope it will help you.

Regards,

Sreelatha Gullapalli