Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

MESSAGE_TYPE_X runtime error occurs in LRSSM_LOADU08 include program

Former Member
0 Kudos
327

MESSAGE_TYPE_X runtime error occurs in the LRSSM_LOADU08 include program in

the SAPLRSSM_LOAD program of the RSSM_RSSELDONE_READ function

module.

Kindly guide what should be the corrective action for this runtime error.

7 REPLIES 7

Sm1tje
Active Contributor
0 Kudos
99

If you are sure that this is not caused by some custom development (user exit, BAdI or whatever), you should check for OSS notes, or create a message to SAP yourself.

Former Member
0 Kudos
99

Hi,

Are you in ECC 6.0? Tell me the value after 'Message type x'. So that I could suggest you.

Thank U,

Jay....

0 Kudos
99

Hi Jay,

Yes, I am working on ECC 6.0. But there is no value after MESSAGE_TYPE_X in the short dump.

Thanks

Edited by: Guestpab on May 29, 2009 10:35 AM

0 Kudos
99

can u please paste the dump error cause/description from ST22??

0 Kudos
99

Runtime Errors MESSAGE_TYPE_X

Date and Time 29.05.2009 04:49:21

-


-


Short text

The current application triggered a termination with a short dump.

-


-


What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

-


-


Error analysis

Short text of error message:

          • Scheduler

Long text of error message:

Technical information about the message:

Message class....... "RSM1"

Number.............. 000

Variable 1.......... " "

Variable 2.......... " "

Variable 3.......... " "

Variable 4.......... " "

-


-


Trigger Location of Runtime Error

Program SAPLRSSM_LOAD

Include LRSSM_LOADU08

Row 81

Module type (FUNCTION)

Module Name RSSM_RSSELDONE_READ

-


-


Source Code Extract

-


Line

SourceCde

-


51

data: l_tabname type tabname.

52

data: from_clause type string.

53

data: l_subrc like sy-subrc.

54

data: l_t_rnr_exp type rssm_t_request.

55

data: l_t_rnr type rssm_t_request.

56

57

data: l_t_seldone_sel like rsseldone occurs 0.

58

data: l_s_seldone_sel like rsseldone.

59

data: l_lines type i.

60

data: l_s_reqdone like rsreqdone.

61

62

*----


63

64

if not i_parameter is initial.

65

import l_t_rnr_exp from data buffer i_parameter.

66

l_t_rnr[] = l_t_rnr_exp[].

67

else.

68

l_t_rnr[] = i_t_rnr[].

69

endif.

70

71

l_t_where[] = i_t_where[].

72

delete l_t_where where field is initial.

73

l_rnr = i_rnr.

74

75

  • if l_rnr is initial.

76

  • l_rnr = i_s_rsseldone-rnr.

77

  • endif.

78

if l_rnr is initial.

79

if l_t_rnr[] is initial and i_t_where[] is initial and

80

i_use_sl_tabs is initial.

>>>>>

message x000.

82

endif.

83

endif.

84

85

clear e_s_rsseldone.

86

refresh e_t_rsseldone.

87

88

if not l_rnr is initial.

89

if i_single_select is initial.

90

select * from rsseldone into table e_t_rsseldone where

91

rnr = l_rnr.

92

else.

93

select single * from rsseldone into e_s_rsseldone where

94

rnr = l_rnr.

95

endif.

96

else.

97

if not l_t_rnr[] is initial.

98

perform fill_temp_table(saplrssm) tables l_t_rnr

99

changing l_tabname

100

l_subrc.

-


former_member226519
Active Contributor
0 Kudos
99

check the reason for the error with ST22.

Former Member
0 Kudos
99

The message raised because of wrong logic of calling parameters of the function.

if you don't pas value at parameter l_rnr it is necessary to enter values at tables

i_t_rnr and i_t_where