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

Similar Messages

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

Urgent(abap runtime error)

hi all,
when i tried to findout the name(collective search) by last name o'brien in PA20 OR PA30 transacton i got the abap runtime error in production
but when i tried samething in development and quality by lastname o'brein in PA20 OR PA30 TRANSACTION i got the 4 names .please let me know what is the problem . it is very urgent.
thanks in advance
rama.

Hi
What is the runtime error u got
Regards
Pavan

ABAP runtime error / DDIC_STRUCLENG_INCONSISTENT

Hi
I got a ABAP runtime error DDIC_STRUCLENG_INCONSISTENT / short dump while creating a pricing condition record.
The error is "accoring to the ABAP load, the structure should have been 1675 bytes long, according to information from ABAP dictionary at run time, the structure is 1756 bytes long".
To correct the error, there was option to regenerate the program SAPMV130. There were other options to look at SAP notes.
I tried regenerating program SAPMV130 and system is asking for access key which i don't have.
Is there any solution?
I am working on a standalone system.
Thanks

HI
Same problem has occured for me while reversing PGI.
I had re-activated the Data type using abaper.In runtime error,u can find data type
First u check whether the data type is inconsistent by
goto SE12, type ur data type then display,then goto Utilities -runtime object-display .here u can see there will be incosistent data type length
So finally goto SE11,there will be activate button ,save
I think ur problem will be solved
Raghu

Why do we call an ABAP Runtime error a "Short Dump"

Hi All,
I was just working on one of the ABAP runtime errors with my technical counterpart and a question came to my mind "Why do we call an ABAP Runtime error a "Short Dump"?".
I tried asking a few friends of mine working in the technical space in SAP and they were not able to answer.
So, some one of you experts help me getting answer to this question.
Thanks in Advance.
Nitin.

ABAP Runtime error is a generalized term .......... meaning the error occured while runtime.
wheare as short dump.
Short - means brief.
dump - error information from the memory
Short dumps (also called ABAP memory dumps). Short dumps occur when an ABAP program fails.
Short dumps provide basic information about which program failed and what the error was.
hope this helps.

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

OPEN_DATASET_NO_AUTHORITY abap runtime errors

Hi,
I have a custom ABAP program which outputs a file to UNIX and then FTP this file to a NT share drive. I have no problem executing this program using my ID. I checked using AL11 that the creator of the file in UNIX is DEVADM & not my user id.
However ,when my user uses this same program to execute, she gets an ABAP runtime error "OPEN_DATASET_NO_AUTHORITY" and the error points to failure at this statement
open dataset filelocation for output in text mode.
It says that the user does not have authorization for this.
Can someone advise me on what authorization I should add in for the user using PFCG Change activity group?
I tried adding the S_DATASET object in the AG.
Manually   Basis: Administration                                        BC_A
Manually   Authorization for File Access                                S_DATASET
5       Manually   Authorization for File Access                                T-DV48009400
Activity                       33, 34                                                                      ACTVT
          Physical file name             Assets*                                                                     FILENAME
          ABAP program name              YZFAU007                                                                    PROGRAM
but during transportation of this activity grup using SCC1 i got the error. Can sonmeone please advise me the right way to resolve this problem? Thanks!
No authorization to change file /usr/sap/trans/log/CC004492.DEV
Message no. PU 808
Diagnosis
When working with the Workbench Organizer, you tried to access certain
    operating system files to change them.
To avoid competing file accesses, semaphore files are created beforehand
    which are deleted again when the respective file change has been
    completed.
You are not authorized to delete such semaphore files. To avoid
    inconsistencies and deadlocks, creation of semaphore files as well as
    the actual file access required is forbidden in this case.
System Response
The function is terminated.
Procedure
The file access authorizations are assigned via the authorization object
   S_DATASET.
First obtain the authorizations generally provided for this object if
   you want to work with the Workbench Organizer.

hi, I read throught the sap notes, 1st one not avail, 2nd one requies BW support package, last one is sql truncate table note which don't look relevant.
I read through the other thread, my purrpose is not to restrict or catch the error, my purpose is to add authorization for my user so that she is able to run '----> open dataset filelocation for output in text mode' without the open_dataset_no_authorization runtime error.
I have already added in the S_dataset object in the AG,
Manually   Authorization for File Access
   Activity                       Read, Write
   Physical file name             Assets*
   ABAP program name              YZFAU007
but i encountered error during transport SCC1 as indicated above, so I wonder if the PFCG change AG is right.

ABAP runtime errors    LIST_NO_PAGETAB

Hi experts,
I got the below runtime error while debugging the finished background job in SM37.
i followed the below steps,
1) select the JOb which i want to debugg
2) then enter the JDBG tcode in command prompt and click on Enter then the below runtime error occured.
Pls any one explain why the below dump occured.
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLKKBL " in
"K_KKB_LIST_DISPLAY".
The main program was "SAPLBTCH ".
The termination occurred in line 307
of the source code of program "LKKBLU01 " (when calling the editor 3070).
Source code extract
002770
002780       l_fieldcat_state = '2'.
002790       l_sort_state = '2'.
002800       call function 'ALV_EXPORT_TO_BUFFER_KKBLO'
Regards,
Ashok

Hi,
> The termination occurred in line 307
> of the source code of program "LKKBLU01 " (when calling the editor 3070).
As indicated, it's in line 307, or more precisely 3070 in the dump. Please, paste the lines around this line.
Sandra
Edited by: Sandra Rossi, 2 minutes later:
Did you search SAP notes? I found this one : Note 901876 - Input help in lists, context menu in lists

ABAP Runtime error MESSAGE_TYPE_X in process chain

in our daily load process chain we have a level where datas are getting loaded in to a cube from 4 dso thru dtp. in this level the DTP fails approximately twice in a week. the DTP is shown in red in the log view. when we check the message its showin MESSAGE_TYPE_X ABAP runtime error.
if we give repeat it runs sucessfully and the following process are going well.
do u ppl have any ideas abt this.

Hi,
This failure would happen for many reasons, like,
Source system connection failure
Short dump.
System overload
Non availability od work processes as a reasonthe load would have been timed out.
Locked due to another load.
That is the reason as to which the load when repeated is successful, as by then,
The source connection would have been restored
there would be free processes available
The other load would have completed.
Regards,
Savitha

ABAP runtime error: snap_no_new_entry

Hi All,
We got the above error.
We tried ST22 --> Go to --> Till here I can go only.....I am not able to Reorganize.
As well as I tried Reorganize again its Throw the DUMP.
Plz Suggest Other Answer.
Regards,
Rableen

Hi Rableen,
ABAP runtime error: snap_no_new_entry.
The error implies SNAP table is full in the SAP system and it cannot write new entries. Since you tried to perform reorganize using ST22 and it failed, I would request you to do the following
1) Check whether Transaction log is full. If yes, then either take backup of transaction log or shrink the same.
2) Restart SAP and database.
3) Repeat the ST22 dump Re-organization process.
Hope this helps.
Regards,
Deepak Kori

Abap runtime error UNICODE_TYPES_NOT_CONVERTIBLE occured

Hi,ecpert:
I have encountered one abap runtime error UNICODE_TYPES_NOT_CONVERTIBLE
and the main logic list below:
First, I define one parameter which user can input from selection screen.
PARAMETERS:P_TABNAM LIKE DD03L-TABNAME .
Then, I get the dynamic internal table based on P_TABNAM .
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = ifc
 IMPORTING
 ep_table = dy_table.
ASSIGN dy_table->* TO <dyn_table> .
Then, after filling data to <dyn_table>, I want to modify the (P_TABNAM).
MODIFY (P_TABNAM) from TABLE <dyn_table>.
And when I run this program , one runtime error UNICODE_TYPES_NOT_CONVERTIBLE occurred.
Pls give suggestions, thanks.

Quite appreciate your help, I tried this T-code
however, I got no information after run it with my program name
In addition, this program can be activated properly in ABAP editor,and error occured
when execute the 'Modify' clause.

ASN Error on Save / publish -"Posting Illegal Statement" ABAP Runtime error

Hi All,
I am working on the ASN Scenario in SNC 7.0. Whenever I create an ASN in the SNC web UI and Save or/and Publish it, the following actions occur:
1. I get the message "ASN got saved / published successfully" in the SNC Web UI
2. Everytime I do this, a ABAP runtime error gets logged in the system. The Runtime Error is "Posting_Illegal_Statement" (seen under ST22)
3. I do not see any XML messages in SXI_Monitor.
4. I do not see any log entries in SLG1
Can anyone explain how to debug this error and what may be the possible causes for this error?
Also can anyone explain how to send the XML messages manually using the report "/N/SCA/DLV_PUBLISH". Whats the config / action needed to trigger the XML and send it to PI?
Thanks,
Bharath

Hallo,
I have had the same problem. The ASN coding crashed and I could not reprocess the ASN posting within the PPF.
The ABAP /SCA/DLV_PUBLISH checks, wether the ASN is meant to be sent by the PPF. Just overwrite the check within the debugger and the ASN will be posted via a XML message.
Set gs_dlv-send_mode to 'D' within the debugger.
In ABAP
Publish ASN
PERFORM publish_asn.
Form publish_asn
IF gs_dlv-send_mode <> /scmb/cl_c_order=>gc_publ_method_direct. -
>> Set Mode in debugger
 MESSAGE ID '/SCA/DM'
 TYPE 'I'
 NUMBER '136'
 WITH lv_asn_number.
 gv_error = 'X'.
 RETURN.
ELSE.
Regards
Martin
Edited by: Martin Renardy on Oct 20, 2011 1:32 PM
Edited by: Martin Renardy on Oct 20, 2011 1:42 PM
Edited by: Martin Renardy on Oct 20, 2011 1:43 PM

Finding the transaction of an abap runtime error

hello,
is it possible to find out the corresponding transaction to an abap runtime error?
till now i've got all informations like they are shown in ST22 in my abap program. but i'd also like to have the transaction code, not only the corresponding devclass, subapplication and application.
does anyone know a function module or any other solution for that problem?
thanks in advance
joschi

When you are analyzing your short dump via ST22, there is a section called "User, transaction..." where the following information is shown:
Client
User
Language key
Transaction
Program
Screen
That section will show you the transaction code you need.
I hope that helps,

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

Similar Messages

Maybe you are looking for