cancel
Showing results for 
Search instead for 
Did you mean: 

SAP SEM - RAISE_EXCEPTION - ILLEGAL_INPUT

Former Member
0 Kudos

Hi All,

I am executing the transaction UPSPL and after I tried to save the excel spreadsheet I receive this error below:

Due the size of short dump, I just cut the important parts.

Runtime Errors RAISE_EXCEPTION

Date and Time 29.11.2007 17:06:26

Short dump has not been completely stored (too big)

ShrtText

Exception condition "ILLEGAL_INPUT" raised.

Error analysis

A RAISE statement in the program "SAPLRSDRI" raised the exception

condition "ILLEGAL_INPUT".

Since the exception was not intercepted by a superior program

in the hierarchy, processing was terminated.

-

"RAISE_EXCEPTION" C

"SAPLRSDRI" or "LRSDRIU06"

"RSDRI_CUBE_WRITE_PACKAGE"

103 * --- a transactional application tries to write into a standard cube

104 ELSE.

105

106 MESSAGE ID 'DBMAN'

107 TYPE 'A'

108 NUMBER 161

109 WITH i_infocube

110 RAISING not_transactional.

111

112 ENDIF.

113

114 * exception handling

115 CASE l_subrc.

116 WHEN 0.

117 WHEN 1.

118 RAISE infocube_not_found.

119 WHEN 2.

120 RAISE data_structure_error.

121 WHEN 3.

>>>>> RAISE illegal_input.

123 WHEN 5.

124 RAISE rollback_error.

125 WHEN 6.

126 RAISE duplicate_records.

127 WHEN 7.

128 RAISE not_transactional.

129 WHEN OTHERS.

130 RAISE x_message.

The unique clue that I have is that in the other country this report works properly with the same userid. Perhaps the excel properties that are setup with number handling with decimal separator = "," and Thousands = "."

I applied the latest patch SAPGui / Bw.

Any idea about this problem.

Thanks in advance and Best Regards.

Celio Almeida

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

The SAP suppport found the problem in USERID that's is just number and need to has a caracters.