<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ABAP structure in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474991#M557030</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A structure is just a list of fields defined under a name. Structures are useful for painting screen fields, and for manipulating data that has a consistent format defined by a discrete number of fields.&lt;/P&gt;&lt;P&gt;Structure in ABAP can not store data.&lt;/P&gt;&lt;P&gt;at DDIC level both are same but a table in SAP has mapping&lt;/P&gt;&lt;P&gt;to a table in the underlying database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: begin of emp_info,&lt;/P&gt;&lt;P&gt;emp_name(20) type c,&lt;/P&gt;&lt;P&gt;emp_age(3) type n,&lt;/P&gt;&lt;P&gt;end of emp_info.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 29 Jun 2007 05:09:30 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-06-29T05:09:30Z</dc:date>
    <item>
      <title>ABAP structure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474989#M557028</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hai .....&lt;/P&gt;&lt;P&gt;What is the advantage of structures? How do you use them in the ABAP programs? can u explain this with an example?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 05:02:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474989#M557028</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T05:02:16Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP structure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474990#M557029</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Strucutre's are usful in grouping the related data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That is if you want to represent a bank account it makes sense that we group all the required information and then use it as a DATA TYPE.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So strucutre are a way of creating  user defined data types to group related information.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;USE:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: struct type SPFLI,&lt;/P&gt;&lt;P&gt;          internal_ table type table of SPFLI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now you can store records of the table SPFLI in internal_table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And then you can LOOP trhough the internal table and get one record at a time into the strucutre as follow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOOP AT internal_table into struct.&lt;/P&gt;&lt;P&gt;*struct will have the copy of a record for every loop pass&lt;/P&gt;&lt;P&gt;ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 05:06:08 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474990#M557029</guid>
      <dc:creator>seshatalpasai_madala</dc:creator>
      <dc:date>2007-06-29T05:06:08Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP structure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474991#M557030</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;A structure is just a list of fields defined under a name. Structures are useful for painting screen fields, and for manipulating data that has a consistent format defined by a discrete number of fields.&lt;/P&gt;&lt;P&gt;Structure in ABAP can not store data.&lt;/P&gt;&lt;P&gt;at DDIC level both are same but a table in SAP has mapping&lt;/P&gt;&lt;P&gt;to a table in the underlying database. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: begin of emp_info,&lt;/P&gt;&lt;P&gt;emp_name(20) type c,&lt;/P&gt;&lt;P&gt;emp_age(3) type n,&lt;/P&gt;&lt;P&gt;end of emp_info.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 05:09:30 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474991#M557030</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T05:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP structure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474992#M557031</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;structures we can use as a work area.&lt;/P&gt;&lt;P&gt;for example see the structure  SCREEN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this structure we can use for changing the fields in the screens.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;see this example.&lt;/P&gt;&lt;P&gt;parameters:i_matnr like mara-matnr,&lt;/P&gt;&lt;P&gt;i_mtart type mara-mtart.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;at selection-screen output.&lt;/P&gt;&lt;P&gt;loop at screen.&lt;/P&gt;&lt;P&gt;if screen-name = 'I_MATNR'.&lt;/P&gt;&lt;P&gt;screen-required = '1'.&lt;/P&gt;&lt;P&gt;modify screen.&lt;/P&gt;&lt;P&gt;endif.&lt;/P&gt;&lt;P&gt;endloop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;rgds,&lt;/P&gt;&lt;P&gt;bharat.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 05:10:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474992#M557031</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T05:10:10Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP structure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474993#M557032</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Pavan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A structure (structured type) comprises components (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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Structures are used to define the data at the interface of module pools and screens and to define the parameter types of function modules.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logical Databse Structure:&lt;/P&gt;&lt;P&gt;The structure defines the data view of the logical database. It determines the structure of the other components and the behavior of the logical database at runtime. The order in which data is made available to the user depends on the hierarchical structure of the logical database concerned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward if useful!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 05:10:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474993#M557032</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T05:10:53Z</dc:date>
    </item>
    <item>
      <title>Re: ABAP structure</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474994#M557033</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Difference between Work Area and Header Line &lt;/P&gt;&lt;P&gt;While adding or retrieving records to / from internal table we have to keep the record temporarily. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The area where this record is kept is called as work area for the internal table.  The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Header line is a implicit work area for the internal table.  It depends on how the internal table is declared that the itab will have the header line or not. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. &lt;/P&gt;&lt;P&gt;data: begin of itab occurs 10, &lt;/P&gt;&lt;P&gt;           ab type c, &lt;/P&gt;&lt;P&gt;           cd type i, &lt;/P&gt;&lt;P&gt;        end of itab.  " this table will have the header line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: wa_itab like itab. " explicit work area for itab &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;data: itab1 like itab occurs 10. " table is without header line. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The header line is a field string with the same structure as a row of the body, but it can only hold a single row. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table.  It is the default work area for the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpfull answers.&lt;/P&gt;&lt;P&gt;Regrads.&lt;/P&gt;&lt;P&gt;Jay&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Jun 2007 05:15:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/abap-structure/m-p/2474994#M557033</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-06-29T05:15:27Z</dc:date>
    </item>
  </channel>
</rss>

