Webdynpro - Component usage gets lost when activating

[Former Member]

hi folks,

when activating a webdynpro view  the usage of methods that are handling events (e.g. the click event of webdynpro ALV) looses the information about the component usage when we display the view in se80.

so the methods don't work after activating a view in eclipse.

we use AIE 2.7 backend 7.40

is this a known error, or a mis-configuration?

best regards

oliver

[dominik_trefzer2]

I can confirm this behavior, I just stumbled upon this myself.

This is a critical issue in my opinion - I cannot use an IDE if there's a possibility it screws up my developments...

[Former Member]

i have an open issue at sap since a few weeks. they could reproduce this problem, but still no correction available. you are right thats i problem i like eclipse but aat the moment i use it just for non-webdynpro codings

[raghuvirab]

Hi Dominik, Oliver,

We are still working on this issue. I will get back to you with updates as soon as possible.

Best Regards,

Raghuvira

[raghuvirab]

Hi Oliver, Dominik,

We have fixed this issue in ADT 2.19 release. To get the fix you would also have to apply the SAP Note 1939612 into the R/3 system.

The Note is applicable for

• 7.31 SP7 and later SPs
• 7.4 and SP2 and later SPs

Please let me know if you face any further issues.

Sorry for the inconvenience and the delay.

Best Regards,

Raghuvira

[Former Member]

New problem with that.

we have 2 used componentes e.g. of WDR_OVR, called OVS1 and OVS2 in a component controller.

OVS1 is used in a method as usage. OVS2 is not used for some reasons.

When activating in Eclipse, the system changes the usage from OVS1 to OVS2 - only at runtime the system dumps as OVS2-Event is not assigneds to a context-element but OVS1.

must be a bug of eclispe.

as nice as eclipse is, in combination with webdynpro we are facing really some problems, so from our point of view, the usage of eclipse with webdynpro-elements is at the moment not really useable, so unfortunately for webdynpro we still use se80.

[pavitra_raghunathan]

Hi Oliver,

The solution has been provided.Sorry for the inconvenience.

We have fixed this issue in ADT 2.19 release. To get the fix you would also have to apply theSAP Note 1957966 into the R/3 system.

The Note is applicable for

• 7.31 SP7 and later SPs
• 7.4 and SP2 and later SPs

Please let me know if you face any further issues.

Regards,

Pavitra Raghunathan

[Former Member]

it is not possible to implement this Note as there is no correction attached? only a link to an SP-Package? how should this be done?

we have ATD 2.24 and 740 SP3 on ERP ehp7

[pavitra_raghunathan]

Hi Oliver,

The Note has been updated. Please try implementing the note again.

If you face any issues let me know.

Regards,

Pavitra Raghunathan

[Former Member]

Hi Pavirta,

i tried but CL_ADT_WDY_CONTROLLER_UTIL UPDATE_EVENTHANDLERS is not automatically implementable.

the snote does not find a lot of code that has to be corrected, can you try this please, it is also not possible manually there is maybe still a problem?

e.g. this contextblock

ELSE.

  "for custom controller

is not in our coding???

regards oliver

[Former Member]

in our syst em this method looks like:

and there is a lot the correction cannot find therefor????

  DATA: ls_new_event_handler    TYPE if_wdy_md_adt_controller=>gty_s_event_handler,

          ls_parameter            TYPE if_wdy_md_adt_controller=>gty_s_parameter,

          lt_event_handlers       TYPE TABLE OF if_adt_wdy_controller=>ty_controller_method,

          wa_parameter            TYPE if_adt_wdy_controller=>ty_parameter,

          wa_event_handler        TYPE if_adt_wdy_controller=>ty_controller_method,

          event                   TYPE string,

          component_controller    TYPE string,

          controller_usage     TYPE          if_adt_wdy_controller=>ty_controller_usage,

          comp_name            TYPE          wdy_component_name,

          ref_comp_name        TYPE         string.



    LOOP AT is_new_controller_data-ctlr_methods INTO wa_event_handler WHERE is_event = abap_true.

      APPEND wa_event_handler TO lt_event_handlers. " expected event handler functions to be saved

    ENDLOOP.



    "Flush all event handler from existing controller_detail assuming client sends all data back

    LOOP AT cs_existing_controller_detail-ctlr_details-event_handler INTO ls_new_event_handler.

      DELETE cs_existing_controller_detail-ctlr_methods WHERE cmpname = ls_new_event_handler-cmpname.

      IF ls_new_event_handler-cmpname NP 'ONACTION*'.

        DELETE cs_existing_controller_detail-ctlr_details-event_handler WHERE cmpname =  ls_new_event_handler-cmpname.

      ENDIF.

    ENDLOOP.



    "all new event handlers are in lt_event_functions . Now add them

    LOOP AT lt_event_handlers INTO wa_event_handler.

      CLEAR ls_new_event_handler.

      MOVE-CORRESPONDING wa_event_handler TO ls_new_event_handler.

      SPLIT wa_event_handler-controller_ref-name AT space INTO event component_controller.

      CONDENSE component_controller NO-GAPS.

     if component_controller CS '-'.

       SPLIT component_controller AT '-' INTO comp_name component_controller.

      endif.

      ref_comp_name = wa_event_handler-ref_component.



      LOOP AT cs_existing_controller_detail-controller_usages INTO controller_usage .

      "WHERE wa_event_handler- eq controller_usage-used_component_name.

      if ref_comp_name eq controller_usage-used_component_name.

       ls_new_event_handler-event_source = controller_usage-controller_usage_name.

         ls_new_event_handler-ref_ctlr_name = component_controller.

      endif.



      ENDLOOP.





*Add paramter data

      LOOP AT wa_event_handler-method_parameters INTO wa_parameter.

        IF wa_parameter-parameter_name <> 'WDEVENT'.

          CLEAR ls_parameter.

          MOVE-CORRESPONDING wa_parameter TO ls_parameter.

          ls_parameter-abap_type = wa_parameter-associated_typ_ref-name.

          APPEND ls_parameter TO ls_new_event_handler-parameters.

        ENDIF.

      ENDLOOP.



      APPEND wa_event_handler TO cs_existing_controller_detail-ctlr_methods.

      APPEND ls_new_event_handler TO cs_existing_controller_detail-ctlr_details-event_handler.

    ENDLOOP.



  ENDMETHOD.

[pavitra_raghunathan]

Hi Oliver,

We are looking into this Note issue. Will update as soon as it is solved.

Regards,

Pavitra Raghunathan

[Former Member]

hi pavitra

thanx a lot so far 

regards oliver

[pavitra_raghunathan]

Hi Oliver,

I have investigated and found that there are many differences between both the code , one in your system and one in the note. If it is urgent would it be possible for you to do a manual fix from a text file which i will share in the note? Meanwhile I will try to resolve the note issue.

Regards,

Pavitra

[Former Member]

Hi Pavitra,

sure that is possible but it is not urgent anyway.

thanks a lot

oliver

[pavitra_raghunathan]

Hi Oliver,

To get the fix please apply the SAP Note 2014340 into the R/3 system.

The Note is applicable for

• 7.31 SP7 and later SPs
• 7.4 and SP2 and later SPs

Please use the above note which has the manual activity also mentioned.

Meanwhile i will try to fix the earlier Note.

Regards,

Pavitra

[Former Member]

hi pavirtra

great, the correction now works ! and the error does not appear anymore

thanx a lot

oliver

[Former Member]

HI Pavitra,

we are facing another serios bug in webdynpro eclipse environment.

when adding a Field (input field with label), the system says on activating or save "INvalid Enumeration Type for Property of field" (i translated to English as we use german eclipse which says "Ungültiger Aufzählungswert für Eigenschaft von Element"). No more details just impossible to save the View.

we have installed the latest version of eclipse ADT (2.24) - this seems to be a bug in eclipse ADT not in the backend???

regards oliver

[pavitra_raghunathan]

Hi Oliver ,

I will ask the concerned person to have a look into this. They will get back to you.

Regards,

Pavitra

[Former Member]

Good Day Pavitra,

I have applied note 2014340, I am still experiencing this error. I am using three different instances of SALV_WD_TABLE in my component controller. One is using event ON_SELECT, the other ON_FUNCTION and the third ON_DATA_CHECK. If I go into this component controller via Eclipse, All event handlers are changed to point to one instance.

Please advise .

Kind Regards,

[former_member256646]

Hi Oliver,

I am working on this issue.Will get back to you on this.\

Regards

Ponraj

[former_member256646]

Hi Oliver,

I tried it on 2.24 version  and system YI3. I was able to create input field with label , save it and

activate it. Did you bind the input field with value with the context attribute? If the issue still exists,

shall we have a call?

Regards

Ponraj

[Former Member]

Hi Ponraj,

the point is it happens not in every view only sometimes, before activating (on saving ) this message arises. maybe our backend 740 SP3 is not the best for AIE 2.24???

[former_member256646]

Hi Oliver,

No, The backend for 740 SP3 IS compatible for AiE. I also checked in SP03 system. It works fine.

[Former Member]

ok thank you we will have a look on it, maybe just a temporary problem. the problem is the message "invalid enumaration type" is not really a "nice" message as its impossible to find out what went wrong`?regards oliver