ABAP DUMP Dynpro_send_in_background occurs in ECC5.0

[Former Member]

Hi experts,

We have one ECC5.0 environment which runs on AIX5.3 , and since yesterday, we have lots of ABAP dump Dynpro_send_in_background in st22, could anyone help me? I have searched from OSS and SDN, but seems no suitable case I can reference for our system. Please give me some hint,thank you.

System information

Version ：ECC5.0

patch level ：version 6.40 level 125

Database version ：Oracle 9.2.0.7

Long text in ST22

Runtime Error DYNPRO_SEND_IN_BACKGROUND

Date and Time 01.07.2008 17:05:09

ShrtText

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.

What can you do?

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.

is especially useful if you want to keep a particular message.

Error analysis

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPMSSY0 " 0120.

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

"SAPMSSY0" or " "

"SYSTEM-EXIT"

-

-

---

If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)".

2. A suitable printout of the system log

To obtain this, call the system log through transaction SM21.

Limit the time interval to 10 minutes before and 5 minutes

after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, select the Editor function "Further Utilities->

Upload/Download->Download".

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

System environment

SAP Release.............. "640"

Application server....... "yatptcp"

Network address.......... "10.1.250.65"

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

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

Hardware type............ "00001E22D700"

Character length......... 16 Bits

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

Work process number...... 4

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

Database server.......... "yatptcp"

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

Database name............ "TCP"

Database owner........... "SAPTCP"

Character set............ "C"

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

Created on............... "May 1 2006 20:49:14"

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

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

Patch level.............. "125"

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"

Memory usage.............

Roll..................... 16192

EM....................... 25139136

Heap..................... 0

Page..................... 835584

MM Used.................. 8185592

MM Free.................. 191328

SAP Release.............. "640"

User and Transaction

Mandant............. 400

Benutzer............ "KOERFCUSER"

Sprachenschlüssel... "E"

Transaktion......... " "

Programm............ "SAPMSSY0"

Dynpro.............. "SAPMSSY0 0120"

Dynprozeile......... 0

Informationen zum Aufrufer des Remote Function Calls (RFC):

System.............. "TCP"

Datenbank-Release... 640

Kernel-Release...... 640

Verbindungstyp...... 3 (2 = R/2, 3 = R/3, E = Extern, R = Reg. Extern)

Aufrufsart.......... "synchron (imode 1)" (S = Synchron, a/A = Asynchron, T =

Transakt. )

Mandant............. 400

Benutzer............ "KOERFCUSER"

Transaktion......... " (Program: SAPLEDIN)"

Funktionsbaustein... "IDOC_START_INBOUND"

Aufruf-Destination.. "NONE"

Quell-Server........ "yatptcp_TCP_01"

Quell-IP-Adresse.... "10.1.250.65"

Zusatzinformation zum RFC-Logon:

Trusted Beziehung... " "

Logon-Returncode.... 0

Trusted-Returncode.. 0

Bemerkung: Bei Releases < 4.0 sind die Informationen zum RFC-Aufrufer teilweise nicht vorhanden.

Information on where terminated

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

The main program was "SAPMSSY4 ".

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).

Active Calls/Events

No. Ty. Program Include

Name

1 EVENT SAPMSSY0 ???

SYSTEM-EXIT

Chosen variables

Name

Val.

No. 1 Ty. EVENT

Name SYSTEM-EXIT

SY-XPROG

SAPMSSY0

0000000000000000000000000000000000000000

0000000000000000000000000000000000000000

5454555322222222222222222222222222222222

310D339000000000000000000000000000000000

SY-XFORM

NEW-LINE

000000000000000000000000000000

000000000000000000000000000000

445244442222222222222222222222

E57DC9E50000000000000000000000

Internal notes

The termination occurred in the function "dynpex00" of the SAP

Basis System, specifically in line 1513 of the module

"//bas/640_REL/src/krn/dynp/dymain.c#9".

The internal operation just processed is "----".

The internal session was started at 20080701170507.

Active Calls in SAP Kernel

Lines of C Stack in Kernel (Structure Differs on Each Platform)

=> 64 bit R/3 Kernel

=> 64 bit AIX Kernel

=> Heap limit = unlimited

=> Stack limit = 4294967296

=> Core limit = 1073741312

=> File size limit = unlimited

=> Heap address = 0x0x118a5cf20

=> Stack address = 0xfffffffffff9f50

=> Stack low = 0xfffffffffff9f50

=> Stack high = 0xffffffffffff890

=> Stack Trace:

#AixStack() at 0x10004ae04

#CTrcStack2() at 0x10004aefc

#rabax_CStackSave__Fv() at 0x10007bb2c

#ab_rabax() at 0x100078bd8

#dypex00() at 0x10020a204

#dynpoutf() at 0x1011990c0

#dynprctl() at 0x10119fcf8

#dynpen00() at 0x10020de20

#Thdynpen00() at 0x1000a51f8

#TskhLoop() at 0x1000a884c

#tskhstart() at 0x1000becdc

#DpMain() at 0x101742da4

#nlsui_main() at 0x101716148

#main() at 0x101716104

[Former Member]

Hi,

I had exactly the same problem.

RFC ID was changed.

system --> dialog

Problem is solved now.

[Former Member]

Hi Han ,

Thank you for your reply.

Do you mean the rfcuser should be dialog type?

Actually I have used dialog user type currently with SAP_ALL authorization , but the error still happen.

I have read some threads show that the error might be caused on authorization or user type, but I don't know why errors still happen?

[Former Member]

hello there,

i am also facing the same problem,

if you get any solution to it.PLease help me also.

Where you have change the user type inSu01 na.

have click on radio button Service.

If not please try

If you get any abap help on it please mail on

anujarch@gmail.com

Thanks

Adi/.

Edited by: anuj adi on Jul 9, 2008 3:14 PM

[Former Member]

Dear All,

Any Solution for this similar problem - In Web Dynpro Application when we call the following application the DYNPRO_SEND_IN_BACKGROUND runtime error happens.

Note

 The following error text was processed in the system XXX : Screen output without connection to user.

 The error occurred on the application server xxxxxxxx_XXX_00 and in the work process 0 .

 The termination type was: RABAX_STATE

 The ABAP call stack was:

SYSTEM-EXIT of program SAPLSTRD

Function: TRINT_POPUP_EDIT_CANCEL_SHOW of program SAPLSTRD

Form: RAISE_ERROR of program SAPLSTRD

Function: TRINT_OBJECTS_CHECK_AND_INSERT of program SAPLSTRD

Function: TR_OBJECTS_CHECK of program SAPLSTRD

Function: RH_HRPOBJECT_CORR_AT_SAVE of program SAPLRHWM

Form: UPDATE of program SAPUP50R

Form: PUT_INFOTYP_BUFFER of program SAPFP50P

Form: %_PROCESS_P_O_C of program SAPMSSY0

Form: %_COMMIT of program SAPMSSY0

What can I do?

 If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system E6Q in transaction ST22.

 If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server xxxxxxx_XXX_00 in transaction SM21.

 If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server qltr01d3801_E6Q_00 . In some situations, you may also need to analyze the trace files of other work processes.

 If you do not yet have a user ID, contact your system administrator.

Error code: ICF-IE-http -c: 300 -u: X.XXXX -l: E -s: E6Q -i: xxxxxx_XXX_00 -w: 0 -d: 20080709 -t: 155438 -v: RABAX_STATE -e: DYNPRO_SEND_IN_BACKGROUND

HTTP 500 - Internal Server Error

Your SAP Internet Communication Framework Team

[Former Member]

Dear experts,

Finally we find the root cause for this dump.

The root cause is exactly the pop-up screen is triggered in background processing, But how? The reason is one of our developer changes the processing behavior, the billing document were printed without immediate printing, but changed to immediate, after the change, the background billing document process triggered the output process and then the dump took place. After we rollback the "without immediate output"action, the issue solved.

I am so appreciate for your help , thank you all.

[Former Member]

Hi Ren,

Please consult with abaper i think some programe error or may be user rights.

Regards,

Anil

[Former Member]

Hi ,

Thanks for your reply both.

The first one about the authorization part,we use a system user KOERFCUSER with the most powerful authozation (SAP_ALL).Is any other missing right I need to check?

And during our checking process, we found that when the inbound IDoc created in this ECC5.0 environment, it continue the billing process automatically, and at the same time, it will update related data into SIS tables ( S640 in this case ). but it failed. If we manually reprocess the IDoc in debug mode, there is a screen popup and shows the message (update control), we think the popup screen cause the ABAP dump, it that right?

And if it is right, how can we solve it?

By the way, please forgive me for the description of the problem since I am junior...

[Former Member]

Hi

No issue of the junior or senior,

this forum is to provide the solution, Be more specific the question u raised in the forum.

I might the SIS tables might not be raised when u have triggered,

Trace the user and do the task again, analyze the log and discuss with the abaper.

Or else

u configure the audit for that user and do the task where u got the dump. make a note of the programs and analyze with the abap team

Regards

Bhaskar

Edited by: bhaskar1818 on Jul 3, 2008 10:13 AM

[Former Member]

Hi sir,

We are always tring to find out the root cause for the ABAP dump.

After checking from SAP developer team in Germany, they tell us that the cause for ABAP dump Dynpro_send_in_background is definitely by the popup screen when our inbound IDoc is processed in background.

But right now we can't know how it happened because it works before, and suddenly the function got errors.

If it caused on user authorizations, how can we check it since the background user has SAP_ALL authorization.

Right now we know the triggered screen is processed in function module GN_INVOICE_CREATE , but how can we fix it?

[Former Member]

Hi

Chen

This dump is raised due to which transcation.

Make a note of it, does that particular user has full authorization on that transaction. because this is an authorization issue.

Regards

Bhaskar