Short Dump when activating the Workflow

Hi,
I have a problem, when i try to activate the workflow I get a short dump with the error "SYSTEM_NO_ROLL". As I understand the error is because there is no enough memory to the transaction, this is not the case i have checked that, so the error must be from my workflow definition or from the SAP it self.
Here goes the description:
The location of the error is in the method "FIND_ELEMENTS" of class "CL_SWF_CNT_CONTAINER". By this I understand that the error was with my container elements in the workflow but I have reviewed all my elements and I cant find any fault element or error. I can check the definition but if i try to activate it i get the short dump.
In the Calls Stack, there is +/- 69297 calls to the above method, because that method is recursive the transaction just consume all the memory and then i get short dump.
I use many multi line elements, for parallel processing with block step mostly, maybe its my container elements but i can find no wrong bindings or faulty elements.
Any help would be greatly appreciated.
Regards,
Diogo Silva.

Hi,
Ok didn't know, thanks for the help, i will post in the other section.
PS: Could you tell me how to reach that component, I tried but without success.
Regards,
Diogo Silva.
Edited by: DiogoSilva on Jun 15, 2011 7:01 PM

Similar Messages

Short dump during activating the BC Set in SCPR20 - "GETWA_NOT_ASSIGNED"

Hi experts,
We have upgraded from SRM 4 to 7.0.We are facing an issue when activating the BC Set in SCPR20. A short dump is occuring inside the program 'VIRSA/SAPLZVIR'. We got the solution that some correction instructions mentioned in the SAP Note 1095700 needs to be mplemented. The steps mentioned in the Note are,
1) Run transaction SE54 and click the button 'Edit Function Group'.
2) Next, enter the name of the function group /VIRSA/ZVR1.
3) Select the radio button option 'Re-generate group-specific programs',and press the 'Change' button.
4) In the following popup please mark only the option 'structure spec.data declaration renewal' and press enter.
We were able to proceed with the first two steps but stuck up during the execution of step3. When we selected the radio button u2018Re-generate group-specific programsu2019 and when clicked on the change button, we are getting a message like u2018the name space u2018/VIRSA/ZVR1u2019 does not exists. Because of this we are not able to proceed with the last step.
Kindly provide some ponters as of how to overcome this issue ..
Thanks in advance,
Dhan

Hi there,
To overcome this error you need to go to se06 and make the "/VIRSA/" namespace as Modifiable.
Also, you should have a look at the following note if my first suggestion doesn't work.
1041089 Tx SCPR20: GETWA_NOT_ASSIGNED dump during BC Set activation
Hope this helps.
Kind Regards,
Matthew

Short dump when executing the query

Hello Friends,
I have a query from MM area which I have insalled from Business Content , and when I try to go to the edit mode or try to excute the query I get a short dump which says "Missing elements ..", I get the same dump when executing from query designer or RSRT . At this time I'm not able to do a "check" on the query also n query designer since it doesnot allow me to go to the edit mode also . Any inputs greatly appreciated .
thanks ,

Hi,
While activating it from the Business Content, have you activated all the underlying objects also. Pls check that. It might help.

Short Dump When activating BI Objects

Hi Experts,
When i try to activate any object ie., InfoObject, InfoCube, etc. it is moving to short dump. Can anyone please help in this issue, why it is going to short dump.
Thanks & Regards
Ramakrishna Kmaurthy

Hi Ramakrishna,
Can you please be more precise? What is the type of shortdump?
Shortdumps do not directly have to be a basis issue.
Please post the "subject" and the "short description" from the shortdump (ST22) in this thread.
Regards,
Steven Groot

ASSERTION_FAILED, Short dump when activating Transformation in BI7.0

Hi All,
I have migrated 3.5 update rule to 7.0. And during transformation activation i am getting short dump giving following messges:
"ASSERTION_FAILED"
"CL_RSTRAN_GEN_STEP= = = = = CP"
"CL_RSTRAN_GEN_STEP= = = = = CM005"
"GET_CONTAINER"
My system support pack is 15. I searched many OSS Notes but i am not able to get the exact soln.
can anybody help me out with this problem?
Regards,
Harsh

this error is generally due to inconsistency in metadata
refer OSS note: 1071255, 1094266, 998730, 829353, 926854
Try to implement this solution from OSS 998730:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space' or 'S'
REF_RULE <> 'space'
If there are inconsistent entries in the RSTRANRULE table such as:
 TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space or GROUPTYPE 'S'
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Edited by: sam hennry on Feb 5, 2008 4:40 PM

Short Dump when writing the file to Unix.

ST22 Dump Log.
Short text Error when writing to the file "/appl/data/backlog/outbound/bop_bwfcstngall_erp
What happened? Resource bottleneck
The current program "ZPS_BACKLOG_NEW_READ" had to be terminated because
a capacity limit has been reached.
_Error analysis
An error occurred when writing to the file
"/appl/data/outbound/bop_bwfcstngall_erp_20110919_151220.dat".
Error text: "A file, file system or message queue is no longer available."
Error code: 52

ask your basis collegues, the dump says that the file system was not available, so it is clear that your writing to Unix could not happen.
have a look into OSS Note 1100926 - FAQ: Network performance

Short dump when opening the segment builder

After the upgrade from CRM 4.0 to 2007, we are no longer able to open the Segment Builder. We always get a short dump (Message_type_X). Anyone encountered this problem before and has a solution?
Thanx in advance!

Hi,
though it is true that in CRM 2007 the GUI transactions should not be used anymore I am able to start the segment builder directly via transactioin CRMD_MKTSEG. It is working without a shortdump.
For documentation I suppose you have to refer to SAP: Help or the documentation available under service.sap.com. The blog posted here might be an alternative as well.
cheers Carsten

Short dump when exporting the ALV grid report in to spread sheet

HI,
I am facing a problem when downloading ALV grid report in to spread sheet LIST>EXPORT>LOCAL FILE -->SPREADSHEET.
in shotdump the cursor shows : "assign cline+cbegin(clength) to <field_cont>."
In SAP internal table LIST,in the first record the value of the filed LENG is 0. when i have changed this value ex:10 etc it is coming properly.
Kindly help me
Nagendra

Is this a standard SAP report, or your own? Can you tell what your report does, if it is a custom ALV report?

Short Dump when trying to open C-project due to status

Hi,
We have a daily batch job in CRM that reports all the project ID's and
sends e-mails out to recipients.
As part of this report it retrieves the statuses for the project ID's,
however the report short dumps when retrieving the status for one of
the projects because it is not finding an active status.
When we try and open the project in C-projects we get the same short
dump error: CX_DPR_FATAL_ERROR so we cannot view or update the status.
When we investigate this issue we find that in table CRM_JCDS there are
3 entries for this project ID. One of the statuses is inactive (I1703)
but there is another status that is active (I1701). The two status
entries were created at exactly the same date and time and by the same
user.
In table CRM_JEST there is only one entry shown which shows an inactive
status and we believe this to be the wrong status. Please can you
advise if this status conflict is causing the problem and also how to
resolve this issue?

Hi Paul,
generally, the project and its elements must have an active status in table CRM_JEST, however, at this point it is not clear how this inconsistency arised. There is no SAP standard report or a 'generally valid' solution that could solve this issue, however, I found a customer message that you have opened in September with exactly the same problem. A colleague from the development team already provided you with a correction report, but there was no feedback from your side if it helped or not.
It is very difficult to provide help as inconsistencies can have several different causes, so the best would be to have this checked in a customer message with an example.
Regards,
Silvia

ASSERTION_FAILED short dump when Transporting Transformation from Dev to QA

Hi Experts,
I' am getting a short Dump when transporting the transformations, DSO & DTPs from Dev server to QA.
I got RC=12, Please have a look below....
Transport log...
    BCQ        System BCQ
               Selection for Import                     08.07.2010 15:28:59    (0) Successfully Completed
               Import                                   08.07.2010 15:35:14    (0) Successfully Completed
               Check Versions                           08.07.2010 15:35:14    (0) Successfully Completed
               Method Execution                         08.07.2010 15:36:20   (12) Canceled
               Import                                   08.07.2010 15:45:39    (0) Successfully Completed
               Check Versions                           08.07.2010 15:45:39    (0) Successfully Completed
               Method Execution                         08.07.2010 15:46:45   (12) Canceled
and the Log detalis.....
Date        Time      Message
08.07.2010 15:35:15 Job started
08.07.2010 15:35:15 Step 001 started (program RDDEXECL, variant , user ID DDIC)
08.07.2010 15:35:15 All DB buffers of application server sxcat136 were synchronized
08.07.2010 15:35:21 STDO: Log could not be written on output device T
08.07.2010 15:35:30 Replication completed successfully
08.07.2010 15:35:31 Struttura di comunicazione /BIC/CS8ZFIZIASA activated
08.07.2010 15:35:40 Regola(e) di trasm. 8ZFIZIASA_AA activated
08.07.2010 15:35:47 ABAP/4 processor: ASSERTION_FAILED
08.07.2010 15:35:47 Job cancelled
Even I've checked the entries on the table RSTRANRULE for those Transpormations but there I got...all the entries with...
RULEID = all numbers
GROUPID = '1' or '2'
GROUPTYPE = 'S' or 'T'
REF_RULE ='0'
we are in to SAP_BW Release 700, Level 0013, SP -SAPKW70013, SAP NetWeaver BI 7.0
Pls help if any one know's the solution for this.
Thanks in adv.
BR,
Ajay Kumar
Edited by: sap.ajaykumar on Jul 9, 2010 12:48 PM

Follow the steps mentioned in OSS note 998730.
FYI.. Solution:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space'
REF_RULE 'space'
If there are inconsistent entries in the RSTRANRULE table such as this:
TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Also check the OSS note: 1006658.
Follow the steps mentioned in OSS note 998730.
FYI.. Solution:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space'
REF_RULE 'space'
If there are inconsistent entries in the RSTRANRULE table such as this:
TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Also check the OSS note: 1006658.
Follow the steps mentioned in OSS note 998730.
FYI.. Solution:
Call transaction SE16 (Table Browser) and the 'RSTRANRULE' table with the following selection parameters:
GROUPID = 'space'
GROUPTYPE = 'space'
REF_RULE 'space'
If there are inconsistent entries in the RSTRANRULE table such as this:
TRANID *
OBJVERS *
RULEID *
SEQNR *
GROUPID 00
GROUPTYPE space
RULETYPE space
REF RULE *
Delete these entries from the table.
Activate the affected transformations.
Also check the OSS note: 1006658.
Also check the oSS note : Note 975675 - Transformation cannot be activated

DUMP when activating an Infsource or accesing the Scheduler

Friends,
I'm having a very annoing dump.
when activating an infosource (Transfer_Structure/Transfer_Rules), connected to a Business Content Datasource, there is a message telling me there is some warnings and that I should check the log.
¿what transaction do I use to check that log?
If I try activating the infosource once or twice, it finally shows activation OK message.
If I create an infopackage for that Infosource, a dump appears, and I can't even see the scheduler.
If the infosurce already have an infopackage, and I double clic on it, the same dump appears.
The dump Error Analysis shows
Short text of error message:
Data request to the OLTP ***
and
"RSM1_CHECK_FOR_DELTAUPD" (tips for notes searching)
I tryed deleting the infopackage (it is created, but you cannot see its scheduler), deleting the infosource assingment, and then recreating it, bu the problem remains the same.
Does anyone have an idea?
thanks in advance
Mauricio

Hi Christian,
thanks for the advice.
We are using BW 3.1 and CRM 4.0
I think note 424848 applies to my situation.
I think note 834249 doesn't apply, but we have 14 SP level, and they recommend using 21 level. This will remain as "Plan B".
I checked tables ROOSPRMSC and ROOSPRMSF in CRM, as the 424848 note says, and I found some entries for some of the datasources I need to fix.
The note says that I should not run the RSSM_OLTP_INIT_DELTA_UPDATE report if I find entries in this tables referencing the datasources I need to fix.
I also checked RSSDLINIT and RSSDLINITSEL tables in BW, and there are no discrepancies with CRM tables. does this mean that I can run the report?
What Should I do?
thanks again.
Mauricio

Short Dump when the Bex-Report scheduled for Broadcast

Hi Guru's
I am getting the short dump when I am scheduling the Bex-Report for Broadcasting. Need your help to reslove this issue.
Thanks
Navin
Note
The following error text was processed in the system BDV : The current application triggered a termination with a short dump.
The error occurred on the application server spdbwd01_BDV_05 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Form: INTERNAL_ERROR of program SAPLSDCL
Form: PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SDOK_PHIO_GET_CONTENT_ACCESS of program SAPLSDCI
Function: SKWF_PHIO_CONTENT_ACCESS_GET of program SAPLSKWF_CONTENT
Method: COPY_MIME_TO_FOLDER of program CL_RSRA_KWF_UTILITIES=========CP
Method: GET_STYLESHEET of program CL_RSRA_KWF_TMPL==============CP
Method: CONSTRUCTOR of program CL_RSRA_KWF_TMPL==============CP
Method: SET_TEMPLATE_FOLDER of program CL_RSRA_ENGINE_BC=============CP
Method: CONSTRUCTOR of program CL_RSRA_ENGINE_BC=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP

HI Navin,
Check the short dump analysis in T-code ST22.
and also check the Information Broadcast Settings / Configuration
Check the error for Emails in t-code SCOT. BASIS Consultants will help you on this issue.
Regards
Daya Sagar

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
55

Hello Sowmya
The BAdI BADI_LAYER is not defined for Multiple-Use (see checkbox on tabstrip Attributes).
Apparently you have created several implementation of this BAdI and activated several (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 1

Hai,
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

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 advice

HI,
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

Short Dump when activating the Workflow

Similar Messages

Maybe you are looking for