cancel
Showing results for 
Search instead for 
Did you mean: 

Open HUb resulting in a DUMP

former_member214778
Participant
0 Kudos

Hi Experts,

I am extracting data from Query using OPenhub to a file in App server. Now when I try to load using Open Hub DTP the load is throwing me dump.

There is not much information in the DTP monitor. The Dump says :

Category               ABAP Programming Error

Runtime Errors         MESSAGE_TYPE_X

ABAP Program           CL_RSB_DEST_VERS==============CP

Application Component  BW-WHM-DBA

Date and Time          21.07.2016 08:11:42

How to correct the error

    Probably the only way to eliminate the error is to correct the program.

    -

    If the error occures in a non-modified SAP program, you may be able to

    find an interim solution in an SAP Note.

    If you have access to SAP Notes, carry out a search with the following

    keywords:

    "MESSAGE_TYPE_X" " "

    "CL_RSB_DEST_VERS==============CP" or "CL_RSB_DEST_VERS==============CM00Q"

    "GET_OBJ_REF_STRUCTDESCR"

Information on where terminated

    Termination occurred in the ABAP program "CL_RSB_DEST_VERS==============CP" -

     in "GET_OBJ_REF_STRUCTDESCR".

    The main program was "RSBATCH_EXECUTE_PROZESS ".

Source Code Extract

37           WHEN cl_abap_typedescr=>typekind_time.

38             l_r_elem = cl_abap_elemdescr=>get_t( ).

39           WHEN cl_abap_typedescr=>typekind_char.

40             l_r_elem = cl_abap_elemdescr=>get_c( l_length ).

41           WHEN cl_abap_typedescr=>typekind_num.

42             l_r_elem = cl_abap_elemdescr=>get_n( l_length ).

43           WHEN cl_abap_typedescr=>typekind_hex.

44             l_r_elem = cl_abap_elemdescr=>get_x( l_length ).

45           WHEN cl_abap_typedescr=>typekind_int1.

46             l_r_elem ?= cl_abap_elemdescr=>describe_by_name( 'INT1' ).

47           WHEN cl_abap_typedescr=>typekind_int2.

48             l_r_elem ?= cl_abap_elemdescr=>describe_by_name( 'INT2' ).

49           WHEN cl_abap_typedescr=>typekind_packed.

50             l_length = l_s_field-intlen.

51             CALL METHOD cl_abap_elemdescr=>get_p

52               EXPORTING

53                 p_length   = l_length

54                 p_decimals = l_decimals

55               RECEIVING

56                 p_result   = l_r_elem.

57           when 'V'. "VARC in case of type file

58             l_r_elem = cl_abap_elemdescr=>get_c( l_length ).

59           WHEN OTHERS.

>>>             MESSAGE x299.

61         ENDCASE.

62         l_s_compdescr-name = l_s_field-fieldnm.

63         l_s_compdescr-type = l_r_elem.

Any inputs or thoughts are appreciated.

Regards,

Mukesh

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member186053
Active Contributor
0 Kudos

Hi Mukesh,

please go through below link, might be helpful.

https://scn.sap.com/thread/3398345

Thanks,
Vengal.

former_member214778
Participant
0 Kudos

Hello Vengal,

The above link is for different Short Dump not related to my issue.

Regards,

Mukesh

former_member186053
Active Contributor
0 Kudos

Hi Mukesh,

You are correct, the short dump which you got is more genric. I thought that link might give an idea to do some more analysis.

Did you try to debug the trasnformation by using DTP in debug mode?

Also try to search in service market place for related sap notes with your short dump key words, but you need to have access for service market place.

Thanks,

Vengal.

former_member214778
Participant
0 Kudos

Hi Vengal,

Yes,  I tried with debugging mode by applying break points at start of transformation in DTP.

However the load is throwing short dump by not going inside of transformation.

searching in Market place now.

Thanks

former_member200967
Active Participant
0 Kudos

Hi Mukesh,

The error seems to be in the start of the DTP llogic where there is a failure due to data type mismatch of some field.

Can you try looking into this area oncec.

Regards

Manpreet

former_member214778
Participant
0 Kudos

Hi Manpreet,

Yes, you are right. I have gone thru the program and found it is related to the type mismatch. The Open hub is taking few calculated Key figures in the report as DF34 which is not acceptable according to the table RSBOHFIELDS. So do we have any other alternative  data type declarations available. Once I delcare the same the issue will resolve.

Regards,

Mukesh