ME5A transaction is giving ABAP dump
Dear Mentors
User While executing ME5A transaction, ABAP run time error is coming
error details
ABAP runtime error :SAPSQL_PARSE_ERROR
exception : CX_SY_DYNAMIC_OSQL_SYNTAX
Function : ME_READ_EBAN_MULTIPLE
Our system details
SAP_APPL 617 SP 1
we applied sap notes
0001855828
0001856538
authorization objects for that user
M_BANF_BSA
M_BANF_EKG
M_BANF_EKO
M_BANF_FRG
M_BANF_WRK
M_BEST_BSA
M_BEST_EKG
M_BEST_EKO
M_BEST_WRK
M_EINK_FRG
S_ADMI_FCD
S_ALV_LAYO
S_ALV_LAYR
S_BDS_DS
S_CTS_ADMI
S_CTS_SADM
S_DEVELOP
S_GUI
S_SPO_ACT
S_SPO_DEV
S_SPO_PAGE
S_TCODE
Please find attachments for more details
Thanks
regards
Sudheer k
Hi,
Do refer the below OSS Note, this error is caused due to internal authorization check in,
method : CL_AUTHCHECK_SQL_MM
This Note includes latest correction for your ABAP Dump from release 616 and 617 which was released in 27.01.2014.
1872223 - Correction WHERE clause CL_AUTHCHECK_SQL_MM
Rgds,
MBPATIL
Similar Messages
-
MIR4 transaction is giving ABAP Runtime Error
Hi Experts,
When I am trying to display the invoice in MIR4 and/or MIRO the system is generating ABAP runtime error. DYNPRO_FIELD_CONVERSION. This is in Version ECC 6.0.
Short text
Conversion error
What happened?
The current screen processing action was terminated since a situation
occurred where the application could not continue.
This is probably due to an error in the ABAP program or in the curren
screen.
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 manag
termination messages, in particular for long term reference.
Error analysis
The program has been interrupted and cannot resume.
Program "SAPLMR1M" attempted to display fields on screen 6310.
An error occurred during the conversion of this data.
How to correct the error
There was a conversion error in the output of fields to the screen.
The formats of the ABAP output field and the screen field may not match.
Some field types require more space on the screen than in the ABAP
program. For example, a date output field on the screen requires two
more characters than the corresponding field in the ABAP program. When
the date is displayed on the screen, an error occurs resulting in this
error message.
Screen name.............. "SAPLMR1M"
Screen number............ 6310
Screen field............. "DRSEG-REMNG"
Error text............... "FX015: Sign lost."
Other data:
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.
Please help us to solve this issue.
Thanks and Regards,
Havina
Edited by: Havina Kutty on May 19, 2009 11:54 AMHello,
Please refer
Note 503934 - MIRO: Dump DYNPRO_FIELD_CONVERSION -> field 'REMNG'
Note 445853 - MIR4:more credit memos than invoices for service
Note 393189 - MIRO: Incorrect update of BPMNG -> DYNPRO_FIELD_CONVERSION
Regards,
Ravi -
Support Pack SAPKB70012 NW2004s giving ABAP dumps
Hello All,
We are trying to apply Basis Support Pack 12 NW2004s in one of our systems. The support packed stoped in Import Proper step becuse of wp max runtime reached. So now when I try to kick it of it gives me the follwoing ABAP dump.
Runtime Errors SYNTAX_ERROR
Date and Time 05/30/2007 14:12:00
Short text
Syntax error in program "SAPLSCP2 ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLSTXC" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "SAPLSCP2 " in include
"CL_SALV_FORM_ELEMENT==========CU " in
line 13:
"The type "IF_SALV_FORM_CONFIG" is unknown."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP "
Error analysis
The following syntax error was found in the program SAPLSCP2 :
"The type "IF_SALV_FORM_CONFIG" is unknown."
Trigger Location of Runtime Error
Program SAPLSTXC
Include LSTXCFFO
Row 518
Module type (FORM)
Module Name FO_DETERMINE_CODEPAGE
Source Code Extract
Line SourceCde
488 data: cp_c4(4) type c,
489 current_dynamic_codepage like tcp00-cpcodepage.
490
491 perform fo_determine_codepage using language
492 changing codepage.
493
494 * only change locale if codepage is different to application server
495 * get effective system codepage
496 call 'CUR_LCL' id 'CODEPAGE' field cp_c4.
497 current_dynamic_codepage = cp_c4.
498 if codepage <> current_dynamic_codepage.
499 * set locale language language.
500 perform nls_switch_language using language.
501 endif.
502
503 endform.
504
505
506 form fo_determine_codepage using p_lang like tcp09-lang
507 changing p_cp like tcp09-cpcodepage.
508 statics: begin of codepage_tab occurs 10,
509 language like tcp09-lang,
510 codepage like tcp09-cpcodepage,
511 end of codepage_tab.
512
513 read table codepage_tab with key language = p_lang.
514 if sy-subrc = 0.
515 p_cp = codepage_tab-codepage.
516 else.
517 codepage_tab-language = p_lang.
>>> call function 'SCP_CODEPAGE_FOR_LANGUAGE'
519 exporting
520 language = codepage_tab-language
521 importing
522 codepage = codepage_tab-codepage
523 exceptions
524 no_codepage = 1
525 others = 2.
526 if sy-subrc <> 0.
527 perform fatal.
528 message a464(td) with codepage_tab-language raising others.
529 endif.
530 append codepage_tab.
531 p_cp = codepage_tab-codepage.
532 endif.
533
534 endform.
535
536
537 ************************************************************************
On every transaction that we try to execute we get the same dump.
Any help would greatly be appreciated.
Thanks
NSQWhat is the status of this thread? Does the error still being encountered? If not, could you provide the resolution so that all the readers of this thread? If it is still being encountered and the last resort is to restore, you could probably try the command: tp r3i <SP> <SID> pf=e:\usr\sap\trans\bin\tp_domain_<SID>.pfl tag=spam. Since there nothing to lose, prior to performing the restoration proper, you could probably try that command.
Actually, the resolution for the error being encountered is in SAPKB70013 NW2004s. We also encountered this problem and with patience on our side, we just waited for a couple of days or so for the SP Level 12 to complete and then, its all ok. However, SAPKB70014 also has a similar error being brought upon by SAPKB70012, again, patience needs to come in so as not to have any problems. Furthermore, note that since these OCS patches (12 and 14), have long runtime, it would be best to make it as a best practice to run SP application in background. -
ABAP dump LOAD_PROGRAM_NOT_FOUND in S_ALR_* transactions
Hi,
I am trying to execute S_ALR_87011792 and S_ALR_87012249 and getting LOAD_PROGRAM_NOT_FOUND abap dumps in tdms receiver client in dev system. We are on ECC6.
Here is the dump details:
Short text
Program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" not found.
What happened?
There are several possibilities:
Error in the ABAP Application Program
The current ABAP program "SAPLKYP4" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
or
Error in the SAP kernel.
The current ABAP "SAPLKYP4" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
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
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely "GP4A1HFKFHN7RW6BOFW65F3ZTQ9".
However, program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" does not exist in the library.
Short text
Program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" not found.
What happened?
There are several possibilities:
Error in the ABAP Application Program
The current ABAP program "SAPLKYP4" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
or
Error in the SAP kernel.
The current ABAP "SAPLKYP4" program had to be terminated because the
ABAP processor detected an internal system error.
What can you do?
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
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely "GP4A1HFKFHN7RW6BOFW65F3ZTQ9".
However, program "GP4A1HFKFHN7RW6BOFW65F3ZTQ9" does not exist in the library.Hello,
Please check the SAP notes 84023 and 361491 and regenerate the reports. It solves this error in 99% percent of the cases.
If you need, please import the report from client 000 in the IMG.
The path to follow is:
Financial Accounting -> General Ledger Accounting
-> Information System -> Drilldown Reports (G/L Accounts)
-> Report -> Import Report from Client 000
Regards,
Renan -
ABAP Dumps while loading data form one DSO to another DSO
Hi All,
We are getting following ABAP dump while loading data from one DSO to another DSO.
Please find below ABAP Dump we are getting.
Please let us know how we can resolve this issue.
Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_X
ABAP Program CL_RSBK_CMD_DP_LOOP===========CP
Application Component BW-WHM-DST
Date and Time 30.05.2014 07:10:03
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).
What can you do?
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
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.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
"MESSAGE_TYPE_X" " "
"CL_RSBK_CMD_DP_LOOP===========CP" or "CL_RSBK_CMD_DP_LOOP===========CM00Q"
"GET_LOG"
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..... 731
SAP Basis Level. 0004
Application server... "cab-bi-prod1"
Network address...... "10.10.72.43"
Operating system..... "Windows NT"
Release.............. "6.1"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 12
Shortdump setting.... "full"
Database server... "nguksvamds039"
Database type..... "ORACLE"
Database name..... "PWB"
Database user ID.. "SAPSR3"
Terminal.......... " "
Char.set.... "C"
SAP kernel....... 720
created (date)... "Dec 20 2011 02:14:54"
create on........ "NT 6.0 6002 S x86 MS VC++ 16.00"
Database version. "OCI_11201_SHARE, 11.2.0.3.0 "
Patch level. 117
Patch text.. " "
Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
SAP database version. 720
Operating system..... "Windows NT 5.1, Windows NT 5.2, Windows NT 6.0, Windows
NT 6.1"
Memory consumption
Roll.... 0
EM...... 12569376
Heap.... 0
Page.... 24576
MM Used. 3422928
MM Free. 764192
User and Transaction
Client.............. 100
User................ "THARDEEP"
Language key........ "E"
Transaction......... " "
Transaction ID...... "03C1E7E3F560F14CA2AD00505698028E"
EPP Whole Context ID.... "53873353A7E31150E10080000A0A2142"
EPP Connection ID....... 00000000000000000000000000000000
EPP Caller Counter...... 0
Program............. "CL_RSBK_CMD_DP_LOOP===========CP"
Screen.............. "SAPMSSY0 1000"
Screen Line......... 6
Debugger Active..... "none"
Information on where terminated
Termination occurred in the ABAP program "CL_RSBK_CMD_DP_LOOP===========CP" -
in "GET_LOG".
The main program was "RSBATCH_EXECUTE_PROZESS ".
In the source code you have the termination point in line 7
of the (Include) program "CL_RSBK_CMD_DP_LOOP===========CM00Q".
The program "CL_RSBK_CMD_DP_LOOP===========CP" was started as a background job.
Job Name....... "BIDTPR_10616_1"
Job Initiator.. "THARDEEP"
Job Number..... 07100200
Source Code Extract
Line SourceCde
1 METHOD get_log.
2 DATA: l_r_request TYPE REF TO cl_rsbk_request.
3 IF p_r_log IS INITIAL.
4 TRY.
5 l_r_request = cl_rsbk_request=>create_from_db( if_rsbk_cmd~n_requid ).
6 CATCH cx_rs_not_found.
>>>>> MESSAGE x299(rsbk).
8 ENDTRY.
9 IF l_r_request->get_uses_new_log( ) = rs_c_false.
10 p_r_log = cl_rsbm_log_cursor_process=>create_for_process( i_r_process ).
11 ELSE.
12
13 TRY.
14 DATA l_runid TYPE rsbrun.
15 l_runid = l_r_request->get_runid( ).
16 IF l_runid = 0.
17 l_runid = 1.
18 ENDIF.
19 p_r_log = cl_rsbm_log_cursor_process_dtp=>create_new(
20 i_requid = if_rsbk_cmd~n_requid
21 i_runid = l_runid ).
22 IF n_datapakid IS NOT INITIAL.
23 p_r_log->goto_datapackage( n_datapakid ).
24 ENDIF.
25 CATCH cx_rs_not_found .
26 MESSAGE x299.
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 1
SY-FDPOS 25
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Process
SY-MSGTY X
SY-MSGID RSBK
SY-MSGNO 299
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20140530
SY-UZEIT 071002
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
Active Calls/Events
No. Ty. Program Include Line
Name
7 METHOD CL_RSBK_CMD_DP_LOOP===========CP CL_RSBK_CMD_DP_LOOP===========CM00Q 7
CL_RSBK_CMD_DP_LOOP=>GET_LOG
6 METHOD CL_RSBK_CMD_DP_LOOP===========CP CL_RSBK_CMD_DP_LOOP===========CM00J 38
CL_RSBK_CMD_DP_LOOP=>SET_DP_IN_PROCESS
5 METHOD CL_RSBK_CMD_DP_LOOP===========CP CL_RSBK_CMD_DP_LOOP===========CM00B 9
CL_RSBK_CMD_DP_LOOP=>IF_RSBK_CMD~SET_PROCESS_PARAMETERS
4 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00E 15
CL_RSBK_PROCESS=>SET_MEMENTO
3 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM003 30
CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~GET_OBJECT_REF
2 FUNCTION SAPLRSBATCH LRSBATCHU13 428
RSBATCH_EXECUTE_PROCESS
1 EVENT RSBATCH_EXECUTE_PROZESS RSBATCH_EXECUTE_PROZESS 374
START-OF-SELECTION
Chosen variables
Name
Val.
No. 7 Ty. METHOD
Name CL_RSBK_CMD_DP_LOOP=>GET_LOG
I_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
SCREEN
%_17NNS0005639652_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30005639652F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
25005F00310037004E004E00530030003000300035003600330039003600350032005F0025005F0025005F0025005F
SPACE
2
0
0
0
2000
SY-REPID
CL_RSBK_CMD_DP_LOOP===========CP
4455544544454554445333333333334522222222
3CF232BF3D4F40FCFF0DDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F0043004D0044005F00440050005F004C004F004F0050003D003D003D003D003D
ME->IF_RSBK_CMD~N_REQUID
0
0000
0000
00000000
L_R_REQUEST
{O:initial}
F0000000
F0000000
FF00000000000000
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
SY-XPROG
SAPCNVE
5454454222222222222222222222222222222222
3103E65000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
53004100500043004E0056004500200020002000200020002000200020002000200020002000200020002000200020
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGID
RSBK
55442222222222222222
232B0000000000000000
00000000000000000000
00000000000000000000
5200530042004B002000200020002000200020002000200020002000200020002000200020002000
SY-MSGNO
299
333
299
000
000
320039003900
SY-MSGV1
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
%_##TVREG_001
2
0
0
0
2000
RS_C_FALSE
2
0
0
0
2000
No. 6 Ty. METHOD
Name CL_RSBK_CMD_DP_LOOP=>SET_DP_IN_PROCESS
I_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
I_DATAPAKID
000236
333333
000236
000000
000000
300030003000320033003600
L_TH_RANGE_X
Table[initial]
L_S_RANGE_X
2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_TH_RANGE
Table[initial]
L_S_RANGE
2222222222222222222222222222220022222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
RSBC_C_DPSTATE-ACTIVE
5
3
5
0
0
3500
L_R_ROOT
{O:1091*\CLASS=CX_RS_FAILED}
B0004000
C0003400
BC00000043040000
ME
{O:72*\CLASS=CL_RSBK_CMD_DP_LOOP}
B0004000
70008000
B700000048000000
ME->P_R_LOG
{O:initial}
F0000000
F0000000
FF00000000000000
No. 5 Ty. METHOD
Name CL_RSBK_CMD_DP_LOOP=>IF_RSBK_CMD~SET_PROCESS_PARAMETERS
I_MEMENTO
ÿ#######4103##############D#####################D#A#T#A#P#A#K#I#D#¼####0#0#0#2#3#6#½#
F00000803333000000000000004000000000000000000000404050405040404040B0000303030303030B0
F621120041030000160000C0004900000000000000000000401040100010B09040C000C000000203060D4
FF0602010102800034313033000000000106000000000C000000440900000000000000000000000000000000000000
I_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
000000000000000000000000000000
000000000000000000000000000000
43004F004E00560045005200530049004F004E005F0045005800490054002000200020002000200020002000200020
SY-SUBRC
0
0000
0000
00000000
ME->N_DATAPAKID
000236
333333
000236
000000
000000
300030003000320033003600
ME
{O:72*\CLASS=CL_RSBK_CMD_DP_LOOP}
B0004000
70008000
B700000048000000
No. 4 Ty. METHOD
Name CL_RSBK_PROCESS=>SET_MEMENTO
I_TH_CMD_MEMENTO
Table IT_42[5x52]
\CLASS=CL_RSBK_PROCESS\METHOD=IF_RSBATCH_EXECUTE~GET_OBJECT_REF\DATA=L_S_PROCESS-TH_CMD_MEMENT
Table reference: 21
TABH+ 0(20) = 10C64700DF070000000000000000000000000000
TABH+ 20(20) = 150000002A000000050000003400000020000000
TABH+ 40(16) = 045A0000A006000005000000A425C000
store = 0x10C64700DF070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 21 (0x15000000)
label = 42 (0x2A000000)
fill = 5 (0x05000000)
leng = 52 (0x34000000)
loop = 32 (0x20000000)
xtyp = TYPE#000010
occu = 5 (0x05000000)
accKind = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUniYes)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0x607B4100DF070000
pgHook = 0x0000000000000000
idxPtr = 0xC08D5000DF070000
id = 36 (0x24000000)
shmTabhSet = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 5 (0x05000000)
lineAlloc = 5 (0x05000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
##LOOP_DP ###쀀
00444554522222222222221000
30CFF0F4000000000000004020
0000000000000000000000000C
00000000000000000000000000
030000004C004F004F0050005F00440050002000200020002000200020002000200020002000200020002000140000
##X_DATASTORE ###쀀
00554454554542222222221000
408F414134F250000000004030
0000000000000000000000000C
00000000000000000000000000
0400000058005F004400410054004100530054004F0052004500200020002000200020002000200020002000140000
##ERROR_FILTER ###쀀
FF455455444545222222221000
FF522F2F69C452000000004040
FF00000000000000000000000C
FF000000000000000000000000
FFFFFFFF4500520052004F0052005F00460049004C0054004500520020002000200020002000200020002000140000
##TRFN ###쀀
FF554422222222222222221000
EF426E00000000000000004040
FF00000000000000000000000C
FF000000000000000000000000
FEFFFFFF5400520046004E002000200020002000200020002000200020002000200020002000200020002000140000
##U_ODSO ###쀀
00554454222222222222221000
605FF43F000000000000004040
0000000000000000000000000C
00000000000000000000000000
0600000055005F004F00440053004F0020002000200020002000200020002000200020002000200020002000140000
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
SYST
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
SYST-REPID
CL_RSBK_PROCESS===============CP
4455544555444553333333333333334522222222
3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F00500052004F0043004500530053003D003D003D003D003D003D003D003D003D
L_R_ERROR
{O:initial}
F0000000
F0000000
FF00000000000000
L_S_CMD_MEMENTO
##LOOP_DP ###쀀
00444554522222222222221000
30CFF0F4000000000000004020
0000000000000000000000000C
00000000000000000000000000
030000004C004F004F0050005F00440050002000200020002000200020002000200020002000200020002000140000
ME->P_TH_CMD_R
Table IT_724[8x48]
{O:1*\CLASS=CL_RSBK_PROCESS}\DATA=P_TH_CMD_R
Table reference: 353
TABH+ 0(20) = 00306E00DF070000000000000000000000000000
TABH+ 20(20) = 61010000D40200000800000030000000FFFFFFFF
TABH+ 40(16) = 04E100005042030009000000BC25C800
store = 0x00306E00DF070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 353 (0x61010000)
label = 724 (0xD4020000)
fill = 8 (0x08000000)
leng = 48 (0x30000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000037
occu = 9 (0x09000000)
accKind = 4 (ItAccessHashed)
idxKind = 3 (ItIndexList)
uniKind = 1 (ItUniYes)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0x302E6E00DF070000
pgHook = 0x0000000000000000
idxPtr = 0x80306E00DF070000
id = 647 (0x87020000)
shmTabhSet = 0x0000000000000000
refCount = 1 (0x01000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 9 (0x09000000)
lineAlloc = 9 (0x09000000)
shmVersId = 0 (0x00000000)
shmRefCount = 2 (0x02000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
########P Í#2# #
000000005222222222C03020
103000000000000000D02000
000000000000000000000000
000000000000000000000000
010000000300000000000000000000005000200020002000200020002000200020002000CD00000032000000200000
########P ·#H# #
000000005222222222B04020
300040100000000000708000
000000000000000000000000
000000000000000000000000
030000000000000004000000010000005000200020002000200020002000200020002000B700000048000000200000
########X ¶#I# #
00FF00005222222222B04020
40FF70108000000000609000
00FF00000000000000000000
00FF00000000000000000000
04000000FFFFFFFF07000000010000005800200020002000200020002000200020002000B600000049000000200000
########T °#O# #
FF00FF005222222222B04020
FF00EF40400000000000F000
FF00FF000000000000000000
FF00FF000000000000000000
FFFFFFFF00000000FEFFFFFF040000005400200020002000200020002000200020002000B00000004F000000200000
########T ®#Q# #
FF0000005222222222A05020
EF0060404000000000E01000
FF0000000000000000000000
FF0000000000000000000000
FEFFFFFF0000000006000000040000005400200020002000200020002000200020002000AE00000051000000200000
L_S_CMD_R
########P ·#H# #
000000005222222222B04020
300040100000000000708000
000000000000000000000000
000000000000000000000000
030000000000000004000000010000005000200020002000200020002000200020002000B700000048000000200000
SY-REPID
CL_RSBK_PROCESS===============CP
4455544555444553333333333333334522222222
3CF232BF02F3533DDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F00500052004F0043004500530053003D003D003D003D003D003D003D003D003D
CX_RS_STEP_FAILED=>FAILED_IN_PARALLEL_MODE
L_S_CMD_MEMENTO-NODE
3
0000
3000
03000000
SY-SUBRC
0
0000
0000
00000000
L_S_CMD_MEMENTO-MEMENTO
ÿ#######4103##############D#####################D#A#T#A#P#A#K#I#D#¼####0#0#0#2#3#6#½#
F00000803333000000000000004000000000000000000000404050405040404040B0000303030303030B0
F621120041030000160000C0004900000000000000000000401040100010B09040C000C000000203060D4
FF0602010102800034313033000000000106000000000C000000440900000000000000000000000000000000000000
ME
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
No. 3 Ty. METHOD
Name CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~GET_OBJECT_REF
I_PROCESS_TYPE
DTP_LOAD
4555444422
440FCF1400
0000000000
0000000000
4400540050005F004C004F004100440020002000
I_BATCH_ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
I_BATCH_PROCESS
238
2222223332
0000002380
0000000000
0000000000
2000200020002000200020003200330038002000
I_PARAMETER
ۿĂȁ#ㄴ㌰##༅##(Ѐޱ##########PROCESSྫ##ꨨ##Ѐڪ##ꨌ##Ѐ###ꨄ##Ѐª##ꨂ##Ȁྭ##ꨴ##Ѐª##ꨨ###ྮ##갴##⠀¼#砠) ㈀㌀㘀##ÿ#
F008330000020B00000000005544455A002000A000000A000000A000000A003000A002100A003000B0220000000FF0
F2104000500801000000000002F3533B008800A00C800A004800A002000D004800A008400E004F00C0090000000FF0
0000330000000000000000000000000000A000000A000000A000000A000000A000000A000000A0020070333333FF00
61201300F0004700000000000000000F00A004600A004800A004000A002F00A004000A008F00C0080080000236FF00
FF060201010280003431303300000000050F0000000028000004B10700000000000000000000000000000000000000
R_R_RSBATCH_EXECUTE
{O:initial}
F0000000
F0000000
FF00000000000000
L_S_PROCESS-PROCESSTYPE
2
0
0
0
2000
L_S_PROCESS-NO_COMMIT
2
0
0
0
2000
L_R_PROCESS
{O:1*\CLASS=CL_RSBK_PROCESS}
F0000000
E0001000
FE00000001000000
L_S_PROCESS-DATAPAKID
000236
333333
000236
000000
000000
300030003000320033003600
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_S_PROCESS-NODE
-1
FFFF
FFFF
FFFFFFFF
L_S_PROCESS-TH_CMD_MEMENTO
Table IT_42[5x52]
No. 2 Ty. FUNCTION
Name RSBATCH_EXECUTE_PROCESS
ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
I_DIALOG_DEBUG_MODE
2
0
0
0
2000
PROCESS
238
E000
E000
EE000000
G_T_COLS[]
Table[initial]
SY-REPID
SAPLRSBATCH
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004C00520053004200410054004300480020002000200020002000200020002000200020002000200020
L_MODULE_TYPE
M
4
D
0
0
4D00
G_PROCESS_TYPE
2222222222
0000000000
0000000000
0000000000
2000200020002000200020002000200020002000
%_FL2*CTRL_200_WAIT
<initial>
<initial>
<initial>
<<iinniittiiaall>>
ICON_SELECT_DETAIL
@16@
4334
0160
0000
0000
4000310036004000
L_S_CTRL-LANGU
E
4
5
0
0
4500
SY-LANGU
E
4
5
0
0
4500
SYST-REPID
SAPLRSBATCH
5454554454422222222222222222222222222222
310C232143800000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5300410050004C00520053004200410054004300480020002000200020002000200020002000200020002000200020
SYST
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
%_FL2*CTRL_1100
<initial>
<initial>
<initial>
<<iinniittiiaall>>
%_DUMMY$$
2222
0000
0000
0000
2000200020002000
L_MODULE_NAME
CL_RSBK_PROCESS
4455544555444552222222222222222222222222
3CF232BF02F35330000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
43004C005F005200530042004B005F00500052004F0043004500530053002000200020002000200020002000200020
%_SPACE
2
0
0
0
2000
G_T_BATCH_SERV
00
22222222222222222222222222222222222222222222222222222222222222222222222222222222233
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_S_CTRL-PROCESS_TYPE
DTP_LOAD
4555444422
440FCF1400
0000000000
0000000000
4400540050005F004C004F004100440020002000
G_SUBRC
0
0000
0000
00000000
L_S_CTRL-BATCH_ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
OKCODE
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_S_CTRL-BATCH_PROCESS
238
2222223332
0000002380
0000000000
0000000000
2000200020002000200020003200330038002000
SAVEOK
2222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
2000200020002000200020002000200020002000200020002000200020002000200020002000200020002000200020
L_PARAMETER
ۿĂȁ#ㄴ㌰##༅##(Ѐޱ##########PROCESSྫ##ꨨ##Ѐڪ##ꨌ##Ѐ###ꨄ##Ѐª##ꨂ##Ȁྭ##ꨴ##Ѐª##ꨨ###ྮ##갴##⠀¼#砠) ㈀㌀㘀##ÿ#
F008330000020B00000000005544455A002000A000000A000000A000000A003000A002100A003000B0220000000FF0
F2104000500801000000000002F3533B008800A00C800A004800A002000D004800A008400E004F00C0090000000FF0
0000330000000000000000000000000000A000000A000000A000000A000000A000000A000000A0020070333333FF00
61201300F0004700000000000000000F00A004600A004800A004000A002F00A004000A008F00C0080080000236FF00
FF060201010280003431303300000000050F0000000028000004B10700000000000000000000000000000000000000
L_R_BATCH_EXECUTE
{O:initial}
F0000000
F0000000
FF00000000000000
L_RETURN
<empty string>
10000000
40001000
1400000001000000
L_T_MSG
Table[initial]
%_TAG*CTRL_200_VAL
<initial>
<initial>
<initial>
<<iinniittiiaall>>
G_CURSOR_LINE
0
0000
0000
00000000
SY-SUBRC
0
0000
0000
00000000
No. 1 Ty. EVENT
Name START-OF-SELECTION
L_T_CTRL
Table IT_26[1x424]
\PROGRAM=RSBATCH_EXECUTE_PROZESS\DATA=L_T_CTRL
Table reference: 15
TABH+ 0(20) = D08B4C00DF070000000000000000000000000000
TABH+ 20(20) = 0F0000001A00000001000000A8010000FFFFFFFF
TABH+ 40(16) = 040000005090000004000000C130C000
store = 0xD08B4C00DF070000
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 15 (0x0F000000)
label = 26 (0x1A000000)
fill = 1 (0x01000000)
leng = 424 (0xA8010000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000013
occu = 4 (0x04000000)
accKind = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniNo)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
stMode = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
isUsed = 1
isCtfyAble = 1
hasScndKeys = 0
hasRowId = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi = 0x10854C00DF070000
pgHook = 0x508C4C00DF070000
idxPtr = 0x0000000000000000
id = 21 (0x15000000)
shmTabhSet = 0x0000000000000000
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 508 (0xFC010000)
lineAlloc = 12 (0x0C000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
rowId = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
DTPR_10616_1 238
4555533333532222222222222222222222223332222222222222222222222222222222222222222222222222222222
4402F10616F10000000000000000000000002380000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
SYST
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
L_S_CTRL
DTPR_10616_1 238 BIDTPR_10616_1 07100200cab-bi-prod1_
4555533333532222222222222222222222223332244455553333353222222222222222222333333336662662776635
4402F10616F100000000000000000000000023800294402F10616F100000000000000000007100200312D29D02F41F
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
SCREEN
%_17NNS0005639652_%_%_%_%_%_%_
2533445333333333352525252525252222222222222222222222222222222222222222222222222222222222222222
5F17EE30005639652F5F5F5F5F5F5F0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
25005F00310037004E004E00530030003000300035003600330039003600350032005F0025005F0025005F0025005F
L_S_CTRL-BATCH_PROCESS
238
2222223332
0000002380
0000000000
0000000000
2000200020002000200020003200330038002000
%_SPACE
2
0
0
0
2000
L_S_PAR-WP_NO
12
332
120
000
000
310032002000
ID
DTPR_10616_1
455553333353222222222222222222
4402F10616F1000000000000000000
000000000000000000000000000000
000000000000000000000000000000
44005400500052005F00310030003600310036005F0031002000200020002000200020002000200020002000200020
L_PROCESS
238
E000
E000
EE000000
L_S_HEADER-HOLD_PAR_PROCS
X
5
8
0
0
5800
SY
##########################A###P#######|#########<#############################T#########XC####
0000000000000000000000100040005000000070000000003000000000000000000000000000105000100000540000
10000010000010000000109010101000000000C000000000C000000000000000000000000000604000E00000830500
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000C
0100000000000000000000000100000000000000000000000100000000000000000000000000000001000000190000
PROCESS
999999999
FC93
F9AB
FFC99A3B
Internal notes
The termination was triggered in function "ab_jmess"
of the SAP kernel, in line 1411 of the module
"//bas/720_REL/src/krn/runt/abdynpro.c#7".
The internal operation just processed is "MESS".
Internal mode was started at 20140530071002.
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=1724)
When : 5/30/2014 7:9:54.12
Threads : 2
Computer Name : NGUKSVRMDS040
User Name : pwbadm
Number of Processors: 4
Processor Type: Intel64 Family 6 Model 37 Stepping 1
Windows Version : 6.1 Current Build: 7601
State Dump for Thread Id 1374
0000000002178EF0 0000000140F6F2A1 0020002000200020 disp+work!DumpStacks [ntstcdbg.c (548)]
0000000002178FF0 000000013FB0E304 0000000074D126B0 disp+work!NTDebugProcess [ntstcdbg.c (383)]
0000000002179020 000000013FD1C439 0000000074D126B0 disp+work!CTrcStack2 [dptstack.c (354)]
0000000002179070 000000013FD21A7F 0000000002179AD0 disp+work!rabax_CStackSave [abrabax.c (8649)]
0000000002179980 000000013FCD37FC 000000000000005C disp+work!ab_rabax [abrabax.c (1419)]
00000000021799C0 000000013FD0BBE1 0000000000000000 disp+work!ab_jmess [abdynpro.c (1418)]
0000000002179B50 000000013FD7E5D8 0000000000000001 disp+work!ab_extri [abextri.c (721)]
0000000002179BA0 000000013FD7EEC5 0000000000000001 disp+work!ab_xevent [abrunt1.c (278)]
0000000002179C30 000000013FD5C589 000007DF000002A0 disp+work!ab_trigg [abrunt1.c (57)]
0000000002179CC0 000000013FB77126 0000000000000016 disp+work!ab_run [absubmit.c (511)]
0000000002179E70 000000013FB7BA2D 0000000000000000 disp+work!dynpmcal [dymainstp.c (2732)]
0000000002179F00 000000013FB7ACDC 000000000217A0E0 disp+work!dynppai0 [dymainstp.c (1355)]
0000000002179FD0 000000013FB34EEF 0000000000000020 disp+work!dynprctl [dymainstp.c (470)]
000000000217F3C0 000000013F9C3CC0 0000000000000000 disp+work!dynpen00 [dymain.c (2026)]
000000000217F690 000000013F9C44BC FFFFFFFFFFFFFF00 disp+work!TskhLoop [thxxhead.c (4871)]
000000000217F6F0 000000013F8EC603 00000000000D9E9C disp+work!ThStart [thxxhead.c (1195)]
000000000217F790 000000013F8C10A1 FFFFFFFF00000001 disp+work!DpMain [dpxxdisp.c (1174)]
000000000217F7C0 0000000141246B8E 0000000000000001 disp+work!nlsui_main [thxxanf.c (80)]
000000000217F7F0 000000007799652D 0000000000000000 disp+work!__tmainCRTStartup [crtexe.c (552)]
000000000217F820 0000000077ACC541 0000000000000000 kernel32!BaseThreadInitThunk
000000000217F870 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart
State Dump for Thread Id 290
000000000E0BF880 000007FEFDAB3C2F 00000000DBAAC265 ntdll!NtFsControlFile
000000000E0BF8F0 0000000141139FAF FFFFFFFFFFFFFFFE KERNELBASE!ConnectNamedPipe
000000000E0BF990 0000000074C81D9F 00000000024BC0D0 disp+work!SigIMsgFunc [signt.c (717)]
000000000E0BF9C0 0000000074C81E3B 0000000074D12AC0 MSVCR100!endthreadex
000000000E0BF9F0 000000007799652D 0000000000000000 MSVCR100!endthreadex
000000000E0BFA20 0000000077ACC541 0000000000000000 kernel32!BaseThreadInitThunk
000000000E0BFA70 0000000000000000 0000000000000000 ntdll!RtlUserThreadStart
List of ABAP programs affected
Index Typ Program Group Date Time Size Lang.
0 Prg RSBATCH_EXECUTE_PROZESS 0 13.08.2013 12:28:38 45056 E
1 Prg SAPMSSY0 1 13.08.2013 09:12:51 111616 E
2 Prg SAPMSSYD 1 13.08.2013 10:17:05 23552 E
3 Prg SAPFSYSCALLS 1 07.03.2005 18:01:13 8192 E
4 Prg RSDBRUNT 0 13.08.2013 10:51:31 306176 E
5 Prg SAPLSPRI 5 13.08.2013 10:49:40 407552 E
6 Typ PRI_PARAMS 0 27.10.1998 15:01:35 5120
7 Typ ARC_PARAMS 0 08.08.1997 14:45:20 5120
8 Typ PRI_LAYOUT 0 04.09.2002 14:38:36 3072
9 Typ PRIPAR_EXT 0 09.09.2011 20:56:18 3072
10 Typ PRIPAR_EX2 0 09.09.2011 20:54:51 2048
11 Typ PRIPAR_EX3 0 09.09.2011 20:54:52 3072
12 Typ TPRI_DEF 0 01.02.2001 17:50:49 5120
13 Prg SAPLSPOO 13 13.08.2013 10:14:36 181248 E
14 Typ TSP03 0 13.08.1998 16:56:08 5120
15 Typ USR01 0 09.09.2011 20:55:50 4096
16 Typ TSP1D 0 09.09.2011 20:57:01 5120
17 Prg SAPLRSPOLSTDRV 17 28.05.2009 08:18:25 64512 E
18 Typ TSPOPTIONS 0 06.12.1996 16:09:18 2048
19 Prg SAPCNVE 19 07.03.2005 18:01:13 9216 E
20 Prg SAPLSPOC 20 09.09.2011 21:19:41 177152 E
21 Typ RSPOCHECK 0 14.07.1997 13:01:20 4096
22 Typ DEVPAR 0 09.09.2011 20:54:15 3072
23 Typ RSPOATTR 0 19.01.2000 18:34:33 2048
24 Typ RSSCR 0 23.11.1999 09:24:41 5120
25 Prg RSDBSPBL 0 07.03.2005 18:01:13 84992 E
26 Prg SAPDB__S 0 07.03.2005 18:01:13 21504 E
27 Typ VARID 0 28.05.2009 08:12:55 5120
28 Typ SSCRFIELDS 0 02.05.1997 13:16:39 5120
29 Prg RSDBSPVA 0 13.08.2013 10:51:31 160768 E
30 Prg %_CSYDB0 0 07.03.2005 18:01:13 40960 E
31 Typ RSVAMEMKEY 0 16.12.1996 19:31:50 2048
32 Prg RSDBSPMC 0 05.09.2006 14:14:08 92160 E
33 Typ DDSHDESCR 0 28.11.1997 16:26:30 4096
34 Typ SPPARAMS 0 07.03.1997 14:48:48 2048
35 Prg SAPLICON 35 13.12.2007 11:37:48 31744 E
36 Prg %_CICON 35 13.12.2007 11:37:48 126976 E
37 Typ ICONT 0 05.09.2006 14:14:08 2048
38 Prg SAPLSABE 38 09.09.2011 21:09:40 14336 E
39 Prg SAPLSECU 39 13.08.2013 10:16:43 110592 E
40 Typ RSSUBINFO 0 22.11.1999 21:15:17 3072
41 Prg RSDBSPVD 0 09.09.2011 21:33:31 102400 E
42 Typ DFIES 0 09.09.2011 20:54:19 10240
43 Typ VARI 0 16.12.1996 19:38:11 6144
44 Typ RSDSFIELDS 0 28.05.2009 08:12:29 3072
45 Prg %_CRSDS 0 07.03.2005 18:01:13 11264 E
46 Typ RSDSEXPR 0 16.12.1996 19:31:30 3072
47 Typ RVARI 0 18.06.1999 11:23:08 4096
48 Prg SAPLSVAR 48 13.08.2013 10:49:34 936960 E
49 Typ RSVARKEY 0 16.12.1996 19:31:51 2048
50 Prg SAPLSSEL 50 13.08.2013 10:42:32 1699840 E
51 Prg RSDBSPDS 0 13.12.2007 11:37:48 66560 E
52 Typ RSEXFCODE 0 18.07.1997 17:04:17 2048
53 Prg SAPLDSYA 53 13.08.2013 10:45:29 52224 E
54 Prg SAPFSDS1 53 07.03.2005 18:01:13 61440 E
55 Typ TDCLD 0 14.07.1998 14:53:43 5120
56 Prg SAPLSDOD 56 13.08.2013 10:42:31 50176 E
57 Typ DOKIL 0 07.04.1997 18:29:04 3072
58 Prg SAPLLANG 58 09.09.2011 21:12:32 11264 E
59 Typ T002 0 25.09.2007 11:09:36 2048
60 Prg SAPFSPOR 0 24.06.2008 18:36:49 16384 E
61 Typ RSPARINT 0 10.03.1995 17:53:00 2048
62 Prg SAPLSCNT 62 07.03.2005 18:01:13 34816 E
63 Prg SAPSHDTV 62 13.08.2013 08:38:56 38912 E
64 Prg SAPFGUICNTL 1 07.03.2005 18:01:13 27648 E
65 Prg SAPLOLEA 65 13.08.2013 08:38:34 110592 E
66 Prg SAPLSGUI 66 04.12.2009 20:43:32 105472 E
67 Prg SAPLSTTM 67 09.09.2011 21:26:18 79872 E
68 Prg SAPLSBDC 68 13.12.2007 10:50:07 49152 E
69 Prg SAPLSFES 69 13.08.2013 10:47:09 316416 E
70 Prg SAPLTHFB 70 13.08.2013 10:21:30 472064 E
71 Typ WPINFO 0 28.05.2009 08:12:57 6144
72 Prg SAPLURFC 72 13.08.2013 10:49:32 29696 E
73 Prg SAPLSPLUGIN 73 09.09.2011 21:19:29 9216 E
74 Typ SWCBCONT 0 09.09.2011 20:56:57 3072
75 Typ OLE_VERBS 0 09.02.1995 13:23:37 2048
76 Typ OLE_PA 0 13.01.1995 11:06:59 2048
77 Typ SSCRTEXTS 0 15.08.1997 14:15:15 3072
78 Prg SAPLRSBATCH 78 13.08.2013 12:29:38 689152 E
79 Prg /1BCDWBEN/SAPLREN0002 79 23.11.2005 13:29:42 294912 E
80 Prg SAPLSENA 80 28.05.2009 08:20:47 39936 E
81 Prg SAPLBTCH 81 13.08.2013 10:51:12 2248704 E
82 Prg SAPLRS_GENERAL 82 13.08.2013 12:20:02 120832 E
83 Prg /1BCDWBEN/SAPLREN0003 83 23.11.2005 13:29:44 282624 E
84 Prg SAPLSYDB 84 09.09.2011 21:28:17 65536 E
85 Typ MSXXLIST_V6 0 28.05.2009 08:12:22 4096
86 Typ BAL_S_MSG 0 09.09.2011 20:53:51 7168
87 Prg CL_RSBK_PROCESS===============CP 87 10.09.2011 08:11:36 103424 E
88 Prg IF_RSBATCH_CALLBACK===========IP 78 09.09.2011 22:39:45 9216 E
89 Prg IF_RSBATCH_EXECUTE============IP 78 09.09.2011 22:39:45 8192 E
90 Typ RSBK_S_PROCESS 0 09.09.2011 20:56:47 4096
91 Typ RSBK_S_CMD_MEMENTO 0 09.09.2011 20:54:56 2048
92 Prg CL_RSBK_REQUEST===============CP 92 13.08.2013 11:53:19 222208 E
93 Prg CL_RSBK_REQUEST_GENERAL=======CP 93 10.09.2011 08:12:31 38912 E
94 Prg SAPLRRSI 94 13.08.2013 12:29:38 393216 E
95 Typ RSD_S_COB_PRO 0 09.09.2011 20:56:49 26624
96 Prg CL_RSR========================CP 96 13.08.2013 12:06:59 180224 E
97 Prg CL_RS_BASE====================CP 97 13.08.2013 12:27:37 15360 E
98 Prg CL_RSD_CHA====================CP 98 13.08.2013 11:55:18 563200 E
99 Prg CL_RSD_IOBJ_VERS==============CP 99 13.08.2013 12:03:26 301056 E
100 Prg SAPLRRMS 100 13.08.2013 12:29:38 49152 E
101 Prg SAPLRRI1 101 13.08.2013 12:29:38 496640 E
102 Typ RSR_S_DEBUGFLAGS 0 13.08.2013 12:01:28 14336
103 Prg CL_RSDDTREX_CORE==============CP 103 13.08.2013 12:29:38 49152 E
104 Prg SAPLRSDI 104 09.09.2011 22:19:14 43008 E
105 Prg SAPLRSDG_IOBJ_DB_READ 105 13.08.2013 12:29:38 355328 E
106 Typ RSD_S_AGGRINFO 0 09.09.2011 20:55:04 2048
107 Typ RSD_S_VIOBJ 0 09.09.2011 20:55:07 30720
108 Prg SAPLRSDN_IOBJ 108 13.08.2013 12:29:38 163840 E
109 Prg CL_RSROA_VQ_SERVICES==========CP 109 13.08.2013 12:29:37 86016 E
110 Prg CL_ABAP_ELEMDESCR=============CP 110 28.05.2009 08:29:24 41984 E
111 Prg CL_ABAP_DATADESCR=============CP 111 28.05.2009 08:29:18 21504 E
112 Prg CL_ABAP_TYPEDESCR=============CP 112 13.08.2013 10:48:27 33792 E
113 Prg CL_ABAP_REFDESCR==============CP 113 13.08.2013 10:48:27 34816 E
114 Prg CL_ABAP_STRUCTDESCR===========CP 114 13.08.2013 10:48:27 49152 E
115 Prg CL_ABAP_COMPLEXDESCR==========CP 115 28.05.2009 08:29:17 19456 E
116 Prg CL_ABAP_TABLEDESCR============CP 116 09.09.2011 21:11:02 37888 E
117 Prg CL_ABAP_CLASSDESCR============CP 117 28.05.2009 08:29:15 34816 E
118 Prg CL_ABAP_OBJECTDESCR===========CP 118 28.05.2009 08:29:28 37888 E
119 Prg CL_ABAP_INTFDESCR=============CP 119 28.05.2009 08:29:25 27648 E
120 Prg CL_ABAP_SOFT_REFERENCE========CP 120 18.11.2005 14:35:28 10240 E
121 Prg CL_ABAP_REFERENCE=============CP 121 07.03.2005 18:01:13 8192 E
122 Prg CL_RSRTS_METADATA=============CP 122 13.08.2013 12:28:25 106496 E
123 Prg CL_RSRTS_METADATA_R3IS========CP 123 13.08.2013 11:55:22 157696 E
124 Prg IF_RSRTS_METADATA=============IP 117 13.08.2013 11:55:54 26624 E
125 Prg %_CABAP 117 28.05.2009 08:14:56 36864 E
126 Prg IF_SERIALIZABLE_OBJECT========IP 117 07.03.2005 18:01:13 5120 E
127 Prg CL_RSROA_VQ_METADATA==========CP 127 13.08.2013 11:55:22 252928 E
128 Prg CL_RSL_ME_METADATA============CP 128 13.08.2013 12:28:21 233472 E
129 Prg IF_RSDRV_TREX_NAME_MAPPER=====IP 117 13.08.2013 12:29:31 8192 E
130 Prg CL_RSDDLTIP_IPROV_TABLE=======CP 130 13.08.2013 11:55:15 147456 E
131 Prg CL_RSAN_PR_ANPR_PROV_TRANSIENTCP 131 13.08.2013 11:55:06 117760 E
132 Prg CL_RSD_DTA====================CP 132 13.08.2013 12:03:25 320512 E
133 Typ LVC_S_ROID 0 19.01.2000 18:31:34 2048
134 Typ RSZCOMPKEY 0 09.09.2011 20:55:16 3072
135 Prg IF_RSO_TLOGO_MAINTAIN=========IP 117 09.09.2011 22:36:34 13312 E
136 Prg IF_RSD_DTA====================IP 117 09.09.2011 22:35:40 30720 E
137 Prg CL_RSRTS_METADATA_ODP=========CP 137 13.08.2013 12:03:31 396288 E
138 Prg IF_RSRTS_TRPR=================IP 117 13.08.2013 12:10:34 10240 E
139 Prg CL_RSR_QPROV_METADATA=========CP 139 13.08.2013 11:55:23 248832 E
140 Typ RSD_S_DTA_PRO 0 09.09.2011 20:55:08 26624
141 Typ RSD_S_IOBJ_OBN 0 09.09.2011 20:56:49 2048
142 Prg CX_RSD_IOBJ_NOT_FOUND=========CP 142 09.09.2011 22:36:07 16384 E
143 Prg CX_RSD_IOBJ_EXCEPTION=========CP 143 09.09.2011 22:36:07 14336 E
144 Prg CX_RS_STATIC_CHECK============CP 144 09.09.2011 22:37:44 19456 E
145 Prg CX_RS_ERROR===================CP 145 09.09.2011 22:37:36 13312 E
146 Prg CX_STATIC_CHECK===============CP 146 18.11.2005 14:35:29 11264 E
147 Prg CX_ROOT=======================CP 147 09.09.2011 21:51:41 13312 E
148 Prg CX_NO_CHECK===================CP 148 18.11.2005 14:35:29 11264 E
149 Typ RSAROUT 0 09.09.2011 20:49:50 4096
150 Typ RSAROUTT 0 09.09.2011 20:50:52 2048
151 Typ RSDVDPA 0 09.09.2011 20:56:49 9216
152 Typ RSDIOBJV 0 09.09.2011 20:54:57 5120
153 Typ RSDKYF 0 09.09.2011 20:46:44 5120
154 Typ RSDVTIM 0 09.09.2011 20:56:49 12288
155 Typ RSDVUNI 0 09.09.2011 20:56:49 9216
156 Typ RSDVCHA 0 09.09.2011 20:55:09 14336
157 Prg CL_RSDRC_NCUM_GEN_TYPES=======CP 157 13.08.2013 12:28:48 9216 E
158 Prg CL_RSD_IOBJ_UTILITIES=========CP 158 09.09.2011 22:25:11 57344 E
159 Prg SAPLRSDN 159 13.08.2013 12:29:38 86016 E
160 Prg SAPLRSVERS 160 13.08.2013 12:29:38 371712 E
161 Typ RSNPAR 0 09.09.2011 20:55:07 3072
162 Prg SAPLSTR4 162 13.08.2013 10:42:32 74752 E
163 Prg %_CTRNSP 162 07.03.2005 18:01:13 10240 E
164Hi Hardeep,
Looks like the transformation and DTP need to be activated again.
The error is RSBK (299) - 'Invalid program status'. So please activate the transformation and DTP possibly activate the DSO's too.
It should then work.
Thanks
Amit -
Hi,
We are getting the following error in the PRD system .
Runtime Errors COMPUTE_BCD_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
Short text
Overflow during the arithmetical operation (type P) in program
What happened?
Error in the ABAP Application Program
The current ABAP program "AQFKSD01========SD_STOCKS-01==" had to be termi
because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', wa
caught and
therefore caused a runtime error.
The reason for the exception is:
An overflow was discovered in an ongoing arithmetical operation with
operands of type P. Possible causes are:
1. The result field of type P is too small for the result.
2. The result or a intermediate result has more than 31 decimal places.
i have tried searching in notes and etc but still not helpful.
Did anyone solve the problem.
Thanks in advanceThis seems to be a query, right (transaction SQ00/SQ01)
The computation fields are too small, the values don´t fit into the types you defined.
Markus -
ABAP dump Error while creating service order in PCUI.
Hi Experts,
We are getting following ABAP dump error while creating service order in PCUI which is working fine in GUI.
Runtime Errors RAISE_EXCEPTION
Date and Time 02.01.2008 14:55:38
Short text
Exception condition "TYPE_NOT_FOUND" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
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
A RAISE statement in the program "CL_CRM_ELEMDESCR==============CP" raised the
exception
condition "TYPE_NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
| function module from the display of active calls.
We have added custom fields in the service application. these custom fields with Z-structure & data elements are included in BSP structure CRMT_BSP_SRV_OIC_SRCHRES in development system.But the same Z structure & custom fields are exist in the production system but not included in BSP Structue CRMT_BSP_SRV_OIC_SRCHRES.
This may be the reason resulting this ABAP dump error in PCUI while creating Service order.
How these Z structures can be included in the BSP Structure CRMT_BSP_SRV_OIC_SRCHRES in production system?
Helpful answers would be rewrded max points as it is high priority issue.
Regards,
Basavaraj PatilHi Thirumala,
Thnaks for the reply.
I have enhanced service application using transaction EEWB to add new custom fields. these fields are there in Z structure created by the system in production system. All the transports are moved to target system. Problem is that Z structure( contains custom fields) created while doing EEWB is not included in BSP structure.
I f transports are missed to move to target system, Is there any other alternative to solve this problem?
Regards,
Basavaraj Patil -
Hello Experts,
I am getting GETWA_NOT_ASSIGNED abap short dump in our our system, we are running on SCM 5.0, in program SAPLZ_FRE_TSD_ANALYTICS or LZ_FRE_TSD_ANALYTICS.
Waiting for your kind response.
Runtime Errors GETWA_NOT_ASSIGNED
Date and Time 14.04.2008 16:43:45
Short text
Field symbol has not yet been assigned.
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLZ_FRE_TSD_ANALYTICS" had to be terminated because
it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
You attempted to access an unassigned field symbol
(data segment 32776).
This error may occur if
- You address a typed field symbol before it has been set with
ASSIGN
- You address a field symbol that pointed to the line of an
internal table that was deleted
- You address a field symbol that was previously reset using
UNASSIGN or that pointed to a local field that no
longer exists
- You address a global function interface, although the
respective function module is not active - that is, is
not in the list of active calls. The list of active calls
can be taken from this short dump.
How to correct the error
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:
"GETWA_NOT_ASSIGNED" " "
"SAPLZ_FRE_TSD_ANALYTICS" or "LZ_FRE_TSD_ANALYTICSF02"
"ANALYSE_STOCK_DATA"
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... "u962004t"
Network address...... "10.200.230.10"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 11
Shortdump setting.... "full"
Database server... "u962004t"
Database type..... "ORACLE"
Database name..... "P46"
Database user ID.. "SAPP46"
Char.set.... "en_US.iso88591"
SAP kernel....... 700
created (date)... "Dec 30 2007 21:06:56"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 141
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16128
EM...... 8379808
Heap.... 0
Page.... 0
MM Used. 5137344
MM Free. 3239680
User and Transaction
Client.............. 110
User................ "SAP_SUPPORT"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "480337E1306170D9E10000000AC8E60A"
Program............. "SAPLZ_FRE_TSD_ANALYTICS"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "P46"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "asynchron with reply and non-transactional (emode 0,
imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 110
User................ "SAP_SUPPORT"
Transaction......... " "
Call Program........."Z_FRE_STOCK_ANALYZE"
Function Module..... "Z_FRE_STOCK_RECONCILE"
Call Destination.... "u962004t_P46_65"
Source Server....... "u962004t_P46_65"
Source IP Address... "10.200.230.10"
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 "SAPLZ_FRE_TSD_ANALYTICS" - in
"ANALYSE_STOCK_DATA".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 135
of the (Include) program "LZ_FRE_TSD_ANALYTICSF02".
Source Code Extract
Line
SourceCde
105
l_error = true.
106
ENDIF.
107
108
READ TABLE ct_comp ASSIGNING <comp>
109
WITH KEY locno = <act>-locno
110
matnr = <act>-matnr
111
tstfr = <act>-tstfr
112
tstto = <act>-tstto
113
BINARY SEARCH.
114
115
IF sy-subrc = 0.
116
l_idx_comp = sy-tabix.
117
118
IF <act>-kval <> <comp>-kval.
119
IF NOT <comp>-init = c_stockch.
120
l_error = true.
121
ENDIF.
122
ENDIF.
123
124
ELSE. " sy-subrc = 0.
125
l_error = true.
126
UNASSIGN: <comp>.
127
ENDIF. " sy-subrc = 0.
128
129
IF l_error = true.
130
MOVE-CORRESPONDING <act> TO ls_result.
131
MOVE <act>-kval TO ls_result-kval_act.
132
133
IF <act>-init = c_error.
134
Error status set because of error from STOCK_FROM_LIME call
>>>>>
IF <comp>-kval <> 0.
136
MOVE text-t05 TO ls_result-text.
137
ENDIF.
138
ELSEIF <comp> IS ASSIGNED.
139
IF <comp>-init = c_error.
140
MARD in ERP initial
141
MOVE text-t04 TO ls_result-text.
142
ELSEIF <comp>-init = c_stockch.
143
Stock change flag in ERP not initial
144
MOVE text-t09 TO ls_result-text.
145
ELSE.
146
DIFFERENCES !!!!
147
MOVE text-t08 TO ls_result-text.
148
ENDIF.
149
ELSE.
150
MOVE text-t02 TO ls_result-text.
151
ENDIF.
152
153
IF <comp> IS ASSIGNED.
154
MOVE <comp>-kval TO ls_result-kval_comp.
Regards,
K R SinghHi K R Singh,
Please contact and get the short dump reviewed by your BASIS team and DBA.
Typically this kind of dump can come due to DB Tablespace issues (and potential inconsistent setup)
Somnath -
SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND
Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text |
| Program "RSORA811" not found. |
|What happened? |
| There are several possibilities: |
| |
| Error in the ABAP Application Program |
| |
| The current ABAP program "RSCOLL00" had to be terminated because it has |
| come across a statement that unfortunately cannot be executed. |
| or |
| Error in the SAP kernel. |
| |
| The current ABAP "RSCOLL00" program had to be terminated because the |
| ABAP processor detected an internal system error. |
|What can you do? |
| 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 |
| On account of a branch in the program |
| (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT) |
| or a transaction call, another ABAP/4 program |
| is to be loaded, namely "RSORA811". |
| |
| However, program "RSORA811" does not exist in the library. |
| |
| Possible reasons: |
| a) Wrong program name specified in an external PERFORM or |
| SUBMIT or, when defining a new transaction, a new |
| dialog module or a new function module. |
| b) Transport error |
|Information on where terminated |
| Termination occurred in the ABAP program "RSCOLL00" - in |
| "LOOP_AT_SYSTEMS_AND_REPORTS". |
| The main program was "RSCOLL00 ". |
| |
| In the source code you have the termination point in line 535 |
| of the (Include) program "RSCOLL00". |
| The program "RSCOLL00" was started as a background job. |
| Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR" |
| Job Initiator.. " bharath" |
| Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath. -
Removing ABAP dump when JDBC is down in RFC- JDBC- RFC scenario
Hi All,
I need help to build one scenario.
I am working on RFC->XI->JDBC->XI->RFC scenario. It is working fine.
But problem is that whenever JDBC server is down RFC is giving ABAP dump in SAP. How can i Remove ABAP dump in SAP and give information to RFC that "JDBC is out of order"
Is it possible to implement without BPM, then How?
If not possible then what could be the steps of BPM?
Thanks & RegardsRohan,
1.Recive Step should open the Synch - Asynch Bridge
2. Block Step --> Send Synchronous inside this step with an Exception Hanler.
3. Now in the exception ahndler step, do the necessary error handling requirement.
4. Send Step --> closes Synch Asynch bridge.
My question is what data do you want to send back to the RFC if the DB is down? This data should be populated inside the exception handling block and then this data should be mapped to the corresponding RFC response and used in the step 4.
Regards,
Bhavesh -
Hello,
I have assigned the gl accounts in CIN for TT UTLZ but when i execute the transaction j2iun the abap dump comes .
Why it comes.
SuggestHi,
I think following note will the solution for the ABAP Dump
Note 1044391 - ABAP dump due to time out error / performance issue in J2IUN
Regards,
Jigar -
Abap Dump in Solman - Create Data Unknown Type - CX_SY_Create_Data_Error
Hi Gurus, I have installed Solution Manager EHP1 with Db2 database and windows operating system with all 64 bit. Solution manager have been successfully installed and configured and it's ready to use. But i'm getting an abap dump in the solution manager system. Approximately 30 abap dump a day which is the same error message. I've tried to find the error message in market place but couldnt find a solution. Can anyone help me to solve this problem. Thanks.
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Exception CX_SY_CREATE_DATA_ERROR
Date and Time 15.04.2010 00:31:09
Short text
CREATE DATA: The specified type "/BI0/V0SDB_C02M2" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SMD_AGGREGATE_MDX==========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.Hello Ram,
Is your issue resolved.Currently i am getting the same issue ,After I have upgraded Solution Manager from EHP1SP20 to SP23.I am getting the Short Dumps.
Runtime Errors CREATE_DATA_UNKNOWN_TYPE
Exception CX_SY_CREATE_DATA_ERROR
Date and Time 08/03/2010 00:30:41
Short text
CREATE DATA: The specified type "/BI0/V0SDB_C02M2" is no valid data type.
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_SMD_AGGREGATE_MDX==========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not
caught in
procedure "INITIALIZE" "(METHOD)", 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:
The dynamically specified type "/BI0/V0SDB_C02M2" at CREATE DATA is no valid
data type.
The type is either unknown or an object type.
How to correct the error
If the specified type "/BI0/V0SDB_C02M2" is an object type, then new objects of
this
type (instances) are not created with CREATE DATA, but with
CREATE OBJECT.
If the type is unknown, then it must be created in the program or in the
ABAP dictionary.
Probably the only way to eliminate the error is to correct the program.
Thank you,
khanth -
Hi,
When I am tryin to change object type in CN41N it is giving ABAP dump with funtion "AC_system_flush" and this function is calling another function "AC_FLUSH_CALL",
Moreover when I checked "AC_FLUSH_CALL" got introduction statement
"NO DIRECT CALLS TO CONTROL FRAMEWORK FROM THIS FUNCTION MODULE".
Anyone has any ideas or come across this situation,,,Or any OSS notes ??
Any help will be appreciated.
Thanks
Abhinayhi
check this Note 1245875 - CN41N: Blank screen displayed and termination without dump. -
ABAP DUMP While doing GI Through Zmovement type in MIGO Transaction
Hi ,
We have migrated from FM FBS to BCS from 12.01.2015.
And we are using 101 profile with GR and IR update.
We received blow ABAP Dump while doing the GI through MIGO Transaction.
Can you please help on this.
Dump detatils
Category ABAP Programming Error
Runtime Errors MESSAGE_TYPE_X
ABAP Program CL_BUAVC_ENTRY================CP
Application Component PSM-FM-BCS-AC
Date and Time 13.01.2015 09:10:00
Operating system..... "AIX 1 6, AIX 1 7" |
| |
| Memory consumption |
| Roll.... 0 |
| EM...... 33518336 |
| Heap.... 0 |
| Page.... 196608 |
| MM Used. 21989120 |
| MM Free. 3145840 |
|User and Transaction |
| Client.............. 256 |
| User................ "MM_BUX00_ZZ" |
| Language key........ "R" |
| Transaction......... "MIGO_GI " |
| Transaction ID...... "54AEDD9E3EE60710E10080000A15C616" |
| |
| EPP Whole Context ID.... "54B35F7088300910E10080000A15C616" |
| EPP Connection ID....... 00000000000000000000000000000000 |
| EPP Caller Counter...... 0 |
| |
| Program............. "CL_BUAVC_ENTRY================CP" |
| Screen.............. "SAPLMIGO 0001" |
| Screen Line......... 18 |
| Debugger Active..... "none" |
|Information on where terminated |
| Termination occurred in the ABAP program "CL_BUAVC_ENTRY================CP" - |
| in "POST". |
| The main program was "SAPLMIGO ". |
| |
| In the source code you have the termination point in line 82 |
| of the (Include) program "CL_BUAVC_ENTRY================CM00J". |
|Source Code Extract |
|Line |SourceCde |
| 52|*--- method has provided some errors!): |
| 53| |
| 54|* Note 1499464: |
| 55|* IF cl_abap_aab_utilities=>is_active( id = 'BUAVC_GROUP' |
| 56|* mode_assert_dump = 'X' ) = 'X'. |
| 57| MOVE 'X' TO l_flg_dump. |
| 58|* ENDIF. |
| 59| |
| 60|*--- Check if the entry buffer of the AVC ledger contains data records |
| 61|*--- from previous COLLECT events: |
| 62| IF ( l_f_avc_ledger-ref_ledger->entry_buffer_lines_count( ) > 0 ). |
| 63|*--- Sorry, must dump: |
| 64| ASSERT ID buavc_group |
| 65| FIELDS c_avc_text 'POSTING_NOT_ALLOWED' |
| 66| CONDITION l_flg_dump <> 'X'. |
| 67| IF l_flg_dump = 'X'. |
| 68| MESSAGE x002(buavc) WITH c_avc_text space |
| 69| 'POSTING_NOT_ALLOWED' space. |
| 70| ENDIF. |
| 71| ENDIF. |
| 72| ENDIF. |
| 73|*---------------------------------------------------------------------- |
| 74|* Note 1666556: |
| 75| IF me->g_commit_before_post EQ 'X'. |
| 76|*--- An unauthorized COMMIT WORK occurred before calling this POST |
| 77|*--- method. This COMMIT WORK has refreshed the AVC entry buffer and |
| 78|*--- would thus create a database inconsistency! |
| 79| MOVE 'X' TO l_flg_dump. |
| 80| IF l_flg_dump = 'X'. |
| 81|*--- Sorry, must dump (see note 1666556): |
|>>>>>| MESSAGE x002(buavc) WITH c_avc_text space |
| 83| 'INVALID_COMMIT' space. |
| 84| ENDIF. |
| 85| ENDIF. |
| 86|*---------------------------------------------------------------------- |
| 87| |
| 88| |
| 89|*--- Call the POST method of the corresponding ledger instance: |
| 90| CALL METHOD l_f_avc_ledger-ref_ledger->post |
| 91| EXPORTING |
| 92| i_ref_appl_log = me->g_ref_appl_log |
| 93| i_doc_ref = i_doc_ref. |
| 94| |
| 95| ENDLOOP. |
| 96|
Thanks Advance.
SAMHi Sam,
Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
Regards,
Prakash. -
ABAP dump in ecc 6.0 for F110 transaction
HI All,
We have recently upgraded to ECC 6.0 from 4.6C.
While displaying the proposal/exception list using F110 transaction for the program RFZALI20. The ABAP dump says "Unable to interpret "1 5D " as a number". It is failing for Key for print parameters (PRI_PARAMS-PRKEYEXT).
Has anyone faced this issue?
Thanks in advance.
-APKHI Balaji,
We could get over this issue by changing the print parameters in the variant we have used.
The variant had some print parameters selected (having green check) even though there are no parameters which are selected. So, I have created a varaint without the print parameters option checked (no more green check in the extended selection).
Hope this is clear.
-Pradeep
Maybe you are looking for
-
Can I replace my itunes library with another user's on the same computer?
I just inherited a MacBook that has the previous user's iTunes library. I'd like to use iTunes to backup my iPhone 5s without mixing my library with his. How can I completely remove the old iTunes library before I sync my phone to this laptop?
-
ISSUE: syncing iCal on iPhone & iPad
I have the iPhone 4 & the newest iPad. I need to sync iCal over iCloud on these devices. Sometimes an even I enter in one iCal appears in the other device, and sometimes it doesn't. It seems very random! This causes much anxiety/frustration, as I nee
-
also on aol mail, Also tried to use the feedback part of this website but when it came to hit the submit button.... it wouldn't change into the hand to let me click... I had this problem as soon as I downloaded the new update, I then couldn't find a
-
HELP ME DOWLOAD VIDEOS!!!!!!!!!!!
ok so i just got a 5th generation ipod. TOTALLY supposed to play videos. when i go to the video option in itunes it allll grayed out like videos arent even an option for me, but it SHOULD be. i cant select any of the "automatically update" or "manual
-
interface Vlan1 nameif inside security-level 100 ip address 172.16.16.3 255.255.248.0 interface Vlan2 nameif outside security-level 0 ip address 172.16.0.3 255.255.248.0 route outside 0.0.0.0 0.0.0.0 172.16.0.1 1 route inside 172.16.0.0 255.255