Unable to interpret "J2EESYSTEM" as a number.

[former_member325638]

Hi All,

We are facign issue in setting up any new report in solution manager system (EWA or SLR etc).  While I try to create a new report it gives run time error "Unable to interpret "J2EESYSTEM" as a number."

It is happening from last two weeks; when we had a j2ee stack upgrade. Before that it was fine. Solution manager system is 7.01.  Could you please advise if anyone has faced below issue. 

Run time error details are given below

"

Runtime Errors         CONVT_NO_NUMBER
Date and Time          16.07.2013 09:47:48

Short text
     Unable to interpret "J2EESYSTEM" as a number.

What happened?
     Error in the ABAP Application Program

     The current ABAP program "RDSVASASLR_CUSTOMIZING_____005" had to be terminated
      because it has
     come across a statement that unfortunately cannot be executed.

Error analysis
     An exception occurred that is explained in detail below.
     This exception cannot be caught in the context of the current statement.
     The reason for the exception is:
     The program attempted to interpret the value "J2EESYSTEM" as a number, but
     since the value contravenes the rules for correct number formats,
     this was not possible.

Trigger Location of Runtime Error
     Program                                 RDSVASASLR_CUSTOMIZING_____005
     Include                                 RDSVASASLR_CUSTOMIZING_____005
     Row                                     2.521
     Module type                             (FORM)
     Module Name                             ACTION_011

2491     md_model_open_in_session lf_model_inst 'EWA Data Model'

2492         space lf_ewa_model_handle.                          "#EC NOTEXT

2493   ENDIF.

2494

2495   md_objects_get lf_ewa_model_handle space 'Performance Ind'

2496       lt_objects lt_attributes space.                       "#EC NOTEXT

2497

2498   READ TABLE lt_objects INTO ls_object WITH KEY object_class = 'Performance Ind'. "#EC NOTEX

2499   READ TABLE lt_attributes INTO ls_attribute WITH KEY object_no = ls_object-object_no

2500                                                       attrib_class = 'Check Table'. "#EC NOT

2501

2502   md_attribute_table_get lf_ewa_model_handle ls_attribute-object_no

2503                          ls_attribute-attrib_no lt_ewa_kpi.

2504

2505 * Fill table Target KPIs

2506   get_current_value 'GENERAL' 'Parent IT_REPORT' variant_name. "#EC NOTEXT

2507

2508   get_value_for_context dsap_context_it_report variant_name

2509     'GENERAL' 'type_key' variant_type.                      "#EC NOTEXT

2510

2511   get_tables lt_check.

2512   DELETE lt_check WHERE cntr = 2.

2513

2514   IF lt_ewa_kpi[] IS INITIAL.       "show all KPIs except BW, HWC, HTTP and RFC types

2515     LOOP AT lt_check INTO ls_check WHERE cntr = 5 AND field8 <> 'RFC' AND field8 <> 'HTTP' A

2516       ls_check-cntr = 2.

2517       APPEND ls_check TO lt_tmp.

2518     ENDLOOP.

2519   ELSE.

2520     LOOP AT lt_ewa_kpi.               "show KPIs available in EWA

>>>>       IF lt_ewa_kpi-field5 = 2 OR lt_ewa_kpi-field5 = 3 OR lt_ewa_kpi-field5 = 4 OR lt_ewa_k

2522 *       adjust KPI key according to profile (DIA or RFC)

2523         IF lt_ewa_kpi-field2 CS 'RFC'.

2524           CONCATENATE lt_ewa_kpi-field5 lt_ewa_kpi-field5 INTO lt_ewa_kpi-field5.

2525         ENDIF.

2526       ENDIF.

2527       IF lt_ewa_kpi-field5 = 11.

2528 *       adjust KPI key according to variant type

2529         CASE variant_type.

2530           WHEN '1'.

2531             lt_ewa_kpi-field5 = '11'.          "Use KPI 'DB Growth (weekly)'

2532           WHEN '2'.

2533             lt_ewa_kpi-field5 = '99'.          "Use KPI 'DB Growth (monthly)'

2534           WHEN OTHERS.

2535             lt_ewa_kpi-field5 = '11'.

2536         ENDCASE.

2537       ENDIF.

2538       READ TABLE lt_check INTO ls_check WITH KEY cntr = 5 field6 = lt_ewa_kpi-field5.

2539       IF sy-subrc = 0.

2540         ls_check-cntr = 2."

Thanks

Varun

[former_member184473 · Accepted solution]

Hello Varun,

Check notes 1819589 and 1684399.

Regards,

Eduardo Rezende

[Former Member · Accepted solution]

Hi varun,

As mentioned by Eduardo please check note

1819589 - Short Dump CONVT_NO_NUMBER when opening Service Level Reporting Setup Screen

as it talks about the same program in which you are facing the issue.

Thanks

Rishi Abrol

[former_member325638 · Accepted solution]

Thanks Edurado and Rishi.  Problem solved