Short dump in debug mode
Hi All,
We have recently upgraded our server from SAP R/3 4.6b to ECC 5.0. Whenever we are debugging any program(Both standard and Z-programs) getting short dump
in the select and endselect statements. This is happening only when we are going on DEBUG MODE only Appreciate any lights on this issue.(All programs are Unicode enabled).
Regards,
Ameer.
hi
your problem will solve if you put the break point after <b>ENDSELECT</b> statement. let the cursor not go inside the select-endselect statement. it causes short-dump.
thx
murthy
Similar Messages
-
Short dump SAPLSLVC_FULLSCREEN in ALV mode
Hi all
I encountered a short dump in production after i load a text file in my customised program. I did not encountered such error in DEV and UAT. This dump occurs when i add or remove the columns in ALV mode.
Runtime Error PERFORM_NOT_FOUND
Exception CX_SY_DYN_CALL_ILLEGAL_FORM
Occurred on 22.05.2008 at 15:02:44
Call (PERFORM) to a non-existent routine.
What happened?
The current program attempted to call an externally defined routine
that does not exist.
Error in ABAP application program.
The current ABAP program "SAPLSLVC_FULLSCREEN" had to be terminated because one
of the
statements could not be executed.
This is probably due to an error in the ABAP program.
The current ABAP program had to be terminated because the
ABAP processor detected an internal system error.
The current ABAP program "SAPLSLVC_FULLSCREEN" had to be terminated because the
ABAP
processor discovered an invalid system state.
Can anyone kindly advice? Thanks.** WA-NAME = 'TOP_OF_PAGE'. "'SLIS_EV_TOP_OF_PAGE'.
** WA-FORM = 'TOPOFPAGE'.
** APPEND WA TO T_EVENTS.
** WA-NAME = 'END_OF_PAGE'.
** WA-FORM = 'ENDOFPAGE'.
** APPEND WA TO T_EVENTS.
** WA-NAME = 'END_OF_LIST'.
** WA-FORM = 'ENDOFLIST'.
** APPEND WA TO T_EVENTS.
please comment like this code in your code.. -
Short dump while filtering an ALV report
Hi ,
I have an ALV report which gives me short dump when I filter any of the 'P' type field. I tried to implement sap note 839839 in debug mode but in vain. Should I implement this note first and then check the chnage?
the short dump error "..........
Error in ASSIGN: Memory protection error.
The current program "SAPLSSEL " uses the ASSIGN statement.
However, the offset of the segment (20208) plus the length (69)
is greater than the length of the segment (20264).
This is not allowed.
If the error is in one of your own ABAP programs or an SAP program that
you have modified, try to correct it.
Reduce the offset and/or length that you are using.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"ASSIGN_OFFSET+LENGTH_TOOLARGE"
"SAPLSSEL " or "LSSELFDI "
"FILL_DYN_FROM_FIELD_SEL" ........."
I appreciate ur inputs.
thanks in advance,
regards,
shanHi Guys,
I found the answer. I had to define all P type fields with eaxact length of 16 . Its working fine.
thanks for all your help.
regards,
shan -
Short dump while executing Ztransaction
Hi,
I am doing module pool programming by desinging the screens, handling events and running it thru a Z-trnasaction.
My first query is how do I debug a module pool prg.. so as to understand that the error/short dump is because of my code or due to some other reason ...
My second query is that I am getting a short dump with "DIAG_RFC_EXCEPTION" ... I do have access to SM59 ... do I need to check for some other RFC propeties ??... Is this error related to Basis guys??? & the line where it is dumping is as follows :-
Einzelbildverarbeitung Transaktionsvarianten/Batch-Input/CATT
call function 'SYSTEM_SCREEN_INPUT'
exporting
modul = p_repid.
endform. " %_CTL_INPUT
Thank You,
SBHi SB,
One way to debug module pool(Pop-up) is like this :
Many times we would like to start debugging from a Pop-up screen, but the editor doesn't allow us to do that.
*Instead, we have to start debugging all the way from main screen.
*Enclosed is a 3 line script would allow us to make our edits in a Pop-up.
*Create a file with following code and save it as 'debugger.txt' in your local drive and drag and drop it (from Windows explorer) on to the Pop-up box and the debug mode will be on.
FILE CONTENTSMany times we would like to start debugging from a Pop-up screen, but the editor doesn't allow us to do that. Instead, we have to start debugging all the way from main screen. Enclosed is a 3 line script would allow us to make our edits in a Pop-up. Create a file with following code and save it as 'debugger.txt' in your local drive and drag and drop it (from Windows explorer) on to the Pop-up box and the debug mode will be on!
<b>Code: (File Contents)</b>
[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommand
Hope this will help you to find out the error while debugging the pop up .
Cheers
Sunny -
While posting the Doc thru GM_CREATE_BUDGET taking to short dump
while posting the Doc thru GM_CREATE_BUDGET taking to short dump
giving the message:-
Runtime Errors MESSAGE_TYPE_X
Error analysis
Short text of error message:
System error during characteristic derivation maintenance
Long text of error message:
Technical information about the message:
Message class....... "ABADR"
Number.............. 599
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
Trigger Location of Runtime Error
Program SAPLABADR
Include LABADRF01
Row 255
Module type (FORM)
Module Name WORK_AREA PUT
225 EXPORTING
226 i_write_to_tabadrx = 'X'
227 i_list_access = buttons-list_access.
228 ENDIF.
229 * test mode: spool trace results
230 IF NOT debug-print_trace IS INITIAL.
231 CALL FUNCTION 'ABADR_TRACE_WRITE'
232 EXPORTING
233 i_write_to_spool = 'X'
234 i_list_access = buttons-list_access.
235 ENDIF.
236 ENDFORM. "trace--show
237
238 ----
239 * FORM WORK_AREA_DIR--ADD *
240 ----
241 * ........ *
242 ----
243 * --- I_IDENTIFIER *
244 ----
245 FORM work_area--put USING i_identifier TYPE t_identifier
246 i_work_area TYPE any.
247 DATA: name TYPE t_name.
248 FIELD-SYMBOLS: <l_work_area> TYPE ANY.
249
250 CHECK NOT i_identifier IS INITIAL.
251 * put item to work area
252 READ TABLE <strategy>-tab_func_parameters INTO name
253 WITH KEY identifier = i_identifier.
254 IF sy-subrc <> 0.
>>> MESSAGE x599(abadr).256 ENDIF.
257 PERFORM namework_areaassign USING name.
258 * unicode
..........................contd...
Pls help.Hi Victor,
this is due to the Config issues, just check the config related to the "Settings for Availability Control Ledger" in the Grantee Managment -
Short Dump Error when we check the Data Source in RSA3
Hi. Experts.
We are using Data Source 2Lis_13_VDITM and when we try to check in RSA3
for recorts it is going short dump. I am just providing the error information.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in procedure "MCEX_BW_LO_API" "(FUNCTION)", 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:
When importing the object "MC13VD0ITM_TAB", the component no. 96 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX".
The data type is "N" in the dataset, but "X" in the program.
Since I don't have much knowledge in ABAP, Please help me out regarding this issue. Suggest me possible solution and let me know if you need any further information.Hi,
Try adding a TRY CATCH block in the extractor function module to catch the exception.
For the type mismatch you will have to make sure the variables are of same type or they can be type converted.
Use the debug mode of RSA3 to find what data is being exchanged.
You will need to change your extractor to avoid the dump.. or ensure that the value being passed to that object is correctly being passed(correct format)
Cheers
Kiran -
What are techniques used for tuning query performance? Please explain in detail?
What are short dumps how can we check?
What methodologies we follow for the PSA cleansing? Where exactly is the PSA change log where we can delete the request based on timestamp details am using BW 3.1c?
plz help points assured....Hi,
This info may be helpful.
Tuning query performance
General tips
Using aggregates and compression.
Using less and complex cell definitions if possible.
1. Avoid using too many nav. attr
2. Avoid RKF and CKF
3. Many chars in row.
By using T-codes ST03 or ST03N
Go to transaction ST03 > switch to expert mode > from left side menu > and there in system load history and distribution for a particual day > check query execution time.
/people/andreas.vogel/blog/2007/04/08/statistical-records-part-4-how-to-read-st03n-datasets-from-db-in-nw2004
/people/andreas.vogel/blog/2007/03/16/how-to-read-st03n-datasets-from-db
Try table rsddstats to get the statistics
Using cache memoery will decrease the loading time of the report.
Run reporting agent at night and sending results to email.This will ensure use of OLAP cache. So later report execution will retrieve the result faster from the OLAP cache.
Also try
1. Use different parameters in ST03 to see the two important parameters aggregation ratio and records transferred to F/E to DB selected.
2. Use the program SAP_INFOCUBE_DESIGNS (Performance of BW infocubes) to see the aggregation ratio for the cube. If the cube does not appear in the list of this report, try to run RSRV checks on the cube and aggregates.
Go to SE38 > Run the program SAP_INFOCUBE_DESIGNS
It will shown dimension Vs Fact tables Size in percent.If you mean speed of queries on a cube as performance metric of cube,measure query runtime.
3. --- sign is the valuation of the aggregate. You can say -3 is the valuation of the aggregate design and usage. ++ means that its compression is good and access is also more (in effect, performance is good). If you check its compression ratio, it must be good. -- means the compression ratio is not so good and access is also not so good (performance is not so good).The more is the positives...more is useful the aggregate and more it satisfies the number of queries. The greater the number of minus signs, the worse the evaluation of the aggregate. The larger the number of plus signs, the better the evaluation of the aggregate.
if "-----" then it means it just an overhead. Aggregate can potentially be deleted and "+++++" means Aggregate is potentially very useful.
Refer.
http://help.sap.com/saphelp_nw70/helpdata/en/b8/23813b310c4a0ee10000000a114084/content.htm
http://help.sap.com/saphelp_nw70/helpdata/en/60/f0fb411e255f24e10000000a1550b0/frameset.htm
4. Run your query in RSRT and run the query in the debug mode. Select "Display Aggregates Found" and "Do not use cache" in the debug mode. This will tell you if it hit any aggregates while running. If it does not show any aggregates, you might want to redesign your aggregates for the query.
Also your query performance can depend upon criteria and since you have given selection only on one infoprovider...just check if you are selecting huge amount of data in the report
Check for the query read mode in RSRT.(whether its A,X or H)..advisable read mode is X.
5. In BI 7 statistics need to be activated for ST03 and BI admin cockpit to work.
By implementing BW Statistics Business Content - you need to install, feed data and through ready made reports which for analysis.
http://help.sap.com/saphelp_nw70/helpdata/en/26/4bc0417951d117e10000000a155106/frameset.htm
/people/vikash.agrawal/blog/2006/04/17/query-performance-150-is-aggregates-the-way-out-for-me
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1955ba90-0201-0010-d3aa-8b2a4ef6bbb2
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ce7fb368-0601-0010-64ba-fadc985a1f94
http://help.sap.com/saphelp_nw04/helpdata/en/c1/0dbf65e04311d286d6006008b32e84/frameset.htm
Achieving BI Query Performance Building Business Intelligence
http://www.dmreview.com/issues/20051001/1038109-1.html
ODS Query Performance
Refer.
/people/juergen.noe/blog/2007/12/13/overview-important-bi-performance-transactions
/people/prakash.darji/blog/2006/01/26/query-optimization
Thanks,
JituK -
DYNPRO_SEND_IN_BACKGROUND Short dump
In updated teask there are some updated function modules are executed. These function modules are giving error in popup saying "Buffer Tables are not up to date". the message long text it is "To analyze the error, you can set a breakpoint in the function module 'BBP_PD_ABORT' and look at the call-up hierarchy in debugging mode."
So I kept some break point in that function module, now it is giving the following short dump "DYNPRO_SEND_IN_BACKGROUND ",
please tell me what to do
Thanks & Regards,
Raghu,Right, it is trying to throw a debug screen when in background. You must remove the breakpoint.
Regards,
Rich Heilman -
Hello Friends,
I am trying to create an extractor in R/3 for BW. This extractor would be based on a function module. The function module is ready and I have seperately tested the function module(FM). It is working fine and fetching the data.
However, since this FM is for an extractor, it requires a table 'E_T_DATA' as a parameter. I have defined the table E_T_DATA as a parameter in the FM.
Now when I go to transaction RSA3 and try to test the extractor it gives me a short dump. It says the following:
When calling the function module "ZTEST_FM_CONTRACTOR", one of the parameters needed according to the interface description was not specified.
This parameter was "E_T_DATA".
Now if I test the extractor in RSA3 in the debuging mode, I find that following:
<i>CALL FUNCTION S_FNAME
EXPORTING
I_REQUNR = S_S_IF_SIMPLE-REQUNR
I_DSOURCE = S_S_IF_SIMPLE-DSOURCE
I_MAXSIZE = S_S_IF_SIMPLE-MAXSIZE
I_INITFLAG = S_S_IF_SIMPLE-INITFLAG
TABLES
I_T_SELECT = S_S_IF_SIMPLE-T_SELECT
I_T_FIELDS = S_S_IF_SIMPLE-T_FIELDS
EXCEPTIONS
NO_MORE_DATA = 1
ERROR_PASSED_TO_MESS_HANDLER = 2
OTHERS.</i>
In the above code <i>S_FNAME</i> holds the name of the FM ZTEST_FM_CONTRACTOR, which I have created. But if we see here the call to my FM is not exporting "E_T_DATA". But still it is giving a short dump saying "E_T_DATA" was not exported. Also since it is the SAP code I cannot even change it.
I hope friends, you are understanding what I am trying to communicate. Please assist me in this. Thanks!
Regards,
Prem.Hi Premanand,
PLease refer the below lilnk to get a better understanding of the FM Extrcator.
FM Extraction -->
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Hope this helps.
Thanks & Regards,
Sh -
Hello
I'm experiencing the following issue :
Iw32 is called by a call transaction in a customer program. In the process, a standard function (pm_partner_update)
ends with an abap runtime error SAPSQL_ARRAY_INSERT_DUPREC.
Instead of the short dump report, the enduser is entering in debugging mode, with the cursor placed on the failed command. Although he cannot do anything because
he has no debugging authorizations, is it possible to prevent the debug screen display?
Regards,
Philippewe need to pass all the three key fields of IHPA table to avoid this duplicate entry error as it gets generated when you try to update duplicate records to master table . In my case i used I_count parameter of ihpa table to increament the counter . In each case if we do not use counters in that case it is bound to give you exception .so make sure you are not updating any duplicate entry .
-
Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE
Hi All
I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
After we release the CU design to Generate order we get SHORT DUMP.
Any help will be of great help.
I am pasting the details from the dump file here.
Please let me know.
Appretaite your help.
Thanks
Meghana
Runtime Errors CALL_FUNCTION_REMOTE_ERROR
Date and Time 27.08.2007 18:01:10
Short text
"The current application triggered a termination with a short dump."
What happened?
Error in the ABAP Application Program
The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.
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 error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "MESSAGE_TYPE_X"
on the called page.
How to correct the error
Please refer to the notes described in the
short dump.
System environment
SAP-Release 700
Application server... "MB1ES1005"
Network address...... "10.191.97.206"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "MB1ES1005"
Database type..... "ORACLE"
Database name..... "EC6"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jul 25 2007 00:57:05"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 121
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
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.... 8176
EM...... 14633136
Heap.... 0
Page.... 131072
MM Used. 5005432
MM Free. 1263944
User and Transaction
Client.............. 200
User................ 10086330
Language key........ "E"
Transaction......... "/***/DESIGN "
Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
Program............. "/***/SAPLCUORDER_N"
Screen.............. "/***/SAPLCUORDER_N 2000"
Screen line......... 34
Information on where terminated
Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
"SAVE_DESIGN".
The main program was "/***/SAPLCUORDER_N ".
In the source code you have the termination point in line 594
of the (Include) program "/***/LCUORDER_NF07".
Source Code Extract
Line
SourceCde
564
ENDIF .
565
ENDLOOP .
566
IF l_ret-type = 'E' OR
567
l_ret-type = 'A' .
568
CLEAR: save_okcode .
569
570
Show Messages
571
CALL FUNCTION '/***/N_LOG_ADD_MSG'
572
EXPORTING
573
i_log_type = 'G'
574
TABLES
575
t_ret = t_ret.
576
PERFORM log_order_create_show .
577
Show first Message
578
MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
579
WITH
580
l_ret-message_v1 l_ret-message_v2
581
l_ret-message_v3 l_ret-message_v4.
582
CALL FUNCTION '/***/N_DESIGN_INIT' .
583
ELSE .
584
IF g_design_mode = con_mode_crea.
585
Need to update DMS documents with real design number
586
PERFORM document_prepare_002 USING con_desnum_tmp_1
587
lv_desnum.
588
ENDIF.
589
Commit design BAPI's
590
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
591
592
IF save_okcode = con_order.
593
Commit order BAPI's
>>>>>
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
595
DESTINATION 'NONE'.
596
597
call of fct. RFC_CONNECTION_CLOSE is important to get a new
598
initial roll area with initial internal tables next time
599
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
600
EXPORTING
601
destination = 'NONE'
602
EXCEPTIONS
603
destination_not_open = 1
604
OTHERS = 2.
605
ENDIF.
606
607
IF lv_desnum IS INITIAL .
608
lv_desnum = /***/cudesign-desnum .
609
ENDIF .
610
SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
611
Changes saved
612
MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
613
ENDIF .
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
2000
SY-UCOMM
CU01
SY-TITLE
Change Design: 50000109
SY-MSGTY
X
SY-MSGID
00
SY-MSGNO
341
SY-MSGV1
MESSAGE_TYPE_X
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070827
SY-UZEIT
180110
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No. Ty. Program Include Line
Name
4 FORM /***/SAPLCUORDER_N /***/LCUORDER_NF07 594
SAVE_DESIGN
3 FORM /***/SAPLCUORDER_N /***/LCUORDER_NF07 2616
CHECK_AND_SAVE_F07
2 FORM /***/SAPLCUORDER_N /***/LCUORDER_NF04 311
USER_COMMAND_D2000
1 MODULE (PAI) /***/SAPLCUORDER_N /***/LCUORDER_NI05 28
USER_COMMAND_2000
Chosen variables
Name
Val.
No. 4 Ty. FORM
Name SAVE_DESIGN
%_DUMMY$$
2222
0000
0000
0000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_DESIGN_MODE
R
5
2
0
0
CON_MODE_CREA
I
4
9
0
0
GT_NODE_CUI
Table[initial]
SY-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DESNUM_TMP_1
TM00000001CY
543333333345
4D0000000139
000000000000
000000000000
LV_DESNUM
222222222222
000000000000
000000000000
000000000000
SAVE_OKCODE
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
CON_ORDER
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DELETE
LVMS
4545222222222222222222222222222222222222222222222222222222222222222222
C6D3000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
No. 3 Ty. FORM
Name CHECK_AND_SAVE_F07
CL_GUI_ALV_GRID=>MC_MB_VIEW
&MB_VIEW
2445544522222222222222222222222222222222222222222222222222222222222222
6D2F695700000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
GT_OP
Table IT_303[2x1320]
PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
Table reference: 118
TABH+ 0(20) = 7039FC3C5824DB3C00000000760000002F010000
TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
TABH+ 40( 8) = 08000000C1308001
store = 0x7039FC3C
ext1 = 0x5824DB3C
shmId = 0 (0x00000000)
id = 118 (0x76000000)
label = 303 (0x2F010000)
fill = 2 (0x02000000)
leng = 1320 (0x28050000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000093
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x2010FC3C
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 234 (0xEA000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 8 (0x08000000)
lineAlloc = 8 (0x08000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x60B7153D
collHook = 0x00000000
ext2 = 0x1024DB3C
>>>>> 2nd level extension part <<<<<
tabhBack = 0xE00FFC3C
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
G_BADI_PROGRAM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LOG_ERROR
2
0
0
0
CON_BUTT_DELETED
@11QDelete@
43355466676422222222222222222222222222222222
011C145C545000000000000000000000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
G_CU_EXIT_CU_EXPLODE
F0000000
F0000000
/***/CUDESIGN-OBJNR
CY00000000000000008835
4533333333333333333333
3900000000000000008835
0000000000000000000000
0000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_SEC_COUNT
0
0000
0000
LV_UPD
X
5
8
0
0
%_SPACE
2
0
0
0
GS_ROW_NO
0.0.0.1.
0000
1000
0000
0000
SCREEN
/***/CUDESIGN-GLTRP
2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGID
00
33222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
SWO_%CONTAINER
000000000
2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
0
0
SY-MSGNO
341
333
341
000
000
/***/CVCUI-CUTYP
2
0
0
0
SY-MSGV1
MESSAGE_TYPE_X
44554445555455222222222222222222222222222222222222
D533175F4905F8000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
No. 2 Ty. FORM
Name USER_COMMAND_D2000
/***/CVCUI
0.0.0.0.0.0.0.1. 000000
2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_MODE_COPY
C
4
3
0
0
LT_BAPI_RETURN
Table IT_1778[2x1088]
PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
Table reference: 310
TABH+ 0(20) = 8837083D407E1C3D0000000036010000F2060000
TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
TABH+ 40( 8) = 08000000C1308101
store = 0x8837083D
ext1 = 0x407E1C3D
shmId = 0 (0x00000000)
id = 310 (0x36010000)
label = 1778 (0xF2060000)
fill = 2 (0x02000000)
leng = 1088 (0x40040000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000113
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x50C6073D
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 1534 (0xFE050000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 8 (0x08000000)
lineAlloc = 8 (0x08000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x6067033D
>>>>> 2nd level extension part <<<<<
tabhBack = 0xE82F063D
delta_head = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
pb_func = 0x00000000
pb_handle = 0x00000000
CON_MODE_ORDE
O
4
F
0
0
TGSBT
22222222222222222222222222222222222222
00000000000000000000000000000000000000
00000000000000000000000000000000000000
00000000000000000000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
LS_NUMBERS-AUFNR_NEW
000001000677
333333333333
000001000677
000000000000
000000000000
T024I
200UT10100PG for Term & Comp
33355333335426672567622246672222222222222222
20054101000706F20452D0603FD00000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
LS_T399X
200UT10UM01 X INST 30UT01UT01
3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CON_VBKZ_U
U
5
5
0
0
/***/CU_ORDER_IO-DISP_FACTOR
2097152
0
0
LS_DESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
/***/CUDESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_DROP_COUNT
0
0000
0000
LS_DESIGN-DESNUM
000050000109
333333333333
000050000109
000000000000
000000000000
No. 1 Ty. MODULE (PAI)
Name USER_COMMAND_2000
GT_SELTAB_INIT
Table[initial]
Internal notes
The termination was triggered in function "RfcExtendedReceive"
of the SAP kernel, in line 422 of the module
"//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
The internal operation just processed is "FUNC".
Internal mode was started at 20070827180011.
Status of connection:
RFC state: " "
RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
CPI-C error text: "The current application triggered a termination with a short
dump."
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=26488)
When : 8/27/2007 18:1:10.942
Threads : 2
Computer Name : MB1ES1005
User Name : ec6adm
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 10
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 5e10
eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:056d71f0=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:62bd5803=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess (ntstcdbg.c (501))
056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack (dptstack.c (1367))
056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2 (dptstack.c (352))
056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack (dptstack.c (182))
056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax (abrabax.c (1243))
056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message (abrfcrcv.c (422))
056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive (abrfcrcv.c (59))
056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get (abfunc.c (5103))
056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc (abfunc.c (554))
056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri (abextri.c (552))
056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent (abrunt1.c (281))
056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep (abdynpro.c (492))
056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal (dymainstp.c (2398))
056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0 (dymainstp.c (1004))
056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl (dymainstp.c (360))
056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00 (dymain.c (1628))
056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00 (thxxhead.c (4773))
056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop (thxxhead.c (4455))
056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart (thxxhead.c (1173))
056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain (dpxxdisp.c (1121))
056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main (thxxanf.c (82))
056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup (crtexe.c (395))
056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 61fc
eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:0799fec0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:64e9e4d3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc (signt.c (610))
0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/***/SAPLCUORDER_N
0
10.08.2007
10:12:44
541696
E
1
Typ
/***/CUDESIGN
0
10.08.2007
10:05:19
7168
2
Typ
/***/CU_ORDER_IO
0
10.08.2007
09:53:38
4096
3
Typ
/***/DESTYPE
0
10.08.2007
10:05:21
2048
4
Typ
/***/PRF_ORD
0
10.08.2007
10:05:21
4096
5
Prg
SAPMSSYD
0
04.04.2007
10:28:36
21504
E
6
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
7
Typ
/***/G_CUST
0
10.08.2007
09:53:39
3072
8
Prg
/***/SAPLTABLES
8
10.08.2007
10:13:00
19456
E
9
Typ
/***/G_CHAR
0
10.08.2007
10:05:21
3072
10
Prg
SAPLCTCE
10
09.09.2004
14:18:34
9216
E
11
Typ
CABN
0
18.09.2001
10:02:26
12288
12
Prg
SAPLICON
12
04.04.2007
10:10:28
27648
E
13
Prg
%_CICON
12
07.02.2006
10:40:00
104448
E
14
Typ
ICONT
0
04.04.2007
10:10:08
2048
15
Typ
NRIV
0
02.04.1998
08:14:54
3072
16
Prg
SAPLBSVA
16
04.04.2007
14:47:00
296960
E
17
Typ
/***/CU_ORDER_S_OP_N
0
10.08.2007
09:53:39
14336
18
Prg
CL_GUI_CONTROL================CP
18
28.02.2005
21:03:09
112640
E
19
Prg
%_CCNTL
18
18.02.2005
14:15:08
15360
E
20
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
21
Prg
CL_GUI_OBJECT=================CP
21
05.07.2005
13:10:15
375808
E
22
Prg
CL_GUI_CFW====================CP
22
28.02.2005
21:03:09
172032
E
23
Prg
CL_GUI_PROPS_CONSUMER=========CP
23
18.02.2005
14:15:08
30720
E
24
Prg
SAPLTHFB
24
04.04.2007
13:24:38
390144
E
25
Typ
EUDB
0
06.11.2003
20:28:08
8192
26
Prg
SAPLSFES
26
08.08.2007
16:46:17
259072
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Prg
SAPLSTTMYes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back. Suddenly it has started giving us this dump.
The code is as follows.
Commit design BAPI's
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
IF save_okcode = con_order.
Commit order BAPI's
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
DESTINATION 'NONE'.
Here con_order is CU01.
Please let me know if anybody has faced this problem earlier.
Thanks in Advance
Meghana -
RE: Short dump after activation of BADI
Hi all,
We are getting short dumps in all the transactions after activating the BADI 'BADI_LAYER'
We are not able to execute any of the transactions.
The details of runtimeerror
Runtime Errors RAISE_EXCEPTION
Date and Time 30.07.2007 09:58:06
Short text
Exception condition "SINGLE_EXIT_MULTIPLY_ACTIVE" 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_EXITHANDLER================CP" raised the
exception
condition "SINGLE_EXIT_MULTIPLY_ACTIVE".
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.
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:
"RAISE_EXCEPTION" " "
"CL_EXITHANDLER================CP" or "CL_EXITHANDLER================CM001"
"GET_INSTANCE"
or
"CL_EXITHANDLER================CP" "SINGLE_EXIT_MULTIPLY_ACTIVE"
or
"SAPMF05A " "SINGLE_EXIT_MULTIPLY_ACTIVE"
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... "sapdevp"
Network address...... "192.168.0.205"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x Intel 80686"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPDEVP"
Database type..... "ORACLE"
Database name..... "TDV"
Database user ID.. "SAPSR4"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 23:08:16"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10103_SHARE "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
Memory consumption
Roll.... 8176
EM...... 6271344
Heap.... 0
Page.... 57344
MM Used. 1728072
MM Free. 360856
User and Transaction
Client.............. 400
User................ "FIUSER01"
Language key........ "E"
Transaction......... "FB50 "
Program............. "CL_EXITHANDLER================CP"
Screen.............. "SAPMF05A 1010"
Screen line......... 7
Information on where terminated
Termination occurred in the ABAP program "CL_EXITHANDLER================CP" -
in "GET_INSTANCE".
The main program was "SAPMF05A ".
In the source code you have the termination point in line 145
of the (Include) program "CL_EXITHANDLER================CM001".
Source Code Extract
Line
SourceCde
115
SELECT SINGLE is_impl FROM badiisimpled INTO is_impl
116
WHERE badi_name = mig_badi_name.
117
IF sy-subrc NE 0.
118
not yet filled
119
is_impl = cl_enh_badi_tool_utilities=>update_badiisimpled( mig_badi_name ).
120
ENDIF.
121
122
IF is_impl = 'X'.
123
ok at least one implementation found
124
act_imp_existing = 'X'.
125
ENDIF.
126
127
ENDIF.
128
ENDIF.
129
ELSE.
130
131
check how many implementations exist for an exit
132
CALL METHOD cl_badi_flt_data_trans_and_db=>act_imps_per_flt_val
133
EXPORTING
134
runtime_call = seex_true
135
exit_name = exit_name
136
EXCEPTIONS
137
singular_exit_multiply_active = 1
138
no_active_implementation = 2
139
only_default_implementation = 3
140
OTHERS = 4.
141
CASE sy-subrc.
142
WHEN 0.
143
act_imp_existing = seex_true.
144
WHEN 1.
>>>>>
RAISE single_exit_multiply_active.
146
WHEN 2.
147
act_imp_existing = seex_false.
148
WHEN 3.
149
act_imp_existing = seex_false.
150
def_impl = seex_true.
151
WHEN 4.
152
RAISE data_incons_in_exit_managem.
153
ENDCASE.
154
155
new parameter considered for performance purposes
156
IF act_imp_existing = seex_true OR
157
def_impl = seex_true OR
158
null_instance_accepted = seex_false.
159
160
ok, then do your job
161
CREATE OBJECT exit TYPE (abs_type_classname).
162
CATCH SYSTEM-EXCEPTIONS move_cast_error = 1.
163
instance ?= exit.
164
ENDCATCH.
Contents of system fields
Name
Val.
SY-SUBRC
1
SY-INDEX
0
SY-TABIX
0
SY-DBCNT
2
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
FSKB
SY-UCOMM
SY-TITLE
Enter G/L Account Document: Company Code TJ01
SY-MSGTY
S
SY-MSGID
B!
SY-MSGNO
015
SY-MSGV1
00001140
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070730
SY-UZEIT
095806
SY-XPROG
SY-XFORM
Active Calls/Events
No. Ty. Program Include Line
Name
5 METHOD CL_EXITHANDLER================CP CL_EXITHANDLER================CM001 145
CL_EXITHANDLER=>GET_INSTANCE
4 METHOD CL_EXIT_MASTER================CP CL_EXIT_MASTER================CM004 2
CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
3 METHOD CL_EX_FI_HEADER_SUB_1300======CP CL_EX_FI_HEADER_SUB_1300======CM003 53
CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
2 FORM SAPMF05A MF05AF00_D0100_PRE_APPL_SUB_2 50
D0100_PRE_APPL_SUB_PBO
1 MODULE (PBO) SAPMF05A MF05AO00_D0100_PRE_APPL_SUB 10
D0100_PRE_APPL_SUB
Chosen variables
Name
Val.
No. 5 Ty. METHOD
Name CL_EXITHANDLER=>GET_INSTANCE
EXIT_NAME
BADI_LAYER
44445445452222222222
2149FC19520000000000
00000000000000000000
00000000000000000000
NULL_INSTANCE_ACCEPTED
2
0
0
0
ACT_IMP_EXISTING
2
0
0
0
INSTANCE
F0000000
F0000000
%_SPACE
2
0
0
0
RSJOBINFO
00000000000000 ##
2222222222222222222222222222222233333333333333222222222222222222222222222222222200
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000
%_DUMMY$$
2222
0000
0000
0000
SEEX_TRUE
X
5
8
0
0
SYST-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
<%_TABLE_BADIISIMPLED>
SY-REPID
CL_EXITHANDLER================CP
4454545444444533333333333333334522222222
3CF589481E4C52DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
SY-XPROG
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
No. 4 Ty. METHOD
Name CL_EXIT_MASTER=>CLASS_CONSTRUCTOR
%_SPACE
2
0
0
0
SYST-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SY-REPID
CL_EXIT_MASTER================CP
4454545544554533333333333333334522222222
3CF5894FD13452DDDDDDDDDDDDDDDD3000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CL_EXIT_MASTER=>LAYER_EXIT
F0000000
F0000000
%_DUMMY$$
2222
0000
0000
0000
No. 3 Ty. METHOD
Name CL_EX_FI_HEADER_SUB_1300=>IF_EX_FI_HEADER_SUB_1300~PUT_DATA_TO_SCREEN_PBO
IM_BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
IM_X_NO_INPUT
2
0
0
0
FLT_VAL
IN
44
9E
00
00
<EXIT_OBJ>-IMP_CLASS
<FLT_CACHE_LINE>-OBJ
|
| F0000000 |
| F0000000 |
| %_DUMMY$$ |
| |
| 2222 |
| 0000 |
| 0000 |
| 0000 |
| ME->INSTANCE_BADI_TABLE |
| Table[initial] |
| <EXIT_OBJ> |
| ??? |
| ?????? |
| ?????? |
| <%_L001> |
| ??? |
| ?????? |
| ?????? |
| RSJOBINFO |
| 00000000000000 ## |
| 2222222222222222222222222222222233333333333333222222222222222222222222222222222200 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000000000000000000000000000000000000000000000 |
| SY-REPID |
| CL_EX_FI_HEADER_SUB_1300======CP |
| 4454554454444455554533333333334522222222 |
| 3CF58F69F851452F352F1300DDDDDD3000000000 |
| 0000000000000000000000000000000000000000 |
| 0000000000000000000000000000000000000000 |
| <%_L001>-METHOD_NAME |
| ??? |
| ?????? |
| ?????? |
| EXIT_OBJ_TAB |
| Table[initial] |
| SY-SUBRC |
| 1 |
| 0000 |
| 1000 |
| ME |
|
F0000000
C0003000
SXRT_TRUE
X
5
8
0
0
No. 2 Ty. FORM
Name D0100_PRE_APPL_SUB_PBO
*BSEG-STBUK
2222
0000
0000
0000
%_DUMMY$$
2222
0000
0000
0000
SY-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
SYST-REPID
SAPMF05A
5454433422222222222222222222222222222222
310D605100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
KDBTAB-DMBTR
0.0.0.0.0.0.1.
0000000
000000C
%_SPACE
2
0
0
0
KDPTAB-BELNR
2222222222
0000000000
0000000000
0000000000
KDPTAB-GJAHR
0000
3333
0000
0000
0000
KDPTAB-BUZEI
000
333
000
000
000
KDBTAB-XRUND
2
0
0
0
SPACE
2
0
0
0
F05ACTRL
2
0
0
0
SYST
######################################ð#######################################~######### C####
00000000000000000000000000000000000000F0000000000000000000000000000000000000107000000050240000
000000200000000000002010100010000000000000000010400000000000000000000000000080E000200080030100
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000040000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000000000D000000C
BSED
0000000# ############## 0000000000000000
2222222222222222233333330200000000000000223333333333333333222222222222222222222222222222222222
00000000000000000000000000000C000000C000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000C0000000C000000C000000000000000000000000000000000000000000000000000000
SY-SUBRC
1
0000
1000
G_APPL_SUB_ACTIVE
X
5
8
0
0
CHAR_X
X
5
8
0
0
%_ARCHIVE
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
BKPF-BUKRS
TJ01
5433
4A01
0000
0000
BKPF
TJ01 2007SA00000000200707300400000000000000000000000000000000000000
2225433222222222233335433333333333333333333333333333333333333333333333333333333222222222222222
0004A01000000000020073100000000200707300400000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_APPL_SUB_DISABLE
2
0
0
0
T005-INTCA
IN
44
9E
00
00
No. 1 Ty. MODULE (PBO)
Name D0100_PRE_APPL_SUB
C_FIELD_DIALOG_ALL
BUTTON_DIALOG_ALL
4555445444444544422222222222222222222222222222222222222222222222222222222222222222222222222222
2544FEF491CF7F1CC00000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ab_jfune"
of the SAP kernel, in line 2561 of the module
"//bas/700_REL/src/krn/runt/abfunc.c#10".
The internal operation just processed is "FUNE".
Internal mode was started at 20070730095806.
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=4436)
When : 7/30/2007 9:58:6.359
Threads : 2
Computer Name : SAPDEVP
User Name : SAPServiceTDV
Number of Processors: 4
Processor Type: x86 Family 6 Model 15 Stepping 6
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 250c
eax=34d52300 ebx=000003f8 ecx=0001ccc0 edx=34d039e0 esi=000003f8 edi=00000000
eip=7c82ed54 esp=053fceb4 ebp=053fcf24 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:053fceb4=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:6627b4c7=00002100
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
053fcf24 77e6ba42 000003f8 0001d4c0 00000000 053fcf5c ntdll!KiFastSystemCallRet
053fcf38 0100b3aa 000003f8 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
053fcf5c 0055b4ac 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess
053fcf60 0055b4e5 7c38b5c8 7c38b5c8 7c38b5c8 01d35ab0 disp+work!NTStack
053fcf7c 0055b519 7c38b5c8 00000000 008536a8 7c38b5c8 disp+work!CTrcStack2
053fcf88 008536a8 7c38b5c8 00000000 005f0059 00300030 disp+work!CTrcStack
053fcfac 008569fa 6d1d037c 0000001b 00000000 01cfc168 disp+work!rabax_CStackSave [abrabax.c (6871)
053fd084 006aaaf4 0134837c 0134835c 00000a01 235f1640 disp+work!ab_rabax
053fd0c0 0067bb56 00000003 34cf5708 00000000 053fd128 disp+work!ab_jfune
053fd128 007af183 00000000 34cf5708 053fd274 34cf8c26 disp+work!ab_extri
053fd13c 00837a37 00000000 34cf7dd6 00596fa0 34cf68b4 disp+work!ab_xevent
053fd148 00596fa0 34cf68b4 000003db 34cf7dd6 00000000 disp+work!ab_dstep
053fd274 00597fa1 34cf5708 34cf5708 053ffd04 00597b13 disp+work!dynpmcal
053fd284 00597b13 34cf5708 34cf5708 00000003 053ffd04 disp+work!dynppbo0
053fd2a0 0056dcf1 34cf5708 0006e768 00000000 0000000c disp+work!dynprctl
053ffd04 00471848 00000013 07de0048 00000001 00494960 disp+work!dynpen00
053ffd14 00494960 0000000c 00000000 00000003 00000002 disp+work!Thdynpen00
053ffee0 00494ee2 00000001 00000000 00000000 00430000 disp+work!TskhLoop
053fff00 00421150 00000000 00000000 7ffd8000 053fff60 disp+work!ThStart
053fff14 00401080 00000003 003f6850 00000001 00000000 disp+work!DpMain
053fff60 011a94a0 00000003 003f6850 003f78f8 01bd5000 disp+work!nlsui_main
053fffc0 77e523e5 00000000 00000000 7ffd8000 88602680 disp+work!wmainCRTStartup
053ffff0 00000000 011a935d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 27bc
eax=00000001 ebx=00000103 ecx=fffffffe edx=003f01f8 esi=00000000 edi=00000000
eip=7c82ed54 esp=075dfec0 ebp=075dff04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:075dfec0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:6845e4d3=50004500
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
075dff04 010f7ffc 000006c0 00000000 00000000 003f77d0 ntdll!KiFastSystemCallRet
075dff84 7c349565 00000000 00000000 00000000 0587ff08 disp+work!SigIMsgFunc
075dffb8 77e6608b 0587ff08 00000000 00000000 0587ff08 MSVCR71!endthreadex
075dffec 00000000 7c3494f6 0587ff08 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMF05A
0
22.05.2007
11:37:49
1563648
E
1
Prg
SAPMSSYD
0
10.01.2007
12:33:28
21504
E
2
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
3
Typ
TFDIR
0
13.02.2005
17:31:57
3072
4
Prg
SAPLAPAR_EBPP_SERVICES
4
03.01.2007
11:23:55
114688
E
5
Typ
T042ZEBPP
0
08.01.2002
14:42:24
2048
6
Typ
T020
0
24.02.1999
03:17:19
3072
7
Typ
RFOPT2
0
11.12.2003
15:00:17
5120
8
Prg
SAPFF001
0
22.05.2007
11:37:49
195584
E
9
Typ
SWOTOBJID
0
04.05.1995
15:20:52
2048
10
Prg
SAPLSWOR
10
10.01.2007
12:33:34
292864
E
11
Typ
TFBUF
0
30.11.1998
22:08:34
3072
12
Typ
ACC_KONTEXT
0
08.01.2003
17:30:26
3072
13
Typ
BKPF
0
13.03.2006
11:01:29
18432
14
Prg
SAPLFACSCORE
14
01.12.2006
22:00:12
13312
E
15
Typ
T001
0
25.08.2005
22:03:13
13312
16
Prg
SAPLACHD
16
03.01.2007
11:23:55
51200
E
17
Prg
SAPFSPOR
0
09.09.2004
14:18:32
15360
E
18
Prg
SAPLSCNT
18
18.02.2005
14:16:06
30720
E
19
Typ
DYCBOX
0
20.08.1998
11:16:53
3072
20
Prg
SAPLSVSM
20
18.02.2005
14:16:06
27648
E
21
Prg
SAPLSGUI
21
10.01.2007
12:33:33
82944
E
22
Prg
SAPLSTTM
22
05.07.2005
13:10:18
69632
E
23
Prg
SAPLSBDC
23
05.07.2005
13:10:18
44032
E
24
Prg
CL_DATAPROVIDER===============CP
24
28.02.2005
21:00:46
49152
E
25
Prg
%_CCNTL
24
18.02.2005
14:15:08
15360
E
26
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
27
Prg
SAPLSTUP
27
08.03.2005
19:04:31
73728
E
28
Prg
SAPLCNDP
28
01.12.2006
22:04:33
193536
E
29
Prg
SAPSHDTV
18
05.01.2005
16:26:16
33792
E
30
Typ
SHDSTU
0
14.12.1998
23:15:34
2048
31
Typ
SHDSTCIU
0
14.12.1998
23:15:34
2048
32
Prg
SAPFGUICNTL
0
18.02.2005
14:15:08
24576
E
33
Prg
SAPLOLEA
33
05.07.2005
13:10:18
96256
E
34
Prg
SAPLSFES
34
10.01.2007
13:26:20
256000
E
35
Prg
SAPLSPLUGIN
35
09.09.2004
14:18:36
8192
E
36
Typ
ARFCRDATA
0
13.02.2005
18:20:24
7168
37
Prg
SAPLGRFC
37
13.02.2005
18:20:25
16384
E
38
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
39
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
40
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
41
Typ
ACGL_HEAD
0
11.12.2003
14:59:21
8192
42
Typ
RF05A
0
11.04.2005
11:50:21
38912
43
Typ
TCURC
0
01.12.1999
12:14:40
2048
44
Prg
SAPLFAGL_ACTIVATION_SERVICES
44
30.04.2007
17:00:55
45056
E
45
Prg
SAPLSTR9
45
09.05.2006
10:39:47
39936
E
46
Prg
CONTEXT_X_TR_SYS_PARAMS
45
09.05.2006
10:39:47
40960
E
47
Typ
TCONT
0
09.09.2004
14:18:43
2048
48
Typ
CONTEXTB
0
09.09.2004
14:15:52
6144
49
Typ
FAGL_ACTIVEC
0
19.08.2004
16:55:10
5120
50
Typ
FAGL_CHECK_SETUP
0
11.12.2003
15:01:05
2048
51
Prg
SAPLSHD0
51
03.01.2007
06:52:22
232448
E
52
Prg
SAPLBFFM3
52
10.01.2007
13:15:21
169984
E
53
Typ
OFIWA
0
15.04.1998
00:11:05
2048
54
Typ
FTEXTS
0
20.08.2001
12:13:26
3072
55
Prg
SAPLITSR
55
10.01.2007
14:23:52
107520
E
56
Typ
FMRFC
0
13.08.1997
12:32:59
2048
57
Typ
TBE01
0
20.01.2003
16:41:38
2048
58
Typ
TBE31
0
03.09.1997
03:01:11
2048
59
Typ
TBE31
0
03.09.1997
03:01:11
2048
60
Typ
TBE11
0
03.09.1997
03:01:06
2048
61
Prg
CONTEXT_X_SP_INFO
55Hello Sowmya
The BAdI BADI_LAYER is not defined for <b>Multiple-Use</b> (see checkbox on tabstrip <i>Attributes</i>).
Apparently you have created <i>several </i>implementation of this BAdI and activated <i>several </i>(at least 2) of these implementations.
If you inactivate all except a single implementation the BAdI (and all transactions using this BAdI) should work again.
Regards
Uwe -
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 -
In SMARTFORMS when openee a Text Node, Giving a Short Dump
Hi
I am getting Short Dump in SMARTFORMS Transaction, when ever I opened a Text Node and made some changes in it.
With out opening a Text Node I can able to change and activate the SmartForm.
But if I open a Text Node I can able to make changes in the Text Node but later if i click on any other Node, it is giving a Short Dump.
But all other systems in my office are working fine.
I have tried the Utilities->Settings-> and changed the editor also.
I have also Installed the SAPGUI once again for this Issue. But still I am getting the same problem.
Can anyone Please help me on this Issue.
I am sending the error enalysis of the Short Dump.
Error analysis
Short text of error message:
Control Framework : Error processing control
Long text of error message:
Diagnosis
An error occurred when the system tried to process the commands
from the Automation Queue on the presentation server.
There are several possible reasons for this:
- The installation of the SAP GUI on the presentation server is
faulty or obsolete.
- There is an error in the application program
- There is an error in the SAPGUI or an integrated control
Procedure
1. Make sure that you have imported the appropriate Support
Package, the current kernel, and GUI patch for the release of your
system
2. Check whether the error occurs locally on one or a few PCs, or
generally on all PCs. Note whether the error only occurs for some
users, for example because of a specific Customizing setting.
If it only occurs locally, this suggests an installation problem
with the PC. Check the installation; if necessary, reinstall the
software. In the dump, search for the SY-MSGLI field, since it may
point to the cause of the error.
3. Activate the Automation Trace (in accordance with SAP Note
158985).
4.Start the transaction and continue until the screen immediately
before the dump.
5. From the System -> Utilities menu, choose Autom. Queue,
Synchronous Processing.
The status bar of the GUI displays the text:
"Automation synchron flush mode on"
6. If you now proceed with the application, the short dump will
display the ABAP call that caused the error; the Automation Trace
will contain the error on the presentation server.
7. If necessary, load the short dump and trace files on to
sapservX, so that SAP can analyze them.
Technical information about the message:
Message class....... "CNDP"
Number.............. 006
Thanks in Advance.Hi
I think dump is because of SAP GUI. If you are ECC 6.0 then install SAP GUI 710 with patch level 2 or more and check
Regards
Shiva -
Short dump when expand info provide
Dear all,
I have 0GL_ACOOUNT info object that act as a master data.
the problem is when I want to expand at the info provider instantly create short dump
the overview of the short dump is :
Runtime Errors ASSERTION_FAILED
Date and Time 12.08.2009 10:08:16
Short text
The ASSERT condition was violated.
What happened?
In the running application program, the ASSERT statement recognized a
situation that should not have occurred.
The runtime error was triggered for one of these reasons:
- For the checkpoint group specified with the ASSERT statement, the
activation mode is set to "abort".
- Via a system variant, the activation mode is globally set to "abort"
for checkpoint groups in this system.
- The activation mode is set to "abort" on program level.
- The ASSERT statement is not assigned to any checkpoint group.
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.
Information on where terminated
Termination occurred in the ABAP program "CL_RSAWBN_OBJ_IOBJ_DATA=======CP" -
in "GET_TRFN_AWBSUBOBJ".
The main program was "RSAWBN_START ".
In the source code you have the termination point in line 23
of the (Include) program "CL_RSAWBN_OBJ_IOBJ_DATA=======CM005".
Source Code Extract
Line SourceCde
1 METHOD get_trfn_awbsubobj .
2
3 DATA: l_tranid TYPE rstranid,
4 l_s_source TYPE rstran_s_tlogo,
5 l_s_target TYPE rstran_s_tlogo,
6 l_objvers TYPE rsobjvers.
7
8 l_tranid = i_objnm.
9 l_objvers = rs_c_objvers.
10
11 * get the source and target for the tranid
12 WHILE l_s_source IS INITIAL OR l_s_target I
13 TRY.
14 cl_rstran_stat=>get_objects(
15 EXPORTING
16 i_tranid = l_tranid
17 i_objvers = l_objvers
18 IMPORTING
19 e_s_source = l_s_source
20 e_s_target = l_s_target
21 ).
22 CATCH cx_rstran_not_found .
>>>>> ASSERT sy-index < 2.
24 ENDTRY.
25 * for possible second run set objvers
26 l_objvers = rs_c_objvers-modified.
27 ENDWHILE.
29 * pass back the su
30 IF i_target = rs
31 re_awbsubobjec
32 ELSE.
33 re_awbsubobjec
34 ENDIF.
35
36 ENDMETHOD.
Please adviceHI,
I have read the sap notes and that is exactly what happen to me.
but I don't understand how to correct it.
It said :
This error cannot be corrected automatically. Use the method DELETE_VERSION_FROM_DB of the class CL_RSTRAN_STAT to delete the existing A version of the transformation manually in the target system.
Ensure that the transformation is permanently deleted from the database; therefore, you should verify that the correct transformation ID is specified (in the short dump, the TranID that is specified in the short dump is in the variable L_TRANID).
anybody know how to use delete_version_from_db ?
please advice
Maybe you are looking for
-
Create plug-in for Adobe with Visual Studio 2008
Hi to all, I'm Italian excuse for my english, I see Adobe SDK Help, but I don't see something for built a plug-in with Visual Studio 2008, I see only built with Visual Studio 2005! my asks is : Because ? Can I create a plug-in with Visual Studio 2008
-
Hi friends, I need to know / confirm dyanamic attributes manual evaluation process. 1. A purchaser creates a bid invitation with dynamic attribute for "text". Evaluation for this attribute is "Manual" 2. Bidder puts his comments against this attr
-
Query Drill Down without affecting the structure layout
Hi All, We have a query which has structure both in Rows & Columns . When we drilldown ( WAD ) the drilldown characteristics goes within the structure . What i want is even we drilldown the sturcture layout shoud not chnage . For example the struct
-
[solved] USB storage devices problem
Hello everyone. I have MSI Wind U270 and recently I've moved from Ubuntu 11.04 to Arch. I really like Arch so far but I have one quite big problem and I can't find any solution, so I hope someone here could help me. After I'd installed Arch, I tried
-
I am able to import .mpeg files into PP CS5. However, while my Source Monitor auto sizes the material correctly, the same material appears zoomed in on my Program Monitor. I have selected "Fit" as the Program Monitor size. How do I correct this?