<?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: Dump in a Select query in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340820#M1397441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Abhii,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First Use sql trace facilty, to find for which query it is consuming more time. Then you can concentrate more on that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check indexes on VBFA table. We are using ecc 6.0, there is one index on VBELN and POSNN.&lt;/P&gt;&lt;P&gt;I beleive, if you have that, you wouldn't be hit with this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For each sales order line item, you are reading billing document. If your are using order related billing, then you can read this table once for a sale order. check this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use VBFA-VBTYP_N (C - ORDERS) in select query. It could filter some data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I beleive, you can replace the calling of function module 'SD_DOCUMENT_PARTNER_READ' with a select query on VBPA table as It seems you are interested on partner number only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Madhu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Nov 2009 14:46:19 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-11-03T14:46:19Z</dc:date>
    <item>
      <title>Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340812#M1397433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am getting a dump &amp;amp; the dump says " TIME LIMIT EXCEEDED". The code as  below:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; LOOP AT it_gen1 INTO wa_gen1.&lt;/P&gt;&lt;P&gt;*&lt;/P&gt;&lt;P&gt;        SELECT  vbelv posnv&lt;/P&gt;&lt;P&gt;          FROM  vbfa&lt;/P&gt;&lt;P&gt;    INTO TABLE  li_vbfa&lt;/P&gt;&lt;P&gt;         WHERE  vbeln = wa_gen1-bil_number&lt;/P&gt;&lt;P&gt;           AND  posnn = wa_gen1-itm_number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        DESCRIBE TABLE li_vbfa  LINES gv_count .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        READ TABLE  li_vbfa  INDEX gv_count  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        IF sy-subrc =  0 .&lt;/P&gt;&lt;P&gt;          MOVE: li_vbfa-vbelv TO gv_vbelv1,&lt;/P&gt;&lt;P&gt;                li_vbfa-posnv TO gv_posnv.&lt;/P&gt;&lt;P&gt;        ENDIF .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        CALL FUNCTION 'SD_DOCUMENT_PARTNER_READ'&lt;/P&gt;&lt;P&gt;          EXPORTING&lt;/P&gt;&lt;P&gt;            i_parvw   = 'ZS'&lt;/P&gt;&lt;P&gt;            i_posnr   = gv_posnv&lt;/P&gt;&lt;P&gt;            i_vbeln   = gv_vbelv1&lt;/P&gt;&lt;P&gt;          IMPORTING&lt;/P&gt;&lt;P&gt;            e_vbpa    = li_vbpa&lt;/P&gt;&lt;P&gt;            e_vbadr   = li_vbadr&lt;/P&gt;&lt;P&gt;          EXCEPTIONS&lt;/P&gt;&lt;P&gt;            not_found = 1&lt;/P&gt;&lt;P&gt;            OTHERS    = 2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        IF sy-subrc &amp;lt;&amp;gt; 0.&lt;/P&gt;&lt;P&gt;          MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno&lt;/P&gt;&lt;P&gt;        WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.&lt;/P&gt;&lt;P&gt;        ENDIF.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        MOVE  li_vbpa-kunnr  TO  wa_gen2-kunnr .&lt;/P&gt;&lt;P&gt;        MOVE-CORRESPONDING wa_gen1 TO wa_gen2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        APPEND  wa_gen2 TO it_gen2  .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;      ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I use Function Module   &lt;STRONG&gt;CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'&lt;/STRONG&gt; before ENDLOOP this will overcome the error says one of my friend.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a feasible solution for this error?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in dvance....&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2009 13:31:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340812#M1397433</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-27T13:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340813#M1397434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Select inside loop is a performance issue.&lt;/P&gt;&lt;P&gt;You are hitting the database for every loop line, so it would be a time consuming issue.&lt;/P&gt;&lt;P&gt;Better select the vbfa details using for all entries and read the table when ever required.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2009 13:37:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340813#M1397434</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-27T13:37:16Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340814#M1397435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The progress indicator is just a nasty workaround to reset the runtime counter. Look for information in "ABAP performance" forum on how to make good use of table indexes, in your example for table VBFA. Cure the cause, not the symptoms.&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2009 13:44:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340814#M1397435</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2009-10-27T13:44:51Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340815#M1397436</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi I have tried that but I am getting so many unwanted records &amp;amp; I am not sure how to restrict them....Also Can you tell if using the FM &lt;STRONG&gt;CALL FUNCTION 'SAPGUI_PROGRESS_INDICATOR'&lt;/STRONG&gt; will help me or not?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2009 13:45:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340815#M1397436</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-27T13:45:33Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340816#M1397437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Thomas a good answer but there are no Index on this table &amp;amp; I have used almost all the important key fields of this table in the where clause.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2009 13:47:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340816#M1397437</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-27T13:47:56Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340817#M1397438</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check out SAP Note 185530. I'll quote the important part for you:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Document flow:&lt;/P&gt;&lt;P&gt;&amp;gt; Incorrect:   SELECT vbelv FROM vbfa WHERE vbeln ...&lt;/P&gt;&lt;P&gt;&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;gt; In table VBFA only the preceeding document is used to search for the subsequent document (for example, delivery for order). Searching the other way makes no sense with this table since the preceding documents (for example, order for delivery) are stored directly in the document tables. Thus reading in table VBFA is a one-way street.&lt;/P&gt;&lt;P&gt;&amp;gt; Correct:  SELECT vgbel FROM lips WHERE vbeln = ...; or  SELECT vgbel FROM vbrp WHERE vbeln = ...; or&lt;/P&gt;&lt;P&gt; &amp;gt; SELECT aubel FROM vbrp WHERE vbeln = ... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thomas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Oct 2009 13:55:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340817#M1397438</guid>
      <dc:creator>ThomasZloch</dc:creator>
      <dc:date>2009-10-27T13:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340818#M1397439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;First fetch all the data you require into an internal table using FOR ALL ENTRIES statement. =&amp;gt; It will help u remove the SELECT query from the loop.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then read the data from there and into another temp internal table and thereafter process as you require. This should save you a lot of time. Use [parallel cursor logic|https://wiki.sdn.sap.com/wiki/display/Snippets/ABAP&lt;EM&gt;Code&lt;/EM&gt;for&lt;EM&gt;Parallel&lt;/EM&gt;Cursor&lt;EM&gt;-&lt;/EM&gt;Loop+Processing] if required.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Srinivas&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Oct 2009 13:02:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340818#M1397439</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-10-29T13:02:23Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340819#M1397440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also, VBFA ...selection we face performance issue and takes much time and dump might occur...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I prefer to use use a FM RV_ORDER_FLOW_INFORMATION  instead of read on VBFA..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Pramod&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 31 Oct 2009 09:25:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340819#M1397440</guid>
      <dc:creator>pramodu</dc:creator>
      <dc:date>2009-10-31T09:25:43Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340820#M1397441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Abhii,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;First Use sql trace facilty, to find for which query it is consuming more time. Then you can concentrate more on that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check indexes on VBFA table. We are using ecc 6.0, there is one index on VBELN and POSNN.&lt;/P&gt;&lt;P&gt;I beleive, if you have that, you wouldn't be hit with this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For each sales order line item, you are reading billing document. If your are using order related billing, then you can read this table once for a sale order. check this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;use VBFA-VBTYP_N (C - ORDERS) in select query. It could filter some data. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I beleive, you can replace the calling of function module 'SD_DOCUMENT_PARTNER_READ' with a select query on VBPA table as It seems you are interested on partner number only.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;P&gt;Madhu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Nov 2009 14:46:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340820#M1397441</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-03T14:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340821#M1397442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for all your inputs. This issue is resolved now. I have used ranges in the select query &amp;amp; removed FOR ALL ENTRIES construct. The select query is working very fastly now with correct data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The code with the changes as below :-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        LOOP AT it_gen1 INTO wa_gen1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          CLEAR r_bil_number.&lt;/P&gt;&lt;P&gt;          CLEAR r_itm_number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          r_bil_number-option = 'EQ'.&lt;/P&gt;&lt;P&gt;          r_bil_number-sign = 'I'.&lt;/P&gt;&lt;P&gt;          r_bil_number-low = wa_gen1-bil_number.&lt;/P&gt;&lt;P&gt;          COLLECT r_bil_number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          r_itm_number-option = 'EQ' .&lt;/P&gt;&lt;P&gt;          r_itm_number-sign = 'I'.&lt;/P&gt;&lt;P&gt;          r_itm_number-low = wa_gen1-itm_number.&lt;/P&gt;&lt;P&gt;          COLLECT r_itm_number.&lt;/P&gt;&lt;P&gt;&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;        SELECT vbelv&lt;/P&gt;&lt;P&gt;               posnv&lt;/P&gt;&lt;P&gt;               vbeln&lt;/P&gt;&lt;P&gt;               posnn&lt;/P&gt;&lt;P&gt;               vbtyp_n&lt;/P&gt;&lt;P&gt;               vbtyp_v                      &lt;/P&gt;&lt;P&gt;               FROM vbfa&lt;/P&gt;&lt;P&gt;               INTO TABLE li_vbfa&lt;/P&gt;&lt;P&gt;         WHERE vbeln IN r_bil_number&lt;/P&gt;&lt;P&gt;         AND posnn   IN r_itm_number&lt;/P&gt;&lt;P&gt;         AND vbtyp_n = c_m.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Abhii.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Nov 2009 13:26:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340821#M1397442</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-04T13:26:19Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340822#M1397443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt; &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;gt; Thanks for all your inputs. This issue is resolved now. I have used ranges in the select query &amp;amp; removed FOR ALL ENTRIES construct. &lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why do you want inputs if you then ignore them?&lt;/P&gt;&lt;P&gt;The correct way to read VBFA was given by Thomas. If you have the billing document, go directly to VBRP to get the preceding document (and not to VBFA).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By the way, your query will &lt;STRONG&gt;not&lt;/STRONG&gt; return (only) the records you want. &lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P&gt; WHERE vbeln IN r_bil_number&lt;/P&gt;&lt;P&gt;AND posnn IN r_itm_number &lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;For example, if you want 2 items (Invoice 100/1 and 200/2), you are doing vbeln in (100,200) and posnn in (1,2) which might mean a total of 4 items (so not only the two you need).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 04 Nov 2009 14:24:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340822#M1397443</guid>
      <dc:creator>Rui_Dantas</dc:creator>
      <dc:date>2009-11-04T14:24:14Z</dc:date>
    </item>
    <item>
      <title>Re: Dump in a Select query</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340823#M1397444</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rui,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am generating invoice output from VF03. Hence the VBELN will always be the same. There is no chance that there will be two VBELN at a time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards&lt;/P&gt;&lt;P&gt;Abhii...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Nov 2009 14:09:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/dump-in-a-select-query/m-p/6340823#M1397444</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-11-05T14:09:36Z</dc:date>
    </item>
  </channel>
</rss>

