ABAP Dump when executing DTP
Dear gurus:
I just faced an annoying problem when executing DTP in t-code RSA1. It appears an ABAP dump here. The ABAP dump is briefly shown below. And I found that it seems to be an authorization problem, because when I use a new account which has SAP_ALL authorization, then it works. So it may lack of some authorizations, but it's hard to figure it out. T-code su53 cannot check it properly. Need your help and thanks a lot.
Runtime Errors MESSAGE_TYPE_X
Date and Time 2007.06.20 11:17:30
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
Error analysis
Short text of error message:
Invalid program status
Long text of error message:
Technical information about the message:
Message class....... "RSBK"
Number.............. 299
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Hai Wei,
This dump is due missing of OCX files while installing SAP GUI Front end just find out the exact files and copy and paste them in the Front end files files then ur prob will be solved.......
If in case any issues let me know.
Regards
Madhavi
Similar Messages
-
Dump when executing DTP right after infopackage in BI 7.0 SP 7
Hello.
whenever I try to execute DTP <b>right after</b> run infopackage (eg.master loading), exception error occurs like below.
<b><u>"A RAISE statement in the program "SAPLRSSTATMAN" raised the exception"</u></b>
can't find any notes related to this problem in SAP notes.
that is okay when i try this job with intervals though.(10sec or so.)
Is there any solution about this?
Thanks in advance.This sounds like you need to create a customer message. You haven't sent the dump but from the process I would guess that some data is still stuck on the database. Anyway a RAISE where you don't find a note is always worth a customer message if you can reproduce it.
Best regards
Dirk -
ABAP Dump when executing tcode CATS_APPR_LITE for multiple selection.
Dear Members,
Issue:
When executing tcode CATS_APPR_LITE for Time Approval from the remote R/3 by selecting multiple selections and click on Approve, if you get a dump saying CALL_FUNCTION_REMOTE_ERROR
Analysis:
If there is an SAP Note applied in 1368487 and at CALL FUNCTION CATS_CHECK _PTEXDIR FM getting the dump because in source system for this function module Remote Enabled Module option is not checked.
To resolve this correction note 1430042 has to be applied.
Regards
DurgaDear Members,
Issue:
When executing tcode CATS_APPR_LITE for Time Approval from the remote R/3 by selecting multiple selections and click on Approve, if you get a dump saying CALL_FUNCTION_REMOTE_ERROR
Analysis:
If there is an SAP Note applied in 1368487 and at CALL FUNCTION CATS_CHECK _PTEXDIR FM getting the dump because in source system for this function module Remote Enabled Module option is not checked.
To resolve this correction note 1430042 has to be applied.
Regards
Durga -
Dear Gurus,
I am loading 2lis_02_hdr and 2lis_02_itm data in to customized ODS.
it loaded sucessfully up to PSA level, when i am loading through DTP it shows the abap runtime error as "CREATE_DATA_UNKNOWN_TYPE"
let me know the solution for the above..urgentHi Ravindra,
As you said i have gone through transformations once again, I mapped the correct data type only.
Including the above error mentioned i am also facing runtime error message as MESSAGE_TYPE_X -
ABAP DUMP WHEN Executing GANTT CHART IN CN41N TCODE
Hi,
we are getting the following error while trying to display gantt chart in CN41N Tcode.
A calculation field is defined too small.
The current ABAP program "FCNGR000" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
caught in
procedure "GET_WORKAREA" "(FORM)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
A value generated during processing is too large for the
field "ALL_OBJ-VDAUER" of the program "FCNGR000".
any suggestion.please.
nazi.Should be rather obvious? The domain for VDAUER is Dec 10,1. The dump would suggest that you've getting a value for VDAUER that's more than 10 digits long?
-
SHORT DUMP WHILE EXECUTING DTP.
Hi Gurus,
I have got a short dump while executing DTP the Error is as Follows.
Runtime Error: MESSAGE_TYPE_X.
Reasons for Error: 1.The installation of the SAP GUI on the present server is faulty or obselete
2.There is a error in the application program
And i have sent the sreen shot of the Short Dump to BASIS TEAM and they have replied me that they have to install some patches and it will take some time.
But i have no much time and i have to someway or the other execute the DTP and load the data.
Is there any shortcuts for this i mean to say without the involvement of Basis team that i can do in th BI System
Regards
Amar.Hi Amar,
If the problem is with with System itself, how can we all have a short cut in that case. You may give it another trial, but you have to wait for the patches to be applied. Ask your basis team to get it done ASAP.
Thanks..
Shambhu -
ABAP dump while executing transaction *PC00_M99_CIPE*
Hi,
Getting ABAP dump while executing transaction PC00_M99_CIPE ,hence cannot do payroll posting .
Information on where terminated
Termination occurred in the ABAP program "CL_HRFPM_CD_CLOSING_HANDLER===CP" -
in "GET_FM_POS_CHECK_DATA".
The main program was "RPCIPE00 ".
In the source code you have the termination point in line 13
of the (Include) program "CL_HRFPM_CD_CLOSING_HANDLER===CM00E".
We have recently upgraded our patch level.
SAP_OCS(SPAM/SAINT) SAPKD70026 SAPKD70033
SAP_ABA SAPKA70012 SAPKA70018
SAP_BASIS SAPKB70012 SAPKB70018
PI_BASIS SAPKIPYJ7B SAPKIPYJ7I
SAP_BW SAPKW70012 SAPKW70020
SAP_AP SAPKNA7008 SAPKNA7015
SAP_APPL SAPKH60009 SAPKH60015
SAP_HR SAPKE60028 SAPKE60039
EA-HR SAPKGPHD07 SAPKGPHD26
Kindly guide me.
Regards,
Rachelthanks for the quick response.
By applying note 1137655,problem got resoved.
FORM CHECK_CMTNT_UPDATE_CLOSED
Delta001
Context Block
FORM check_cmtnt_update_closed
USING
u_key_date TYPE begda
CHANGING
c_flg_cmtnt_closed.
Delete Block
DATA ls_encumb_iv TYPE t77hrfpm_encumb.
DATA l_gsval TYPE t77s0-gsval.
DATA ls_fm_pos_key TYPE hrfpm_fm_doc_pos-key_pos.
DATA lx TYPE REF TO cx_hrfpm.
STATICS so_closing_handler TYPE REF TO cl_hrfpm_cd_closing_handler.
CLEAR c_flg_cmtnt_closed .
*--- old switch from note??? active?
*--- if so: use the old logic
cl_hr_t77s0=>read_gsval(
EXPORTING
grpid = 'HRFPM'
semid = 'CHKAC'
IMPORTING
returnvalue = l_gsval ).
TRY.
IF NOT l_gsval IS INITIAL .
TRY.
c_flg_cmtnt_closed = 'X'.
Insert Block
DATA: ls_encumb_iv TYPE t77hrfpm_encumb.
STATICS:
s_gsval TYPE t77s0-gsval,
s_gsval_read TYPE flag.
IF s_gsval_read IS INITIAL .
SELECT SINGLE gsval
FROM t77s0
INTO s_gsval
WHERE grpid = 'HRFPM'
AND semid = 'CHKAC' .
s_gsval_read = 'X'.
ENDIF.
CLEAR c_flg_cmtnt_closed .
TRY.
c_flg_cmtnt_closed = 'X'.
Delta002
Context Block
CATCH
cx_hrfpm_db_operation
cx_hrfpm_ad_customizing .
Delete Block
ENDTRY.
ELSE.
*--- using closed period functionality of PBC
IF so_closing_handler IS INITIAL .
CREATE OBJECT so_closing_handler.
ENDIF.
IF so_closing_handler->consumption_in_closed_period(
i_key_date = u_key_date
is_fm_pos_key = ls_fm_pos_key )
IS INITIAL.
c_flg_cmtnt_closed = 'X'.
ENDIF.
ENDIF.
CATCH cx_hrfpm INTO lx.
lx->raise_sy_message( ).
ENDTRY.
ENDFORM. "check_cmtnt_update_closed
Insert Block
ENDTRY.
ENDFORM. "check_cmtnt_update_closed -
Short dump when executing the query
Hello Friends,
I have a query from MM area which I have insalled from Business Content , and when I try to go to the edit mode or try to excute the query I get a short dump which says "Missing elements ..", I get the same dump when executing from query designer or RSRT . At this time I'm not able to do a "check" on the query also n query designer since it doesnot allow me to go to the edit mode also . Any inputs greatly appreciated .
thanks ,Hi,
While activating it from the Business Content, have you activated all the underlying objects also. Pls check that. It might help. -
Dump while Executing DTP - PSA To ODS
While executing DTP, I am getting the following ABAP Dump: "MESSAGE_TYPE_X".
"MESSAGE_TYPE_X" " "
"SAPLRSSTATMAN" or "LRSSTATMA
"RSSTATMAN_GET_PARTTAB_PSA"
I was facing some selection issue in the Info Package (generic Data source), then I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly.
Now I am facing the issue while loading data from PSA to ODS through DTP. I already activated all the objects again (Data Source, ODS, & DTP).
Please guide me.
Thanks in Advance u2026u2026
KiruthikaI tried with Error DTP, I am getting same Dump. When I click Execute button with debug option directly it's going to Dump.
I am getting the following Error message
Runtime Errors MESSAGE_TYPE_X
keywords:
"MESSAGE_TYPE_X" " "
"SAPLRSSTATMAN" or "LRSSTATMA
"RSSTATMAN_GET_PARTTAB_PSA"
Information on where terminated
Termination occurred in the ABAP program "SAPLRSSTATMAN" - in
"RSSTATMAN_GET_PARTTAB_PSA".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 1165
of the (Include) program "LRSSTATMANU10".
I have deleted all the entries in the table u201CRSSELDONEu201D against that Data source. After that I was able to load the data from R/3 server to PSA smoothly. As per my understanding table u201CRSSELDONEu201D is used for info package selection.
If there any problem related to this, please guide me.
Regards,
Kiruthika
Edited by: kiruthika marappan on Sep 4, 2009 2:16 PM -
Getting Short dump When Executing MIGO: SYNTAX_ERROR
Please Help,
I am getting this dump, when i hit MIGO transaction
Runtime Errors SYNTAX_ERROR
Date and Time 10.12.2008 08:28:03
Short text
Syntax error in program "MB_MIGO_BADI==================CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"MB_MIGO_BADI==================CP " in include
"MB_MIGO_BADI==================CM000 " in
line 0:
"The specified type cannot be converted into the target variables."
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 "CL_EX_MB_MIGO_BADI============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "MB_MIGO_BADI==================CP
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program
MB_MIGO_BADI==================CP :
"The specified type cannot be converted into the target variables."
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "DMATE"
Network address...... "140.1.1.141"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "dmate"
Database type..... "ADABAS D"
Database name..... "AD0"
Database user ID.. "SAPAD0"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jun 23 2008 00:09:46"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQLDBC 7.6.0.018 CL 119055 "
Patch level. 166
Patch text.. " "
Database............. "MaxDB 7.6, MaxDB 7.7"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 8379680
Heap.... 0
Page.... 40960
MM Used. 1627776
MM Free. 2559440
User and Transaction
Client.............. 040
User................ "LAKSHMI"
Language key........ "E"
Transaction......... "MIGO "
Transactions ID..... "EE72C6DDC96BF1F99FA4001143E563CA"
Program............. "CL_EX_MB_MIGO_BADI============CP"
Screen.............. "SAPLMIGO 0001"
Screen line......... 2
Information on where terminated
Termination occurred in the ABAP program "CL_EX_MB_MIGO_BADI============CP" -
in "IF_EX_MB_MIGO_BADI~INIT".
The main program was "SAPLMIGO ".
In the source code you have the termination point in line 1
of the (Include) program "CL_EX_MB_MIGO_BADI============CM001".
Source Code Extract
Line SourceCde
>>>>> method IF_EX_MB_MIGO_BADI~INIT.
2 CLASS CL_EXIT_MASTER DEFINITION LOAD.
3
4 DATA l_badi TYPE REF TO MB_MIGO_BADI.
5
6
7
8
9
10 TRY.
11
12 GET BADI l_badi
13 CONTEXT me.
14
15 CALL BADI l_badi->INIT
16
17 CHANGING
18 CT_INIT = CT_INIT.
19
20
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 1
SY-DBCNT 1
SY-FDPOS 1
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE
SY-MSGTY S
SY-MSGID VBDOCUBATCH
SY-MSGNO 001
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20081210
SY-UZEIT 082802
SY-XPROG
SY-XFORM
Active Calls/Events
No. Ty. Program Include Line
Name
4 METHOD CL_EX_MB_MIGO_BADI============CP CL_EX_MB_MIGO_BADI============CM001 1
CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
3 METHOD SAPLMIGO LMIGOGL2 54
LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
2 FORM SAPLMIGO LMIGOIN1 11
INITIALIZATION
1 MODULE (PBO) SAPLMIGO LMIGOPBO 11
PBO_INITILIZATION
Chosen variables
Name
Val.
No. 4 Ty. METHOD
Name CL_EX_MB_MIGO_BADI=>IF_EX_MB_MIGO_BADI~INIT
CT_INIT
Table[initial]
%_DUMMY$$
2222
0000
0000
0000
SYST-REPID
CL_EX_MB_MIGO_BADI============CP
4454554454444544443333333333334522222222
3CF58FD2FD97FF2149DDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-SUBRC
0
0000
0000
No. 3 Ty. METHOD
Name LCL_MIGO_GLOBALS=>CLASS_CONSTRUCTOR
SY-REPID
SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LCL_MIGO_GLOBALS=>CNTL_ERROR
2
0
0
0
ABAP_FALSE
2
0
0
0
SYST-REPID
SAPLMIGO
5454444422222222222222222222222222222222
310CD97F00000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
GOSEARCH_PO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
TEXT-220
Dest
46772222
45340000
00000000
00000000
%_SPACE
2
0
0
0
%_TAG*TS_GOITEM
<initial>
<initial>
<initial>
X
X
5
8
0
0
LCL_MIGO_GLOBALS=>IF_BADI
F0000000
70008000
%_FL2*TV_GOFREIGHT
<initial>
<initial>
<initial>
%_PRINT
000 0###
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
LCL_MIGO_GLOBALS=>T_BADI
Table[initial]
/SPE/CL_INB_ACTION_INFO=>C_DIALOG_MIGO
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
OREF_TITLEBAR
F0000000
F0000000
L_BADIS_1
0
0000
0000
SY-MSGID
VBDOCUBATCH
54444544544222222222
624F3521438000000000
00000000000000000000
00000000000000000000
OREF_TIP
F0000000
F0000000
TV_GOSERIAL-CX
<initial>
<initial>
<initial>
SPACE
2
0
0
0
SY-MSGNO
001
333
001
000
000
No. 2 Ty. FORM
Name INITIALIZATION
OREF_ARCH
F0000000
F0000000
LCL_MIGO_GLOBALS=>KERNEL
F0000000
D0002000
%_CX_TABLEVIEW_VERSION
0
3
0
0
0
GODEFAULT-DEF_XBOM
2
0
0
0
LCL_MIGO_GLOBALS=>KERNEL->C_REFDOCTYPE_MATDOC
MAT
445
D14
000
000
No. 1 Ty. MODULE (PBO)
Name PBO_INITILIZATION
GOITEM-UMWRK
2222
0000
0000
0000
GOITEM-UMNAME1
222222222222222222222222222222
000000000000000000000000000000
000000000000000000000000000000
000000000000000000000000000000
Internal notes
The termination was triggered in function "ab_genprog"
of the SAP kernel, in line 1551 of the module
"//bas/700_REL/src/krn/runt/abgen.c#10".
The internal operation just processed is "CPOP".
Internal mode was started at 20081210082802.
Program name.........: "MB_MIGO_BADI==================CP ".
Error message........: "The specified type cannot be converted into the target
variables.".
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=5776)
When : 12/10/2008 8:28:3.84
Threads : 2
Computer Name : DMATE
User Name : SAPServiceAD0
Number of Processors: 4
Processor Type: EM64T Family 15 Model 4 Stepping 1
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 14f0
FramePtr ReturnAd Param#1 Function Name
0000000007eb8800 0000000077d7047f 00000000411b4070 ntdll!NtWaitForSingleObject
0000000007eb88a0 000000000173b1d1 000000000000042c kernel32!WaitForSingleObjectEx
0000000007eb8af0 00000000006179c5 0000000000000001 disp+work!NTDebugProcess [ntstcdbg.c (501)]
0000000007eb8b20 0000000000b05d9c 0000000000000001 disp+work!CTrcStack [dptstack.c (182)]
0000000007eb8b70 0000000000b0afc0 0000000000000001 disp+work!rabax_CStackSave [abrabax.c (7093)]
0000000007eb9550 0000000000a51c94 0000000001d12320 disp+work!ab_rabax [abrabax.c (1231)]
0000000007ebc220 00000000007f753a 0000000000000001 disp+work!ab_genprog [abgen.c (1555)]
0000000007ebc2f0 00000000007f7dc8 00000000ffffffff disp+work!newload [abload1.c (336)]
0000000007ebc350 00000000007f7e8e 0000000000000056 disp+work!ab_LoadProgOrTrfo [abload1.c (160)]
0000000007ebc380 00000000007bc84d 000007fe725a5f70 disp+work!ab_LoadProg [abload1.c (78)]
0000000007ebc450 00000000007be91a 00002a441022f402 disp+work!LoadGlobalClass [abobject.c (943)]
0000000007ebc4a0 00000000007c1bdd 0000000000000000 disp+work!ab_FillCfix [abobject.c (1603)]
0000000007ebc580 000000000083ae52 0000000000000000 disp+work!ab_jaboo [abobject.c (2248)]
0000000007ebc700 0000000000a1ccb7 000000000000000d disp+work!ab_extri [abextri.c (554)]
0000000007ebc750 0000000000ad50ac 000000000000000d disp+work!ab_xevent [abrunt1.c (281)]
0000000007ebc7e0 0000000000679328 000000000000000d disp+work!ab_dstep [abdynpro.c (492)]
0000000007ebc960 000000000067d02d 000007fe725d6f20 disp+work!dynpmcal [dymainstp.c (2396)]
0000000007ebc9f0 000000000067ca2a 0000000000000000 disp+work!dynppbo0 [dymainstp.c (543)]
0000000007ebcaa0 00000000006395c5 0000000000000000 disp+work!dynprctl [dymainstp.c (360)]
0000000007ebfc30 00000000004dbc4c 000000000000000c disp+work!dynpen00 [dymain.c (1646)]
0000000007ebfeb0 000000000042f096 0000000007f62ff0 disp+work!TskhLoop [thxxhead.c (4538)]
0000000007ebfee0 000000000040108d ffffffff00000003 disp+work!DpMain [dpxxdisp.c (1136)]
0000000007ebff10 00000000019e84b1 0000000000000000 disp+work!nlsui_main [thxxanf.c (84)]
0000000007ebff70 0000000077d5966c 0000000000000000 disp+work!wmainCRTStartup [crtexe.c (498)]
0000000007ebffa0 0000000000000000 00000000019e8340 kernel32!BaseProcessStart
State Dump for Thread Id b94
FramePtr ReturnAd Param#1 Function Name
000000000c9dfe40 0000000077d5f651 0000000000000000 ntdll!NtFsControlFile
000000000c9dfeb0 00000000018ce23f fffffffffffffffe kernel32!ConnectNamedPipe
000000000c9dff40 000007ff7fc411c4 0000000000000000 disp+work!SigIMsgFunc [signt.c (679)]
000000000c9dff70 0000000077d6b69a 0000000077d6b660 msvcrt!endthreadex
000000000c9dffa0 0000000000000000 0000000000000000 kernel32!BaseThreadStart
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg SAPLMIGO 0 04.05.2008 12:54:34 1561600 E
1 Prg SAPMSSYD 0 25.02.2008 17:02:32 21504 E
2 Prg SAPFSYSCALLS 0 09.09.2004 14:18:32 7168 E
3 Prg CL_MMIM_USERDEFAULTS==========CP 3 06.05.2002 10:42:38 21504 E
4 Typ ESDUS 0 01.03.1999 13:36:04 2048
5 Typ GOHEAD 0 07.02.2006 10:07:36 11264
6 Typ MKPF 0 25.08.2005 22:02:19 7168
7 Typ KBEFU 0 16.03.2008 17:46:49 6144
8 Typ LFA1 0 16.03.2008 17:47:20 22528
9 Typ MIGO_CUST_ACTION 0 30.11.1999 10:19:14 3072
10 Typ MIGO_CUST_REFDOC 0 30.11.1999 10:19:14 2048
11 Typ X031L 0 05.07.2005 13:10:15 6144
12 Prg SAPLSDIFRUNTIME 12 19.11.2006 16:35:34 96256 E
13 Typ DFIES 0 28.12.2004 17:06:45 10240
14 Prg SAPLSDNT 14 09.03.2008 19:02:04 219136 E
15 Prg SAPLSUGS 15 31.03.2006 11:23:11 47104 E
16 Prg SAPLV01D 16 24.03.2008 17:03:30 40960 E
17 Typ IWRKZ 0 04.04.1995 15:56:46 2048
18 Typ TCUCH 0 07.01.2002 15:50:54 3072
19 Typ TCUBN 0 07.01.2002 15:50:53 2048
20 Typ TCUWS 0 13.08.1997 13:57:58 2048
21 Typ TCUDRV 0 07.01.2002 15:50:54 2048
22 Prg SAPLVBDOCUBATCH_BF 22 16.01.2004 14:28:56 10240 E
23 Typ TCUDB 0 14.01.2004 10:05:59 2048
24 Prg CL_GUI_CFW====================CP 24 28.02.2005 21:03:09 168960 E
25 Prg CL_GUI_PROPS_CONSUMER=========CP 25 18.03.2008 13:25:33 29696 E
26 Prg %_CCNTL 25 18.02.2005 14:15:08 15360 E
27 Prg SAPLTHFB 27 18.03.2008 13:24:52 394240 E
28 Typ EUDB 0 06.11.2003 20:28:08 8192
29 Typ TCURM 0 01.03.2005 10:56:26 5120
30 Prg CL_EXITHANDLER================CP 30 18.03.2008 13:11:35 30720 E
31 Prg SAPLSEXV 31 18.03.2008 13:12:58 117760 E
32 Typ SXS_ATTR 0 07.02.2006 10:09:24 5120
33 Typ BADIISIMPLED 0 19.05.2005 19:10:34 3072
34 Prg CL_ENH_BADI_TOOL_UTILITIES====CP 34 17.03.2008 11:03:36 13312 E
35 Typ BADI_MAIN 0 08.12.2004 18:01:11 2048
36 Typ BADI_IMPL 0 09.12.2004 19:05:43 3072
37 Typ TADIR 0 07.02.2006 10:08:38 5120
38 Prg CL_SWITCH=====================CP 38 17.03.2008 11:13:47 19456 E
39 Typ SFW_PACKAGE 0 07.03.2008 12:18:16 2048
40 Prg CL_ABAP_SWITCH================CP 40 14.10.2006 15:40:30 33792 E
41 Prg SAPLPA_PACKAGE_SERVICES 41 18.03.2008 13:12:54 152576 E
42 Typ TDEVC 0 08.12.2004 18:02:41 6144
43 Prg CL_EX_MB_MIGO_BADI============CP 43 05.12.2008 17:09:58 30720 E
44 Prg IF_EX_MB_MIGO_BADI============IP 30 19.05.2005 19:30:39 14336 E
45 Typ SYST 0 09.09.2004 14:18:12 31744
46 Typ GOSEARCH_PO 0 20.07.2001 19:17:34 4096
47 Prg /SPE/CL_INB_ACTION_INFO=======CP 47 24.03.2008 20:30:06 20480 E
48 Prg /SPE/IF_CONST=================IP 47 14.10.2006 18:49:02 7168 E
49 Typ GODEFAULT 0 14.01.2004 10:04:46 5120
50 Typ GOITEM 0 07.02.2006 10:07:36 65536
Directory of Application Tables
Name Date Time Lngth
Val.
Program SAPLMIGO
SYST . . : : 00004612
\0\0\0\0\x0001\0\x0370\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0
GOITEM . . : : 00005524
00000000000000000000
GOSEARCH_PO . . : : 00000492
GODEFAULT . . : : 00000220
Program SAPLV01D
TCUCH . . : : 00000122
0401100020061029095148ANOOPJ 00000000000000
TCUWS . . : : 00000060
040020061227101454CONSULTANT
TCUBN . . : : 00000060
040020061227101454CONSULTANT
TCUDRV . . : : 00000064
00000000000000
Program CL_GUI_PROPS_CONSUMER=========CP
EUDB . . : : 00004068
%CAA72C6DDAD55F1179FA4001143E563CA \0\0\0
ABAP Control Blocks (CONT)
Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 Source Code Line
94 BRAX 01 FFEB CL_EX_MB_MIGO_BADI============CM001 15
95 CLEA 00 0020 CL_EX_MB_MIGO_BADI============CM001 15
96 EXCP 08 0000 CL_EX_MB_MIGO_BADI============CM001 22
97 BRAX 00 0005 CL_EX_MB_MIGO_BADI============CM001 22
98 EXCP 00 0007 CL_EX_MB_MIGO_BADI============CM001 22
99 BRAX 00 0003 CL_EX_MB_MIGO_BADI============CM001 22
100 EXCP 07 0000 CL_EX_MB_MIGO_BADI============CM001 22
101 BRAX 00 0001 CL_EX_MB_MIGO_BADI============CM001 23
102 EXCP 0B 0000 CL_EX_MB_MIGO_BADI============CM001 23
103 METH 01 0000 0000 0000 0000 0000 0000 0000 CL_EX_MB_MIGO_BADI============CM001 24
107 -
00 0000 CL_EX_MB_MIGO_BADI============CM001 24
108 ABOO 02 0000 0005 0000 CL_EX_MB_MIGO_BADI============CM001 1
>>>>> CPOP 00 0000 CL_EX_MB_MIGO_BADI============CM001 1
111 -
00 0000 CL_EX_MB_MIGO_BADI============CM001 1
112 METH 04 0000 0005 0002 0000 0003 0000 0000 CL_EX_MB_MIGO_BADI============CM002 1
116 PAR2 04 0000 C000 0000 CL_EX_MB_MIGO_BADI============CM002 1
118 PAR2 04 0000 C001 0000 CL_EX_MB_MIGO_BADI============CM002 1
120 PAR2 14 0000 C002 0000 CL_EX_MB_MIGO_BADI============CM002 1
122 PAR2 14 0000 C003 0000 CL_EX_MB_MIGO_BADI============CM002 1
124 PAR2 14 0000 C004 0000 CL_EX_MB_MIGO_BADI============CM002 1Hai,
Seems to be problem with the Program.
Please check the point 'What Happened' in the dump for more details.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"MB_MIGO_BADI==================CP " in include
"MB_MIGO_BADI==================CM000 " in
line 0:
"The specified type cannot be converted into the target variables."
Error in the ABAP Application Program
The current ABAP program "CL_EX_MB_MIGO_BADI============CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "MB_MIGO_BADI==================CP
You can also perform the syntax check from the ABAP Editor.
Take help from a ABAP consultant and try to check the syntax of the Program.
If you have access even you can check the syntax of the specified program from SE38.
Goto SE38 and put the program name and select 'Source code' and press F8, IN THE SOURCE CODE PAGE, press control+F2 and check whether there is any problem with the syntax or not.
If you find any take help from ABAP consultants.
Hope this helps.
Regards,
Yoganand.V -
Hi All,
In process chain, While executing DTP( from PSA to ZINFOOBJECT-Master data), I am getting the following ABAP Dump:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
The internal table "???" could not be further extended. To enable
error handling, the table had to be delete before this log was written.
As a result, the table is displayed further down or, if you branch to
the ABAP Debugger, with 0 rows.
At the time of the termination, the following data was determined for
the relevant internal table:
Memory location: "Session memory"
Row width: 5356
Number of rows: 0
Allocated rows: 138348
Newly requested rows: 2 (in 69173 blocks)
How to correct the error
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 416432
Extended memory (EM)........... 2002720576
Assigned memory (HEAP)......... 1999932640
Short area..................... " "
Paging area.................... 24576
Maximum address space.......... 4294967295
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"SAPLRSSTATMAN" or "LRSSTATMANU12"
"RSSTATMAN_UPDATE_DATASTATE_EXT"
Could any one suggest solution
Thanks and Regards,
Umakanth JalduHi Ramanm
Please suggest how to do repair custom info object in RSRV and the info object is loading from two different dtps and both dtps are failing because of same error.The process of DTP is showing but not moving to next process type.
Dump:
Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED
Date and Time 31.03.2015 22:19:53
|Short text |
| No more storage space available for extending an internal table. |
|What happened? |
| You attempted to extend an internal table, but the required space was |
| not available. |
|What can you do? |
| Note which actions and input led to the error. |
| |
| For further help in handling the problem, contact your SAP administrator |
| . |
| |
| You can use the ABAP dump analysis transaction ST22 to view and manage |
| termination messages, in particular for long term reference. |
| |
| Try to find out (e.g. by targetted data selection) whether the |
| transaction will run with less main memory. |
| |
| If there is a temporary bottleneck, execute the transaction again. |
| - |
| |
| If the error persists, ask your system administrator to check the |
| following profile parameters: |
| |
| o ztta/roll_area (1.000.000 - 15.000.000) |
| Classic roll area per user and internal mode |
| usual amount of roll area per user and internal mode |
| o ztta/roll_extension (10.000.000 - 500.000.000) |
| Amount of memory per user in extended memory (EM) |
| o abap/heap_area_total (100.000.000 - 1.500.000.000) |
| Amount of memory (malloc) for all users of an application |
| server. If several background processes are running on |
| one server, temporary bottlenecks may occur. |
| Of course, the amount of memory (in bytes) must also be |
| available on the machine (main memory or file system swap). |
| Caution: |
| The operating system must be set up so that there is also |
| enough memory for each process. Usually, the maximum address |
| space is too small. |
| Ask your hardware manufacturer or your competence center |
| about this. |
| In this case, consult your hardware vendor |
| abap/heap_area_dia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each dialog process. |
| Parameters for background processes: |
| abap/heap_area_nondia: (10.000.000 - 1.000.000.000) |
| Restriction of memory allocated to the heap with malloc |
| for each background process. |
| Other memory-relevant parameters are: |
| em/initial_size_MB: (35-1200) |
| Extended memory area from which all users of an |
| application server can satisfy their memory requirement. |
|Error analysis |
| The internal table "???" could not be further extended. To enable |
| error handling, the table had to be delete before this log was written. |
| As a result, the table is displayed further down or, if you branch to |
| the ABAP Debugger, with 0 rows. |
| |
| At the time of the termination, the following data was determined for |
| the relevant internal table: |
| |
| Memory location: "Session memory" |
| Row width: 5356 |
| Number of rows: 0 |
| Allocated rows: 138348 |
| Newly requested rows: 2 (in 69173 blocks) |
|How to correct the error |
| The amount of storage space (in bytes) filled at termination time was: |
| |
| Roll area...................... 416432 |
| Extended memory (EM)........... 2002720576 |
| Assigned memory (HEAP)......... 1999932640 |
| Short area..................... " " |
| Paging area.................... 24576 |
| Maximum address space.......... 4294967295 |
| |
| If the error occures in a non-modified SAP program, you may be able to |
| find an interim solution in an SAP Note. |
| If you have access to SAP Notes, carry out a search with the following |
| keywords: |
| |
| "TSV_TNEW_PAGE_ALLOC_FAILED" " " |
| "SAPLRSSTATMAN" or "LRSSTATMANU12" |
| "RSSTATMAN_UPDATE_DATASTATE_EXT" |
| |
| If you cannot solve the problem yourself and want to send an error |
| notification to SAP, include the following information: |
| |
| 1. The description of the current problem (short dump) |
| |
| To save the description, choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 2. Corresponding system log |
| |
| Display the system log by calling transaction SM21. |
| Restrict the time interval to 10 minutes before and five minutes |
| after the short dump. Then choose "System->List->Save->Local File |
| (Unconverted)". |
| |
| 3. If the problem occurs in a problem of your own or a modified SAP |
| program: The source code of the program |
| In the editor, choose "Utilities->More |
| Utilities->Upload/Download->Download". |
| |
| 4. Details about the conditions under which the error occurred or which |
| actions and input led to the error. |
| |
|System environment |
| SAP-Release 701 |
| |
| Application server... "sapXXXa1" |
| Network address...... "10.10.29.72" |
| Operating system..... "AIX" |
| Release.............. "7.1" |
| Hardware type........ "00CB77444C00" |
| Character length.... 16 Bits |
| Pointer length....... 64 Bits |
| Work process number.. 4 |
| Shortdump setting.... "full" |
| |
| Database server... "sXXX341.sac.XXX" |
| Database type..... "ORACLE" |
| Database name..... "XXX" |
| Database user ID.. "SAPSR3" |
| |
| Terminal.......... "GSSM0510" |
| |
| Char.set.... "C" |
| |
| SAP kernel....... 720 |
| created (date)... "Feb 10 2014 21:43:58" |
| create on........ "AIX 2 5 00092901D600" |
| Database version. "OCI_102, 11.2.0.2.0, V1, default" |
| |
| Patch level. 525 |
| Patch text.. " " |
| |
| Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*" |
| SAP database version. 720 |
| Operating system..... "AIX 2 5, AIX 3 5, AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 416432 |
| EM...... 2002720576 |
| Heap.... 1999932640 |
| Page.... 24576 |
| MM Used. 3938002576 |
| MM Free. 59192960 |
|User and Transaction |
| Client.............. 100 |
| User................ "XXXX" |
| Language Key........ "E" |
| Transaction......... " " |
| Transactions ID..... "551B198729F80700E10080000A0A1D12" |
| |
| Program............. "SAPLRSSTATMAN" |
| Screen.............. "SAPLRSBM_REQUEST_GUI 0300" |
| Screen Line......... 5 |
| |
| Information on caller of Remote Function Call (RFC): |
| System.............. "XXX" |
| Database Release.... 701 |
| Kernel Release...... 720 |
| Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) |
| Call Type........... "synchronous and non-transactional (emode 0, imode 0)" |
| Inbound TID.........." " |
| Inbound Queue Name..." " |
| Outbound TID........." " |
| Outbound Queue Name.." " |
| |
| Client.............. 100 |
| User................ "XXXX" |
| Transaction......... "RSA1" |
| Call Program........."SAPLRSM1" |
| Function Module..... "RSS2_CALL_FCODE_EMPTY_GLOBALS" |
| Call Destination.... "NONE" |
| Source Server....... "sapXXXa1_XXX_12" |
| Source IP Address... "10.10.29.72" |
| |
| Additional information on RFC logon: |
| Trusted Relationship " " |
| Logon Return Code... 0 |
| Trusted Return Code. 0 |
| |
| Note: For releases < 4.0, information on the RFC caller are often |
| only partially available. |
|Information on where terminated |
| Termination occurred in the ABAP program "SAPLRSSTATMAN" - in |
| "RSSTATMAN_UPDATE_DATASTATE_EXT". |
| The main program was "SAPMSSY1 ". |
| |
| In the source code you have the termination point in line 306 |
| of the (Include) program "LRSSTATMANU12". |
|Source Code Extract |
|Line |SourceCde |
| 276| l_s_ext_db-records_techok <> l_s_ext-records_techok. |
| 277| l_s_ext-ts_tech_changed = l_timestamp. |
| 278| l_s_ext-ts_data_changed = l_timestamp. |
| 279| l_changed = 'X'. |
| 280| else. |
| 281| l_s_ext-ts_tech_changed = l_s_ext_db-ts_tech_changed. |
| 282| endif. |
| 283| if l_s_ext-requests_techok = 0. |
| 284| clear l_s_ext-ts_tech_changed. |
| 285| endif. |
| 286| |
| 287| if l_s_ext_db-requests_error <> l_s_ext-requests_error or |
| 288| l_s_ext_db-records_error <> l_s_ext-records_error. |
| 289| l_s_ext-ts_error_changed = l_timestamp. |
| 290| l_s_ext-ts_data_changed = l_timestamp. |
| 291| l_changed = 'X'. |
| 292| else. |
| 293| l_s_ext-ts_error_changed = l_s_ext_db-ts_error_changed. |
| 294| endif. |
| 295| if l_s_ext-requests_error = 0. |
| 296| clear l_s_ext-ts_error_changed. |
| 297| endif. |
| 298| |
| 299| if l_s_ext_db-requests_all <> l_s_ext-requests_all or |
| 300| l_s_ext_db-records_all <> l_s_ext-records_all. |
| 301| l_s_ext-ts_data_changed = l_timestamp. |
| 302| l_changed = 'X'. |
| 303| endif. |
| 304| |
| 305| l_t_part[] = i_t_part[]. |
|>>>>>| sort l_t_part by timestamp_verb descending. |
| 307| read table l_t_part into l_s_part index 1. |
| 308| l_s_ext-ts_last_request = l_s_part-timestamp_verb. |
| 309| l_s_ext-last_request = l_s_part-partnr. |
| 310| if l_s_ext_db-ts_last_request <> l_s_ext-ts_last_request or |
| 311| l_s_ext_db-last_request <> l_s_ext-last_request. |
| 312| l_s_ext-ts_data_changed = l_timestamp. |
| 313| l_changed = 'X'. |
| 314| endif. |
| 315| if l_changed = 'X'. |
| 316| modify rsmdatastate_ext from l_s_ext. |
| 317| endif. |
| 318| endif. |
| 319| |
| 320| if not ( i_dta_type = rsstm_c_types-psa_new or |
| 321| i_dta_type = rsstm_c_types-psa_old ). |
| 322| call function 'RSM_LAST_CHANGE_CHECK_UPDATE' |
| 323| exporting |
| 324| i_dta = i_dta(30) |
| 325| i_tstmp = l_s_ext-ts_data_changed. |
|
|Active Calls/Events |
|No. Ty. Program Include Line |
| Name |
| 16 FUNCTION SAPLRSSTATMAN LRSSTATMANU12 306 |
| RSSTATMAN_UPDATE_DATASTATE_EXT |
| 15 FORM SAPLRSM1 LRSM1U23 768 |
| RSM1_UPDATE_RSMDATASTATE |
| 14 FORM SAPLRSM1 LRSM1F08 5520 |
| RSM1_INIT_PARTTAB |
| 13 FORM SAPLRSM1 LRSM1U23 187 |
| RSSM_UPDATE_RSMDATASTATE |
| 12 FUNCTION SAPLRSM1 LRSM1U23 139 |
| RSSM_UPDATE_RSMDATASTATE |
| 11 METHOD CL_RSSM_STATMAN===============CP CL_RSSM_STATMAN===============CM00L 15 |
| CL_RSSM_STATMAN=>IF_RSBK_REQUEST_OBSERVER~AFTER_FINAL_STATE_TRANSITION |
| 10 METHOD CL_RSBK_REQUEST_STATE=========CP CL_RSBK_REQUEST_STATE=========CM01S 13 |
| CL_RSBK_REQUEST_STATE=>AFTER_FINAL_STATE_TRANSITION |
| 9 METHOD CL_RSBK_REQUEST===============CP CL_RSBK_REQUEST===============CM00H 11 |
| CL_RSBK_REQUEST=>IF_RSBK_REQUEST~SET_USTATE_RED |
| 8 FORM SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUIF01 26 |
| SET_USTATE_300 |
| 7 MODULE (PAI) SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUII01 122 |
| USER_COMMAND_0300 |
| 6 MODULE (PAI) SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUII01 70 |
| USER_COMMAND_100 |
| 5 FUNCTION SAPLRSBM_REQUEST_GUI LRSBM_REQUEST_GUIU01 24 |
| RSBM_SHOW_REQUEST |
| 4 FUNCTION SAPLRSS2 LRSS2U26 39 |
| RSS2_CALL_FCODE_EMPTY_GLOBALS |
| 3 FORM SAPLRSS2 LRSS2U26 1 |
| RSS2_CALL_FCODE_EMPTY_GLOBALS |
| 2 FORM SAPMSSY1 SAPMSSY1 85 |
| REMOTE_FUNCTION_CALL |
| 1 MODULE (PBO) SAPMSSY1 SAPMSSY1 30 |
| %_RFC_START |
Please advise me,
Thanks and Regards,
Uma -
ABAP dump when user login in to PRD system
Hi Experts,
From today morning our users are facing one severe issue.The users when ever they login into the system the ABAP dump is occuring like "Database inconsistency: Start transaction SICK ",when i execute the SICK t-code it is showing errors.
SAP System Check
no application server offers an VB service
Severe problems were detected during initial system check.
Please, do not use that system before fixing these problems.
our go live was before one month only,now we are facing this issue.our kernel release is 740 and DB sybase ASE 15.7.0.1010. please suggest us what can we do.
regards,
Patan Thavaheer.|15.05.2014 Active parameters 12:47:40 |
|Parameter Name |Parameter value Parameter Value - Continued |
|login/disable_multi_gui_login |1 |
|rdisp/wp_no_enq |1 |
|login/no_automatic_user_sapstar |0 |
|SAPSYSTEMNAME |XXX |
|SAPGLOBALHOST |XXXXXX |
|SAPSYSTEM |00 |
|INSTANCE_NAME |DVEBMGS00 |
|DIR_CT_RUN |$(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64 |
|DIR_EXECUTABLE |$(DIR_INSTANCE)\exe |
|DIR_PROFILE |\\XXXXXX\sapmnt\XXX\SYS\profile |
|_PF |$(DIR_PROFILE)\XXX_DVEBMGS00_XXXXXX |
|SETENV_00 |PATH=$(DIR_EXECUTABLE);%PATH% |
|Start_Program_00 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) |
|_CPARG0 |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybjdbc.lst |
|_CPARG1 |source:$(DIR_GLOBAL)/syb/NTAMD64 |
|Start_Program_01 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0) $(_CPARG1) |
|Start_Program_02 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) |
|_CPARG2 |list:$(DIR_GLOBAL)/syb/NTAMD64/cpe_sybodbc.lst |
|_CPARG3 |source:$(DIR_GLOBAL)/syb/NTAMD64/sybodbc |
|Start_Program_03 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG2) $(_CPARG3) |
|_CPARG4 |list:$(DIR_CT_RUN)/sapcrypto.lst |
|Start_Program_04 |immediate $(DIR_CT_RUN)\sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG4) |
|SAPJVM_VERSION |6.1.048 |
|DIR_SAPJVM |$(DIR_EXECUTABLE)$(DIR_SEP)sapjvm_6 |
|jstartup/vm/home |$(DIR_SAPJVM) |
|Start_Program_05 |immediate $(DIR_CT_RUN)\strdbs.cmd XXX |
|sec/libsapsecu |$(ssl/ssl_lib) |
|ssf/ssfapi_lib |$(ssl/ssl_lib) |
|rdisp/wp_no_dia |10 |
|rdisp/wp_no_btc |3 |
|_DW |$(DIR_EXECUTABLE)\disp+work$(FT_EXE) |
|Start_Program_06 |local $(_DW) pf=$(_PF) |
|_IG |$(DIR_EXECUTABLE)\igswd$(FT_EXE) |
|Start_Program_07 |local $(_IG) -mode=profile pf=$(_PF) |
|rdisp/wp_no_vb |1 |
|rdisp/wp_no_vb2 |1 |
|rdisp/wp_no_spo |1 |
|ssl/ssl_lib |$(DIR_EXECUTABLE)$(DIR_SEP)$(FT_DLL_PREFIX)sapcrypto$(FT_DLL) |
|SETENV_01 |SECUDIR=$(DIR_INSTANCE)/sec | -
ABAP Dump when running S_ALR_87100205 (RFHABU00N)
Hi,
We are implementing New GL for a company code in Turkey. When I trying to run the report RFHABU00N for non-leading ledger, I am getting an abap dump because the program is not able to report the output for non-leading ledger documents. The report outputs correct information when executed for the leading ledger.
has any one else faced this issue in the past and if so how was it resolved.
We are currently on SAP ECC 6.04.
Thanks,
NitinHi,
What is the dump message exactly? Anyway, for execution of this report for non-leading ledger, please, consult the following notes:
1883338 - RFHABU00N Long runtimes and termination
1965855 - RFHABU00/RFHABU00N: General Ledger View
1965562 - SAPDBBRF: Fiscal year not correctly delimited for non-leading ledgers
1939154 - RFHABU00N: Documents from non-leading ledgers ignored
Regards,
Eli -
ABAP Dump when calling Function Module Starting New Task
Hi all. I have a tricky situation now, I am doing a POC on parallel processing.
I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program):
METHOD start.
CALL FUNCTION 'Z_ZZCLS_STEER_114NUMC'
STARTING NEW TASK me->id
CALLING me->finish ON END OF TASK.
ENDMETHOD. "start
However I get the following ABAP dump:
Short text
Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"
The function module only contains a wait statement to simulate parallel processing. It is strange that it dumps here, because when I change the FM call to another call that has been triggered successfully from other classes, it still produces the same ABAP dump.
The background of the Proof Of Concept is to see if I can get an event to trigger the next process that depends on the outcome of the previous process. Parallel processes are run in the start methods by calling RFC.
<Garbled code removed>
Moderator Message: Please post relevant portions of the code only.
Edited by: Suhas Saha on Jul 17, 2011 1:17 PMWell, the thing is I did manage to run 3 other Function Modules asynchronously succeesfully prior to that function call, with the same exact function call syntax. Further more, I have tried editing it with your suggestion but I get the exact same dump.
The complete function group can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZmFhNzcwMTgtYzQ0Mi00NzQ4LTg5YTMtNDNlNWUxYTM2NTg3&hl=en_US
The complete program can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4YWJmNjU3ODYtODRmMy00Nzg2LThkNTUtZjNkNDRhZGQ3MTUw&hl=en_US
The complete ST22 dump can be found here:
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZDU1YmFkZDAtOTU5MS00ZTgwLWFlZTktNWZhMDUxMzJlZWNl&hl=en_US
Basically I ST22 gives me the following:
Runtime Errors RPERF_ILLEGAL_STATEMENT
Date and Time 17.07.2011 05:29:54
|Short text |
| Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK" |
|What happened? |
| Error in the ABAP Application Program |
| |
| The current ABAP program "Z_ZZB1_CLOSE_PERIOD_TEST2" had to be terminated |
| because it has |
| come across a statement that unfortunately cannot be executed. |
And it explains it here (but is not helpful / relevant at all) as I ran the program from SE38.
|Error analysis |
| There is probably an error in the program |
| "Z_ZZB1_CLOSE_PERIOD_TEST2". |
| The program was probably called in a conversion exit |
| or in a field exit. These are implemented by |
| function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or |
| USER_EXIT_xxxxx_INPUT. |
| Conversion exits are triggered during screen field transports or |
| WRITE statements, field exits during field transports from the |
| screen to the ABAP/4 program. |
| In this connection, the following ABAP/4 statements are not allowed: |
| |
I hope you try to download the slinkee files and you will notice the call function I performed was no different than the other call function RFC calls that really are working. -
DUMP when execute any tasks - OBJECTS_OBJREF_NOT_ASSIGNED_NO
Hi Experts,
I need help. When we try to execute any tasks at UCMON we have the following DUMP:
Erro tpo.exec. OBJECTS_OBJREF_NOT_ASSIGNED_NO
Exceção CX_SY_REF_IS_INITIAL
Data e hora 16.03.2011 11:53:29
Dump breve ABAP não está complet.gravado (demas.extenso)
TxtBreve
Access with 'ZERO' object reference not possible.
O que aconteceu ?
Error in ABAP application program.
The current ABAP program "CL_UC_COMPOUND================CP" had to be
terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
O que pode ser feito?
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.
Análise do erro
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_REF_IS_INITIAL', was
neither
caught nor passed along using a RAISING clause, in the procedure
"GET_GUI_DATA_SELACC" "(METHOD)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
There was an attempt to access a component using a 'NULL' object
reference (points to nothing).
An object reference must indicate an object (an instance of a class),
before it can be used to access components.
Either the reference was never set or it was set to 'NULL' using a
CLEAR statement.
Notas p/eliminação de erros
Probably the only way to eliminate the error is to correct the program.
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:
"OBJECTS_OBJREF_NOT_ASSIGNED_NO" CX_SY_REF_IS_INITIALC
"CL_UC_COMPOUND================CP" or "CL_UC_COMPOUND================CM00H"
"GET_GUI_DATA_SELACC"
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.
The exception must either be prevented, caught within the procedure
"GET_GUI_DATA_SELACC"
"(METHOD)", or declared in the procedure's RAISING clause.
Someone help me please?
Thanks
MariliaIs it a Groundhog Day again:
TSV_TNEW_PAGE_ALLOC_FAILED - BCS load from data stream task
Raise Exception when execute UCMON
and this very thread
in all these cases, IMHO, the proper way was the following:
1. Try to find the proper OSS note
2. if not succesfull - properly regenerate the data basis,
3. if not succesfull - open a new OSS note to SAP.
Edited by: Eugene Khusainov on Mar 16, 2011 10:42 PM
Maybe you are looking for
-
Getting links in one frame to open content in another...
Hello, I would like links in the 'menu' frame of my site to open the new page in another frame, called 'content'. Although I have entered the name of the frame ('content') in the target box in the link properties, the page consistently opens in a new
-
In my Mail POP account, for my Hughes.net mail server, I can't figure out how to format the incoming mail server. Hughes support got me straightened out with the SMTP Outgoing Mail, but they say my problems with the incoming mail is an Apple problem.
-
Installment Plan Migration failing (Emigall)
Hi all, I'm trying to migrate installment plan data using the INSTPLAN object. I can upload successfully as long as I'm only migrating ONE payment. The problem is when I try to migrate multiple payments. The way I read the docs, I should just be a
-
Transfer data from Sap system to .xls format
Hi Friends, How to transfer data from a internal table in SAP system to the .xls file in legacy system. Is gui_download the correct one. Thanks, Anuradha
-
Upgrading from trial verion to full version.
Hello all, Our company has just download the trail version for Sun One Web Server 6.1. Now we are all happy with it and going to buy a full version. My question is do we need to reinstall the trail version or there is a place to enter the licence key