Short Dump ASSIGN_TYPE_CONFLICT in Virtual KF implementation

Hi
Iam getting a short dump in my virtual KF code. Here is the code that I have written. If I have only bill date it works fine. The minute I add company code it gives the short dump. Can you pls let me know what is it that Iam doing wrong. any help will be greatly useful. Thanks.
INCLUDE ZXRSRU02
DATA: L_S_CHANM TYPE RRKE_S_CHANM.
DATA: L_SUBRC1 TYPE SY-SUBRC. "execute only, if key figure really used
CASE I_S_RKB1D-INFOCUBE.
 WHEN '0SD_C03'.
 L_S_CHANM-CHANM = '0BILL_DATE'.
 L_S_CHANM-MODE = RRKE_C_MODE-READ.
 APPEND L_S_CHANM TO E_T_CHANM.
 L_S_CHANM-CHANM = '0COMP_CODE'.
 L_S_CHANM-MODE = RRKE_C_MODE-READ.
 APPEND L_S_CHANM TO E_T_CHANM.
 APPEND 'ZCOUNT1' TO E_T_KYFNM.
ENDCASE.
*Include ZXRSRTOP*
DATA : G_POS_0SD_C03_0BILL_DATE TYPE I.
DATA : G_POS_0SD_C03_0COMP_CODE(4).
DATA : G_POS_0SD_C03_ZCOUNT1 TYPE I.
Include ZXRSRZZZ
FORM USER_0SD_C03 USING I_S_RKB1D TYPE RSR_S_RKB1D
CHANGING C_S_DATA TYPE ANY.
DATA: l_zcount1 TYPE int4.
FIELD-SYMBOLS <L_0BILL_DATE>.
FIELD-SYMBOLS <L_0COMP_CODE>.
FIELD-SYMBOLS <L_ZCOUNT1>.
ASSIGN COMPONENT G_POS_0SD_C03_0BILL_DATE
OF STRUCTURE C_S_DATA TO <L_0BILL_DATE>.
ASSIGN COMPONENT G_POS_0SD_C03_0COMP_CODE
OF STRUCTURE C_S_DATA TO <L_0COMP_CODE>.
ASSIGN COMPONENT G_POS_0SD_C03_ZCOUNT1
OF STRUCTURE C_S_DATA TO <L_ZCOUNT1>.
IF <L_0COMP_CODE> = 'AB99'.
 CALL FUNCTION 'ZCALC_WDAYS_BETWEEN_DATES'
 EXPORTING
 P_DATE1 = <L_0BILL_DATE>
 P_DATE2 = SY-DATUM
 P_CAL_ID = 'Z1'
 IMPORTING
 P_DAYS = l_zcount1.
 <L_ZCOUNT1> = l_zcount1.
ELSEIF <L_0COMP_CODE> = 'DC99'.
 CALL FUNCTION 'ZCALC_WDAYS_BETWEEN_DATES'
 EXPORTING
 P_DATE1 = <L_0BILL_DATE>
 P_DATE2 = SY-DATUM
 P_CAL_ID = 'Z2'
 IMPORTING
 P_DAYS = l_zcount1.
 <L_ZCOUNT1> = l_zcount1.
ENDIF.
The short dump:
ASSIGN_TYPE_CONFLICT
"CL_IM_RSR_OLAP_BADI===========CP" or "CL_IM_RSR_OLAP_BADI===========CM002"
"IF_EX_RSR_OLAP_BADI~INITIALIZE"
get field postions for characteristics in structure
LOOP AT i_th_sfc ASSIGNING <l_s_sfc>
 WHERE user_exit NE rrke_c_mode-none.
field name in structure is keyreturnnm
name of the global variable
CONCATENATE '(SAPLXRSR)G_POS' i_s_rkb1d-infocube <l_s_sfc>-chanm
 INTO l_global_name
 SEPARATED BY '_'.
fill the global variable
UNASSIGN <l_global>.
>>>>>>>> ASSIGN (l_global_name) TO <l_global>.

My suggestion is that you review the how-to papers on SDN regarding exit RSR00002 or RSR_OLAP_BADI. These are alternative methods of accomplishing virtual characteristics and key figures. The code you have given is for exit RSR00002 (although it is full of syntax errors so is not executable), but the short dump you are getting refers to RSR_OLAP_BADI, so you must have implemented that Class as well, but incompletely.
Which method are you attempting to use?

Similar Messages

Short dump:ASSIGN_TYPE_CONFLICT- While loading data through DTP

Dear all:
We currently work with BI NW2004s SP10. We created transformation for mapping InfoSource and InfoCube based on 3.x transfer rule. For example, we used cube 0PUR_C04 and Data Source 2LIS_02_ITM_CP. And the transformation is "TRCS Z2LIS_02_ITM_CP -> CUBE 0PUR_C04". Everytime when we tried to load data via DTP. A runtime short dump occurred: ASSIGN_TYPE_CONFLICT
Error analysis:
You attempted to assign a field to a typed fie but the field does not have the required type.
we went back and forth to activated transformation and DTP. But still, same error occurred.
Any idea, please !!!!
BR
SzuFen

Hi Pavel:
Please refer to the following information-
User and Transaction
 Client.............. 888
 User................ "TW_S
 Language key........ "E"
 Transaction......... " "
 Program............. "GPD0
 Screen.............. "SAPM
 Screen line......... 6
===========================================================
Information on where terminated
 Termination occurred in the ABAP program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" - in
 "EXECUTE".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 704
 of the (Include) program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL".
 The program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" was started as a background job.
 Job Name....... "BIDTPR_284_1"
 Job Initiator.. "TW_SZU"
 Job Number..... 16454800
===========================================================
Short text
 Type conflict with ASSIGN in program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL".
===========================================================
Error analysis
 You attempted to assign a field to a typed field symbol,
 but the field does not have the required type.
===========================================================
Information on where terminated
 Termination occurred in the ABAP program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" - in
 "EXECUTE".
 The main program was "RSBATCH_EXECUTE_PROZESS ".
 In the source code you have the termination point in line 704
 of the (Include) program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL".
 The program "GPD0QBVJ2WFQZZXBD0IJ1DSZAEL" was started as a background job.
 Job Name....... "BIDTPR_284_1"
 Job Initiator.. "TW_SZU"
 Job Number..... 16454800
===========================================================
Line SourceCde
674 ELSE.
675 ASSIGN rdsTG_1->* to <_ys_TG_1>.
676 CLEAR <_ys_TG_1>.
677 MOVE-CORRESPONDING G1 TO <_ys_TG_1>.
678 <_ys_TG_1>-requid = l_requid.
679 l_recno_TG_1 = l_recno_TG_1 + 1.
680 ls_cross-insegid = 1.
681 ls_cross-inrecord = l_recno_SC_1.
682 ls_cross-outsegid = 1.
683 ls_cross-outrecord = l_recno_TG_1.
684
685 CALL METHOD i_r_log->add_cross_tab
686 EXPORTING
687 I_S_CROSSTAB = ls_cross.
688
689 ** Record# in target = sy-tabix - if sorting of table won't be changed
690 <_ys_TG_1>-record = l_recno_TG_1.
691 INSERT <_ys_TG_1> INTO TABLE <_yth_TG_1>.
692 IF sy-subrc <> 0.
693 CALL METHOD cl_rsbm_log_step=>raise_step_failed_callstack.
694 ENDIF.
695
696 ENDIF. "Read table
697 *
698 ENDIF.
699 CLEAR skipseg_all.
700 ENDLOOP.
701 * -
insert table into outbound segment -
702
703 <_yt_TG_1>[] = <_yth_TG_1>[].
>>>>>
705 rTG_1->insert_table( rdtTG_1_dp ).
706 ENDMETHOD. "execute
707
708
709
710 endclass. "lcl_transform IMPLEMENTATION
711
712 &----
713 *& Form get_runtime_ref
714 &----
715 * text
716 ----
717 * -->C_R_EXE text
718 ----
719 form get_runtime_ref
720 changing c_r_exe type ref to object.
721
722 data: l_r_exe type ref to lcl_transform.
723 create object l_r_exe.
===========================================================
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 3
SY-TABIX 0
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Process
SY-MSGTY E
SY-MSGID R7
SY-MSGNO 057
SY-MSGV1 0TOTDELTIME
SY-MSGV2 A
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20070420
SY-UZEIT 164557
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
===========================================================
Active Calls/Events
No. Ty. Program Include
 Name
 6 METHOD GPD0QBVJ2WFQZZXBD0IJ1DSZAEL GPD0QBVJ2WFQZZXBD0IJ1DSZAEL
 LCL_TRANSFORM=>EXECUTE
 5 METHOD CL_RSTRAN_TRFN_CMD============CP CL_RSTRAN_TRFN_CMD============CM005
 CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
 4 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00Q
 CL_RSBK_PROCESS=>PROCESS_REQUEST
 3 METHOD CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM002
 CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
 2 FUNCTION SAPLRSBATCH LRSBATCHU13
 RSBATCH_EXECUTE_PROCESS
 1 EVENT RSBATCH_EXECUTE_PROZESS RSBATCH_EXECUTE_PROZESS
 START-OF-SELECTION
===========================================================
Thank you and BR
SF

Dynnamic Field Symbol returning short dump ASSIGN_TYPE_CONFLICT

Hi everyone,
I have a RFC FM and make a dynamic access via SYMBOL FIELD, declared as ANY TABLE. The problem is that sometimes I can get a structure instead of a table and then the error occurs. How do I handle this error if the check IS ASSIGN not work? How do I capture and return an error message?
I tryed this:
FIELD-SYMBOLS: <fs_tabela> TYPE ANY TABLE.
 TRY.
 ASSIGN (st_b2b_text-tabname) TO <fs_tabela>. <<<<----
DUMP HERE!
 CATCH cx_root INTO v_erro.
 v_text = v_erro->get_text( ).
 MOVE v_text TO st_return-message.
 APPEND st_return TO t_return.
 PERFORM f_return_error_pi USING event.
 ENDTRY.
 IF <fs_tabela> IS ASSIGNED.
 CONCATENATE 'S' st_b2b_text-tabname INTO vl_wkarea.
 CONDENSE vl_wkarea NO-GAPS.
 ASSIGN (vl_wkarea) TO <fs_wkarea>.
 IF <fs_wkarea> IS ASSIGNED.
 LOOP AT <fs_tabela> ASSIGNING <fs_wkarea>.
 ASSIGN COMPONENT c_posnr
 OF STRUCTURE <fs_wkarea> TO <fs_posnr>.
Does anyone have any tips?
Tnks,
Marco Antonio
from Brazil

I solved with this test that I did:
TABLES: vbak.
TYPES: BEGIN OF ty_ctrlimo,
 equnr TYPE equnr,
 anln1 TYPE anln1,
 anln2 TYPE anln2,
 aufnr TYPE aufnr,
 bukrs TYPE bukrs,
 zanln1_andam TYPE anln1,
 zanln2_andam TYPE anln2,
 END OF ty_ctrlimo.
DATA: estrutura TYPE ty_ctrlimo,
 tabela TYPE STANDARD TABLE OF ty_ctrlimo
 INITIAL SIZE 0 WITH HEADER LINE,
 tabela2 TYPE TABLE OF ty_ctrlimo,
 variavel TYPE char30.
DATA: is_tabela.
Evento: START-OF-SELECTION ***
START-OF-SELECTION.
BREAK-POINT.
PERFORM f_check_is_tabela USING 'TABELA' CHANGING is_tabela.
WRITE: / '1 ', 'TABELA =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'TABELA2' CHANGING is_tabela.
WRITE: / '2 ', 'TABELA2 =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'ESTRUTURA' CHANGING is_tabela.
WRITE: / '3 ', 'ESTRUTURA =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'VARIAVEL' CHANGING is_tabela.
WRITE: / '4 ', 'VARIAVEL =', is_tabela.
SKIP 1.
PERFORM f_check_is_tabela USING 'VBAK' CHANGING is_tabela.
WRITE: / '5 ', 'VBAK =', is_tabela.
SKIP 1.
*& Form F_CHECK_IS_TABELA
FORM f_check_is_tabela USING value(p_nome_tabela_estrutura)
 CHANGING p_is_tabela.
FIELD-SYMBOLS <check> TYPE ANY.
DATA: lcls_strdscr TYPE REF TO cl_abap_structdescr,
 lcls_typdscr TYPE REF TO cl_abap_typedescr.
CLEAR: p_is_tabela.
ASSIGN (p_nome_tabela_estrutura) TO <check>.
lcls_typdscr ?= cl_abap_structdescr=>describe_by_data( <check> ).
IF lcls_typdscr->type_kind = cl_abap_structdescr=>typekind_table.
 p_is_tabela = cl_abap_structdescr=>true.
ENDIF.
WRITE: / 'tipo data: ', lcls_typdscr->type_kind.
ENDFORM. " F_CHECK_IS_TABELA

How to find which Badi Implementation is causing Short Dump

Hi Experts,
We are getting short dump on IW32 transaction when the users hit SAVE button.
The Dump Details:
Runtime Errors SYNTAX_ERROR
Short text
Syntax error in program "WORKORDER_UPDATE==============CP ".
What happened?
Error in the ABAP Application Program
The current ABAP program "CL_EX_WORKORDER_UPDATE========CP" had
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
"WORKORDER_UPDATE==============CP " in include
"WORKORDER_UPDATE==============CM000 " in
line 12:
"The specified type cannot be converted into the target variable
The current ABAP program "CL_EX_WORKORDER_UPDATE========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
Error analysis
The following syntax error was found in the program
WORKORDER_UPDATE==============CP :
"The specified type cannot be converted into the target variables."
Information on where terminated
Termination occurred in the ABAP program "CL_EX_WORKORDER_UPDATE========CP" -
in "IF_EX_WORKORDER_UPDATE~AT_SAVE".
The main program was "SAPLCOIH ".
After going through the dump analysis, I found that there are around 25 BADI Implementations got created on Enhancement Spot "WORKORDER_UPDATE".
How to find out which BADI Implementations is causing this dump?
Please let me know.
Thanks.
Edited by: ravi kumar on Feb 22, 2011 1:12 PM

Yes, I tried the Active Calls Stack also. The Short Dump is occuring exactly at the line :-
method IF_EX_WORKORDER_UPDATE~AT_SAVE.
in Class:-
CL_EX_WORKORDER_UPDATE
I was informedby the user that this is working perfectly fine in DEV System. The Short Dump is occuring in SBX System.
When I executed the Class "CL_EX_WORKORDER_UPDATE" and Method "IF_EX_WORKORDER_UPDATE~AT_SAVE" via SE24 in SBX, I got the same dump. However it worked fine in DEV System.
I am wondering if the issue is with the Standard Program itself?
Any ideas?
Thanks a lot again.
Another thing is: It is short dumping even before calling any of the BADI Implementations.
Wanted to give some more info on this: I put a break point in Function "CO_ZV_ORDER_POST" after the CALL FUNCTION 'CO_BADI_GET_BUSINESS_ADD_IN'.
And the program dumps right after that when it calls the: CALL METHOD lp_badi_if->at_save.
Thanks.
Edited by: ravi kumar on Feb 22, 2011 1:51 PM
Edited by: ravi kumar on Feb 22, 2011 2:11 PM

BCS Release Request Short dump

Hello,
I'm trying to release my costumizing request, that contains the SEM-BCS configuration, although i'm getting a short-dump.
The description is as follows:
Short text
 Access via 'NULL' object reference not possible.
What happened?
 Error in the ABAP Application Program
 The current ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
Error analysis
 You attempted to use a 'NULL' object reference (points to 'nothing')
 access a component (variable: " ").
 An object reference must point to an object (an instance of a class)
 before it can be used to access components.
 Either the reference was never set or it was set to 'NULL' using the
 CLEAR statement.
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:
 "OBJECTS_OBJREF_NOT_ASSIGNED" " "
 "CL_UG_MD_TR_METHOD_EXPORT=====CP" or "CL_UG_MD_TR_METHOD_EXPORT=====CM003"
 "UGMD_EXTRACT_SID_2"
Information on where terminated
 Termination occurred in the ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" -
 in "UGMD_EXTRACT_SID_2".
 The main program was "RDDM0001 ".
 In the source code you have the termination point in line 62
 of the (Include) program "CL_UG_MD_TR_METHOD_EXPORT=====CM003".
Source Code Extract
Line SourceCde
 32 FIELD-SYMBOLS <lt_table> TYPE INDEX TABLE.
 33 FIELD-SYMBOLS <ld_fsid> TYPE ug_sid.
 34 FIELD-SYMBOLS <ld_vsid> TYPE ug_sid.
 35 * FIELD-SYMBOLS <lt_target> TYPE ANY TABLE.
 36
 37 ASSIGN io_itab->rd_wa->* TO <ls_wa>.
 38 IF i_value_sid IS NOT INITIAL.
 39 ASSIGN COMPONENT i_value_sid
 40 OF STRUCTURE <ls_wa>
 41 TO <ld_vsid>.
 42 CHECK sy-subrc = 0.
 43 ELSE.
 44 CREATE DATA lr_sid.
 45 ASSIGN lr_sid->* TO <ld_vsid>.
 46 CLEAR <ld_vsid>.
 47 ENDIF.
 48
 49 IF NOT i_fieldname_sid IS INITIAL. "Start hah160603.1
 50 ASSIGN COMPONENT i_fieldname_sid
 51 OF STRUCTURE <ls_wa>
 52 TO <ld_fsid>.
 53 CHECK sy-subrc = 0.
 54 ELSE.
 55 CALL METHOD ugmd_get_fieldname_to_table
 56 EXPORTING
 57 i_tabname = i_datainfo-tabname
 58 IMPORTING
 59 e_fieldname = ld_fieldname.
 60 lo_fieldname = cl_ug_md_fieldname=>if_ug_md_fieldname~get_instance(
 61 ld_fieldname ).
 62 >>>>> ld_fieldname_sid_fix = lo_fieldname->ds_data-sid.
 63 ASSIGN ld_fieldname_sid_fix TO <ld_fsid>.
 64 ENDIF. "End hah160603.1
 65
Contents of system fields
Name Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 1
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY TDR_FULL
SY-UCOMM REFR
SY-TITLE Transport organizer: ordens
SY-MSGTY I
SY-MSGID FINB_TR
SY-MSGNO 009
SY-MSGV1 &
SY-MSGV2 &
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080904
SY-UZEIT 200112
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
If someone have gone trough a similar experience, or have any tip of how to solve this issue, i'd apreciate a comment.
Will award points for valuable help.
Thank you

Hi Ricardo,
You tried to transport the BCS' configuration, right?
If in the request was the full set of settings from the start of the project, the it will definitely fail.
There are some restrictions in BCS transport. See, for example the OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'. It particularly says:
"For the initial system setup, and after substantial changes in the data model, you should transport the Customizing by means of manually created transport requests. We advise you not to use the automatic recording of all Customizing settings during the first implementation phase in the development system and not to use this request for the structure of the test and productive systems.
During the transport of a new consolidation area, the following settings should be transported in the following sequence:
1. Data basis
2. Consolidation area
3. Special versions
After the import of the data basis and the consolidation area, these settings should be checked in the target system. In particular, the RFC destination, the InfoCubes and ODS objects, as well as the InfoObjects. Note that RFC destinations, InfoCubes, ODS objects, virtual cubes and InfoObjects cannot be transported from the consolidation workbench with the transport functions. For instance, you have to transport and activate the InfoCubes and InfoObjects using the BW."
I usually transport the BCS setting in a little transport requests in this order:
- all BW objects and settings
- data basis (with source DB)
- cons area
- special versions
- versions
- master data
...etc.
Hope this helps.

BPC 7.5 NW on BW 7.3 - Short Dump when using BADI

Hello all,
When migrating from MS bpc to Netweaver we've had to move some logic from script to BADI.
(Runlogic not supported)
However we now get shortdumps in when calling the BADI'
It works in BW 7.0 but now that we are on BW7.3 the error appears and shordumps occur.
During the upgrade SAP have updated the Class CL_UJR_WRITE_BACK to include a method "GET_DELTA"
That's where we have the problem. No OSS notes for it yet.
The problem shortsumps as follows:
Short Dump Log.
Category ABAP Programming Error
ABAP Program CL_UJR_WRITE_BACK=============CP
Application Component CPM-BPC
"ASSIGN_TYPE_CONFLICT" " "
"CL_UJR_WRITE_BACK=============CP" bzw.
"CL_UJR_WRITE_BACK=============CM00U"
"GET_DELTA"
Error occurs at line statement
ASSIGN COMPONENT uj00_cs_fieldname-keyfigure OF STRUCTURE <ls_data> TO <l_value>.
Any help out there?
Please.........
Thanks
Paul

Hi Paul,
First of all, there is a How To Guide for RUNLOGIC implementation. It uses BAdI approach as well, but doesn't call WRITE_BACK that can change from version to version.
Second, you should be able to see that method GET_DELTA is being called under
IF D_CALC_DELTA eq abap_true and df_bw_delta eq abap_false.
D_CALC_DELTA is set to TRUE only in Method WRITE_BACK_INT; I hope you aren't using that one.
DF_BW_DELTA is taken from DM Package parameters. Can you check what you have there or put just a break-point in PACKAGE_LOGIC_1 to see what value those 2 variables have?
Hope this helps,
Gersh

Tranformation activation throws short dump

Hi all,
I am on SP9 earlier when assinging formulas in transformations i used to get "ASSERTION_FAILED" error. I searched for oss note and installed the following notes (along with there prequisites) in the below order
971020
1008381
1011638.
Now on activation i get a syntax error.
Runtime Errors SYNTAX_ERROR
Date and Time 01/09/2007 13:47:19
Short text
Syntax error in program "CL_RSTRAN_GEN=================CP ".
 What happened?
Error in the ABAP Application Program
The current ABAP program "CL_RSTRAN_TRFN================CP" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program
 "CL_RSTRAN_GEN=================CP " in include
 "CL_RSTRAN_GEN=================CM00T " in
 line 54:
 "Field "I_NO_FREE" is unknown. It is neither in one of the specified ta"
 "bles nor defined by a "DATA" statement. "DATA" statement. "DATA" state"
 "ment."
The include has been created and last changed by:
 Created by: "BSHKSC "
 Last changed by: "SAP "

Hi Everyone,
We are on support package 9. I had the same assertion failed issues during imports. There were three key notes I wanted to implement, 1008381, 1011638, and 980549. These triggered the need for the rest to be implemented as well. Despite all those notes, we still have the short dump for the the syntax error with "I_NO_FREE" for CL_RSTRAN_GEN. I think there may be one or two other side effects as well since we are seeing other short dumps as well.
Thanks everyone. Craig
=========NOTES IMPLEMENTED===========
0000965972 Time-dependent master data - no data is read
0000976162 Currency trans/unit conversion: Target currency/unit initial
0000977225 Query on remote char terminates with ASSIGN_TYPE_CONFLICT
0000977926 Error BRAIN 070 occurs when filling a unit DataStore
0000979607 Runtime attribute: For example, source system is unavailable
0000980549 Endless D0/WHILE with inconsistent metadata
0000981806 RSUOM 065: No quantity conversion possible
0000983478 Request terminates with CX_SY_CONVERSION_ERROR
0000991119 RSM2 720 - Record (0) or segment (0001) unknown
0000995479 Breakpoints in der Simulation der Transformation
0001007327 RSTRAN 302 Exception .. aufgetreten DatenSatz geskipped
0001007765 Syntaxfehler bei Aktivierung einer Transformation
0001008381 Syntax error although the formula or routine is correct
and...
0001011638, 0000930495, 0000965507, 0000968517, 0000973258, 0000984890,
0000986199

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

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

Hi 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

Not enough memory short dump

I am investigating a performance problem with a SAP standard report. It falls over when trying to sort a table, the table size is [194994x294]. In know this is large but is it common for it to cause a EXSORT_NOT_ENOUGH_MEMORY short dump?

Hi,
Go to my computer and right click on it....
and go to properties.....
then go to advanced tab...
in it go to performance settings...
then go to advanced tab
in that go to virtual memory....in it click on change...
in change click on the radio button 'system managed size'
click on set and save it...
it might help you...
Regards
Debarshi

BCS Short Dumps after Upgrade (3.5 to BI7)

Hi SDN,
We have recently upgraded our dev system from BW3.5 to BW 7 (SEM BW 6) and following the upgrade none of the queries based on the BCS virtual info provider(Remote Cube) ZVBCS01 are working or the listcube transaction on cube ZVBCS01 in RSA1.
Both the queries and listcube short dump with DATREF_NOT_ASSIGNED (Details "DATREF_NOT_ASSIGNED" "SAPLUCR0" "LUCR0U08" "PROVIDE_SEM_DATA_TABLE_3")
We have raised a call with SAP OSS they recommended to activate the InfoObject 0BCS_REPMOD from business content and regenerate the data basis. We did all this but still experience the short dumps. (We havenu2019t assigned 0BCS_REPMOD to any Infoproviders or the data basis)
We will be unable to upgrade to BI7 unless we can resolve this issue so any help would be appreciated.
Kind regards,
Jamie Flaxman

Thanks for the responses, we have managed to get BCS working now following the upgrade.
Following the activation of the business content, I had to regen the Data Basis but the way I did it originally wasnu2019t enough to force a regeneration. So I had to make a small change to the data basis (move of field names and back again) which was enough to do the re-gen.
We have experienced quite a few issues with the upgrade from SEM 4 to 6.
Thanks for the help.
Jamie Flaxman

How to avoid short dump in ECC 5.0

Hi
Can anyone tell me how to avoid short dump in ECC 5.0
I'm told we can avoid program going to short dump, instead IT WILL GRACEFULLY EXIT..

Hi
By implementing the code as for every unsuccess/failure conditions control has come out of the program. then only u can avoid dumps even though u code the not perfect functionality.
Regards,
kumar

Short Dump While Changing Non-KeyField of Sorted Table

Hello,
A short dump occurs while trying to change a field of a sorted table item passed as CHANGING parameter. Are non-key fields in a sorted structure protected? The error message does not explicitely say so. Can anyone link to documentation explaining this behavior?
best regards,
JNN

You are passing by reference with CHANGING.
It looks like read-only stuff can't be passed to method CHANGING.
When I pass a literal or constant, there is a syntax error.
System could have given you a syntax error instead of dump.
Have a look at this snippet. Both method calls throw syntax error.
CLASS mainclass DEFINITION.
PUBLIC SECTION.
    CLASS-METHODS main.
PRIVATE SECTION.
    CLASS-METHODS passref CHANGING cv_test TYPE i.
ENDCLASS.                    "mainclass DEFINITION
CLASS mainclass IMPLEMENTATION.
METHOD main.
    "pass literal by ref
    passref(
      CHANGING
        cv_test = '2'
    "pass constant by ref
    CONSTANTS lc_test TYPE i VALUE 1.
    passref(
      CHANGING
        cv_test = lc_test
ENDMETHOD.                    "main
METHOD passref.
    "nothing
ENDMETHOD.                    "passref
ENDCLASS.                    "mainclass IMPLEMENTATION
START-OF-SELECTION.
mainclass=>main( ).

Short Dump While Accessing RSA1 in BI7.0 with SP 21

Hi,
The following short dump occurs, while Accessing RSA1 in BI7.0
Runtime Errors SYNTAX_ERROR
Date and Time 26.10.2010 10:19:35
Short text
 Syntax error in program "CL_RSTRAN_STAT================CP ".
What happened?
 Error in the ABAP Application Program
 The current ABAP program "CL_RSAWBN_OBJ_TRFN============CP" had to be
 terminated because it has
 come across a statement that unfortunately cannot be executed.
 The following syntax error occurred in program
 "CL_RSTRAN_STAT================CP " in include
 "CL_RSTRAN_STAT================CM00X " in
 line 34:
 "Der formale Parameter "E_TLOGO_MASK" existiert nicht."
 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_RSAWBN_OBJ_TRFN============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 "CL_RSTRAN_STAT================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
 CL_RSTRAN_STAT================CP :
 "Der formale Parameter "E_TLOGO_MASK" existiert nicht."
i.e parameter E_TLOGO_MASK is not existing.
I have gone through below old thread, but its for old SP
Runtime Error SYNTAX_ERROR while accessing the T-code RSA1
In our case, I guess it refers to our patch level as this SAP Note is referring to support package 17,
but we have implemented support package 21.
Please help <REMOVED_BY_MODERATOR> as this is blocking our next level in BI upgrade process.
Thanks in advance.
Regards,
Manikandan Dhanakoti
Edited by: Manikandan.D on Oct 29, 2010 8:37 AM
Edited by: Pravender on Nov 1, 2010 12:30 PM

See if below threat is any help.
Runtime Error SYNTAX_ERROR while accessing the T-code RSA1

How to keep short dumps for a longer time

Hi All,
I need to write a program to fetch all the below mentioned fields from the system dump tables and insert into a user defind table. Please help me with the code. Thanks in advance....
PROBLEM DESCRIPTION
ABAP runtime errors (also known as short-dumps) are kept in the system only for two days, mainly because every short-dump can use a lot of disk space depending on short-dump type. Problem is that this reduced time frame (two days) is not allowing us to focus in solve the more frequent ones and we do not have any statistic about:
    how many are we getting
    how often
    repetitive ones
PROPOSED SOLUTION
We need a program to be executed in a daily job right after midnight which will take the basic information of all todays short-dumps and store it in a custom table.
Information to be kept:
      DATE
      TIME
      HOST
      USER
      SYSTEM
      CLIENT
      ERROR ID
      TRANSACTION
      PROGRAM NAME
      PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
      PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
      SCREEN
      SCREEN LINE
      MAIN PROGRAM NAME
      MAIN PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)
      MAIN PROGRAM NAME VERSION TIMESTAMP (transported to PPx)
      PROGRAM LINE NUMBER AT TERMINATION
      SAP RELEASE
      SAP KERNEL
      PATCH LEVEL
      DATABASE VERSION
The program must have archiving capabilities implemented. In the month end run it will also perform the table house-keeping accordingly with a parameter like this:
     ERROR-ID
     MONTHS TO KEEP
We need to have the possibility of defining different retention periods for different kind of errors, for example our friend GETWA_TOO_MANY_SEGMENT could be stored for a year and a simple CONVT_NO_NUMBER only for a month. One of the parameters should be the default one, something like
        ERROR-ID **************
        MONTHS TO KEEP 01.

Aruna,
Following may be the action points for your requirements.
1. Create Custom table with all fields you required.
2. Create ABAP program to extract the data from SAP standard table where runtime error information is stored.
Like: select * from snap_beg into wa_snap_beg
          where seqno = '000'
          and   datum in s_datum
          and   uzeit in s_uzeit
          and   ahost in s_ahost
          and   uname in s_uname
          and   mandt in s_mandt.......
So SNAP_BEG is a table where you can find dump information.
After extracting the data from this table insert it into a Custom table which you have created in Step 1.
Use INSERT statement for this.
3. Create transaction for this report.
4. Schedule this program every day so that you will get all data into custom table.
I hope this will help you.
Regards,
Amey

Short Dump ASSIGN_TYPE_CONFLICT in Virtual KF implementation

Similar Messages

Maybe you are looking for