Dump while executing FM IDOC_INPUT

[Former Member]

Dear Friends,

We are trying to execute the function module "IODC_INPUT" and getting a short dump.

Basically the scnario is that we are trying to change an IDOC through transaction WE19 and then we execute the same by pressing tab "STANDARD INBOUND".

But as soon as we press this button we get the short dump. whereas if I process the IDOC by pressing tab "Inbound Function Module" , there is no error and we are able to process the idoc successfully.

Request you to please guide why this problem is there and what is the resolution for the same.

Regards,

Lalit Kabra

[Former Member]

solved

[Former Member]

Dear collegues,

we want to integrate an stock transfer order (ME27 or ME21N-type UB) IDOC. We have tried with the ORDERS type (ORDERS05) but a lot of errors appears.

Somebody knows the correct way to create an stock transfer order with an inboud IDOC ?

Thanks in advance.

Best regards,

Y.López

[Former Member]

Dear Lalit,

could you pls post the short dump here, thanks.

kr,

andreas

[Former Member]

Hi Andreas,

Pls find below the dump... As i am not be send in single reply, I have slit it in 2 (Pls see below)

Your kind response would be highly appreciated.

Regards,

Lalit Kabra

Edited by: Lalit Kabra on Jul 20, 2009 5:51 PM

[Former Member]

Please find Dump report with this and subsequent reply.......

Runtime Errors SYNTAX_ERROR

Date and Time 20.07.2009 17:09:35

Short text

Syntax error in program "SAPLBD20 ".

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLEDIR" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLBD20 " in include "LBD20U05

" in

line 99:

"Type "IDOC_DATA_CRYPTION" is unknown"

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "SAP "

Error in the ABAP Application Program

The current ABAP program "SAPLEDIR" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

Error analysis

The following syntax error was found in the program SAPLBD20 :

"Type "IDOC_DATA_CRYPTION" is unknown"

"Type "IDOC_DATA_CRYPTION" is unknown"

Trigger Location of Runtime Error

Program SAPLEDIR

Include LEDIRU02

Row 182

Module type (FUNCTION)

Module Name IDOC_START_INBOUND

[Former Member]

2nd mail to provide dump......

Source Code Extract

Line SourceCde

152

153 WHEN '6' " ALE / function module

154 OR '8'.

155 * unfortunately we need to move the idoc numbers into a second table

156 LOOP AT t_control_records.

157 l_t_unprocessed_idocs = t_control_records-docnum.

158 APPEND l_t_unprocessed_idocs.

159 ENDLOOP.

160

161 * pass idocs into application

162 * call ALE function 'IDOC_INPUT'

163 * nur für BECK-test

164 * if sy-uname eq 'XMB_USER'.

165 * CALL FUNCTION 'IDOC_INPUT'

166 * starting new task 'ZADE'

167 * EXPORTING

168 * mass_processing = c_true

169 * direct_call = c_true

170 * end_event_enabled = c_true

171 * idoc_start_event_enabled = pi_start_event_enabled

172 * do_commit = pi_do_commit

173 * process_code = pi_inbound_process_data-evcode

174 * TABLES

175 * unprocessed_idocs = l_t_unprocessed_idocs

176 * idoc_data = t_data_records

177 * idoc_control = t_control_records

178 * EXCEPTIONS

179 * others = 0.

180 * else.

181 * "beck - später zu löschen

>>>>> CALL FUNCTION 'IDOC_INPUT'

183 EXPORTING

184 mass_processing = c_true

185 direct_call = c_true

186 end_event_enabled = c_true

187 idoc_start_event_enabled = pi_start_event_enabled

188 do_commit = pi_do_commit

189 process_code = pi_inbound_process_data-evcode

190 TABLES

191 unprocessed_idocs = l_t_unprocessed_idocs

192 idoc_data = t_data_records

193 idoc_control = t_control_records

194 EXCEPTIONS

195 idoc_open_lock = 1

196 idoc_open_not_exist = 1

197 idoc_open_invalid = 2

198 idoc_open_already = 2

199 idoc_write_number_invalid = 2

200 idoc_write_status_invalid = 1

201 idoc_write_no_status = 2