<?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: create internal table in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895404#M680652</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;creat a structure of what ever fields you want &lt;/P&gt;&lt;P&gt;by useing types &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;ex&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;TYPES : BEGIN OF ST_OBJID_SH,&lt;/P&gt;&lt;P&gt;         OTYPE TYPE HRP1000-OTYPE,&lt;/P&gt;&lt;P&gt;         OBJID TYPE HRP1000-OBJID,&lt;/P&gt;&lt;P&gt;        END OF ST_OBJID_SH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;creat the internal table like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : IT_OBJID_SH TYPE STANDARD TABLE OF ST_OBJID_SH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;creat the work area like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : WA_OBJID_SH TYPE ST_OBJID_SH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is the better way to use internal tables &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward if usfull&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 11 Oct 2007 07:19:53 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-11T07:19:53Z</dc:date>
    <item>
      <title>create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895403#M680651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;please let me know how to create the internal table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;sujatha&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 07:17:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895403#M680651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-11T07:17:24Z</dc:date>
    </item>
    <item>
      <title>Re: create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895404#M680652</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;creat a structure of what ever fields you want &lt;/P&gt;&lt;P&gt;by useing types &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;ex&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;TYPES : BEGIN OF ST_OBJID_SH,&lt;/P&gt;&lt;P&gt;         OTYPE TYPE HRP1000-OTYPE,&lt;/P&gt;&lt;P&gt;         OBJID TYPE HRP1000-OBJID,&lt;/P&gt;&lt;P&gt;        END OF ST_OBJID_SH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;creat the internal table like this &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : IT_OBJID_SH TYPE STANDARD TABLE OF ST_OBJID_SH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;creat the work area like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA : WA_OBJID_SH TYPE ST_OBJID_SH.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is the better way to use internal tables &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;reward if usfull&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 07:19:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895404#M680652</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-11T07:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895405#M680653</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;e.g. DATA: BEGIN OF STRUC, &lt;/P&gt;&lt;P&gt;        NAME(10) TYPE C, &lt;/P&gt;&lt;P&gt;        SALDO    TYPE P, &lt;/P&gt;&lt;P&gt;      END OF STRUC, &lt;/P&gt;&lt;P&gt;      ITAB LIKE TABLE OF STRUC. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need an internal table with header, you can work with "occurs 0" or "with header line"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Nicole&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 07:20:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895405#M680653</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-11T07:20:10Z</dc:date>
    </item>
    <item>
      <title>Re: create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895406#M680654</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi sujatha.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1st way :- &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES: BEGIN OF t_table_mpla,&lt;/P&gt;&lt;P&gt;       warpl     TYPE   mpla-warpl,   "Maintenance Plan&lt;/P&gt;&lt;P&gt;       topos     TYPE   mpla-topos,   "Tolerance&lt;/P&gt;&lt;P&gt;       abrho     TYPE   mpla-abrho,   "Scheduling Period&lt;/P&gt;&lt;P&gt;       hunit     TYPE   mpla-hunit,   "Unit of Scheduling Period&lt;/P&gt;&lt;P&gt;       END OF t_table_mpla.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Data :  i_table_mpla    TYPE STANDARD TABLE OF t_table_mpla.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2nd way :- &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DATA: BEGIN OF i_table_final OCCURS 0,&lt;/P&gt;&lt;P&gt;             aufnr       LIKE     aufk-aufnr,    &lt;/P&gt;&lt;P&gt;             ktext       LIKE     aufk-ktext,    &lt;/P&gt;&lt;P&gt;             ilart       LIKE     afih-ilart,    &lt;/P&gt;&lt;P&gt;             pdat2       LIKE     aufk-pdat2,    &lt;/P&gt;&lt;P&gt;           end of  i_table_final.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rewars if useful.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 07:23:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895406#M680654</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-11T07:23:27Z</dc:date>
    </item>
    <item>
      <title>Re: create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895407#M680655</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt;good&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;reward point if helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;P&gt;mruytun^&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 07:23:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895407#M680655</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-11T07:23:37Z</dc:date>
    </item>
    <item>
      <title>Re: create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895408#M680656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Internal table in ABAP &lt;/P&gt;&lt;P&gt;*An internal table is a run time instance. It get created when program starts execution. &lt;/P&gt;&lt;P&gt;*It get destroyed when program terminates. it has two different parts. HeaderLine(optional) &amp;amp; Body(Compulsory). &lt;/P&gt;&lt;P&gt;*Any value that comes to or goes from interanal table , that travels through headerline.\ &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*&lt;/P&gt;&lt;P&gt;A related program is . &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;*declaration. &lt;/P&gt;&lt;P&gt;data: begin of inernaltable occurs 0, &lt;/P&gt;&lt;P&gt;         x type c, &lt;/P&gt;&lt;P&gt;         y type i, &lt;/P&gt;&lt;P&gt;      end of itab. &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;*initializing headerline &lt;/P&gt;&lt;P&gt;   internaltable-x = 'd'. &lt;/P&gt;&lt;P&gt;   internaltable-y = 34. &lt;/P&gt;&lt;P&gt;   &lt;/P&gt;&lt;P&gt;*storing value into internal table &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;appene internaltable .  &lt;/P&gt;&lt;P&gt;appene internaltable . &lt;/P&gt;&lt;P&gt;appene internaltable . &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;*reading internal table &lt;/P&gt;&lt;P&gt;loop at itab . &lt;/P&gt;&lt;P&gt;   write: / internaltable-x, internaltable-y.  "writes to output list &lt;/P&gt;&lt;P&gt;endloop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;TYPES&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;STANDARD table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Key access to a standard table uses a linear search. This means that the time required&lt;/P&gt;&lt;P&gt;for a search is in linear relation to the number of table entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should use index operations to access standard tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SORTED table &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Defines the table as one that is always saved correctly sorted.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Key access to a sorted table uses a binary key. If the key is not unique, the system takes&lt;/P&gt;&lt;P&gt;the entry with the lowest index. The runtime required for key access is logarithmically&lt;/P&gt;&lt;P&gt;related to the number of table entries.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HASHED table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Defines the table as one that is managed with an internal hash procedure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can only access a hashed table using the generic key operations or other generic&lt;/P&gt;&lt;P&gt;operations ( SORT, LOOP, and so on). Explicit or implicit index operations (such as&lt;/P&gt;&lt;P&gt;LOOP ... FROM oe INSERT itab within a LOOP) are not allowed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INDEX table&lt;/P&gt;&lt;P&gt;A table that can be accessed using an index.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Index table is only used to specify the type of generic parameters in a FORM or&lt;/P&gt;&lt;P&gt;FUNCTION. That means that you can't create a table of type INDEX.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Standard tables and sorted tables are index tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Syntax :&lt;/P&gt;&lt;P&gt;DATA itab TYPE table type of line type [WITH UNIQUE/NON-UNIQUE KEY ]&lt;/P&gt;&lt;P&gt;[Iinitial size n] [WITH HEADER LINE]&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal table declaration - various ways of declaring an internal table&lt;/P&gt;&lt;P&gt;Declaring internal tables is an essential part of writing ABAP code as this is where most of the data retrieved &lt;/P&gt;&lt;P&gt;from database tables will be stored. During the select statement you retrieve data from a database table into &lt;/P&gt;&lt;P&gt;an internal table (multiple rows) or a work area or header line (single row). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;REPORT  ZTYPES                                                  .&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Table declaration (old method)&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;DATA: BEGIN OF tab_ekpo OCCURS 0,             "itab with header line&lt;/P&gt;&lt;P&gt;  ebeln TYPE ekpo-ebeln,&lt;/P&gt;&lt;P&gt;  ebelp TYPE ekpo-ebelp,&lt;/P&gt;&lt;P&gt; END OF tab_ekpo.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;*Table declaration (new method)     "USE THIS WAY!!!&lt;/P&gt;&lt;P&gt;TYPES: BEGIN OF t_ekpo,&lt;/P&gt;&lt;P&gt;  ebeln TYPE ekpo-ebeln,&lt;/P&gt;&lt;P&gt;  ebelp TYPE ekpo-ebelp,&lt;/P&gt;&lt;P&gt; END OF t_ekpo.&lt;/P&gt;&lt;P&gt;DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,      "itab&lt;/P&gt;&lt;P&gt;      wa_ekpo TYPE t_ekpo.                    "work area (header line)&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Build internal table and work area from existing internal table&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;DATA: it_datatab LIKE tab_ekpo OCCURS 0,      "old method&lt;/P&gt;&lt;P&gt;      wa_datatab LIKE LINE OF tab_ekpo.&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Build internal table and work area from existing internal table,&lt;/P&gt;&lt;/LI&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;adding additional fields&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;TYPES: BEGIN OF t_repdata.&lt;/P&gt;&lt;P&gt;        INCLUDE STRUCTURE tab_ekpo.  "could include EKKO table itself!!&lt;/P&gt;&lt;P&gt;TYPES: bukrs  TYPE ekpo-werks,&lt;/P&gt;&lt;P&gt;       bstyp  TYPE ekpo-bukrs.&lt;/P&gt;&lt;P&gt;TYPES: END OF t_repdata.&lt;/P&gt;&lt;P&gt;DATA: it_repdata TYPE STANDARD TABLE OF t_repdata INITIAL SIZE 0,   "itab&lt;/P&gt;&lt;P&gt;      wa_repdata TYPE t_repdata.                 "work area (header line)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward pts for usefull answers &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Shakir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 Oct 2007 07:23:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895408#M680656</guid>
      <dc:creator>abdulazeez12</dc:creator>
      <dc:date>2007-10-11T07:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: create internal table</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895409#M680657</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;&amp;lt;b&amp;gt; Creating Internal Tables&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Like other elements in the ABAP type concept, you can declare internal tables as abstract data &lt;/P&gt;&lt;P&gt;types in programs or in the ABAP Dictionary, and then use them to define data objects. &lt;/P&gt;&lt;P&gt;Alternatively, you can define them directly as data objects. When you create an internal table as a &lt;/P&gt;&lt;P&gt;data object, you should ensure that only the administration entry which belongs to an internal &lt;/P&gt;&lt;P&gt;table is declared statically. The minimum size of an internal table is 256 bytes. This is important if an &lt;/P&gt;&lt;P&gt;internal table occurs as a component of an aggregated data object, since even empty internal &lt;/P&gt;&lt;P&gt;tables within tables can lead to high memory usage. (In the next functional release, the size of the &lt;/P&gt;&lt;P&gt;table header for an initial table will be reduced to 8 bytes). Unlike all other ABAP data objects, you &lt;/P&gt;&lt;P&gt;do not have to specify the memory required for an internal table. Table rows are added to and &lt;/P&gt;&lt;P&gt;deleted from the table dynamically at runtime by the various statements for adding and deleting &lt;/P&gt;&lt;P&gt;records.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can create internal tables in different types.&lt;/P&gt;&lt;P&gt;You can create standard internal table and then make it sort in side the program.&lt;/P&gt;&lt;P&gt;The same way you can change to hashed internal tables also.&lt;/P&gt;&lt;P&gt;There will be some performance issues with regard to standard internal tables/ hashed internal &lt;/P&gt;&lt;P&gt;tables/ sorted internal tables.&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>Thu, 11 Oct 2007 07:27:06 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/create-internal-table/m-p/2895409#M680657</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-11T07:27:06Z</dc:date>
    </item>
  </channel>
</rss>

