Error Calling BAPI_INCOMINGINVOICE_SAVE: "Screen output without connection"

[Former Member]

Hello all,

I have a problem with a creation of ad adapter which call a BAPI_INCOMINGINVOICE_SAVE function module with Jco 3.0.

When the program starts, I have this follow error:

Screen output without connection to user

Edited by: Davide Bruno on Jul 7, 2009 12:51 PM

[Former Member]

.

[Former Member]

---

#Error run-time DYNPRO_SEND_IN_BACKGROUND

Verific. il 06.07.2009 h 16:49:56

*Screen output without connection to user.

1. What happened?

Error in ABAP application program.

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

statements could not be executed.

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

#What happened?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

#Error analysis

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPLRHRD " 0100.

#How to correct the error

If the error occurred in one of your own programs or in an SAP program

that you modified, try to correct it yourself.

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"DYNPRO_SEND_IN_BACKGROUND" C

"SAPLRHRD" or " "

"SYSTEM-EXIT"

[Former Member]

Environment

-

---

SAP Release.............. "620"

Application server....... "svuni045"

Network address.......... "10.131.97.21"

Operating system......... "AIX"

Release.................. "5.3"

Hardware type............ "00C6E25F4C00"

Character length......... 8 Bits

Pointer length........... 64 Bits

Work process number...... 0

Short dump setting....... "full"

Database server.......... "svuni045"

Database type............ "ORACLE"

Database name............ "AVQ"

Database owner........... "SAPR3"

Character set............ "en_US.ISO8859-1"

SAP kernel............... "640"

Created on............... "Aug 17 2008 21:06:36"

Created in............... "AIX 1 5 00538A4A4C00"

Database version......... "OCI_920 "

Patch level.............. "247"

Patch text............... " "

Supported environment....

Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE

10.2.0.."

SAP database version..... "640"

Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Utente, transazione.....

Client.............. 030

User................ "CFMDMAHC"

Language key........ "E"

Transaction......... " "

Program............. "SAPLRHRD"

Screen.............. "SAPLRHRD 0100"

Row of screen....... 0

Information about program making the Remote Function Call (RFC):

System.............. "########"

Database Release.... 711

Kernel Release...... 711

Connection type: "E" (2 = R/2, 3 = R/3, E = External, R = Reg.external)

Call type: "synchron (imode 0)" (S = Synchronous, a/A = Asynchronous, T =

Transaction)

Client.............. "###"

User................ "############"

Transaction......... "####################"

Function module..... "BAPI_INCOMINGINVOICE_SAVE"

Call destination.... "SAP_SERVER"

Source server....... "caudana"

Source IP address... "172.23.131.42"

Additional RFC logon information:

Trusted Relation....." "

Logon return code....0

Trusted return code..0

Note: Prior to Release 4.0, there was less information available on RFC

calling programs.

Information on where terminated

-

---

The termination occurred in the ABAP program "SAPLRHRD" in "SYSTEM-EXIT".

The main program was "SAPMSSY1 ".

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

program " "

of the source code of program " " (when calling the editor 00).

Thank you very much

Davide Bruno