<?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: Error message pops up again after correction (ALV DATA_CHANGED) in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084338#M1357503</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Have you called the method CHECK_CHANGED_DATA in the PAI of your program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 01 Sep 2009 10:14:16 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-09-01T10:14:16Z</dc:date>
    <item>
      <title>Error message pops up again after correction (ALV DATA_CHANGED)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084337#M1357502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi experts:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am doing a list using ALV control (OO), I put my validation logic in data changed handler. The validation is simple, to check whether a field is blank or not, if it is blank, pup up error messages and let the user to correct his/her input. But the strange thing is that after the error message firstly pops up, I input something in the field and press enter. No error message should be popped up. But the same error message pops up again. I debug the program found that after the first error, even I input something in the field, but the program does not get the value I input, so the same checking failed, and the error message pops up.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  METHOD HANDLE_DATA_CHANGED. "#EC NEEDED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    DATA: LW_INS      TYPE LVC_S_MOCE,&lt;/P&gt;&lt;P&gt;          LV_FNAME    TYPE LVC_FNAME,&lt;/P&gt;&lt;P&gt;          LT_MOD      TYPE LVC_T_MODI,&lt;/P&gt;&lt;P&gt;          LW_MOD      TYPE LVC_S_MODI,&lt;/P&gt;&lt;P&gt;          LV_TEXT(10) TYPE C,&lt;/P&gt;&lt;P&gt;          LV_MAX      TYPE I,&lt;/P&gt;&lt;P&gt;          LV_ROWID    TYPE I,&lt;/P&gt;&lt;P&gt;          LV_RES(12)  TYPE C,&lt;/P&gt;&lt;P&gt;          LW_LIST     TYPE ZTSRE007.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    LOOP AT GT_LIST INTO LW_LIST.&lt;/P&gt;&lt;P&gt;      IF LW_LIST-ID &amp;gt; LV_MAX.&lt;/P&gt;&lt;P&gt;        LV_MAX = LW_LIST-ID.&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;    LT_MOD[] = ER_DATA_CHANGED-&amp;gt;MT_MOD_CELLS[].&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    LOOP AT LT_MOD INTO LW_MOD.&lt;/P&gt;&lt;P&gt;      IF LW_MOD-FIELDNAME = CNS_ZZTTSN.&lt;/P&gt;&lt;P&gt;        LV_FNAME = CNS_ZZTTSN.&lt;/P&gt;&lt;P&gt;        CALL METHOD ER_DATA_CHANGED-&amp;gt;GET_CELL_VALUE&lt;/P&gt;&lt;P&gt;          EXPORTING&lt;/P&gt;&lt;P&gt;            I_ROW_ID    = LW_MOD-ROW_ID&lt;/P&gt;&lt;P&gt;            I_FIELDNAME = LV_FNAME&lt;/P&gt;&lt;P&gt;          IMPORTING&lt;/P&gt;&lt;P&gt;            E_VALUE     = LV_RES&lt;/P&gt;&lt;P&gt;            .&lt;/P&gt;&lt;P&gt;        IF LV_RES IS INITIAL.&lt;/P&gt;&lt;P&gt;          LV_ROWID = LW_MOD-ROW_ID.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;          CALL METHOD ER_DATA_CHANGED-&amp;gt;ADD_PROTOCOL_ENTRY&lt;/P&gt;&lt;P&gt;            EXPORTING&lt;/P&gt;&lt;P&gt;              I_MSGID     = CNS_MSGID&lt;/P&gt;&lt;P&gt;              I_MSGTY     = CNS_MSGTY&lt;/P&gt;&lt;P&gt;              I_MSGNO     = CNS_MSGNO&lt;/P&gt;&lt;P&gt;              I_FIELDNAME = LV_FNAME&lt;/P&gt;&lt;P&gt;              I_ROW_ID    = LW_MOD-ROW_ID&lt;/P&gt;&lt;P&gt;              .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;        ENDIF.&lt;/P&gt;&lt;P&gt;      ENDIF.&lt;/P&gt;&lt;P&gt;      CLEAR:  LV_ROWID,&lt;/P&gt;&lt;P&gt;              LV_FNAME.&lt;/P&gt;&lt;P&gt;    ENDLOOP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  ENDMETHOD.                    "handle_data_changed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Changjiu Tan on Sep 1, 2009 11:58 AM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 09:58:37 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084337#M1357502</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-01T09:58:37Z</dc:date>
    </item>
    <item>
      <title>Re: Error message pops up again after correction (ALV DATA_CHANGED)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084338#M1357503</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Have you called the method CHECK_CHANGED_DATA in the PAI of your program?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 10:14:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084338#M1357503</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-01T10:14:16Z</dc:date>
    </item>
    <item>
      <title>Re: Error message pops up again after correction (ALV DATA_CHANGED)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084339#M1357504</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;No, it is triggered by DATA_CHANGED event of CL_GUI_ALV_GRID. It is a event handler of event DATA_CHANGED&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 10:18:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084339#M1357504</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-01T10:18:17Z</dc:date>
    </item>
    <item>
      <title>Re: Error message pops up again after correction (ALV DATA_CHANGED)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084340#M1357505</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Make sure that you are setting handler only once for ONE alv reference. Also make sure that only ONE instance of ALV is created during runtime. It might be that your event is triggered twice as there are two instances of ALVs and your handler method is registered for both.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Marcin&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 10:52:23 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084340#M1357505</guid>
      <dc:creator>MarcinPciak</dc:creator>
      <dc:date>2009-09-01T10:52:23Z</dc:date>
    </item>
    <item>
      <title>Re: Error message pops up again after correction (ALV DATA_CHANGED)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084341#M1357506</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;in that case probably the handler method is getting called twice.&lt;/P&gt;&lt;P&gt;Are you changing the ALV grid data within the handler method itself??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In that case it might call the handler method once again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Ankur Parab&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 10:56:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084341#M1357506</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-01T10:56:48Z</dc:date>
    </item>
    <item>
      <title>Re: Error message pops up again after correction (ALV DATA_CHANGED)</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084342#M1357507</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 have checked my code, there seems no such probelm. Any other possible reasons?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Added: After the second error message screen has been closed. when press enter, no message pops up.&lt;/P&gt;&lt;P&gt;Vincent&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edited by: Changjiu Tan on Sep 1, 2009 2:14 PM&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Sep 2009 12:11:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/error-message-pops-up-again-after-correction-alv-data-changed/m-p/6084342#M1357507</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-09-01T12:11:52Z</dc:date>
    </item>
  </channel>
</rss>

