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

Similar Messages

ABAP short dump after BI upgrade

hi all,
While executing any program in SE38, it is giving Short dump while same program executing in SA38, it is executing .
Firstly, we got short dump in TCode - RSRT, while executing report.
Regards,
Prasad
Edited by: Prasad Mahindrakar on Apr 14, 2010 8:15 AM

Kindly find the Error, which is generating at time of Report Execution
Error Analysis:
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
caught in
procedure "WRITE_DATA" "(METHOD)", nor was it propagated by a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
On account of a branch in the program
(CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
or a transaction call, another ABAP/4 program
is to be loaded, namely "GP42LSZTOVG57DGEB7BO763P3PN ".
However, program "GP42LSZTOVG57DGEB7BO763P3PN " does not exist in the library.
Possible reasons:
a) Wrong program name specified in an external PERFORM or
SUBMIT or, when defining a new transaction, a new
dialog module or a new function module.
b) Transport error

SEM-BCS Short Dump while executing Manual Posting Task

Hi SEM-BCS Colleagues,
I am having a peculiar problem with relation to the settings for Manual Postings. I have three scenarios for which I have defined manual document types and tasks 1) Standardizing Entry (Data Collection) 2) Manual Document in IU for adjustment 3) COI Group level manual postings. I am just creating and not changing any settings for document field properties also. I have configured monthly consolidation frequency and period category and I am posting document type 1 in Local Currency and 2 and 3 in Group Currency since they are after currency translation.
Have any of you faced similar problem and help me please?

Hello,
I am also getting short dump during data collection in BCS.
we recently upgraded the system to SP20. Is it anyway related to upgrade.
I also checked the MYSELF as a source system, but not found one.
Could you please let me know how you have solved this issue.
short dump:
Runtime Errors         PERFORM_TOO_MANY_PARAMETERS
Exception              CX_SY_DYN_CALL_PARAM_NOT_FOUND
Date and Time          04.12.2009 05:21:11
Short text
     Too many parameters specified with PERFORM.
What happened?
     In a subroutine call, there were more parameters than in the
     routine definition.
     Error in the ABAP Application Program
     The current ABAP program "SAPLRSDRI" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was
      not caught in
     procedure "RSDRI_CUBE_WRITE_PACKAGE_RFC" "(FUNCTION)", nor was it propagated by
      a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     A PERFORM was used to call the routine "CUBE_WRITE_PACKAGE" of the program
      "GPD1S8520HM8UV0U2XBDVPADF03".
     This routine contains 7 formal parameters, but the current call
     contains 10 actual parameters.

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 <b>Multiple-Use</b> (see checkbox on tabstrip <i>Attributes</i>).
Apparently you have created <i>several </i>implementation of this BAdI and activated <i>several </i>(at least 2) of these implementations.
If you inactivate all except a single implementation the BAdI (and all transactions using this BAdI) should work again.
Regards
Uwe

Short dump after AC_FLUSH_CALL

Hi all,
I'm using Netweaver 04 and I've developed a report that displays a dynpro containing a dynamic document and it auto-refreshes itself through the CL_GUI_TIMER class.
After a period of correct working the report crashes with a short dump about the wrong exit of AC_FLUSH_CALL function module (CL_GUI_CFW->FLUSH method). sy-subrc = 2.
Can you help me? Thanks in advance.
Angelo

My monitoring application accesses each second a DB table to check if its contents are changed and dispay a particular record on the dynpro.
FILL_HEADER is fixed and FILL_VALUES can change.
This is most of PBO code:
SET PF-STATUS 'STATUS1100'.
SET TITLEBAR 'TITLE1100'.
CLEAR flag.
IF first = 'X'.     " prima display
    CLEAR:   i_text, is_ma_data.
    REFRESH: i_text, is_ma_data.
    CREATE OBJECT head_cont
       EXPORTING container_name = top_screen.
    CREATE OBJECT values_cont
       EXPORTING container_name = values.
    CREATE OBJECT fill_header
      EXPORTING no_margins = 'X'.
    CREATE OBJECT fill_values
      EXPORTING no_margins = 'X'.
    CALL METHOD fill_header->initialize_document.
    PERFORM fill_field_names.
    CALL METHOD fill_header->merge_document.
    CALL METHOD fill_header->display_document
      EXPORTING
        parent             = head_cont
        container          = 'FILL_HEADER'
        reuse_control      = 'X'
        reuse_registration = 'X'.
    first = ' '.
ENDIF.
    CALL METHOD fill_values->initialize_document
      EXPORTING
        background_color = bg_color.
    PERFORM fill_field_values.
merge document
    CALL METHOD fill_values->merge_document.
    CALL METHOD fill_values->display_document
      EXPORTING
        parent             = values_cont
        container          = 'FILL_VALUES'
        reuse_control      = 'X'
        reuse_registration = 'X'.
ENDIF.
refresh
CREATE OBJECT gui_timer.
SET HANDLER event_handler->on_finished FOR gui_timer.
gui_timer->interval = timeout.
CALL METHOD gui_timer->run.
CALL METHOD cl_gui_cfw=>update_view.
Thanks.
Angelo

Dynamic sql is throwing dump after upgrade to EHP 7.0

Hi All,
My customer recently upgraded to EHP 7.0.
I have one query like below :
select * from (ls_table_list-tabname) into
                         table <table>
                         where (condition).
where ls_table-tabname is the table name, <table> is with the structure of same table and condition is very simple where condition. (id = 'XXXXX').
We are getting dump with "CX_SY_DYNAMIC_OSQL_SYNTAX" and the dump message is "
When parsing a dynamic statement, an error occurred.
Before upgrade same statements were working fine.
Please send us the response asap. Its urgent.
Thanks in advance,
Sreedhar

Hi Divyanshu,
Following is the text of Short dump :
Category ABAP Programming Error
Runtime error SAPSQL_PARSE_ERROR
Exception CX_SY_DYNAMIC_OSQL_SYNTAX
ABAP program / GETPF / SAPLTABLE_CONTENT_CHECK
Application component not assigned
Date and Time 07.02.2014 14:57:48
Short text
When parsing a dynamic statement, an error occurred.
What happened?
Error in ABAP application program.
The current ABAP program "/ GETPF / SAPLTABLE_CONTENT_CHECK" had to be canceled
be as it appears on
an instruction is encountered, which unfortunately can not be executed.
Error Analysis
There is an exception has occurred, which is discussed further below.
The exception, which is assigned to the class 'CX_SY_DYNAMIC_OSQL_SYNTAX'
was in the procedure "/ GETPF / TABLE_CONTENT_CHECK" "(FUNCTION)" neither
intercepted,
still propagated by a RAISING clause.
Since the caller of the procedure is not with the occurrence of the exception
could be expected, the running program was terminated.
Error was at below statement :
      SELECT * FROM (ls_table_list-tabname) INTO
TABLE <table>
WHERE (condition).

Short Dump for upgrade from 3.5 to 7.0

Hi All,
We have upgraded the BI system from 3.5 to 7.0 .
In the upgraded system , when i run the program RRINCLTAB_REBUILD , it throws the short dump as SAPSQL_WHERE_FOR_ALL_MISMATCH.
In the dump it says to check the field length and field type of LINKNO for the standard table and the internal table used in program.
Standard table - /BIC/KILIACG
Internal table - l_t_nodesid type standard table of RSDMHSITAB
I checked it , but unable to find any in-consistency there in two field definations.
Pls suggest the ways to resolve it.
Regards,
Sarang Kahu

Hi,
the error is not related to a standard table.
/BIC/KILIACG is the sid table of the hierarchy of infoobject ILIACG. I would recommend to check that infoobject in the target system and try to activate if it isn't active already. Otherwise, goto se14. for the that table and check the ddic object as well as the runtime object. Try to repair the table with se14. Then run the program again.
regards
Siggi

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

Short Dump while maintaining conditions in Product master

Hi Experts,
We are getting short dump while we want to maintain conditions in the product master.
The dump message is as follows -
CREATE DATA: The specified type "/1CN/WS_ID_300PRODUCTBBP_SKU_T" is no valid
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CREATE_DATA_ERROR', was not
caught in
procedure "/SAPCND/MNT_INIT_OW" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The dynamically specified type "/1CN/WS_ID_300PRODUCTBBP_SKU_T" at CREATE DATA
is no valid data type.
The type is either unknown or an object type.
I checked for OSS note but could not get success and also i could not explore in SDN. Can anybody help me in this.
Thanks a lot in advance!!
Thank You
Abhinandan

Hi
<b>Please go through the following SAP OSS Notes, which will definitely help -></b>
<u>Note 930816 - Cond. Maint. group not generated after remote client copy</u>
<u>Note 1051896 - Cond. group WS deleted in source aft. remote client copy</u>
Note 971825 - Short dump caused by dynamic working set
Note 969475 Short dump after applying notes 966127&966197
Note 661287 - Name of the condition maintenance group
Note 1009001 - ShortDump when Creating Mkt-Obj by Copying
Do let me know.
Regards
- Atul

Short dump in web dynpro

Hi All,
I am new to web dynpro.I developed one web dynpro apllication in my personal system.when i try to execute this web application it was going to short dump after entering into the logon pad.
Any other tcode is there to execute web applications, plz help me to overcome this short dump in web application.
Thanks in advance.
Thanks,
Ram

Hi,
If it is giving short dump then you please mention that dump. or you can go to st22 and get the details and do some modification. you can go to se 80 and make your application again and than try to execute it.
hope it will useful.
thanks
hemant ghiya

Short Dump in class ORDER_SAVE~CHANGE_BEFORE_UPDATE

I am geting a short dump after in the class ORDER_SAVE method CHANGE_BEFORE_UPDATE. This happens when I call the function module CRM_ORDER_SAVE. The dump error is "Too frequent recursive call of CRM_ORDER_SAVE_OW using actions".
The code at which the dump occurs is
if gv_recursive_save > 5.
message x041.
exit.
endif.
Can anyone help.
Thanks

Did you try debugging ( breakpoint at ORDER_SAVE).
check if this thread helps..
What is the difference between 'CRM_ORDER_SAVE' and 'CRM_ORDER_MAINTAIN'?
Thanks,
Sastry

Fetch Next Cursor Short Dumps

Hello All,
   I have the following code which short dumps after losing its cursor position.
OPEN CURSOR WITH HOLD dbcur FOR
      select * from ekpo where bukrs in s_bukrs2.
      do.
          FETCH NEXT CURSOR dbcur INTO table iekpo package size pkgsize.
          if sy-subrc <> 0.
             close cursor dbcur.
             exit.
          else.
              perform ouput_to_text_file.
              refresh: iekpo.
           endif.
      enddo.
I have millions of records to be extracted and simple select to an internal table causes memory problems. Thus I need to extract a chunk of records write them to a text file, then get the next chunk.
Any suggestions?
Thank you,
Jerry

GUI Download probably causes problem, writing to a dataset on app server might not cause the problem, maybe you want to try.
Regarding the select, here is some pseudo code outlining what I mean:
clear wa_ekpo.
do.
select * from ekpo into table lt_ekpo up to 10,000 rows
      where ebeln > wa_ekpo-ebeln or ( ebeln = wa_ekpo-ebeln and ebelp > wa_ekpo-ebelp )
      order by primary key.
if sy-subrc ne 0.
    exit.
endif.
download lt_ekpo (appending to existing file)
l_lines = lines( lt_ekpo ).
read table lt_ekpo into wa_ekpo index l_lines.
enddo.
Will run for a while, but should not dump out
Thomas

Unicode conversion after upgrade

I am well aware that sap recommends to convert to unicode first before converting to 2004s. however does anyone know what any consiequences would be of waiting to do it until after ther upgrade. Our landscape is very simple, we do not plan to immediately integrate new tools, and we don't have the abundance of code pages someone here mentioned (nor do we use foreign currencies). so with that said, are there any known consequences to simply doing the unicode conversion after upgrading from 3 to BI7?

> Let's take the system user table for example:
> (USER, NAME , SURNAME, ADDRESS).
>
> USER1 | שלום | עליכם | יקרים |
> USER2 | %%$% | אלי | #$$%#$ |
> USER3| #$%#$% | $##%$#%| $#%#$$%%#
I would say that those entries were not correctly specified in your vocabulary as being Hebrew - OR
Addresses have another speciality, they have a "creation language" field (LANGU_CREA). That field may be wrong filled if you e. g. create the user with an english logon and then change the user data to Hebrew (with Hebrew characters). The entry in the LANGU_CREA field however stays english. If you use that field now to decide the conversion of the addresse it will be converted wrong and you see gibberish.
Markus

Short Dump-Syntax error program"CL_RSD_MULTIPROV==CP" after EHP1SP5 upgrade

Hi,
MultiProvider Activation/Display data is resulting into short dump with following text
Error in the ABAP Application Program
The current ABAP program "CL_RSD_MULTIPROV_CHECK========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_RSD_MULTIPROV==============CP " in include
"CL_RSD_MULTIPROV==============CM010 " in
line 1:
"Method "CHECK_LINITFL" is not declared or inherited in class "CL_RSD_M"
"ULTIPROV". -"
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_RSD_MULTIPROV_CHECK========CP" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
We have recently upgraded to EHP1SP5. We noticed this issue just after that.
Regards,
PD

Hi,
Please check the note 1461401.
1461401 - System error in the program CL_RSD_MULTIPROV_CHECK
This note should help you.
Regards,
Rafael

Short dump in BP after upgrade to ECC 6.0

Hi,
We have upgraded system to ECC 6.0 from ECC 5.0
After upgrade system is giving short dump in transaction BP, event tried to navigate on BP screen.
Short dump description:
A RAISE statement in the program "CL_OS_TRANSACTION=============CP" raised the exception condition "OS_COMMIT_TOP_FAILED".
Since the exception was not intercepted by a superior program, processing was terminated.
Please advise to resolve this issue.
Regards,
Dipak

When exactly does this error appear? On save? clicking on a specific entry?
I suggest opening an OSS call for this problem, this doesn't seem to known (at least I didn't find any notes)
Markus

BCS Short Dumps after Upgrade (3.5 to BI7)

Similar Messages

Maybe you are looking for