Dump while using BAPI BAPI_SALESORDER_CREATEFROM in background

[Former Member]

Hi All,

I am using bapi BAPI_SALESORDER_CREATEFROM to create sales order in background. I am picking a file from server and converting that into header and line iten and passing that to above BAPI. Its creating order successfully and background job is also finished successfully. But when we check ST22 there is always a short dump corresponding to above job.

Can someone please help me? Following is some of the text from dump

Runtime Error DYNPRO_SEND_IN_BACKGROUND

Occurred on 06.05.2009 at 16:07:12

Screen output without connection to user.

What happened?

Error in ABAP application program.

The current ABAP program "SAPMSSY0" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

Information on where terminated

The termination occurred in the ABAP program "SAPMSSY0" in "%_CTL_OUTPUT".

The main program was "SAPMV75B ".

The termination occurred in line 30 of the source code of the (Include)

program "<SYSINI>"

of the source code of program "<SYSINI>" (when calling the editor 300).

Error occurred during batch input processing

000270 * Nach DCO

000280 module %_CTL_OUTPUT output.

000290 perform %_CTL_OUTPUT in program SAPMSSYD using SY-REPID if found.

> endmodule.

000310

Regards,

Sanjay

[Former Member]

Have you hard coded the file path properly.

Regards,

Lalit Mohan Gupta.

[Former Member]

Hi Lalit,

I didn't understand what do you mean?

I have uploaded header and line item file into internal table and converted them according to BAPI requirement and then I am passing internal tables to BAPI. Its creating order successfully and as I said earlier also job is also finished successfully but when I check ST22 there is a dump corresponding to above job.

thanks,

Regards,

Sanjay

[Former Member]

Run your BAPI in se37 and pass the same data that you are passing in the program.

There might be some screen popping up when the BAPI runs.

If you get a unexpected screen, you get this type of error.

Regards,

Ravi

[Former Member]

It was happening because there were some unexpected pop-ups.