<?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: BAPI Lock issue in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508382#M567167</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;Try to call after BAPI_TRANSACTION_COMMIT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
      call function 'ENQUE_SLEEP'
        exporting
          seconds = ntime. "&amp;lt;&amp;lt; give seconds to sleep

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;after the BAPI call. May this will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aRs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        a®&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 06 Jul 2007 15:39:41 GMT</pubDate>
    <dc:creator>former_member194669</dc:creator>
    <dc:date>2007-07-06T15:39:41Z</dc:date>
    <item>
      <title>BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508378#M567163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Friends,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a situation where several instance of a workflow gets created at one time which as a part of the process calls a BAPI and updates a table. Only few instances could update the table successfully (Sometimes none). Rest of them couldnt. The BAPIRETURN message says 'E-PV100-Business Event nnnn is currently locked; Try again later'. I tried to call BAPI_TRANSACTION_COMMIT after the BAPI call. It didnt help. I tried to read all the locks for the user using FM ENQUE_READ and delete them using FM ENQUE_DELETE before and after the BAPI call. It doesnt help either. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can this be handled? Prompt replies would be appreciated and rewarded suitably.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nathan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 15:19:13 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508378#M567163</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T15:19:13Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508379#M567164</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When testing the locks using the enqueue function, try setting the _WAIT parameter to 'X'.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 15:27:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508379#M567164</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T15:27:05Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508380#M567165</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;  Thanks. But where is this parameter?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nathan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 15:30:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508380#M567165</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T15:30:34Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508381#M567166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It should be an importing parameter for the enqueue function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 15:33:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508381#M567166</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T15:33:05Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508382#M567167</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;Try to call after BAPI_TRANSACTION_COMMIT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
      call function 'ENQUE_SLEEP'
        exporting
          seconds = ntime. "&amp;lt;&amp;lt; give seconds to sleep

&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;after the BAPI call. May this will help you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aRs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: &lt;/P&gt;&lt;P&gt;        a®&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 15:39:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508382#M567167</guid>
      <dc:creator>former_member194669</dc:creator>
      <dc:date>2007-07-06T15:39:41Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508383#M567168</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nathan&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Function BAPI_TRANSACTION_COMMIT has a Parameter WAIT. Call with WAIT = 'X' and it should be OK - although it takes more time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 16:00:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508383#M567168</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-07-06T16:00:39Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508384#M567169</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;  I tried BAPI_TRANSACTION_COMMIT with WAIT = SPACE as well as WAIT = 'X'. Either case the workflow doesnt proceed after the BAPI step and the records are not updated. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other way?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nathan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 20:12:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508384#M567169</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T20:12:32Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508385#M567170</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you try this with the enqueue function as I suggested?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 20:22:33 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508385#M567170</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T20:22:33Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508386#M567171</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rob,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Yes i tried that as well. I called ENQUEUE_E_TABLE before BAPI call, passing the table name and &lt;U&gt;WAIT = 'X' and called DEQUEUE&lt;/U&gt;E_TABLE. Still no luck.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nathan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 Jul 2007 20:43:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508386#M567171</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-06T20:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508387#M567172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Nathan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if COMMIT and WAIT does not help, a COMMIT without work has been issued before. Many not too experienced/responsible developers tend to issue COMMIT WORKS in any kind of user exit just to make sure that their specific changes get written to the database. And you have to survive with the results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you could do is check the locks and do a loop before calling BAPI as long as the object is locked. Here's some stone-old code we used for material updates:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;
FORM WARTEN_VERBUCHER
  USING P_MAX_WAIT_SECONDS TYPE I
  CHANGING P_SUBRC LIKE SY-SUBRC.
  DATA:
  L_ENDTIME LIKE SY-UZEIT,
  L_TABIX LIKE SY-TABIX,
  L_TRIES TYPE I,
  L_SUCCESS LIKE SY-SUBRC,
  L_ANSW TYPE C,
  L_TRY_AGAIN LIKE RMCLS-XFLAG VALUE 'X'.
  GET TIME.
  L_ENDTIME = SY-UZEIT.
  ADD P_MAX_WAIT_SECONDS TO L_ENDTIME.
  WHILE L_TRY_AGAIN = 'X'.
    LOOP AT ITAB.
      PERFORM CHECK_LOCK_EMMARCE
        USING ZAUF-WERKS ITAB-MATNR CHANGING P_SUBRC.
      GET TIME.
      IF P_SUBRC &amp;lt;&amp;gt; 0 OR SY-UZEIT &amp;gt;= L_ENDTIME.
        EXIT.                          "Loop
      ENDIF.                           " sy-subrc = 0.
    ENDLOOP.                           " AT itab.
    IF P_SUBRC = 0.
      CLEAR: L_TRY_AGAIN.
    ELSE.
      IF SY-UZEIT &amp;gt;= L_ENDTIME .
        PERFORM POPUP_TO_CONFIRM_WAIT
          USING P_MAX_WAIT_SECONDS CHANGING L_ENDTIME P_SUBRC.
        IF P_SUBRC &amp;lt;&amp;gt; 0.
          CLEAR L_TRY_AGAIN.
        ELSE.
          CLEAR P_SUBRC.
        ENDIF.                         " p_subrc &amp;lt;&amp;gt; 0.
      ENDIF.                           " sy-uzeit &amp;gt;= l_endtime.
    ENDIF.                             " p_subrc = 0.
  ENDWHILE.                            " l_try_again = 'X'.
ENDFORM.                               " WARTEN_VERBUCHER
*&amp;amp;---------------------------------------------------------------------*
*&amp;amp;      Form  POPUP_TO_CONFIRM_WAIT
*&amp;amp;---------------------------------------------------------------------*
*
*----------------------------------------------------------------------*
*      --&amp;gt;P_WAIT_SECONDS
*      &amp;lt;--P_ENDTIME
*----------------------------------------------------------------------*
FORM POPUP_TO_CONFIRM_WAIT USING    P_WAIT_SECONDS TYPE I
                           CHANGING P_ENDTIME LIKE SY-UZEIT
                                    P_SUBRC LIKE SY-SUBRC.
  DATA:
  L_STARTCOLUMN LIKE SY-CUCOL VALUE 10,
  L_STARTROW    LIKE SY-CUROW VALUE 20,
  L_TITLE(35),
  L_TEXTLINE1(70),
  L_TEXTLINE2(70),
  L_ANSW.
  L_TITLE = 'Warten auf gesperrte Tabelle'.
  L_TEXTLINE1 = 'Tabelle(n) sind zur Zeit gesperrt'.
  IF NOT SY-MSGV1 IS INITIAL.          "Foreign lock
    CONCATENATE L_TEXTLINE1 'durch Benutzer' SY-MSGV1
                INTO L_TEXTLINE1 SEPARATED BY SPACE.
  ENDIF.                               " sy-msgv1 IS INITIAL.
  WRITE: P_WAIT_SECONDS TO L_TEXTLINE2.
  CONDENSE: L_TEXTLINE2.
  CONCATENATE:
    'Wollen Sie weitere' L_TEXTLINE2 'Sekunden warten?'
    INTO L_TEXTLINE2 SEPARATED BY SPACE.
  L_STARTCOLUMN = SY-UZEIT+2(2) MOD 30 + 10.
  L_STARTROW    = SY-UZEIT+2(2) MOD 10 + 3.
  CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
       EXPORTING
*         DEFAULTOPTION  = 'Y'
            TEXTLINE1      = L_TEXTLINE1
            TEXTLINE2      = L_TEXTLINE2
            TITEL          = L_TITLE
          START_COLUMN   = L_STARTCOLUMN
          START_ROW      = L_STARTROW
*         CANCEL_DISPLAY = 'X'
    IMPORTING
           ANSWER         = L_ANSW
       EXCEPTIONS
            OTHERS         = 1.
  IF L_ANSW = 'J'.                     "(!)
    GET TIME.
    P_ENDTIME = SY-UZEIT.
    ADD P_WAIT_SECONDS TO P_ENDTIME.
    P_SUBRC = 0.
  ELSE.
    P_SUBRC = 8.
  ENDIF.                               " l_answ = 'J'. "(!)
ENDFORM.                               " POPUP_TO_CONFIRM_WAIT
*&amp;amp;---------------------------------------------------------------------*
*&amp;amp;      Form  CHECK_LOCK_EMMARCE
*&amp;amp;---------------------------------------------------------------------*
*      Prüfen ob Sperre gesetzt
*      Code teilweise aus RSENQRR2 übernommen
*----------------------------------------------------------------------*
*      --&amp;gt;P_WERKS  text                                           *
*      --&amp;gt;P_MATNR  text                                           *
*      &amp;lt;--P_SUBRC  text                                              *
*----------------------------------------------------------------------*
FORM CHECK_LOCK_EMMARCE
                USING    VALUE(P_WERKS) LIKE MARC-WERKS
                         VALUE(P_MATNR) LIKE MARC-MATNR
                CHANGING P_SUBRC.

  DATA: ENQ LIKE SEQG3 OCCURS 0 WITH HEADER LINE.
  DATA: DEL LIKE SEQG3 OCCURS 0 WITH HEADER LINE.
  DATA: SELECT_ALL.
  DATA: GUSR     LIKE  SEQG3-GUSR.
  DATA: GMODE    LIKE  SEQG3-GMODE.
  DATA: GNAME    LIKE  SEQG3-GNAME.
  DATA: GARG     LIKE  SEQG3-GARG.
  DATA: GTARG    LIKE  SEQG3-GTARG.
  DATA: GOBJ     LIKE  SEQG3-GOBJ.
  DATA: GUNAME   LIKE  SEQG3-GUNAME.
  DATA: GCLIENT  LIKE  SEQG3-GCLIENT.
  DATA: GTCODE   LIKE  SEQG3-GTCODE.
  DATA: GUSE     LIKE  SEQG3-GUSE.
  DATA: GUSEVB   LIKE  SEQG3-GUSEVB.
  DATA: GBCKTYPE LIKE  SEQG3-GBCKTYPE..
  DATA: GRANULE  LIKE SEQTA.
*** initializations ****************************************************
  FREE ENQ.
  FREE DEL.
  CLEAR: P_SUBRC.
* Konvertieren Matnr

  CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
       EXPORTING
            INPUT  = P_MATNR
       IMPORTING
            OUTPUT = P_MATNR
       EXCEPTIONS
            OTHERS = 1.

  GNAME   = 'MARC'.
  GOBJ    = 'EMMARCE'.
  GUNAME  = SY-UNAME.
  GCLIENT = SY-MANDT.
  CONCATENATE SY-MANDT P_MATNR P_WERKS INTO GARG.

* first try via RFC, retry up to 3 times ******************************
  DO 3 TIMES.
    CALL FUNCTION 'ENQUEUE_READ'
         EXPORTING
              GCLIENT = GCLIENT
              GUNAME  = GUNAME
              GNAME   = GNAME
         IMPORTING
              SUBRC   = P_SUBRC
         TABLES
              ENQ     = ENQ
         EXCEPTIONS
              OTHERS  = 1.
    IF SY-SUBRC = 0.
      EXIT.
    ENDIF.
  ENDDO.

* if RFC fails read via NFS ********************************************
  IF SY-SUBRC &amp;lt;&amp;gt; 0.

    CALL FUNCTION 'ENQUE_READ'
         EXPORTING
              GCLIENT = GCLIENT
              GUNAME  = GUNAME
              GNAME   = GNAME
              GARG    = GARG
         IMPORTING
              SUBRC   = P_SUBRC
         TABLES
              ENQ     = ENQ.
    MESSAGE ID '03' TYPE 'W' NUMBER 113.
  ENDIF.                               "sy-subrc &amp;lt;&amp;gt; 0.
  LOOP AT ENQ.
    CHECK ENQ-GARG(25) = GARG(25).
    CHECK ENQ-GOBJ = GOBJ.
    SY-MSGV1 = ENQ-GUNAME.
    P_SUBRC = 8.
    EXIT.
  ENDLOOP." AT enq WHERE garg(25) = garg(25) and gobj = 'EMMARCE'.
ENDFORM.                               " CHECK_LOCK_EMMARCE
&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please adapt to your needs; I think as your processes are running in background, you can take out the POPUP_TO_CONFIRM_WAIT. We used it just to have a chance to get out of the waiting loop if someone slept at his terminal...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Clemens&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 08 Jul 2007 13:43:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508387#M567172</guid>
      <dc:creator>Clemenss</dc:creator>
      <dc:date>2007-07-08T13:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: BAPI Lock issue</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508388#M567173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Clemens,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;   Thanks for the code. Will try it and get back. Thanks once again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Nathan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 05:55:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/bapi-lock-issue/m-p/2508388#M567173</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-07-09T05:55:54Z</dc:date>
    </item>
  </channel>
</rss>

