UNCAUGHT_EXCEPTION ==> CX_WD_CONTEXT

[former_member429661]

Hi all,

my Dynpro works fine in Q-environment but after transportation into P-environment it didn't work.

In Q i see the developed screen but in P it throws an error before. I tried to analyse if m own code had a problem, but all my breakpoints on my own code didn't reached. So I think it is somewhere in the framework in conclusion with basis infrastucture definitions. Someone an idea where to look ?

Error messages from ST22.

Error-text in the browser is: it is not a valid attribute type.

The error kind is: RABAX_STATE

Source-code from ST22 is:

1 method getattribute_rtti.

2

3 data:

4 rtti_attr type ref to cl_abap_elemdescr,

5 rtti type ref to cl_abap_typedescr,

6 ddfields type ddfields,

7 full_name type string,

8 attr_index type i,

9 fixed_values type ddfixvalues,

10 val_set_wa type wdr_context_attr_value.

11

12 field-symbols:

13 <rtti_comp> like line of me->static_element_rtti->components,

14 <dfies_comp> type line of ddfields,

15 <fixed_value> like line of fixed_values.

16

17 if attr_ref is initial.

18 read table attributes->* with table key name = attr_name reference int

19 check sy-subrc = 0.

20 else.

21 o_attr_ref = attr_ref.

22 endif.

23 check o_attr_ref->rtti is not bound. " otherwise data are already there

24

25 if o_attr_ref->is_static = abap_false.

26 try.

27 if o_attr_ref->rtti is initial and o_attr_ref->type_name is initia

>>> raise exception type cx_wd_context

29 exporting

30 textid = cx_wd_context=>no_valid_attribute_type

31 attribute_name = full_name

32 problem_hint = o_attr_ref->type_name.

33 elseif o_attr_ref->rtti is initial.

34 call method cl_abap_typedescr=>describe_by_name

35 exporting

36 p_name = o_attr_ref->type_name

37 receiving

38 p_descr_ref = rtti

39 exceptions

40 others = 4

Trasaction info:

Programm............ "CL_WDR_CONTEXT_NODE_INFO======CP"

Dynpro.............. "SAPMHTTP 0010"

Dynprozeile......... 2

SAP-Release 701

The dynpro should read different table which i defined in context of the component controller and drag and drop into my view. That's all.

Hope this gives a idea of my problem/error.

Thanks in advance,

-- Bernd

[Former Member · Accepted solution]

Did you created any new data elements in Q system which are bound to any one of context attributes.

Problem might be a data element could be missing in P system for defined attributes type in context of WD component.

Check if any data elements that are created in Q system and are used in this wd component are transported to P system

Regards

Manas Dua

[former_member429661 · Accepted solution]

Hi Manas,

that was the right hint. Problem was an untransportet structure of my colleg, which wasn't in P-environment.

Thanks a lot for the fast an helpful answer...

--Bernd

[Former Member · Accepted solution]

Where I see it? Could tell, thanks.