topic Re: ABAP Dump DYNPRO_SEND_IN_BACKGROUND in Application Development and Automation Discussions

ABAP Dump DYNPRO_SEND_IN_BACKGROUND

Former Member — Fri, 08 Aug 2008 11:08:49 GMT

Hi all,

I got the following dump and corresponding update error when using the transaction VL02N . I would like to know how to proceed with this error. I happened to go the ABAPER to check in which include program it actually happened.

He could not help and he wanted the exact include program The basis person also could not help me.

It is saying that the dump has occured in SAPVM04 screen 4004. But in which include it has occured. If i could get that information, it would be useful.

The DUMP File is given below

Runtime Error DYNPRO_SEND_IN_BACKGROUND

Occurred on 07.08.2008 at 16:20:21

Screen output without connection to user.

What happened?

Error in ABAP application program.

The current ABAP program "SAPMV50A" 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.

Error analysis

During background processing, the system attempted to send a

screen to a user.

Current screen: "SAPMV50A " 4004.

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

"SAPMV50A" or " "

"SYSTEM-EXIT"

If you cannot solve the problem yourself, please send the

following documents to SAP:

1. A hard copy print describing the problem.

To obtain this, select the "Print" function on the current screen.

2. A suitable hardcopy prinout of the system log.

To obtain this, call the system log with Transaction SM21

and select the "Print" function to print out the relevant

part.

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

supply the source code.

To do this, you can either use the "PRINT" command in the editor or

print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

System environment

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

Application server....... "awnts200"

Network address.......... "192.168.10.10"

Operating system......... "Windows NT"

Release.................. "5.2"

Hardware type............ "16x Intel 80686"

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

Pointer length........... 32 Bits

Work process number...... 18

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

Database server.......... "AWNTS200"

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

Database name............ "PRD"

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

Character set............ "English_United State"

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

Created on............... "Feb 25 2008 00:15:42"

Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version......... "OCI_920_SHARE "

Patch level.............. "222"

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

Supported environment....

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

10.2.0.."

SAP database version..... "640"

Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,

Windows NT 6.0"

User, transaction...

Client.............. 999

User................ "C_FGSTR"

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

Transaction......... "VL02N "

Program............. "SAPMV50A"

Screen.............. "SAPMV50A 4004"

Screen line......... 0

Information on where terminated

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

The main program was "SAPMV50A ".

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

The program "SAPMV50A" was started in the update system.

Contents of system fields

SY field contents..................... SY field contents.....................

SY-SUBRC 0 SY-INDEX 0

SY-TABIX 19 SY-DBCNT 0

SY-FDPOS 30 SY-LSIND 0

SY-PAGNO 0 SY-LINNO 1

SY-COLNO 1 SY-PFKEY E0

SY-UCOMM SY-TITLE Change Outbound Delivery

SY-MSGTY E SY-MSGID TD

SY-MSGNO 600 SY-MSGV1 *

SY-MSGV2 * SY-MSGV3 *

SY-MSGV4

Active calls / events

No.... Type........ Name..........................

Program

Include Line

Class

1 EVENT SYSTEM-EXIT

SAPMV50A

??? 0

Chosen variables

1 EVENT SYSTEM-EXIT

SAPMV50A

??? 0

SY-XPROG SAPCNVE

5454454222222222222222222222222222222222

3103E65000000000000000000000000000000000

SY-XFORM CONVERSION_EXIT

444545544454545222222222222222

3FE65239FEF5894000000000000000

Application Calls

No dump information available

Application Information

No dump information available

Internal notes

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

Basis System, specifically in line 1992 of the module

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

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

The internal session was started at 20080807162021.

Active calls in SAP kernel

SAP (R) - R/3(TM) Callstack, Version 1.0

Callstack without Exception:

App : disp+work.EXE (pid=4428)

When : 8/7/2008 16:20:21.500

Threads : 2

Computer Name : AWNTS200

User Name : SAPSERVICEPRD

Number of Processors: 16

Processor Type: x86 Family 6 Model 15 Stepping 11

Windows Version : 5.2 Current Build: 3790

Stack Dump for Thread Id c4c

eax=0006cce8 ebx=00000420 ecx=8281c518 edx=00000000 esi=00000420 edi=00000000

eip=7c8285ec esp=040de140 ebp=040de1b0 iopl=0 nv up ei ng nz ac po cy

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000297

function : KiFastSystemCallRet

7c8285ec c3 ret

7c8285ed 8da42400000000 lea esp,[esp] ss:040de140=7c827d0b

7c8285f4 8d642400 lea esp,[esp] ss:2f25d153=????????

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name

040de1b0 77e61c8d 00000420 0001d4c0 00000000 040de1e8 ntdll!KiFastSystemCallRet

040de1c4 00f60beb 00000420 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject

040de1e8 0053f349 0053f382 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess >

> [ntstcdbg.c (501)]

040de1ec 0053f382 7c38b5c8 7c38b5c8 7c38b5c8 01760a0c disp+work!NTStack >

> [dptstack.c (1360)]

040de208 0053f3b6 7c38b5c8 00000000 0081edb0 7c38b5c8 disp+work!CTrcStack2 >

> [dptstack.c (345)]

040de214 0081edb0 7c38b5c8 00040000 32315f59 34303030 disp+work!CTrcStack >

> [dptstack.c (175)]

040de230 008222e9 00000000 8281cee0 00800000 3f3f3f3f disp+work!rabax_CStackSave >

> [abrabax.c (6987)]

040de6d0 00551139 01767f04 01767ee8 000007c8 017665e4 disp+work!ab_rabax >

> [abrabax.c (1051)]

040de798 00582427 01775a1c 8281c5b0 00000003 040dfdcc disp+work!dytrcexit >

> [dymain.c (1992)]

040de7b4 00553e5d 8281c5b0 00000009 00000001 00000000 disp+work!dynprctl >

> [dymainstp.c (351)]

040dfdcc 00477159 00000013 040dfe74 00000001 0049afb5 disp+work!dynpen00 >

> [dymain.c (1401)]

040dfddc 0049afb5 00000009 01033800 003e6018 00000002 disp+work!Thdynpen00 >

> [thxxhead.c (4517)]

040dfeec 0049b36a 00000001 a27db000 00000000 00000000 disp+work!TskhLoop >

> [thxxhead.c (4280)]

040dff04 00422eef 00000000 00000000 040dff60 0040108a disp+work!tskhstart >

> [thxxhead.c (1046)]

040dff14 0040108a 00000003 003e6018 00000001 00000000 disp+work!DpMain >

> [dpxxdisp.c (1013)]

040dff60 010e2a79 00000003 003e6018 003e2b28 01658000 disp+work!nlsui_main >

> [thxxanf.c (85)]

040dffc0 77e6f23b 00000000 00000000 a27db000 00000000 disp+work!mainCRTStartup >

> [crtexe.c (398)]

040dfff0 00000000 010e2936 00000000 00905a4d 00000003 kernel32!ProcessIdToSessionId

Stack Dump for Thread Id 14b4

eax=00000001 ebx=00000103 ecx=7c829f59 edx=00450000 esi=00000000 edi=00000000

eip=7c8285ec esp=069dfeb0 ebp=069dfef4 iopl=0 nv up ei pl zr na po nc

cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246

function : KiFastSystemCallRet

7c8285ec c3 ret

7c8285ed 8da42400000000 lea esp,[esp] ss:069dfeb0=7c8270fb

7c8285f4 8d642400 lea esp,[esp] ss:31b5eec3=????????

FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name

069dfef4 01033f40 00000634 00000000 00000000 003e82b0 ntdll!KiFastSystemCallRet

069dff84 7c349565 00000000 00000000 00000000 003e7930 disp+work!SigIMsgFunc >

> [signt.c (632)]

069dffb8 77e64829 003e7930 00000000 00000000 003e7930 MSVCR71!endthreadex

069dffec 00000000 7c3494f6 003e7930 00000000 00000000 kernel32!GetModuleHandleA

List of ABAP programs affected

Type

Program

Gen. Date Time

Load Size

Prg	SAPMV50A	06.04.2008 13:42:44	1951744
Prg	SAPMSSYD	05.06.2002 17:09:33	16384
Prg	SAPFSYSCALLS	14.02.2002 14:22:47	6144
Prg	SAPLEHS002	06.04.2008 13:42:44	10240
Prg	SAPLR3_EXTENSION_SWITCH	10.06.2007 08:12:48	18432
Typ	PAKHIERARC	20.01.2003 16:27:06	3072
Typ	TDEVC	28.09.2001 11:44:29	5120
Prg	SAPLPA_PACKAGE_SERVICES	10.06.2007 08:39:01	84992
Prg	SAPLITSR	10.06.2007 09:03:06	98304
Prg	CONTEXT_X_SP_INFO	10.06.2007 08:12:36	33792
Typ	TCONT	29.07.1998 19:46:10	2048
Typ	TCONT	29.07.1998 19:46:10	2048
Prg	CL_EXITHANDLER================CP	10.06.2007 08:42:10	27648
Prg	SAPLSEXV	10.06.2007 08:39:17	107520
Prg	CL_BADI_FLT_DATA_TRANS_AND_DB=CP	10.06.2007 08:42:10	33792
Typ	SXS_ATTR	20.08.2001 12:23:27	4096
Typ	V_EXT_ACT	09.11.2000 14:27:05	2048
Typ	SXC_EXIT	09.11.2000 14:23:43	2048
Prg	CL_EX_EHS_DG_001==============CP	06.04.2008 13:42:43	211968
Prg	IF_EX_EHS_DG_001==============IP	06.04.2008 13:42:43	80896
Prg	CL_EX_LE_SHP_DELIVERY_PROC====CP	10.06.2007 09:43:25	91136
Prg	IF_EX_LE_SHP_DELIVERY_PROC====IP	10.06.2007 09:43:25	21504
Prg	SAPLSEXE	10.06.2007 08:42:13	72704
Typ	TADIR	10.06.2007 08:12:32	4096
Typ	SXS_MLCO	04.12.2000 14:59:55	2048
Prg	CL_EX_BADI_SD_COM_COUNTRY=====CP	06.04.2008 13:42:43	39936
Prg	IF_EX_BADI_SD_COM_COUNTRY=====IP	06.04.2008 13:42:43	13312
Prg	SAPLV01Z	01.02.2008 07:41:21	186368
Prg	SAPFV50P	06.04.2008 13:42:43	1027072
Prg	SAPFV50V	06.04.2008 13:42:43	504832
Prg	SAPFV50C	28.05.2008 20:24:44	648192
Typ	TVSHP	04.01.2004 04:12:00	3072
Typ	T180	20.02.1998 09:17:43	3072
Prg	SAPLV00F	10.06.2007 08:12:50	67584
Typ	T185V	15.11.2000 17:56:17	6144
Prg	SAPLSUSE	10.06.2007 08:33:11	45056
Typ	TCDCOUPLES	29.03.2001 16:08:37	2048
Typ	TVPAD	12.03.1999 15:16:46	2048
Prg	SAPLSBDC	11.06.2006 05:40:46	38912
Prg	SAPLSYSDEF	10.06.2007 08:12:50	16384
Typ	TSYSDEF	13.08.1997 14:03:17	2048
Prg	SYSTEMSWITCHOV2	14.02.2002 14:15:49	12288
Prg	SAPLSTXD	10.06.2007 08:40:05	346112
Typ	STXDRID	26.02.1999 14:48:42	2048
Typ	STXDRLANG	26.02.1999 14:48:42	2048
Typ	STXDRNAME	26.02.1999 14:48:42	2048
Typ	STXDROBJ	26.02.1999 14:48:42	2048
Prg	CL_ABAP_CHAR_UTILITIES========CP	11.12.2005 15:17:11	11264
Typ	TCATALOG	25.05.1998 12:19:20	3072
Prg	SAPCNVE	14.02.2002 14:22:47	6144
Prg	SAPLLANG	10.06.2007 08:12:19	8192
Prg	SAPLV52P	06.04.2008 13:42:44	70656
Typ	VBEXAN	15.11.1995 02:50:24	2048
Typ	VBEXAN	15.11.1995 02:50:24	2048
Typ	VBEXAN	15.11.1995 02:50:24	2048
Typ	VBEXAN	15.11.1995 02:50:24	2048
Typ	VBEXAN	15.11.1995 02:50:24	2048
Prg	SAPLVFSP	06.04.2008 13:42:44	202752
Typ	VBPAVB	22.02.2001 10:03:22	8192
Typ	SADRVB	03.01.2004 20:12:44	7168
Prg	SAPLSHD0	10.06.2007 08:25:47	198656
Typ	SHDFVGUICU	15.11.2000 17:53:49	2048
Typ	SHDTVSVCIU	14.12.1998 23:15:38	2048
Typ	SHDSTU	14.12.1998 23:15:34	2048
Typ	SHDSTCIU	14.12.1998 23:15:34	2048
Typ	LIPSVB	10.06.2007 09:41:02	45056
Prg	%_CSXRT	11.12.2005 15:15:45	11264
Prg	CL_EXIT_MASTER================CP	10.06.2007 08:22:50	15360
Typ	V_EXT_IMP	09.11.2000 14:27:05	2048
Typ	V_EXT_IMP	09.11.2000 14:27:05	2048
Typ	SXC_IMPSWH	09.11.2000 14:23:44	2048
Prg	/SAPTRX/CL_IM_LE_SHIPPING=====CP	06.04.2008 13:42:43	59392
Prg	CL_IM_WB2_PROCESS_DL==========CP	10.06.2007 09:43:25	37888
Prg	ZCL_IM_DELIVERY_CHECK=========CP	06.04.2008 13:42:44	50176
Prg	ZCL_IM_VL_CHECK_ST_LOC========CP	10.06.2007 09:43:27	34816
Prg	SAPLASTAT_TRIG	14.02.2002 14:22:47	11264
Typ	ASTAT_TYP2	10.11.1998 05:35:18	2048
Typ	ASTAT_TYP1	30.11.1998 15:54:16	2048
Prg	SAPLWB2_EA_GLTRADE_ACTIVE	25.01.2002 13:24:11	6144
Typ	TBE11	03.09.1997 03:01:06	2048
Prg	SAPFV50U	06.04.2008 13:42:43	488448
Typ	PROGSTRUC	07.05.1997 13:01:48	2048
Typ	SHP_CUA_EXCLUDE	20.11.2001 15:34:13	1024
Prg	SAPLSTUP	11.06.2006 05:52:35	65536
Prg	SAPLCNDP	10.06.2007 08:28:09	169984
Prg	SAPFGUICNTL	09.01.2003 17:18:52	20480
Prg	SAPLOLEA	10.06.2007 08:34:43	79872
Prg	SAPLSGUI	10.06.2007 08:39:07	31744
Prg	SAPLSTTM	11.12.2005 15:35:28	75776
Prg	SAPLSFES	10.06.2007 08:41:18	223232
Prg	SAPLTHFB	10.06.2007 08:41:18	315392
Typ	WPINFO	26.02.1999 14:49:01	5120
Prg	SAPLURFC	11.12.2005 15:36:18	17408
Prg	SAPLSPLUGIN	14.02.2002 14:22:48	6144
Typ	SWCBCONT	15.11.2000 17:55:11	3072
Typ	OLE_VERBS	04.04.1995 16:02:20	2048
Typ	OLE_PA	04.04.1995 16:02:19	2048
Prg	SAPLSCNT	14.02.2002 14:22:47	24576
Prg	SAPSHDTV	03.01.2004 22:52:26	28672
Typ	SHDSTUSR	06.02.2001 14:29:52	2048
Typ	SYST	04.12.2000 14:54:51	27648

List of internal tables

No dump information available

Directory of Application Tables

Program

Name................ Contents....1........2........3........4........5....+....

SAPMV50A

SYST |\0\0\0\0\0\0\0\0\x13\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0

LIKP |999 00000000000000

LIKPD | 0000000000 |

TVLK | 000000

TVLKT | |

LIPS | 000000 00000000000000

LIPSD | \0\0\0\0\0\0\0\x0C\0\0\0\0\0\0\x0C \0\0\0\0 000000

VBUK | 00000000

T180 |VL02N SAPMV50A

T185 |

T185F |SAPMV50A V

T185V | 0000\0\x0C\0

RV50A |

R185D | Delivery processing

V50AGL | 00 X \0\0\0\0

BDCRUN | 00000000000000

V50AGL_CUST | |

TVSHP | |

TVPAD | 00000000|

SAPLPA_PACKAGE_SERVICES

PAKDATBUF |XXINACTIVE_PACKAGES \0\0\0\000000000000000\0\0\0\0\0\0

CONTEXT_X_SP_INFO

CONTEXTB |999IBSP_INFO 000004000220080807160000 \0\0\0

TCONT |SP_INFO 20040104164901|

SAPLV00F

T185F | V

T185 |

T185V |SAPMV50A E0VL020000\0\x0C\0

SAPLSYSDEF

TSYSDEF |00 00000000|

SAPSHDTV

SHDSTU | |

SHDSTCIU | |

Directory of Application Tables (Administrative Information)

Program

Name.......................... Time.......... Length...

SAPSHDTV

SYST 00002404

LIKP 20070610085811 00000972

LIKPD 00000016

TVLK 00000161

TVLKT 00000028

LIPS 00001568

LIPSD 00000208

VBUK 20070610085847 00000098

T180 00000073

T185 00000275

T185F 00000069

T185V 00000326

RV50A 00001614

R185D 00000211

V50AGL 00000144

BDCRUN 00000169

V50AGL_CUST 00000001

TVSHP 00000013

TVPAD 00000025

SAPLPA_PACKAGE_SERVICES

PAKDATBUF 00002932

CONTEXT_X_SP_INFO

CONTEXTB 00002944

TCONT 00000034

SAPLV00F

T185F 00000069

T185 00000275

T185V 00000326

SAPLSYSDEF

TSYSDEF 00000022

SAPSHDTV

SHDSTU 00000053

SHDSTCIU 00000050

ABAP control blocks CONT

Include Line source code

Index Name F1 Co Par01 Par2. Par3. Par4. Tabl

-- -- -

>>>>> -

<SYSINI> 20 perform (SY-XFORM) in program

1 xper 02 0011

3 PERP 80

4 -

<SYSINI> 24 perform %_CTL_INIT in program

5 xper 06 32 0013

7 PERP 80

8 PERP 80

<SYSINI> 25 endmodule.

9 ENDM 00

10 -

<SYSINI> 29 perform %_CTL_OUTPUT in progra

11 xper 06 69 0014

13 PERP 80

14 PERP 80

<SYSINI> 30 endmodule.

15 ENDM 00

16 -

<SYSINI> 34 perform %_CTL_INPUT in program

17 xper 06 89 0015

19 PERP 80

20 PERP 80

<SYSINI> 35 endmodule.

21 ENDM 00

22 -

<SYSINI> 39 perform %_CTL_AT_EXIT in progr

23 xper 06 67 0016

End of runtime analysis

Re: ABAP Dump DYNPRO_SEND_IN_BACKGROUND

Former Member — Fri, 08 Aug 2008 11:42:57 GMT

Hi ,

If you goto ST22 and select your DUMP, navigate to ABAP Developer view --> Source Code Extract. This will show you exact point of code at which error occured.

Regards,

Mohaiyuddin

Re: ABAP Dump DYNPRO_SEND_IN_BACKGROUND

Former Member — Fri, 08 Aug 2008 12:01:01 GMT

Hi,

The transaction you are using is Njoy type,which are controls based rather than screen based.So you will end up with a dump, when you try to run it in background.Try to use conventional transaction or to go for suitable BAPI.

Please read the attached note: 311440 Batch-Input and Controls

This will help you in sorting out the issue.

Regards,

Keerthi

Re: ABAP Dump DYNPRO_SEND_IN_BACKGROUND

Former Member — Sat, 09 Aug 2008 04:50:01 GMT

Hi,

There is no source code extract. That is why its getting difficult for me.

Regards,

siddhartha

Re: ABAP Dump DYNPRO_SEND_IN_BACKGROUND

Former Member — Sat, 09 Aug 2008 05:03:29 GMT

Hi Siddarth,

It seems something has changed the characteristics of you interface program

and it is trying to access a dialog transaction screen in the background,

and this is not possible. Debug the program.

Mohinder

Re: ABAP Dump DYNPRO_SEND_IN_BACKGROUND

Former Member — Sat, 09 Aug 2008 05:28:58 GMT

Hi Siddhartha.

I would like to suggest my opinion, though I am not that sure about it.

[SDN Library - Standard Reference - PDF - Mastering Five remote function call (RFC) types in ABAP|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c75674694]

I would like to refer few lines from the reference above which might add some weightage (Page no - 104).

There is one additional, logical requirement for displaying dialog screens - There must be someone to whom the dialogs display. That is your program must be executed in foreground via a "regular" SAP GUI user (e.g. a dialog user). If you use a dedicated RFC user account for the target system, the RFC communication user must also be a dialog user.

If this condition is not met, the system raises the ABAP runtime error "DYNPRO_SEND_IN_BACKGROUND", when it encounters a screen on remote system.

Hope you meet your requirement.

Good Luck & Regards.

Harsh Dave