ABAP Runtime error on FB50 or FB60 after supplying SAP Support Packs

After applying the latest SAP Financial support stacks and OSS Notes we get the following:
Too many parameters specified with PERFORM.
In a subroutine call, there were more parameters than in the routine definition.
Error in ABAP application program.
The current ABAP program "SAPLGLIN" had to be terminated because one of the statements could not be executed.
This is probably due to an error in the ABAP program.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class
'CX_SY_DYN_CALL_PARAM_NOT_FOUND', was neither
caught nor passed along using a RAISING clause, in the procedure "G_RWIN_CHECK"
"(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
A PERFORM was used to call the routine "G_RWIN_CHECK" of the program
"SAPLGLIN".
This routine contains exactly 3 formal parameters, but the current
call contains 4 actual parameters.
parameters.
We have suspended testing for this reason. Please help.
Thanks,
Barbara

hi barbara
not sure if this is the right forum for this post and you may not get replies
you could try the financials forum
SAP ERP Financials
or the ABAP and Basis forums which you can find from the list in /community [original link is broken]

Similar Messages

ABAP Runtime Error while executing planning folder

Hi experts.
We have a situation where I can access our planning folders but that's not the case for one of our user. She encountered with an ABAP Runtime Error as follow:
Appreciate if anyone can help me out with this.
Runtime Error RAISE_EXCEPTION
Date and Time 20.04.2007 16:50:23
ShrtText
Exception condition "X_MESSAGE" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
is especially useful if you want to keep a particular message.
Error analysis
A RAISE statement in the program "SAPLRSSBR" raised the exception
condition "X_MESSAGE".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
Cancel
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
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"RAISE_EXCEPTION" C
"SAPLRSSBR" or "LRSSBRU03"
"RSSB_AUTHORITY_IOBJVL_CHECK"
or
"SAPLRSSBR" "X_MESSAGE"
or
"UPB_PM_CUST_START " "X_MESSAGE"
If you cannot solve the problem yourself and you wish to send
an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
To obtain this, select in the current display "System->List->
Save->Local File (unconverted)".
2. A suitable printout of the system log
To obtain this, call the system log through transaction SM21.
Limit the time interval to 10 minutes before and 5 minutes
after the short dump. In the display, then select the function
"System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, select the Editor function "Further Utilities->
Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "640"
Application server....... "S53KJ165"
Network address.......... "10.1.53.165"
Operating system......... "AIX"
Release.................. "5.3"
Hardware type............ "00C3A11F4C00"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "S53KJ170"
Database type............ "ORACLE"
Database name............ "BWP"
Database owner........... "SAPBWP"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
Created on............... "Oct 29 2006 20:42:11"
Created in............... "AIX 1 5 00538A4A4C00"
Database version......... "OCI_920 "
Patch level.............. "155"
Patch text............... " "
Supported environment....
Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
10.2.0.."
SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16128
EM....................... 16759712
Heap..................... 0
Page..................... 57344
MM Used.................. 10079624
MM Free.................. 2487240
SAP Release.............. "640"
User and Transaction
Client.............. 350
User................ "S51643"
Language key........ "E"
Transaction......... "UPSPL "
Program............. "SAPLRSSBR"
Screen.............. "SAPLUPB_PM_ALV 1000"
Screen line......... 2
Information on where terminated
The termination occurred in the ABAP program "SAPLRSSBR" in
"RSSB_AUTHORITY_IOBJVL_CHECK".
The main program was "UPB_PM_CUST_START ".
The termination occurred in line 416 of the source code of the (Include)
program "LRSSBRU03"
of the source code of program "LRSSBRU03" (when calling the editor 4160).
Source Code Extract
Line
SourceCde
386
l_s_range-low = l_activity.
387
APPEND l_s_range TO l_sx_auth_check_detail-range.
388
INSERT l_sx_auth_check_detail INTO TABLE <l_sx_auth_check>-auth_check_detail.
389
390
CALL FUNCTION 'RSSB_AUTHORITY_IOBJVL_REDUCED'
391
EXPORTING
392
i_infocube = g_sx_iobjvl_check-infocube
393
i_uname = l_uname
394
i_th_hierarchy = g_sx_iobjvl_check-hierarchy
395
i_message = i_message
396
i_activity_force_check = i_activity_force_check
397
CHANGING
398
c_tsx_auth_check_detail = <l_sx_auth_check>-auth_check_detail
399
c_tx_no_auth = l_tx_no_auth
400
c_ts_auth_tlevel = e_ts_auth_tlevel
401
EXCEPTIONS
402
user_not_authorized = 1
403
auth_check_failure = 2
404
auth_check_error = 3
405
inherited_error = 4
406
x_message = 5.
407
IF sy-subrc = 0.
408
REFRESH l_tx_no_auth.
409
CR 20050826 HW873685 SP29 Part 2/3 begin
410
SY-SUBRC = 2 means Auth-Obj missing in users profiles, we need this later
411
ELSEIF sy-subrc = 2.
412
ao_missing = rs_c_true.
413
e_subrc = 2.
414
CR 20050826 HW873685 SP29 Part 2/3 end
415
ELSEIF sy-subrc = 5.
>>>>>
RAISE x_message.
417
ELSE.
418
e_subrc = 2.
419
ENDIF.
420
421
correct the kid now
422
LOOP AT l_tx_no_auth INTO l_sx_no_auth.
423
l_sx_no_auth-kid = <l_sx_auth_check>-kid.
424
APPEND l_sx_no_auth TO e_tx_no_auth.
425
ENDLOOP.
426
427
ENDLOOP.
428
429
End LOOP: Check all SUBNR (FEMS)
430
431
432
CR 20050826 HW873685 SP29 Part 3/3 begin
433
If an Auth-Obj. is missing, no SUBNR can be authorized. Due to OLAP-logic
434
this means empty no_auth table
435
IF ao_missing = rs_c_true.
Contents of system fields
Name
Val.
SY-SUBRC
5
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
0
SY-FDPOS
1
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
210
SY-UCOMM
SELECT
SY-TITLE
Execute All Cost Element
SY-MSGTY
E
SY-MSGID
R7
SY-MSGNO
057
SY-MSGV1
0CO_AREA
SY-MSGV2
A
SY-MSGV3
SY-MSGV4
Active Calls/Events
No. Ty. Program Include Line
Name
40 FUNCTION SAPLRSSBR LRSSBRU03 416
RSSB_AUTHORITY_IOBJVL_CHECK
39 FORM SAPLRSDRC LRSDRCF15 113
AUTHORITY_CHECK
38 FORM SAPLRSDRC LRSDRCF27 57
BASIC_QUERY_DATA_GET_ROLAP
37 FUNCTION SAPLRSDRC LRSDRCU05 44
RSDRC_BASIC_QUERY_DATA_GET
36 FUNCTION SAPLRSDRC LRSDRCU15 189
RSDRC_BASIC_CUBE_DATA_GET
35 FORM SAPLRSDRC LRSDRCF25 373
DATA_GET
34 FUNCTION SAPLRSDRC LRSDRCU02 249
RSDRC_CUBE_DATA_GET
33 FUNCTION SAPLRSDRI LRSDRIU01 352
RSDRI_INFOPROV_READ
32 FORM /1SEM/UPCBW_350TMWPA01 UPC_BWINTERFC__FIX 174
DATA_READ
31 FUNCTION SAPLUPCBW LUPCBWU06 56
UPC_BW_DATA_READ
30 FUNCTION SAPLUPC1 LUPC1U06 67
UPC_DATA_READ
29 METHOD /1SEM/CL_DATA_350TMWPA01======CP UPC_DATA_READ_DB 25
/1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA_INTERNAL~READ_DB
28 METHOD /1SEM/CL_BUFFER_350TMWPA01====CP UPC_BUFFER_GET 167
/1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~GET
27 METHOD /1SEM/CL_BUFFER_350TMWPA01====CP UPC_BUFFER_READ 5
/1SEM/CL_BUFFER_350TMWPA01=>IF_SEM_BUFFER~READ
26 METHOD /1SEM/CL_DATA_350TMWPA01======CP UPC_DATA_READ 46
/1SEM/CL_DATA_350TMWPA01=>IF_SEM_DATA~READ
25 FORM 45AJEHYBGH37F61DTX80Q9ZFP UPP_PLAN 395
READ_TRANSACTION_DATA
24 FORM 45AJEHYBGH37F61DTX80Q9ZFP UPP_PLAN 561
GET_DATA
23 FORM 45AJEHYBGH37F61DTX80Q9ZFP UPP_PLAN 800
EC500_SELECT_DATABASE
22 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 575
SELECT_DATABASE
21 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 464
SELECT_AND_FIND_HEADER_COMBI
20 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 217
LOGICAL_SCREEN_FILL_HEADER
19 FORM SAPLUPP_PP_KERNEL LUPP_PP_KERNELF97 60
LOGICAL_SCREEN_FILL
18 FUNCTION SAPLUPP_PP_KERNEL LUPP_PP_KERNELU01 114
UPP_PP_KERNEL_CONSTRUCTOR
17 METHOD CL_UPB_PL_ALV=================CP CL_UPB_PL_ALV=================CM01E 176
CL_UPB_PL_ALV=>CONSTRUCTOR
16 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 623
OUTPUT_CREATE
15 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 202
OUTPUT_INIT
14 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 1062
OUTPUT_PROCESS
13 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF01 1225
OUTPUT_SWITCH_TO_LAYOUT
12 FORM SAPLUPB_PM_ALV LUPB_PM_ALVF05 748
INIT_CONTROLS
11 MODULE (PBO) SAPLUPB_PM_ALV LUPB_PM_ALVO01 13
STATUS
10 FUNCTION SAPLUPB_PM_ALV LUPB_PM_ALVU01 24
UPB_PM_ALV_START
9 METHOD CL_UPB_PM_APPLC===============CP CL_UPB_PM_APPLC===============CM00A 88
CL_UPB_PM_APPLC=>EXECUTE_PM
8 METHOD CL_UPB_PM_ADMIN===============CP CL_UPB_PM_ADMIN===============CM00L 76
CL_UPB_PM_ADMIN=>PAI_ONE_NODE
7 METHOD CL_UPB_PM_ADMIN===============CP CL_UPB_PM_ADMIN===============CM00L 23
CL_UPB_PM_ADMIN=>PAI_ONE_NODE
6 METHOD CL_UPB_PM_ADMIN===============CP CL_UPB_PM_ADMIN===============CM003 121
CL_UPB_PM_ADMIN=>PAI
5 FORM SAPLUPB_PM LUPB_PMF04 80
USER_COMMAND_0210
4 MODULE (PAI) SAPLUPB_PM LUPB_PMI04 11
USER_COMMAND_0210
3 FUNCTION SAPLUPB_PM LUPB_PMU22 86
UPB_PM_MAIN
2 FORM UPB_PM_CUST_START UPB_PM_START_ADMIN 251
PM_START
1 EVENT UPB_PM_CUST_START UPB_PM_START_ADMIN 14
START-OF-SELECTION
Chosen variables
Name
Val.
No. 40 Ty. FUNCTION
Name RSSB_AUTHORITY_IOBJVL_CHECK
I_ACTIVITY
03
33
03
I_ACTIVITY_FORCE_CHECK
2
0
I_MESSAGE
X
5
8
I_SX_IOBJVL_CHECK
ZCTMWMA05 ####
5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
I_UNAME
S51643
533333222222
351643000000
E_SUBRC
0
0000
0000
E_TS_AUTH_TLEVEL
Table[initial]
E_TX_NO_AUTH
Table[initial]
RSSB_C_AUTH_KEYFIGURE
1KYFNM
3454442222
1B96ED0000
SY-REPID
SAPLRSSBR
5454555452222222222222222222222222222222
310C233220000000000000000000000000000000
SYST-REPID
SAPLRSSBR
5454555452222222222222222222222222222222
310C233220000000000000000000000000000000
%_SPACE
2
0
RS_C_RANGE_SIGN
IE
44
95
SY-SUBRC
5
0000
0005
L_TX_NO_AUTH
Table[initial]
SY-XFORM
CONVERSION_EXIT
444545544454545222222222222222
3FE65239FEF5894000000000000000
SYST
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1. ###################################################à##############
0000000000000000000000000002000000000000000000000000000000000000000000000000000E00000000000000
0001000000000000000000000000000000000000000000010001000000010000000000000000000000000000000000
L_SX_NO_AUTH
############ÿÿÿÿ
000000000000FFFF
000000000000FFFF
L_SX_NO_AUTH-KID
Table[initial]
<L_SX_AUTH_CHECK>-KID
Table IT_33029[1x4]
FUNCTION-POOL=RSSBRDATA=G_SX_IOBJVL_CHECK-AUTH_CHECK[1]-KID
Table reference: 2052
TABH+ 0(20) = 07000000908D2FD0000000000000000000000000
TABH+ 20(20) = 00000804000081050000000100000004FFFFFFFF
TABH+ 40(16) = 040002F1000003480001432821000000
store = 0x07000000908D2FD0
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 2052 (0x00000804)
label = 33029 (0x00008105)
fill = 1 (0x00000001)
leng = 4 (0x00000004)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000003
occu = 1 (0x00000001)
access = 2 (ItAccessSorted)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 2 (table_line)
cmpMode = 5 (cmpSingle)
occu0 = 0
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000908E0CC8
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 1 (0x00000001)
lineAlloc = 1 (0x00000001)
store_id = 6998 (0x00001B56)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
No. 39 Ty. FORM
Name AUTHORITY_CHECK
I_TH_SFC
Table IT_32090[14x128]
FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFC
Table reference: 1757
TABH+ 0(20) = 070000009052D8F8070000009081372800000000
TABH+ 20(20) = 000006DD00007D5A0000000E00000080FFFFFFFF
TABH+ 40(16) = 040002DB000017C80010839401000000
store = 0x070000009052D8F8
ext1 = 0x0700000090813728
shmId = 0 (0x00000000)
id = 1757 (0x000006DD)
label = 32090 (0x00007D5A)
fill = 14 (0x0000000E)
leng = 128 (0x00000080)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000099
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000090811F18
pghook = 0x0000000000000000
idxPtr = 0x070000009052D950
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6872 (0x00001AD8)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0700000090813588
hsdir = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
CL_RSO_REPOSITORY=>P_C_BAL_LOG_SUBOBJEC_INST
SY-REPID
SAPLRSDRC
5454554542222222222222222222222222222222
310C234230000000000000000000000000000000
L_S_RANGE-LOW
1ROWCOUNT
354544545222222222222222222222222222222222222222222222222222
12F73F5E4000000000000000000000000000000000000000000000000000
<L_S_SFK>-KYFNM
1ROWCOUNT
354544545222222222222222222222
12F73F5E4000000000000000000000
RSDRC_C_QUERYMODE-CUMULATIVE
C
4
3
S_S_COB_PRO
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_SX_SELDR-RANGE+8(8)
Table IT_32110[2x136]
FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_SX_SELDR
Table reference: 1902
TABH+ 0(20) = 0700000090813D10000000000000000000000000
TABH+ 20(20) = 0000076E00007D6E0000000200000088FFFFFFFF
TABH+ 40(16) = 040002DB00001AA00010254421000000
store = 0x0700000090813D10
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 1902 (0x0000076E)
label = 32110 (0x00007D6E)
fill = 2 (0x00000002)
leng = 136 (0x00000088)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000112
occu = 16 (0x00000010)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 2 (table_line)
cmpMode = 8 (cmpManyEq)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000908800F8
pghook = 0x0000000000000000
idxPtr = 0x0000000000000000
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6876 (0x00001ADC)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_S_RANGE
IEQ1ROWCOUNT
4453545445452222222222222222222222222222222222222222222222222222222222222222222222222222222222
95112F73F5E40000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_TSX_SELDR
Table IT_32094[13x120]
FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TSX_SELDR
Table reference: 1870
TABH+ 0(20) = 0700000090813AE007000000908DF36800000000
TABH+ 20(20) = 0000074E00007D5E0000000D00000078FFFFFFFF
TABH+ 40(16) = 040002DB000018A8000C4B9C01000000
store = 0x0700000090813AE0
ext1 = 0x07000000908DF368
shmId = 0 (0x00000000)
id = 1870 (0x0000074E)
label = 32094 (0x00007D5E)
fill = 13 (0x0000000D)
leng = 120 (0x00000078)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000103
occu = 12 (0x0000000C)
access = 2 (ItAccessSorted)
idxKind = 1 (ItIndexLinear)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 3 (cmpSingleMcmpU)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x070000009087FB40
pghook = 0x0700000090813D68
idxPtr = 0x0700000090813DA0
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 36 (0x00000024)
lineAlloc = 36 (0x00000024)
store_id = 6875 (0x00001ADB)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x07000000908DED00
hsdir = 0x0000000000000000
ext2 = 0x0000000000000000
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
L_SX_SELDR
00001KYFNM ########300 0 ####ÿÿÿÿ#### 0 ######## ####ÿÿ
333334544422222222222222222222222222000000003332223222220000FFFF0000223200000000222222220000FF
00001B96ED00000000000000000000000000000000003000000000000000FFFF0000000000000000000000000000FF
G_RUNNING
0
0000
0000
L_BASICCUBE
ZCTMWMA05
545454433222222222222222222222
A34D7D105000000000000000000000
L_TH_FREE
Table IT_32093[6x30]
FUNCTION-POOL=RSDRCFORM=AUTHORITY_CHECKDATA=L_TH_FREE
Table reference: 1763
TABH+ 0(20) = 0700000090813760000000000000000000000000
TABH+ 20(20) = 000006E300007D5D000000060000001EFFFFFFFF
TABH+ 40(16) = 040002DB00001B800010831401000000
store = 0x0700000090813760
ext1 = 0x0000000000000000
shmId = 0 (0x00000000)
id = 1763 (0x000006E3)
label = 32093 (0x00007D5D)
fill = 6 (0x00000006)
leng = 30 (0x0000001E)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000116
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 2 (table_line)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x07000000908137B8
pghook = 0x0000000000000000
idxPtr = 0x07000000908139B0
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6874 (0x00001ADA)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = Not allocated
hsdir = Not allocated
ext2 = Not allocated
>>>>> 2nd level extension part <<<<<
tabhBack = Not allocated
delta_head = Not allocated
pb_func = Not allocated
pb_handle = Not allocated
SYST-REPID
SAPLRSDRC
5454554542222222222222222222222222222222
310C234230000000000000000000000000000000
L_SX_IOBJVL_CHECK
ZCTMWMA05 ####
5454544332222222222222222222222222222222222222222222222222222222222222222222222222222222220000
A34D7D1050000000000000000000000000000000000000000000000000000000000000000000000000000000000000
L_ACTIVITY
03
33
03
SY-UNAME
S51643
533333222222
351643000000
S_MULTICUBE
222222222222222222222222222222
000000000000000000000000000000
E_SUBRC
0
0000
0000
%_VIASELSCR
0
4
S_CHANM
222222222222222222222222222222
000000000000000000000000000000
I_RAISE_EXCEPTION
X
5
8
RS_C_TRUE
X
5
8
SCREEN
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
No. 38 Ty. FORM
Name BASIC_QUERY_DATA_GET_ROLAP
E_T_DATA
Table[initial]
E_END_OF_DATA
2
0
C_FIRST_CALL
X
5
8
S_S_QPARAM
XX 0 ##ÿÿÿÿ####DB-VIEW R ###dABAP-TABLE
25523200FFFF0000442544522222222222222222222222222222222222222222222222520006444525444422222222
08800000FFFF000042D6957000000000000000000000000000000000000000000000002000041210D412C500000000
C_S_QPARAM-AUTHORITY_CHECK
R
5
2
RSDRC_C_AUTHCHK-NONE
2
0
RSJOBINFO
00000000000000 ####
222222222222222222222222222222223333333333333322222222222222222222222222222222220000
000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RSD_C_DPANM
0REQUID 0CHNGID 0RECORDTP 0IOB
3545544222222222222222222222223444444222222222222222222222223544454552222222222222222222223444
025159400000000000000000000000038E794000000000000000000000000253F244000000000000000000000009F2
SPACE
2
0
I_BASICCUBE
ZCTMWMA05
545454433222222222222222222222
A34D7D105000000000000000000000
I_TH_SFC
Table IT_32090[14x128]
I_TH_SFK
Table IT_32091[2x128]
FUNCTION=RSDRC_BASIC_CUBE_DATA_GETDATA=L_TH_SFK
Table reference: 1767
TABH+ 0(20) = 0700000090887AC00700000090813CD800000000
TABH+ 20(20) = 000006E700007D5B0000000200000080FFFFFFFF
TABH+ 40(16) = 040002DB000018380010839421000000
store = 0x0700000090887AC0
ext1 = 0x0700000090813CD8
shmId = 0 (0x00000000)
id = 1767 (0x000006E7)
label = 32091 (0x00007D5B)
fill = 2 (0x00000002)
leng = 128 (0x00000080)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000101
occu = 16 (0x00000010)
access = 4 (ItAccessHashed)
idxKind = 0 (ItIndexNone)
uniKind = 1 (ItUnique)
keyKind = 3 (user defined)
cmpMode = 2 (cmpSingleMcmpR)
occu0 = 1
collHash = 0
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x0700000090884C90
pghook = 0x0000000000000000
idxPtr = 0x0700000090827A98
refCount = 1 (0x00000001)
tstRefCount = 0 (0x00000000)
lineAdmin = 16 (0x00000010)
lineAlloc = 16 (0x00000010)
store_id = 6857 (0x00001AC9)
shmIsReadOnly = 0 (0x00000000)
>>>>> 1st level extension part <<<<<
regHook = 0x0700000090813B38
hsdir = 0x0000000000000000

Have you check or trace Authorization??
In DUMP:
Information on where terminated
The termination occurred in the ABAP program "SAPLRSSBR" in
"RSSB_AUTHORITY_IOBJVL_CHECK".
The main program was "UPB_PM_CUST_START ".

Abap runtime error CL_AI_CRM_OBJECT_LMDB============CP

Dear All,
We are setting up Solman 7.1 sp08 for VAR scenario.
As we faced some issues with duplicated ibase components SAP suggested us to implement note 2012029.
After following step by step and running the reporrts mentioned in above note like report AI_CRM_PRODUCT_DELETE we started getting an abap runtime error.
SAP is telling us to re implement the note but it does not resolve our issue.
Now we are unable to create incidents, or to run trx ib_gen.
Because of this, job refresh_admin_data_from_support is getting cancelled.
find attached screenshot showing dump.
all suggestions or comments are welcome!
regards,
German

Hi German,
Looks like your report CL_AI_CRM_OBJECT_LMDB============CP is corrupted. Can you try restoring this program to original version by going to Version management in SE38?
Regards,
Vivek

ABAP runtime error while executing T.code : PC00_M40_CALC

Hi,
I have applied SAP note 1568264 - Budget Changes 2011 as released by
SAP and i also applied the pre-requiste SAP notes mentioned in the
above SAP note
1) SAP Note 1558475- Amendments to IT calculation notified under
circular:08/2010.
2) SAP Note 1572614- Tax calculations inconsistent for emp. without a
vaild PAN.
3) SAP Note 1575366- HINCALC0:Tax calculation inconsistent in case of
invalid PAN.
After applying the SAP notes, when i am trying to execute the T.Code :
PC00_M40_CALC, i am getting an "Abap runtime error"
" Error in the ABAP Application Program
The current ABAP program "????????????????????????????????????????" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "HINCALC0 " in include "PCTAXIN0
" in
line 905:
""ENDUZ-" expected, not "EDU_""
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "S2K_BASIS "
Error in the ABAP Application Program
The current ABAP program "????????????????????????????????????????" had to be
terminated because it has
come across a statement that unfortunately cannot be executed.   "
Kindly suggest me what has to be done on priority basis.
Regards
Vish

The dump error is generally encountered if your system is at a lower Support Pack level. For implementing Note 1568264 (Budget Changes 2011), you need to be at the below mentioned pre-requisite level corresponding to your Release:
Prerequisites:
   Release     Support Package
     604         HRSP29
     600         HRSP63
     500         HRSP80
     470         HRSPB4
     46C         HRSPG9
The correct sequence to implement the Notes is:
SAP Note 1558475- Amendments to IT calculation notified under
circular:08/2010.
SAP Note 1572614- Tax calculations inconsistent for emp. without a
vaild PAN.
SAP Note 1575366- HINCALC0:Tax calculation inconsistent in case of
invalid PAN.
SAP Note 1568264- Budget Changes 2011
This should solve the issue unless there is some problem while implementing the Notes.
Regards,
Nishtha

Reg : Daily i got 120 ABAP Runtime Error with in 40 Mins(Early Morning)

Dear Friends,
I got following errors regularly. when i run t.code RSBTCDEL and RSSNAPDL. what can i do? then Regularly morning i got same morethan 120 Error. User is SAPSYS 000 Client. How can avoid this type of ABAP Runtime Error.
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          10.06.2009 15:04:23
Short text
     SQL error in the database when accessing a table.
What can you do?
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
How to correct the error
     Database error text........: "[601] Could not continue scan with NOLOCK due to
      data movement."
     Internal call code.........: "[RSQL/FTCH/TBTCO ]"
     Please check the entries in the system log (Transaction SM21).
     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:
     "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
     "SAPLBTCH" or "LBTCHF19"
     "EXECUTE_BP_JOB_SELECT"
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 u2192 List u2192 Save u2192 Local File u2192 (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. The exception must either be prevented, caught within proedure
"EXECUTE_BP_JOB_SELECT" "(FORM)", or its possible occurrence must be declared
in the RAISING clause of the procedure. To prevent the exception, note the following:
Client.............. 400
User................ "BASIS"
Language key........ "E"
Transaction......... "SE38 "
Transactions ID..... "D7A155DEA42EF1EEB52A000423BF7C3A"
Program............. "SAPLBTCH"      ( Run a Sap Standard Report RSBTCDEL)
Screen.............. "SAPMSSY0 1000"
Regards
keshav

Hi Juan,
My System is
ECC 6.0
Database : MS SQL Server 2005
OS - Windows 2003 server
SAP Patches level is Basis - SAPKB70016
                               ABAP - SAPKA70016
                               Kernel patch level - 185
when i has update the kernel patches after only i got this error morethan 120 like early morning 4.40 AM to 5.18 AM regularly. what can i do?
Regards
keshav

ABAP Runtime ERROR Error Code & Syntax Error in program SAPLSFES

Hi,
I am installing SAP XI 3.0 and as part of that I have installed the ABAP and Java WAS. I am applying SPs for the ABAP stack and I successfully applied the BASIS SPs 10 and 11(applied seperately). I was applying the SPs 12 and 13(together) and after running for some time the system crashed and I restarted the O/S and SAP to see that the SPs didn't go thru. Now when I try to log on using SAP GUI, it says "ABAP Runtime ERROR Error Code" which is blank and at the Bottom there is this message "Syntax Error in program SAPLSFES".
Pls any one help me ,
Kind Regards,
Gopi.

Hi Gopi,
If u r applying patches, the system would be running a background job SAPLSTPA. Hence you willnot be able to login till the job is complete.
You can check the job completion in the Windows MMC console.
Rgds
Ganesh

ABAP Runtime Error - " Reshedule Periodic jobs"

Dear Friends,
I got around 120 ABAP runtime error in PRD system regularly(Daily) for the period of 4.40 AM to 5.18 AM.
How can i solve following ABAP Runtime Error, Pls give me suggession.
SM21 - System Logs:
Client           :     000
User          :     sapsys
Package          :     SDYN, SABP, SBAC
Prgm          :     SAPMSSY2
Problem Class     :     SAP Web AS Problem
Access table      :     TBTCO
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20090422051802production_PRD_02 SAPSYS 000)
How to correct the Error
==================
"RESCHEDULE_PERIODIC_JOBS"
The exception must either be prevented, caught within proedure
"RESCHEDULE_PERIODIC_JOBS" "(FORM)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
Information on where terminated:
=======================
   Termination occurred in the ABAP program "SAPMSSY2" - in
     "RESCHEDULE_PERIODIC_JOBS".
    The main program was "SAPMSSY2 ".
    In the source code you have the termination point in line 4115
    of the (Include) program "SAPMSSY2".
    The program "SAPMSSY2" was started as a background job.
    Job Name....... " "
    Job Initiator.. " "
    Job Number..... " "
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "RESCHEDULE_PERIODIC_JOBS" "(FORM)", but it was neither handled
     locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPMSSY2 "; its source code begins in line
    3823 of the (Include program "SAPMSSY2 ".
Regards
kesav

Hi
1) Check the dev_w* trace of the work process corresponding to the entry in the system log, to get more information on "Transaction Canceled 00 671 "
2) DBIF_RSQL_SQL_ERROR- refers to database error in the RSQL module of the database interface,usually relating to timeouts. See Note 976203 - Interception of background jobs: Timeout
3) Contact ABAP team and see what they have to say on this, as mentioned in the dump:
"The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "RESCHEDULE_PERIODIC_JOBS" "(FORM)", but it was neither handled
locally nor declared in the RAISING clause of its signature. "
4) Moreover, the ABAP program SAPMSSY2 is used to switch operation modes assigned to instances, refer : http://help.sap.com/saphelp_nw70/helpdata/en/c4/3a5f1f505211d189550000e829fbbd/content.htm
5) The most common cause for an operation mode switch failing is inconsistencies in the total number of work processes or in the profiles.You must define the whole 24u2212hour range for operation modes to work. You cannot leave any time period unassigned, otherwise the switch will not be possible and can cause problems in the background processing system. check the operation mode from control panel refer: http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a5f7a505211d189550000e829fbbd/content.htm
6) Explore the follwoing cases as well:
SAP note Note 208924 - Operation mode switch incorrect
SAP Note 1082783 - Work processes hang after operation mode switching
Ravi
Edited by: ravi raj on Apr 23, 2009 8:20 AM

ABAP runtime error for 0CRM_OPPT_H and I while running RSA3

hello Gurus,
 I'm having problems while running RSA3 transaction for these data sources.
0CRM_OPPT_H
0CRM_OPPT_I
0CRM_SALES_ACT_1
0CRM_SALES_ACT_I.
I'm getting ABAP runtime error for these.
This is the error:
Runtime Error CALL_FUNCTION_CONFLICT_TAB_TYP
Exception CX_SY_DYN_CALL_ILLEGAL_TYPE
I tried finding OSS notes for these, but I didnt succeed.
I activated the data source from RSA5, and then I tried RSA3. That time I got Errors occurred during extraction.
After that I activated delta at BWA5, then I started getting runtime error.
Even though I activated at BWA5, I am not able to see the data sources at BWA7.
Am I missing any thingplease guide me through this.
Thanks
RKR

Thanks for your replay... All the DS and related tables are active..
But wen I tried to re-generate the DS again... this is the warning I'm getting... Any idea why I'm getting this....
The even-numbered length of the DEC field SAMPLE_QTY_ALLOW can lead to problems
Message no. R8569
Diagnosis
You want to use the field SAMPLE_QTY_ALLOW in the extract structure for DataSource 0CRM_OPPT_I. This field has a field of type 'DEC' (or 'CURR' or 'QUAN') with an even number of characters.
This can create problems since the length resulting from calculations in ABAP (for example, in extractors or Customer Exits for extraction) is too large to be inserted in the database later (PSA in BW), causing a short dump.
Procedure
This warning is only relevant when the maximum length of this field is exceeded during extraction, for example when the field is expanded in the Customer Exit through a calculation.
More information and a remedy can be found in SAP Note 641744.
When I search the OSS note, SAP suggesting to apply 883310 note.
In my company we are using CRM 4.0 servie pak8. SAP suggsting to install service pak 11, but my client is not interested to upgrade to 11 as CRM people are working on service pak 8.
By any chance we can use specific note which change the ABAP code to solve this problem... Please give me some suggetions...
Thanks
RKR

ABAP runtime errors    CONVERSION_CODEPAGE_UNKNOWN

Hi All,
We performed a system build. Upon validating the new system, we are encountering ABAP program errors when generating STMS import queue, viewing tables, testing RFC connections. Please refer to dump details below:
ABAP runtime errors    CONVERSION_CODEPAGE_UNKNOWN
       Occurred on     17.11.2010 at 15:34:01
Unable to convert from code page '1200' to code page '0120'.
What happened?
The current ABAP/4 program "SAPLTMSC " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
One of your chosen conversion tables (CODE PAGE) '1200' or '0120'
is unknown to the system.
For a list of conversion tables known to the system, see table
TCP00. To display this, use Transaction SPAD.
How to correct the error
You can avoid this error by using a conversion table known
to the system. Transaction SPAD allows you to display a
list of these conversion tables.
If you have modified the conversion table, use Transaction SP12
to invalidate the code page buffer (CCC).

Hi Nils,
Thank you for your response. We checked the transaction SCP, unfortunately, it does not exist. Could you verify if this is the correct transaction code? With regard to kernel patch, yes we have the latest kernel patch. First, we performed kernel patch upgrade because we encountered issue during our SAP installation for V6R1. Our kernel patch level is not compatible with the said OS version. So, we performed reinstallation after the patch upgrade and we believe we are using the latest kernel for this system. Talking about the memory, we did not encounter any memory issues during the installation and after the installation of the SAP system.
You mey refer to kernel and OS details below:
46D patch level 2548
OS version V6R1
SAP version 46.C
Could you give me further details regarding the character set? Based on the dumps, there's a problem with the conversion of character set. We already created SAP message on this matter and they want to connect into the system but unfortunately we do not have the saprouter to open the SAP connection.
Your feedback/inputs will be greatly appreciated.
Thank you in advance and have a great day ahead.
Regards,
Mark

LSO_PSV2 - Create /w Resources freezing, ABAP runtime error, TIME_OUT

Hello Experts,
I have an individual user that is a part of a team that manages our LSO environment. He is experiencing a problem when performing a "Create with resources" on an instructor-led course.
After choosing this option his session just spins but never enters the course details screen as expected.
After anywhere from 15 - 30min the session returns an ABAP runtime error of "TIME_OUT". The error details state that the time out for ABAP programs is set to 3000sec (50min). The odd thing is that the program never reaches the 50 min marks but still throws the error.
The user is able to select the "create w/o resources" option and get to the next screen as expected.
I have run security traces (ST01) on his account and all looks fine (rc=0)
He is one of several people that executes this transaction but is the only user that is receiving this issue. The team is assigned to the same position and shares the same PD profile. They share the same security roles and the same ABAP program is being run.These users are a third party vendor that remote in via citrix desktop.
I have had our Basis team exam the ABAP runtime error and what is happening behind the scenes as this runs and they see no indication that the program is retrieving data even though it processes for a long time.
Obviously this is a complex issue, I have searched for two weeks with no success. Any thoughts, suggestions are more than welcome at this point as the user is unable to perform needed work functions.

Any solution on this one? I have the same problem with LSO_PSV2 :/

ABAP runtime errors TYPELOAD_NEW_VERSI ON (SAPM/SAINT UPDATE)

Hi ,All
I am using SAP4.6c with Orcle8i database on aWindows 2k Adv server. I have imported SPAM (KD00050.CAR) but after imporiting I am unable to use SPAM/SAINT Transaction code and its showing ABAP runtime error like
"ABAP runtime errors TYPELOAD_NEW_VERSION
Data type "PAT03" was found i n a newer version than required.
Runtime Error
of the statement s could not be executed at runtime.
The current ABAP program"SAPLSPAM" had t o be terminated because one
of the statements could not be executed at runtime.

Hello Jhony,
http://help.sap.com/saphelp_nw04/helpdata/en/d7/56e89a884b11d2b422006094b9ea64/content.htm
Regards
ismail KARAYAKA

ABAP runtime errors    SNAP_NO_NEW_ENTR

The following errors occured just after login, can anyone tell me how to handle it?
ABAP runtime errors    SNAP_NO_NEW_ENTRY
       Occurred on     0000.00.00 at 13:47:44
Runtime error: Unable to write short dump.
What happened?
The current ABAP/4 program " " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Unfortunately, the original cause of the error cannot be determined
because there is no suitable short dump in the table SNAP (which
records information about the point of termination).
termination).
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
Error analysis
Unfortunately, the original cause of the error cannot be
determined, since there is no suitable short dump in table SNAP.
The table SNAP probably already contains a number of short dumps
and cannot accept any more. Please check the situation using the
system log.
The table SNAP contains all the short dumps for the last 7 days.
How to correct the error
Check the system log for each cause of error.
More space probably needs to be provided for table SNAP
using database means.
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:

hello,
Check these:
Note 495297 - DB6: Monitoring transaction log
Re: Question. usage of transaction log
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/f03d5fb8-b619-2b10-c383-c6d56872829e&overridelayout=true
Ideally, db2diag.log should tell you this information.
Hope it helps.
thanks,
Prasanna

ABAP runtime errors SNAP_NO_NEW_ENTRY

The following errors occured just after login, can anyone tell me how to handle it?
ABAP runtime errors SNAP_NO_NEW_ENTRY
Occurred on 0000.00.00 at 13:47:44
Runtime error: Unable to write short dump.
What happened?
The current ABAP/4 program " " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Unfortunately, the original cause of the error cannot be determined
because there is no suitable short dump in the table SNAP (which
records information about the point of termination).
termination).
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
Error analysis
Unfortunately, the original cause of the error cannot be
determined, since there is no suitable short dump in table SNAP.
The table SNAP probably already contains a number of short dumps
and cannot accept any more. Please check the situation using the
system log.
The table SNAP contains all the short dumps for the last 7 days.
How to correct the error
Check the system log for each cause of error.
More space probably needs to be provided for table SNAP
using database means.
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:

补充两句：
1. SNAP表的Reorganization应该在后台通过定期的（每天）job执行，参看Note 16083。
2. 如果登录系统即发生Dump，怀疑是否SNAP的table space是导致这个Dump的原因，考虑可能有其它致命错误。如果登录后还可以执行transaction，尝试执行SM21，DB02检查。

MIR4 transaction is giving ABAP Runtime Error

Hi Experts,
When I am trying to display the invoice in MIR4 and/or MIRO the system is generating ABAP runtime error. DYNPRO_FIELD_CONVERSION. This is in Version ECC 6.0.
Short text
    Conversion error
What happened?
    The current screen processing action was terminated since a situation
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the curren
    screen.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manag
    termination messages, in particular for long term reference.
Error analysis
    The program has been interrupted and cannot resume.
    Program "SAPLMR1M" attempted to display fields on screen 6310.
    An error occurred during the conversion of this data.
How to correct the error
    There was a conversion error in the output of fields to the screen.
    The formats of the ABAP output field and the screen field may not match.
    Some field types require more space on the screen than in the ABAP
    program. For example, a date output field on the screen requires two
    more characters than the corresponding field in the ABAP program. When
    the date is displayed on the screen, an error occurs resulting in this
    error message.
                  Screen name.............. "SAPLMR1M"
                  Screen number............ 6310
                  Screen field............. "DRSEG-REMNG"
                  Error text............... "FX015: Sign lost."
    Other data:
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
2. Corresponding system log
   Display the system log by calling transaction SM21.
   Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Please help us to solve this issue.
Thanks and Regards,
Havina
Edited by: Havina Kutty on May 19, 2009 11:54 AM

Hello,
Please refer
Note 503934 - MIRO: Dump DYNPRO_FIELD_CONVERSION -> field 'REMNG'
Note 445853 - MIR4:more credit memos than invoices for service
Note 393189 - MIRO: Incorrect update of BPMNG -> DYNPRO_FIELD_CONVERSION
Regards,
Ravi

Reg : USMM Abap runtime Error

Dear Friends,
Greetings, I got ABAP runtime error in tcode USMM after implement the oss note 1150840 correction.
ERROR is SYNTAX_ERROR
Syntax error in program "RSUVM000 " this program unfortunatley can not be executed.
The following syntax error occurred in program "RSUVM000 " in include "RSUVMINC " in line 1605
"The type "SX_ADDRESS" is unknown."
ECC 6.0 with SQl Server 2005 and windows 2003 server
Pls give suggession to me friends
Regards
keshav

Hi Subash,
Basis Patch level is SAPKB70013, ABAP KA70013.
Now we have plan to updation of patches. Before that SAp asking USMM(User Measurement report) so i can execute USMM report.
what can i do now?
Regards
kesav

ABAP Runtime error on FB50 or FB60 after supplying SAP Support Packs

Similar Messages

Maybe you are looking for