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 ".

Similar Messages

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

Runtime error while executing rule

Hello All,
While executing the DTP for a cube, im facing the error as Runtime error while executing rule -> see long text .
For this source is another Cube, where im loading the data from Cube to Cube.
Error Description are as follows:-
Error Location: Object Type    TRFN
Error Location: Object Name    0T9SCR6Q4VWS1SOPNRRBOY1YD51XJ7PX
Error Location: Operation Type ROUTINE
Error Location: Operation Name
Error Location: Operation ID   00034 0000
Error Severity                 100
Original Record: Segment       0001
Original Record: Number        557
and Also descripton is :-
Diagnosis
    An error occurred while executing a transformation rule:
    The exact error message is:
    Division by zero
    The error was triggered at the following point in the program
    GP4H0CW3MLPOTR3E8Y93QZT2YHA 4476
System Response
    Processing the data record has been terminated.
Procedure
The following additional information is included in the higher-level
node of the monitor:
   Transformation ID
   Data record number of the source record
   Number and name of the rule which produced the error
Let me know ur valuable suggestions on these error...
thanks.

Hello,
I have checked all the transformation and End Routines.All are working fine.Yesterday i have loaded some data into it, but today its gettting errored out.
Checked completely in the forum for threads related to this, but couldnt find proper thread which had solutions....
thanks,
srinivas.

Runtime error while executing rule - see long text RSTRAN 301

Hi BW Gurus,
When I executing the DTP, the following error occured.
Runtime error while executing rule -> see long text     RSTRAN     301
Diagnosis
    An error occurred while executing a transformation rule:
    The exact error message is:
    The argument 'GBP' cannot be interpreted as a number
    The error was triggered at the following point in the program:
    GP46DQFOYRZTUS0QITMO07IFTS0 1137
Appreciate any useful suggestions.
Thanks in advance.
Maruthi

Guess you are doing some calculation in your routines ..based on Currency Key i.e USD or INR , GBP..etc ..it should be currency value..rather than currency key. Check your field caluclation

Diadem runtime error while executing command "SchemeMeasStar"

Hello:
I used DIAdem9.0 and DAQCard6062E to acquire 16 channel data. I collected 65536 data for every channel. Whereas After the data acquisition stopped, an Error Message would poped up, but the data is still stored in data portal. the Error is like follows:
-Error- DIAdem
Runtime Error While Executing Command "SchemeMeasStar"
Error Type: UNKNOWN
Error Address:00001720
Module Name:GFSBase.Dll
Would you like to give me some suggestions?
thanks very much
jing

Dear MarcusP:
Thank you very much.
your solution really works. The attached is the detailed information of the problem. Would you like to tell me more about the prolem and how to solve the problem thoroughly.
Thank you very much.
yours
Jing
Attachments:
DIAdem_Error.doc ‏305 KB

Runtime Error While executing the WebDynpro Application

I am getting the Runtime Error While executing the WebDynpro Application. The error message is "TSV_TNEW_OCCURS_NO_ROLL_MEMORY".
It says like "
Short text
    No roll storage space of length 9728 available for OCCURS area.
What happened?
    Each transaction requires some main memory space to process
    application data. If the operating system cannot provide any more
    space, the transaction is terminated.
But while executing some other Web Dynpro Applications, i am not facing this problem.

Generally this error is a result of an infinite loop on internal table or select endselect statement where by severs temporary memory gets full. With no memory to insert new records in temporary memory system generates the dump.
Check your application or ask basis consultant to look at the memory parameters in instance profile.
Regards
Rohit Chowdhary

Error while executing planning Function

Hi All,
I'm getting some error while executing planning function. Below are errors. Please check and provide solution.
Errors occurred when executing planning function RTFMPF01/RTFMPG01
Value 08 of chara Region does not correspond to the attrib.val MI of chara Store
Value 10 of chara Region does not correspond to the attrib.val RM of chara Store
Value 11 of chara Region does not correspond to the attrib.val NA of chara Store
Thanks,
Vamsi

Hi,
Value 08 of chara Region does not correspond to the attrib.val MI of chara Store
Looks like there is a characteristics relationship which derives the attribute store from Region.
Check the master data for Region for attribute Store and the corresponding values.
The values that are maintained in the master data will only be allowed to enter in the cube.
Thanks
pratyush

ABAP runtime error while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N

Dear All Expert,
I am facing problem while doing ME21N, ME22N, ME23N, ME51N,ME52N, ME53N,
Please find the below ABAP Runtime Error.
Runtime Errors         LOAD_TYPE_VERSION_MISMATCH
Date and Time          10.02.2011 11:13:07
Short text
     Change of a Dictionary structure at runtime of a program.
What happened?
     Runtime error
     The current ABAP program "CL_IM_WRF_MM_PROC_PO==========CP" had to be
      terminated because one
     of the statements could not be executed at runtime.
What can you do?
     Restart the program.
     If the error persists, 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.
Error analysis
     The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY"
      changed
     during the flow of the transaction.
     As the type was already used in the old version
     and in the new type should be used in the same transaction in the new
      version, the transaction had to be cancelled to avoid inconsistencies.
How to correct the error
    Try to restart the program.
System environment
    SAP-Release 700
    Application server... "iqe"
    Network address...... "172.25.0.85"
    Operating system..... "Linux"
    Release.............. "2.6.9-55.ELsmp"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 0
    Shortdump setting.... "full"
    Database server... "iqe"
    Database type..... "ORACLE"
    Database name..... "IQE"
    Database user ID.. "SAPSR3"
    Terminal................. "MUMJML5727"
    Char.set.... "C"
    SAP kernel....... 700
    created (date)... "Dec 26 2010 20:17:07"
    create on........ "Linux GNU SLES-9 x86_64 cc3.3.3"
    Database version. "OCI_102 (10.2.0.2.0) "
Patch level. 285
Patch text.. " "
Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"
SAP database version. 700
Operating system..... "Linux 2.6"
Memory consumption
Roll.... 16192
EM...... 25139088
Heap.... 0
Page.... 40960
MM Used. 8038136
MM Free. 4528408
User and Transaction
Client.............. 600
User................ "JKMM"
Language key........ "E"
Transaction......... " "
Transactions ID..... "4D524AD1FD7A42F9E1000000AC190055"
Program............. "CL_IM_WRF_MM_PROC_PO==========CP"
Screen.............. " "
Screen line......... " "
Information on where terminated
    The termination occurred during generation of the ABAP/4 program
     "CL_IM_WRF_MM_PROC_PO==========CP".
    The termination occurred in line 213
    of the source code of program "CL_IM_WRF_MM_PROC_PO==========CM007" (when
     calling the editor 2130).
Source Code Extract
Line SourceCde
183   DATA: l_flag TYPE wrf_pbas_boolean.
184
185   CALL FUNCTION 'WRF_POHF_MSG_READ_PREVIEW_FLAG'
186     IMPORTING
187       e_preview_flag = l_flag.
188
189   IF NOT l_flag IS INITIAL.
190
191     DATA: l_header TYPE REF TO cl_po_header_handle_mm.
192
193     MOVE im_header ?TO l_header.
194
195     CALL METHOD l_header->if_output_mm~preview( ).
196
197     CALL FUNCTION 'WRF_POHF_MSG_RESET_PREV_FLAG'.
198
199 ***$ Widening Cast for printing information.
200 **    CALL FUNCTION 'WRF_POHF_STORE_PRINT_INFO_SET'
201 **      EXPORTING
202 **        im_header = l_header.
203
204 * Printing Preview
205 * IF NOT gv_preview IS INITIAL.
206 *    CALL METHOD l_header->if_output_mm~overview( ).
207 *    CALL METHOD l_header->if_output_mm~preview( ).
208 * clear gv_preview.
209   ENDIF.
210
211 * ENDIF.
212
>>>>> ENDMETHOD.
Internal notes
    The termination was triggered in function "ab_RxDdicStruShareFailed"
    of the SAP kernel, in line 2539 of the module
     "//bas/700_REL/src/krn/runt/abtypload.c#11".
    The internal operation just processed is " ".
    Internal mode was started at 20110210111306.
    Name of the changed type......: "WRF_POHF_KOMP_STY"
    New version of the type.......: 20070508193207
    Old version of the type.......: 20070508193207
    New user......................: "Type" "WRF_POHF_KOMP_STY"
    Version of the new user.......: 20070508193207
    Old user......................: "???" "???"
    Version of the old user.......: "???"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(CTrcStack2+0x78)[0x6cbb78]
(CTrcStack+0xb)[0x6cc17b]
(ab_rabax+0x3be5)[0xb8d985]
(_Z24ab_RxDdicStruShareFailedPKtm4RUDIS0_S1_S0_+0x163)[0xb16823]
(_Z19ab_GetDdicTypeIndexPKtm4RUDI+0x1f6)[0xb0dbb6]
(_Z11ab_LoadViewPtjPKtPK11PROGRAMHEADPj+0x27e)[0xb16ede]
(_Z18ab_GetDdicTypeLoad4RUDI+0x6e)[0xb1705e]
(ab_GetView+0xc1d)[0xb0ee1d]
(_Z20CompressInitRcByDatajPK6CG_DIRjjS1_jj4RUDIPKhj+0x60d)[0xe32b2d]
(_Z21cg_CompressStackFrameP4TRIGjj+0x169)[0xe33399]
(_Z8cg_blkleP3ENV+0x75f)[0xe4779f]
(_Z9sc_cblklePKt8ENV_KINDP7SC_INFO+0x394)[0xe90024]
(sc_blkle+0xdd)[0xec6e4d]
(rs_oper_abap1729+0x37)[0x10eb237]
(rs_expan_abap+0xa1996)[0xfd7a2a]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_inclu+0x5fa)[0xe0d50a]
(rs_oper_abap2160+0x3a)[0x1115d6a]
(rs_expan_abap+0xcd41d)[0x10034b1]
(_Z8sc_expanj+0x76d)[0xe1d55d]
(_Z5parsejPi+0x258)[0xe19998]
(sc_check+0xb9c)[0xe1857c]
(sc_checkStart+0x41)[0xe1ac51]
(cg_generate+0xb65)[0xe57755]
(ab_gabap+0x14a)[0xb01a5a]
(dy_gen_abap+0x63c)[0x74428c]
(ab_genprog+0x13d3)[0xb03d13]
(_Z17ab_LoadProgOrTrfoPKtjPj+0xb56)[0x8f9ab6]
(_Z11ab_LoadProgPKtj+0x11)[0x8f9ca1]
(_Z15LoadGlobalClassPKtjjj9ClasState+0x24c)[0x958c2c]
(_Z11FillCfixIntPK4CREFP4CFIXjj9ClasState+0x214)[0x957404]
(_Z11ab_FillCfixtj+0x65)[0x957ae5]
(_Z26ab_CrefToCladId_ActivateOKtPh+0x7d)[0x957b6d]
(_Z8ab_jaboov+0x623)[0x959793]
(_Z8ab_extriv+0x607)[0x8ba9c7]
(_Z9ab_xeventPKt+0x1c1)[0xa1c021]
(_Z8ab_triggv+0x9c)[0xa1c77c]
(ab_run+0x97)[0xbde5c7]
(N_ab_run+0x9)[0x736359]
(dynpmcal+0x669)[0x7333b9]
(dynppai0+0x8eb)[0x734d9b]
(dynprctl+0x3e9)[0x733db9]
(dynpen00+0x4a5)[0x726eb5]
(Thdynpen00+0x359)[0x541bd9]
(TskhLoop+0xc49)[0x54d999]
(ThStart+0x20f)[0x55b29f]
(DpMain+0x2da)[0x4bd49a]
(nlsui_main+0x9)[0x4910c9]
(main+0x33)[0x491103]
/lib64/tls/libc.so.6(__libc_start_main+0xdb)[0x3cde51c3fb]
Please help me to resolve the issue.
Thanks & Regards
SKK

read this part again: The ABAP runtime system detected that the Dictionary-type "WRF_POHF_KOMP_STY" changed during the flow of the transaction. As the type was already used in the old version and in the new type should be used in the same transaction in the new version, the transaction had to be cancelled to avoid inconsistencies. How to correct the error Try to restart the program
how often had you restarted ME21N before you posted this message?
In best case this message appears only once, because the program / or dictionary was changed while you executed ME21N
If many times, then contact your ABAPer, because then he probably did not transport all objects that were changed, or the objects have to be regenerated in your system.

ABAP Runtime error while activating Update rules.

Hi Gurus,
Actually we are in NW 2004's SP9.
While activating the update rules of cube "0PY_PPC01" it is going to ABAP runtime error. It is giving the key words like "MESSAGE_TYPE_X"
"%_T005K2" or "INSTANTIATE". And i apply NOTEs also i am unable to fix it.
Can any one give correct NOTE number that can fix it or any suggestions.
Thanks in advance.
Thanks
Raju.k

Hi Sven,
Now we are also in SP11, But the thing is all the other UR are working fine Except
this UR. Even there is no perticular NOTE number for this.
Thanks
Raju.k

Macro Error while executing planning functions or saving data

Dear All,
I am getting following error in BEx Analyzer while executing planning function or pressing a save button.
Note: Excel is 2007 version.
Cannot run the macro "XXXXXX.xlsx". The macro may not be available in this workbook or all macros may be disabled.
I changed the settings in Macro Settings (Office Button -> Excel Options -> Trust Center -> Trust Center Settings-> Macro Settings) eventhough it is showing that above message.
selected ->
Enalble all macros
Trust access to VBA project object model.
If anybody faced this issue kindly reply to this.
Best Regards,
SG

Hello everybody,
i am facing exactlythe same issue! I am currently running GUI Patch Level 14 and BI Add on Patch Level 10.
I have also adjusted all necessary settings in Excel Options like Activate all Macros and Trust VBA Coding.
Does anybody have another Solution.
As mentioned before Gui Patch 13 and BI Add On Patch 10 obviously arent the solutiuon.
Best regards
Janos

Getting ABAP runtime error while doing MIGO-GR against PO.

Hi,
Getting ABAP runtime error message while doing GR against PO.
47 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_01 SPOTS ES_SAPLMBWL STATIC.
48
49 ENHANCEMENT-POINT MB_POST_GOODS_MOVEMENTS_02 SPOTS ES_SAPLMBWL.
50    CALL FUNCTION 'MB_CREATE_MATERIAL_DOCUMENT_UT'
51         EXCEPTIONS
52           error_message = 4.
53 * As soon as we have started to put things into UPDATE TASK, we must
54 * ensure that errors definitely terminate the transaction.
55 * MESSAGE A is not sufficient because it can be catched from
56 * external callers which COMMIT WORK afterwards, resulting in
57 * incomplete updates. Read note 385830 for the full story.
58    IF NOT sy-subrc IS INITIAL.
>>       MESSAGE ID sy-msgid TYPE x NUMBER sy-msgno WITH            "385830
60                  sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
61 *     MESSAGE A263.
62    ENDIF.
63 * Optische Archivierung
64 * Spaete Erfassung mit Barcode
65 * Redesign of barcode handling -> note 780365
66   PERFORM barcode_update(sapmm07m) USING xmkpf-mblnr
67                                          xmkpf-mjahr
68                                          barcode.
69
70   MOVE-CORRESPONDING xmkpf TO emkpf.
71   CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
72     EXCEPTIONS
73       error_message = 4.
74    MOVE-CORRESPONDING xmkpf TO emkpf.
75    CALL FUNCTION 'MB_MOVEMENTS_REFRESH'
76         EXCEPTIONS
77           error_message = 4.
78    IF NOT sy-subrc IS INITIAL.
Any pointers
Code Formatted by: Alvaro Tejada Galindo on Jan 14, 2010 6:00 PM

Hi ,
Any inputs
for this error
No RFC destination is defined for SAP Global Trade Services
Regards
Ashu

I was gettiing runtime error while executing a Webdynpro-ABAP application

Hi,
I am working on Webdynpro-ABAP and created a ALV report using Service call BAPI method in IDES version. After creating component and designed view and created Webdynpro application. While executing application I am getting some error in explorer.
For any application I am getting same error.
I think some setting in explorer..I am not sure. If yes how can I rectify ?
waiting for quick response.
I am giving details error below what I faced.
Error when processing your request
What has happened?
The URL http://sapserver:8001/sap/bc/webdynpro/sap/zz_00_bapiflight was not called due to an error.
Note
     The following error text was processed in the system DM0 : Die URL enthält keine vollständige Domainangabe (sapserver statt sapserver.).
     The error occurred on the application server sapserver_DM0_01 and in the work process 0 .
     The termination type was: RABAX_STATE
     The ABAP call stack was:
Method: CHECK of program CX_FQDN=======================CP
Method: LATE_CONSTRUCTOR of program CL_WDR_UCF====================CP
Method: HANDLE_REQUEST of program CL_WDR_UCF====================CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
What can I do?
     If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system DM0 in transaction ST22.
     If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapserver_DM0_01 in transaction SM21.
     If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server sapserver_DM0_01 . In some situations, you may also need to analyze the trace files of other work processes.
     If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 800 -u: SAPUSER -l: E -s: DM0 -i: sapserver_DM0_01 -w: 0 -d: 20091226 -t: 135942 -v: RABAX_STATE -e: UNCAUGHT_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Best Regards,
BDP

hi
It is the Fully Qualified Domain Name (FQDN) error . Refer SAP online help :
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/67/be9442572e1231e10000000a1550b0/frameset.htm
refer the similar thread :
Problem executing sample Webdynpro application
regards,
amit

Runtime error while executing New Hire action in PA40

Hi All,i am getting short dump while executing PA40 for new hire action typecan anyone look into this and guide as i am new to HCMNote: getting dump only for one user id for rest all other user id i am not getting dump.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           /1PAPAXX/HDR_21000A
Application Component Not Assigned
Date and Time          21.08.2014 14:07:03
Short text
    Syntax error in program "/1PAPAXX/HDR_21000A ".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
    The following syntax error occurred in program "/1PAPAXX/HDR_21000A " in
    include "/1PAPAXX/HDR_21000AO01 " in
    line 52:
    ""LV_LENGTH" has already been declared"
    The include has been created and last changed by:
    Created by: "HCM04 "
    Last changed by: "HCM03 "
    Error in the ABAP Application Program
    The current ABAP program "SAPFP50M" 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 "/1PAPAXX/HDR_21000A ".
    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 /1PAPAXX/HDR_21000A :
    ""LV_LENGTH" has already been declared"
How to correct the error
    Probably the only way to eliminate the error is to correct the program.
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
System environment
    SAP Release..... 731
    SAP Basis Level. 0007
    Application server... "dc-ds-erp"
    Network address...... "172.16.23.111"
    Operating system..... "Linux"
    Release.............. "3.0.13-0.27-default"
    Hardware type........ "x86_64"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 1
    Shortdump setting.... "full"
    Database server... "dc-ds-erp"
    Database type..... "ORACLE"
    Database name..... "ECD"
    Database user ID.. "SAPSR3"
    Terminal.......... "NLC-HP"
    Char.set.... "C"
    SAP kernel....... 720
    created (date)... "Sep 14 2013 06:16:24"
    create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr130820"
    Database version. "OCI_112, 11.2.0.3.0, V1, default"
    Patch level. 500
    Patch text.. " "
    Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*"
    SAP database version. 720
    Operating system..... "Linux 2.6, Linux 3"
    Memory consumption
    Roll.... 0
    EM...... 37708200
    Heap.... 0
    Page.... 106496
    MM Used. 4666776
    MM Free. 3709976
User and Transaction
    Client.............. 210
    User................ "HCM03"
    Language key........ "E"
    Transaction......... "PA40 "
    Transaction ID...... "53EF470299AB5D67E1000000AC10176F"
    EPP Whole Context ID.... "005056A301D11EE48A9D08B337F884E3"
    EPP Connection ID....... 00000000000000000000000000000000
    EPP Caller Counter...... 0
    Program............. "SAPFP50M"
    Screen.............. "MP000000 1000"
    Screen Line......... 3
    Debugger Active..... "none"
Information on where terminated
    Termination occurred in the ABAP program "SAPFP50M" - in
    "GET_HEADER_WITH_TCLAS".
    The main program was "MP000000 ".
    In the source code you have the termination point in line 146
    of the (Include) program "FP50MDHD".
Source Code Extract
Line
SourceCde
116
CALL FUNCTION 'HR_HEADER_GET'
117
      EXPORTING
118
           DHDID                    = FHD_HID
119
           BEGDA                    = BEGDA
120
           TCLAS                    = TCLAS
121
* Es wird nur einer der folgenden 3 Parameter benutzt.
122
* Ausgewertet wird zunaechst MOLGA, dann P0001 dann PERNR.
123
* Der erste der nicht initial ist wird ausgewertet.
124
*           MOLGA                   =
125
           P0001                    = P0001
126
           PERNR                    = PSPAR-PERNR
127
      IMPORTING
128
           PROG                     = HEADER_PROG
129
           DNUM                     = HEADER_DYNNR
130
       EXCEPTIONS
131
            HEADER_DEACTIVATED          = 1
132
            HEADER_UNKNOWN              = 2
133
            HEADER_GENERATE_DEACTIVATED = 3
134
            HEADER_GENERATE_FAILED      = 4
135
            INTERNAL_ERROR              = 5
136
            OTHERS                      = 6.
137
138
IF NOT SY-SUBRC IS INITIAL.
139
* Bei Problemen gibt's eben ein leeres Dynpro.
140
    HEADER_PROG = 'SAPMP50A'.
141
    HEADER_DYNNR = '0090'.
142
ELSE. " NOT sy-subrc IS INITIAL.                                   "
143
* Dann setzen wir jetzt auch noch das Datum fest.
144
    PERFORM HEADER_BEGDA_SET IN PROGRAM (HEADER_PROG) USING BEGDA.
145
* Und schalten auf Uebergabe der PERNR mit globalen Variablen.
>>>>>
    PERFORM HEADER_LAZY_ON IN PROGRAM (HEADER_PROG).
147
ENDIF. " (ELSE) NOT sy-subrc IS INITIAL.                           "
148
* Merken wie der Header heisst. Damit MPPERS00 sich erinnern kann.
149
* Wird mit Einfuehrung des Headerobjekts obsolet.
150
PERFORM REMEMBER_HEADER "                             "XYVPH4K015649
151
    USING HEADER_PROG HEADER_DYNNR 'S'. "               "XYVPH4K015649
152
ENDFORM.
153
154
*       FORM RE588I                                                   *
155
156
157
158
* --> T588I_DHDID                                                   *
159
* --> T588I_MOLGA                                                   *
160
* --> T588I_TCLAS

Implement SAP Note 1004280.. your issue if fixed
If your issue is resolved request you to close the thread or else free feel to touch base
BR
Anil

RSIMPCURR: Runtime error while executing

Hi Everyone,
I want to create a process chain to transfer global settings from my ECC system to the BI system. For this purpose I was checking the ABAP program RSIMPCURR which is used to transfer the currecny exchange rates. But when this program is executed, it throws a runtime error and ends with a dump.
Here's a snippet of the ABAP dump:
151   CALL FUNCTION 'RSAR_DESTINATION_GET'
152     EXPORTING
153       i_logsys      = l_source
154     IMPORTING
155       e_destination = l_destination
156     EXCEPTIONS
157       not_exist     = 1
158       OTHERS        = 2.
159   IF sy-subrc <> 0.
' >>>>>     MESSAGE x000(rh).
161   ENDIF.
162
The thing is, when I manually transfer the currencies from the RSA1 > Source system screen, I'm not facing any issues. Its only while executing the program that I get the dump.
Any suggestions?
Thanks,
Ram

Hi,
I don't think this is a resource issue, because the global settings get transferred when I do it from RSA1 > Source system.
Also the FM 'RSAR_DESTINATION_GET' is the one that throws the exception 'Cannot find destination'. I think this is because I cannot enter the Source System in the program parameters because it is disabled. The other parameters (like 'Exchange Rate type' and 'Changes since') are not disabled and I'm able to enter the selections into those.
Is there anyway that I can enable the source-system box and provide my source system as a location extract the currencies?

Runtime error while executing VA01

Hi All,
I'm getting ABAP dump while executing VA01. Especially while doing variant configurations.
Please have a look into following dump.
Category               ABAP Programming Error
Runtime Errors         SYNTAX_ERROR
ABAP Program           SAPMV45A
Application Component SD-SLS
Date and Time          15.12.2011 00:37:01
     Short text
          Syntax error in program "SAPMV45A ".
     What happened?
          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 "SAPMV45A " in include
           "DI_ESD_SAPMV45A===============E " in
          line 184:
          ""TEXT" has already been declared"
          The include has been created and last changed by:
          Created by: "SAP "
          Last changed by: "SANJAY "
          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.
     What can you do?
          Please eliminate the error by performing a syntax check
          (or an extended program check) on the program "SAPMV45A ".
          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 SAPMV45A :
          ""TEXT" has already been declared"
     How to correct the error
          Probably the only way to eliminate the error is to correct the program.
          If you cannot solve the problem yourself and want to send an error
          notification to SAP, include the following information:
          1. The description of the current problem (short dump)
             To save the description, choose "System->List->Save->Local File
          (Unconverted)".
          2. Corresponding system log
             Display the system log by calling transaction SM21.
             Restrict the time interval to 10 minutes before and five minutes
          after the short dump. Then choose "System->List->Save->Local File
          (Unconverted)".
          3. If the problem occurs in a problem of your own or a modified SAP
          program: The source code of the program
             In the editor, choose "Utilities->More
          Utilities->Upload/Download->Download".
          4. Details about the conditions under which the error occurred or which
          actions and input led to the error.
     System environment
          SAP Release..... 702
          SAP Basis Level. 0003
          Application server... "SANDERP"
          Network address...... "172.16.1.12"
          Operating system..... "Windows NT"
          Release.............. "6.0"
          Hardware type........ "4x AMD64 Level"
          Character length.... 16 Bits
          Pointer length....... 64 Bits
          Work process number.. 3
          Shortdump setting.... "full"
          Database server... "SANDERP"
          Database type..... "DB6"
          Database name..... "OLS"
          Database user ID.. "SAPOLS"
Thanks in Advance,
Uday

Hi
there is a syntax error in the user exit SAPMV45A created for VA01. Last change was done by sanjay.
Request your abap team to correct the syntax to resolve the issue.
Hope this is useful.
Regards,
Deepak Kori

ABAP Runtime Error while executing planning folder

Similar Messages

Maybe you are looking for