ABAP 7 - Runtime Errors
Hi,
I need a documentation about ABAP 7 and the possibles runtime errors.
Thanks.
Rafael.
Message was edited by:
Rafael Rocha
Hi rafeal
Plss refer to thid link
<a href="http://">This problem was discussed in a blog at /people/bjoern.mielenhausen/blog/2005/04/25/the-new-abap-editor
<b>
"Donot forgot to reward points if helpful"</b>
Regards
hitesh
Similar Messages
-
ABAP/4 runtime error SNAP_NO_NEW_ENTRY
Hi All,
I am unable to login in to my SAP server, after entering user id and password, the below ABAP Dump is displayed
ABAP/4 runtime error SNAP_NO_NEW_ENTRY
I have checked the SAP notes, but no luck
Please advise
SAPXPTHello,
SAP note 17537 describes the following :
The error may be caused by the following:
- Table SNAP is full,
- short dump was not written due to database problems,
- short dump has already been solved by reorganization.
So check if the SNAP table is full or if there is a general database problem.
Probably it is the last one, maybe a connection problem to the DB, archiver stuck, ...
Can you still connect to the database with the command : R3trans -d
Merry Christmas,
Wim Van den Wyngaert -
Hi,
I have a problem with my BI7 sandbox system. If I do any changes or modifycations in BI7 system it`s giving ABAP rentime error.
Runtime Errors: SAPSQL_INVALID_TABLENAME
Except. CX_SY_DYNAMIC_OSQL_SEMANTICS
Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
not caught in
procedure "RSDU_DATA_EXISTS_TABLE_DB6" "(FUNCTION)", nor was it propagated by a
RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
An invalid table name "/BI0/D0PT_C012" was specified in an Open SQL command:
Due to one of the following reasons, the error occurs only at runtime:
- the table name was specified dynamically, or
- the SELECT clause, WHERE clause, GROUP-BY clause, HAVING clause, or
ORDER-BY clause was specified dynamically.
I thought problem could be memory or tables space problem. I was infirmed to basis people. Basis people checked and said that there is enough dabase space and table space.
Does anybody can help on this.
Thanks in advance,
VenkatHi...
Re: SAPSQL_TABLE_NOT_FOUND
Error in SQL Statement: SAPSQL_INVALID_TABLENAME
This may help you.........
Regards,
Debjani......... -
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.
ThanksHI
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 -
Runtime Error : UNCAUGHT_EXCEPTION
Hi Solman Experts,
While downloading softwares through Maintenace Optimizer ( Solution Manager ),I am getting below error..
First Error :
Function module /SDF/AL_MAP_TRANSID_LOGH does not exist.
The Maintenance Optimizer can automatically determine which files you require to update the ABAP and Java software components of your systems.
The search is performed for all instances of the selected systems flagged as relevant.
I have already checked in service market place and apply the SAP note 1135893 and we have activate the some components (BC Set)
See Note 898614 after that i am getting big problem.
Second Error : ( ABAP Dump )
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_SOCM_NOT_IMPLEMENTED
Date and Time 31.03.2008 15:04:31
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_SOCM_NOT_IMPLEMENTED' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_CHM1_CHANGE_REQU_INSTANCE==CP' has to be
terminated.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_SOCM_NOT_IMPLEMENTED', was not
caught and
therefore caused a runtime error.
The reason for the exception is:
An exception occurred
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
*"UNCAUGHT_EXCEPTION" "CX_SOCM_NOT_IMPLEMENTED"
"CL_CHM1_CHANGE_REQU_INSTANCE==CP" or "CL_CHM1_CHANGE_REQU_INSTANCE==CM009"
"IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION"*
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "ALBE0510"
Network address...... "10.201.180.10"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "4x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "ALBE0510"
Database type..... "MSSQL"
Database name..... "SP0"
Database user ID.. "sp0"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Oct 23 2007 00:33:51"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 133
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 41898400
Heap.... 0
Page.... 40960
MM Used. 33604960
MM Free. 4099184
User and Transaction
Client.............. 001
User................ "KONS222"
Language key........ "E"
Transaction......... "DSWP "
Transactions ID..... "AE21FFDCBA44F199AB15005056836080"
Program............. "CL_CHM1_CHANGE_REQU_INSTANCE==CP"
Screen.............. "RDSMOP_MAIN 0100"
Screen line......... 5
Information on where terminated
Termination occurred in the ABAP program "CL_CHM1_CHANGE_REQU_INSTANCE==CP" -
in "IF_EX_SOCM_CHECK_CONDITION~CHECK_CONDITION".
The main program was "RDSMOP_MAIN ".
In the source code you have the termination point in line 612
of the (Include) program "CL_CHM1_CHANGE_REQU_INSTANCE==CM009".
Source Code Extract
Line
SourceCde
582
conditions_ok = cl_socm_integration=>false.
583
ENDIF.
584
ENDIF.
585
586
WHEN 'S_USER_CHECK'.
587
conditions_ok = cl_socm_integration=>true.
588
CALL METHOD cl_sm_base_sender=>get_assigned_suser
589
EXPORTING
590
i_no_dialogue = 'X'
591
IMPORTING
592
e_suser = e_suser
593
e_partner_no = lv_parnr
594
EXCEPTIONS
595
no_user_assigned = 1
596
no_customer_number = 2
597
OTHERS = 3.
598
IF sy-subrc = 1 OR sy-subrc = 3.
599
conditions_ok = cl_socm_integration=>false.
600
ENDIF.
601
WHEN 'NO_CRTCL_OBJ'.
602
conditions_ok = me->check_crtcl_obj( ).
603
WHEN '0NO'.
604
conditions_ok = cl_socm_integration=>false.
605
WHEN '0YES'.
606
conditions_ok = cl_socm_integration=>true.
607
WHEN '0BREAK'.
608
BREAK-POINT. "#EC NOBREAK
609
WHEN space.
610
avoid exception since it is the default in table TSOCM_COND_MAPP
611
WHEN OTHERS.
>>>>>
RAISE EXCEPTION TYPE cx_socm_not_implemented.
613
ENDCASE.
614
615
ENDMETHOD.
Please suggest. Thanks in Advance...
Regards,
Suresh KumarHi Ruben,
I have Implemented both notes now i am getting differt error...
Error is : Error No customer numbers in transaction AISUSER ...
Message Number: SOLMAN_SAP_BACKEND016
Diagnosis
There are no entries with a customer number in the 'Customer Number' field in the table AISUSER.
System Response
You cannot get customer number-specific RFC destinations.
Procedure
Maintain these entries manually or start the report
SMBI_AISUSER_VAR_MIG to copy any existing customer number from the table AISDK_CF_OSS_USR.
Please suggest..
Thanks in Advance..
Regards,
Suresh Kumar
Edited by: suresh k on Apr 15, 2008 3:15 PM -
Runtime Errors: COMPUTE_INT_MINUS_OVERFLOW
Dear experts:
When I execute a program which was developed by ours ABAPer, the runtime error will happen.
The detail error information as follows (error happens in program "LSTXBCTB3" at 010730):
Runtime Errors COMPUTE_INT_MINUS_OVERFLOW
Exception CX_SY_ARITHMETIC_OVERFLOW
010640 endloop.
010650 if sy-subrc = 0.
010660 append l_otfline to l_lastinfo.
010670 endif.
010680 * get corrected value for l_blockpos: should be the position
010690 * set by the command of 'positioning' (last in the block).
010700
010710 * look for 'last' ST command
010720 l_index = l_blockend.
010730 while l_flag eq c_true.
> l_index = l_index - 1.
010750 read table p_cell_otf into l_otfline index l_index.
010760 if l_otfline-tdprintcom <> pc_id_codepage and
010770 l_otfline-tdprintcom <> pc_id_call_font and
010780 l_otfline-tdprintcom <> pc_id_space_width and
010790 l_otfline-tdprintcom <> pc_id_uline and
010800 l_otfline-tdprintcom <> pc_id_color_text and
010810 l_otfline-tdprintcom <> pc_id_move_to and
010820 l_otfline-tdprintcom <> pc_id_md_after_par.
010830
010840 l_flag = c_false.
010850 endif.
010860 endwhile.
Anyone who can help me to solve the problem? Thanks a million!
Edited by: Guo Qing Wu on Dec 17, 2007 8:49 AM
Edited by: Guo Qing Wu on Dec 17, 2007 8:54 AM
Edited by: Guo Qing Wu on Dec 17, 2007 8:55 AM
Edited by: Guo Qing Wu on Dec 17, 2007 8:57 AMError analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_ARITHMETIC_OVERFLOW',
was neither
caught nor passed along using a RAISING clause, in the procedure
"TAB_SPLIT_CELL" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
In the current program "SAPLSTXBC ", subtracting the number 1 from
the number "-2147483648" (using the operation - or 'SUBTRACT') resulted
in a value either greater than 2147483647 or smaller than
-2147483648. This results in a whole number overflow.
How to correct the error
The exception must either be prevented, caught within the procedure
"TAB_SPLIT_CELL"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
You may be able to split the process into separate components, so that
the values generated are smaller.
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "yihai-appl1"
Network address.......... "10.10.10.161"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x Intel 80686"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 4
Short dump setting....... "full"
Database server.......... "DB-YIHAI"
Database type............ "MSSQL"
Database name............ "PRD"
Database owner........... "prd"
Character set............ "Chinese_CHN.936"
SAP kernel............... "620"
Created on............... "Dec 19 2004 22:59:44"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "SQL_Server_7.00 "
Patch level.............. "1773"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"
User, transaction...
Client.............. 888
User................ "ZHANGLUWEI"
Language key........ 1
Transaction......... "ZSD136 "
Program............. "SAPLSTXBC "
Screen.............. "ZDIA_SD_KERRY_DO 0601"
Screen line......... 25
Information on where termination occurred
The termination occurred in the ABAP program "SAPLSTXBC " in "TAB_SPLIT_CELL".
The main program was "ZDIA_SD_KERRY_DO ".
The termination occurred in line 1074 of the source code of the (Include)
program "LSTXBCTB3 "
of the source code of program "LSTXBCTB3 " (when calling the editor 10740).
Processing was terminated because the exception "CX_SY_ARITHMETIC_OVERFLOW"
occurred in the
procedure "TAB_SPLIT_CELL" "(FORM)" but was not handled locally, not declared
in the
RAISING clause of the procedure.
The procedure is in the program "SAPLSTXBC ". Its source code starts in line
897
of the (Include) program "LSTXBCTB3 ".
Source code extract
010440 append l_otfline to l_lastinfo.
010450 exit.
010460 endif.
010470 if l_otfline-tdprintcom = pc_id_call_font.
010480 exit.
010490 endif.
010500 endloop.
010510 endif.
010520 * find last UL command
010530 loop at p_cell_otf into l_otfline
010540 to l_blockend
010550 where tdprintcom = pc_id_uline.
010560 endloop.
010570 if sy-subrc = 0.
010580 append l_otfline to l_lastinfo.
010590 endif.
010600 * find last CT command
010610 loop at p_cell_otf into l_otfline
010620 to l_blockend
010630 where tdprintcom = pc_id_color_text.
010640 endloop.
010650 if sy-subrc = 0.
010660 append l_otfline to l_lastinfo.
010670 endif.
010680 * get corrected value for l_blockpos: should be the position
010690 * set by the command of 'positioning' (last in the block).
010700
010710 * look for 'last' ST command
010720 l_index = l_blockend.
010730 while l_flag eq c_true.
> l_index = l_index - 1.
010750 read table p_cell_otf into l_otfline index l_index.
010760 if l_otfline-tdprintcom <> pc_id_codepage and
010770 l_otfline-tdprintcom <> pc_id_call_font and
010780 l_otfline-tdprintcom <> pc_id_space_width and
010790 l_otfline-tdprintcom <> pc_id_uline and
010800 l_otfline-tdprintcom <> pc_id_color_text and
010810 l_otfline-tdprintcom <> pc_id_move_to and
010820 l_otfline-tdprintcom <> pc_id_md_after_par.
010830
010840 l_flag = c_false.
010850 endif.
010860 endwhile.
010870
010880 if l_otfline-tdprintcom = pc_id_string.
010890 * find last MT or MB command
010900 loop at p_cell_otf into l_otfline
010910 to l_index
010920 where tdprintcom = pc_id_move_to or
010930 tdprintcom = pc_id_md_after_par.
Contents of system fields
SY field contents..................... SY field contents.................
SY-SUBRC 4 SY-INDEX -2147483641
SY-TABIX 0 SY-DBCNT 0
SY-FDPOS 3 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY MAIN2000
SY-UCOMM PREV SY-TITLE KerryÒÔ¶Ô·½Îª×¼·½°¸ÊµÏÖ
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
17 FORM TAB_SPLIT_CELL
SAPLSTXBC
LSTXBCTB3 1074
16 FORM TAB_SPLIT_LINE_OTF
SAPLSTXBC
LSTXBCTB3 681
15 FORM TAB_END_ROW
SAPLSTXBC
LSTXBCTB2 510
14 FORM TAB_ROW_END
SAPLSTXBC
LSTXBCTB2 109
13 FUNCTION SSFCOMP_TABLE_ROW_END
SAPLSTXBC
LSTXBCU44 9
12 FORM %EV2
/1BCDWB/SAPLSF00000039
/1BCDWB/LSF00000039F01 1133
11 FORM %WI3_BODY
/1BCDWB/SAPLSF00000039
/1BCDWB/LSF00000039F01 688
10 FORM %WI3
/1BCDWB/SAPLSF00000039
/1BCDWB/LSF00000039F01 645
9 FORM CALLBACK
SAPLSTXBC
LSTXBCFDC 258
8 FORM PROCESS_PAGES
SAPLSTXBC
LSTXBCFDC 220
7 FUNCTION SSFCOMP_PROCESS_DOCUMENT
SAPLSTXBC
LSTXBCU03 106
6 FUNCTION /1BCDWB/SF00000039
/1BCDWB/SAPLSF00000039
/1BCDWB/LSF00000039U01 375
5 FORM SMART_PRINT
ZDIA_SD_KERRY_DO
ZINC_SD_KERRY_DO_0601 168
4 MODULE (PAI) TC_0601_USER_COMMAND
ZDIA_SD_KERRY_DO
ZINC_SD_KERRY_DO_0601 87
3 FORM LOAD_DO_NO61
ZDIA_SD_KERRY_DO
ZINC_SD_KERRY_DO_0601 51
2 MODULE (PAI) PAI_2000
ZDIA_SD_KERRY_DO
ZINC_SD_KERRY_DO_MAIN 533
1 EVENT END-OF-SELECTION
ZDIA_SD_KERRY_DO
ZINC_SD_KERRY_DO_MAIN 34
sen variables
17 FORM TAB_SPLIT_CELL
Is it enough? Thanks a lot for your great help. -
error analysis as in ST22 TRANSACTION:
AN EXCEPTION OCCURED THE EXCEPTION ASSIGNED TO CLASS CX_SY_CONVERSION_NO_NUMBER WAS NOT CAUGHT WHICH LED TO AN ERROR. THE REASON FOR THIS EXCEPTION IS :
THE PROGRAM TRIED TO INTERPRET VALUE ':4' AS NUMBER SINCE THE VALUE CONTRAVENES THE CORRECT NUMBER FORMAT THIS WAS NOT POSSIBLE.
ATTACHED IS MY PROGRAM
REPORT ZVXR0303
LINE-COUNT 60(3)
LINE-SIZE 132
MESSAGE-ID VN.
Tables: VBEP, VBAP, NAST.
DATA: BEGIN OF HEADER,
ORDER(15) VALUE 'ORDER',
LINE(5) VALUE 'LINE',
MATERIAL(14) VALUE 'MATERIAL',
DUE(15) VALUE 'DUE (MAD)',
CREATED(10) VALUE 'CREATED',
QTY(10) VALUE 'QUANTITY',
KEY(5) VALUE 'KEY',
TYPE(5) VALUE 'TYPE',
END OF HEADER.
DATA: Begin of IDAT OCCURS 0,
VBELN LIKE VBAP-VBELN,
POSNR LIKE VBAP-POSNR,
werks LIKE VBAP-WERKS,
cuobj LIKE vbap-CUOBJ,
MBDAT LIKE vbep-mbdat,
ERDAT LIKE VBAP-ERDAT,
MATNR LIKE VBAP-MATNR,
KWMENG LIKE VBAP-KWMENG,
QTY TYPE I,
END of IDAT.
class cl_abap_char_utilities definition load.
constants: tab type c value cl_abap_char_utilities=>HORIZONTAL_TAB.
DATA: t_record(1000) TYPE C.
DATA: C_KWMENG(20) TYPE C.
data: OUTFILE(50) value '/usr/users/ftpsapfi/locks_540318'.
DATA: BEGIN OF TKOMCON OCCURS 50.
INCLUDE STRUCTURE CONF_OUT.
DATA: END OF TKOMCON.
DATA: iKEY TYPE I,
offset TYPE I,
KeyTypeLOC TYPE I,
KeyNumberLOC TYPE I,
type(15) TYPE C.
select-options: sVBELN FOR VBEP-VBELN obligatory,
sMAD FOR VBEP-MBDAT obligatory,
sERDAT FOR VBAP-ERDAT,
sMATNR FOR VBAP-MATNR,
sWERKS FOR VBAP-WERKS,
sKWMENG FOR VBAP-KWMENG.
SELECT
vbap~vbeln
vbap~POSNR
vbap~werks
vbap~cuobj
VBEP~MBDAT
VBAP~ERDAT
VBAP~MATNR
VBAP~KWMENG
INTO CORRESPONDING FIELDS of IDAT
FROM ( VBEP INNER JOIN VBAP ON vbepvbeln = vbapvbeln
AND vbepposnr = vbapposnr )
WHERE BMENG > 0
AND vbep~MBDAT IN sMAD
AND VBEP~VBELN in sVBELN
AND VBAP~werks IN sWERKS
AND VBAP~ERDAT IN sERDAT
AND VBAP~MATNR IN sMATNR
AND VBAP~KWMENG IN sKWMENG
AND VBAP~ABGRU = SPACE.
APPEND IDAT.
ENDSELECT.
PERFORM TOP-OF-PAGE.
if sy-batch = 'x'.
OPEN DATASET OUTFILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
TRANSFER t_record TO OUTFILE.
endif.
IF SY-SUBRC = 0.
LOOP at IDAT.
write IDAT-KWMENG DECIMALS 0 TO C_KWMENG.
REFRESH TKOMCON.
CALL FUNCTION 'VC_I_GET_CONFIGURATION'
EXPORTING
INSTANCE = idat-cuobj
LANGUAGE = NAST-SPRAS
TABLES
CONFIGURATION = TKOMCON
EXCEPTIONS
OTHERS = 4.
LOOP AT TKOMCON
WHERE ATNAM = 'S_SK_SPEC_KEY' OR ATNAM = 'S_MK_SPEC_KEY'
OR ATNAM = 'S_SK_CONSC_KEY' OR ATNAM = 'S_MK_CONSC_KEY'.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
KeyTYPELOC = 0.
keynumberloc = 2.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
Else.
Offset = 0.
DO.
IF offset <= 9.
offset = offset + 1.
If TKOMCON-ATWRT+Offset(1) = ':'.
KeyTypeLOC = Offset + 1.
KeyNumberLOC = Offset + 3.
EXIT.
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
IDAT-KWMENG = TKOMCON-ATWRT(3).
PERFORM OUT-OF-RANGE-FOUND.
ENDIF.
ENDIF.
ENDIF.
ENDLOOP.
ENDLOOP.
ENDIF.
CLOSE DATASET OUTFILE.
FORM OUT-OF-RANGE-FOUND *
FORM OUT-OF-RANGE-FOUND.
WRITE: / IDAT-VBELN.
WRITE: 10 IDAT-POSNR.
WRITE: 20 IDAT-MATNR.
WRITE: 35 IDAT-MBDAT.
WRITE: 50 IDAT-ERDAT.
WRITE: 65(3) IDAT-KWMENG DECIMALS 0.
WRITE: 75 TKOMCON-ATWRT+KeyTypeLOC(6).
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
WRITE: 85 'Consecutive'.
ELSE.
WRITE: 85 'Specific'.
ENDIF.
IF TKOMCON-ATNAM = 'S_SK_CONSC_KEY'
OR TKOMCON-ATNAM = 'S_MK_CONSC_KEY'.
TYPE = 'Consecutive'.
ELSE.
TYPE = 'Specific'.
ENDIF.
* PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
IDAT-VBELN
IDAT-POSNR
IDAT-MATNR
IDAT-MBDAT
IDAT-ERDAT
C_KWMENG
TKOMCON-ATWRT+KeyTypeLOC(6)
TYPE
INTO t_record SEPARATED BY tab.
if sy-batch = 'x'.
TRANSFER t_record TO OUTFILE.
endif.
ENDFORM.
FORM TOP-OF-PAGE *
FORM TOP-OF-PAGE.
WRITE: / 'ORDER'.
WRITE: 10 'LINE'.
WRITE: 20 'MATERIAL'.
WRITE: 35 'DUE (MAD)'.
WRITE: 50 'CREATED'.
WRITE: 65 'QTY'.
WRITE: 75 'KEY'.
WRITE: 85 'TYPE'.
PREPARING A RECORD TO BE SENT TO FILE
CONCATENATE
header-ORDER
header-LINE
header-MATERIAL
header-DUE
header-CREATED
header-QTY
header-KEY
header-TYPE
INTO t_record SEPARATED BY tab.
ENDFORM.
THIS IS WORKING FINE WITH DIFFERENT RANGES BUT WHEN I USE RANGE
Sales Order 1250000 TO 2250000
MAD 01/18/2005 TO 03/02/2005
Material LOCK9250FR TO LOCK9250XF
PLANT 4500
IT GIVES THE RUNTIME ERROR I MENTIONED ABOVE
ANY HELP WOULD BE GREATLY APPRECIATED
THANKS.HI ROB YOUR REPLY LOOKS TO BE VERY CLOSE OTHER GUYS SAID IT MIGHT BE PROBLEM WITH VARIABLE C_KWMENG BUT I REMOVED THAT PIECE OF CODE WITH C_KWMENG BUT STILL I WAS GETTING THE ERROR ATTACHED IS THE COMPLETE ERROR DETAILS FROM ST22
Runtime Errors CONVT_NO_NUMBER
Exception CX_SY_CONVERSION_NO_NUMBER
Occurred on 09/29/2005 at 14:33:21
Unable to interpret "04:" as a number.
What happened?
Error in ABAP application program.
The current ABAP program "ZVXR0303" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
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.
Error analysis
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_CONVERSION_NO_NUMBER', was
not caught, which
led to a runtime error. The reason for this exception is:
The program attempted to interpret the value "04:" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
Integers are represented in ABAP using a sequence of digits and, in some
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[mantissa]E[sign][exponent]
[whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
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:
"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC
"ZVXR0303" or "ZVXR0303"
"START-OF-SELECTION"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "grrsap54"
Network address.......... "10.80.96.102"
Operating system......... "HP-UX"
Release.................. "B.11.11"
Hardware type............ "9000/800"
Character length......... 8 Bits
Pointer length........... 64 Bits
Work process number...... 3
Short dump setting....... "full"
Database server.......... "grrsap54"
Database type............ "ORACLE"
Database name............ "D01"
Database owner........... "SAPR3"
Character set............ "en_US.iso88591"
SAP kernel............... "640"
Created on............... "Aug 28 2005 20:25:49"
Created in............... "HP-UX B.11.00 A 9000/800"
Database version......... "OCI_920 "
Patch level.............. "88"
Patch text............... " "
Supported environment....
Database................. "ORACLE 8.1.7.., ORACLE 9.2.0.., ORACLE
10.1.0.."
SAP database version..... "640"
Operating system......... "HP-UX B.11"
User, transaction...
Client.............. 050
User................ "NSHAKER"
Language key........ "E"
Transaction......... "SE38 "
Program............. "ZVXR0303"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
The termination occurred in the ABAP program "ZVXR0303" in
"START-OF-SELECTION".
The main program was "ZVXR0303 ".
The termination occurred in line 156 of the source code of the (Include)
program "ZVXR0303"
of the source code of program "ZVXR0303" (when calling the editor 1560).
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
001260 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001270 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001280 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001290 ?
001300 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001310 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
001320 ? PERFORM OUT-OF-RANGE-FOUND.
001330 ? ENDIF.
001340 ? ENDIF.
001350 ? Else.
001360 ? Offset = 0.
001370 ? DO.
001380 ? IF offset <= 9.
001390 ? offset = offset + 1.
001400 ? If TKOMCON-ATWRT+Offset(1) = ':'.
001410 ? KeyTypeLOC = Offset + 1.
001420 ? KeyNumberLOC = Offset + 3.
001430 ? EXIT.
001440 ? ENDIF.
001450 ? ELSE.
001460 ? EXIT.
001470 ? ENDIF.
001480 ? ENDDO.
001490 ?
001500 ? TRANSLATE TKOMCON-ATWRT+KeyNumberLOC(4) USING ': '.
001510 ?
001520 ? IF TKOMCON-ATWRT+KeyNumberLOC(4) CO '0123456789 '.
001530 ? iKey = TKOMCON-ATWRT+KeyNumberLOC(4).
001540 ? IF ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'FR' AND iKey >= 454 )
001550 ? OR ( TKOMCON-ATWRT+KeyTypeLOC(2) = 'XF' AND iKey >= 1150 ).
? IDAT-KWMENG = TKOMCON-ATWRT(3).
001570 ? PERFORM OUT-OF-RANGE-FOUND.
001580 ? ENDIF.
001590 ? ENDIF.
001600 ? ENDIF.
001610 ? ENDLOOP.
001620 ? ENDLOOP.
001630 ? ENDIF.
001640 ? CLOSE DATASET OUTFILE.
001650 ?
001660 ? *----
001670 ? * FORM OUT-OF-RANGE-FOUND *
001680 ? *----
001690 ? * ........ *
001700 ? *----
001710 ? FORM OUT-OF-RANGE-FOUND.
001720 ?
001730 ? WRITE: / IDAT-VBELN.
001740 ? WRITE: 10 IDAT-POSNR.
001750 ? WRITE: 20 IDAT-MATNR.
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0 SY-INDEX 44
SY-TABIX 7 SY-DBCNT 1
SY-FDPOS 4 SY-LSIND 0
SY-PAGNO 2 SY-LINNO 18
SY-COLNO 94 SY-PFKEY
SY-UCOMM SY-TITLE Out of Range Keys
SY-MSGTY I SY-MSGID SF
SY-MSGNO 616 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4
Active calls / events
No.... Type........ Name..........................
Program
Include Line
Class
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
Chosen variables
1 EVENT START-OF-SELECTION
ZVXR0303
ZVXR0303 156
%_SPACE
2
0
SY-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
TKOMCON-ATWRT 04:XF1260
333543333222222222222222222222
04A861260000000000000000000000
KEYNUMBERLOC 5
0000
0005
SYST-REPID ZVXR0303
5555333322222222222222222222222222222222
A682030300000000000000000000000000000000
SY-LDBPG SAPDB__S
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
IKEY 1260
000E
004C
KEYTYPELOC 3
0000
0003
SY ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
SVBELN IBT00012500000002250000
44533333333333333333333
92400012500000002250000
IDAT-KWMENG ########
00000000
0000000C
TKOMCON-ATWRT+0(3) 04:
333
04A
SYST ###,####################################
0002000000000001000000000000000000000000
000C00020007000E00000001000A000000000000
... + 40 ###########^###<########################
0000000000050003000100080000000000000009
00010004000E000C000200040000000000000000
... + 80 ########################################
0000000000000000000000000000000000000000
0000000000000000000A00000000000000000000
... + 120 #######################################_
0000000000000000000000000000000000010005
00000000000000000000000000000000000A000F
... + 160 ############ÿÿ¹°XC############# E2 X1
000000000000FFBB540000000000000222432253
0000000A0000FF90830040000C0000C000520081
... + 200 000 ####__S 050
3332222222220000555222222222222222223332
0000000000000000FF3000000000000000000500
... + 240 00
222223322222222
000000000000000
OUTFILE /usr/users/ftpsapfi/locks_540318
2777277677267776766266667533333322222222
F532F53523F64031069FCF3B3F54031800000000
... + 40
2222222222
0000000000
Application Calls
No dump information available
Application Information
No dump information available
Internal notes
The termination occurred in the function "ab_Move" of the SAP
Basis System, specifically in line 529 of the module
"//bas/640_REL/src/krn/runt/abmove1.c#6".
The internal operation just processed is "MOVE".
The internal session was started at 20050929142552.
Active calls in SAP kernel
( 0) 0x4000000001751924 CTrcStack2 + 0x2bc dw.sapD01_DVEBMGS00
( 1) 0x4000000001751658 CTrcStack + 0x18 dw.sapD01_DVEBMGS00
( 2) 0x4000000001db7478 rabax_CStackSave__Fv + 0x100 dw.sapD01_DVEBMGS00
( 3) 0x4000000001dc3abc ab_rabax + 0x1e1c dw.sapD01_DVEBMGS00
( 4) 0x4000000001b44cb4 ab_cnverr__FiPcPCvN21T2 + 0x18c dw.sapD01_DVEBMGS00
( 5) 0x40000000016c96f8 ab_Move + 0x1910 dw.sapD01_DVEBMGS00
( 6) 0x40000000016d4434 ab_jmove__Fv + 0x384 dw.sapD01_DVEBMGS00
( 7) 0x4000000001022348 ab_extri__Fv + 0x17a0 dw.sapD01_DVEBMGS00
( 8) 0x4000000001726dc8 ab_xevent__FPCc + 0x38 dw.sapD01_DVEBMGS00
( 9) 0x40000000019f7efc ab_trigg__Fv + 0x94 dw.sapD01_DVEBMGS00
(10) 0x40000000019dc9ec ab_run + 0xc4 dw.sapD01_DVEBMGS00
(11) 0x4000000000f65e0c N_ab_run + 0x14 dw.sapD01_DVEBMGS00
(12) 0x4000000000f5fa88 dynpmcal + 0x198 dw.sapD01_DVEBMGS00
(13) 0x4000000000f5d500 dynppai0 + 0x830 dw.sapD01_DVEBMGS00
(14) 0x4000000000f5b8b4 dynprctl + 0x43c dw.sapD01_DVEBMGS00
(15) 0x4000000000f56728 dynpen00 + 0x2118 dw.sapD01_DVEBMGS00
(16) 0x400000000102f1b4 Thdynpen00 + 0x69c dw.sapD01_DVEBMGS00
(17) 0x400000000102e1e4 TskhLoop + 0x523c dw.sapD01_DVEBMGS00
(18) 0x4000000001022f50 tskhstart + 0x1e0 dw.sapD01_DVEBMGS00
(19) 0x4000000000dce3c4 DpMain + 0x484 dw.sapD01_DVEBMGS00
(20) 0x40000000022784cc nlsui_main + 0x14 dw.sapD01_DVEBMGS00
(21) 0x4000000000a39534 main + 0x14 dw.sapD01_DVEBMGS00
(22) 0xc00000000000a588 $START$ + 0xa0 /usr/lib/pa20_64/dld.sl
List of ABAP programs affected
Type Program Gen. Date Time Load Size
Prg ZVXR0303 09/29/2005 14:25:42 39936
Prg SAPMSSY0 05/01/2005 00:21:19 66560
Prg SAPMSSYD 06/05/2002 17:09:33 16384
Prg SAPFSYSCALLS 02/14/2002 14:22:47 6144
Prg RSDBRUNT 06/13/2004 00:43:20 226304
Typ RSSCR / / : m:15 5120
Prg RSDBSPBL 01/07/2003 18:47:02 59392
Prg SAPDB__S 02/14/2002 14:22:47 15360
Typ VARID 05/12/1997 16:51:30 4096
Prg %_CSYDB0 02/14/2002 14:22:46 28672
Prg RSDBSPVA 09/06/2005 22:54:22 112640
Prg SAPLSVAR 09/06/2005 22:57:28 625664
Typ VARIS 05/12/1997 15:27:21 2048
Typ RSVAMEMKEY 05/07/1997 13:07:49 2048
Prg RSDBSPMC 06/05/2002 17:09:26 66560
Typ DDSHDESCR 09/03/1997 03:05:16 3072
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ SPPARAMS 05/07/1997 13:10:38 2048
Typ RSSELINT 04/04/1995 16:12:37 2048
Prg SAPLICON 03/12/2004 06:57:52 23552
Prg %_CICON 02/14/2002 14:22:46 65536
Prg SAPLSABE 02/14/2002 14:22:47 11264
Prg SAPLSECU 05/23/2005 14:04:05 64512
Typ RSSUBINFO 10/14/1999 22:01:03 3072
Prg %_CRSDS 02/14/2002 14:22:46 8192
Typ RSDSEXPR 08/20/1998 10:57:18 2048
Prg SAPLDSYA 02/14/2002 14:22:47 39936
Prg SAPFSDS1 01/07/2003 18:32:17 47104
Typ TDCLD 11/02/1998 09:51:35 5120
Prg SAPLSDOD 04/30/2005 22:53:50 39936
Typ DOKIL 05/12/1997 16:46:17 3072
Prg SAPCNVE 02/14/2002 14:22:47 6144
Prg SAPLLANG 02/14/2002 14:22:47 8192
Typ T002 02/14/1998 10:24:58 2048
Typ RSEXFCODE 08/13/1997 12:52:57 1024
Prg SAPFSPOR 03/13/2004 19:20:44 12288
Prg SAPLOMCV 05/01/2005 00:14:10 16384
Prg CL_EXITHANDLER================CP 06/13/2004 00:40:58 26624
Prg SAPLSEXV 09/06/2005 22:55:26 107520
Prg CL_BADI_FLT_DATA_TRANS_AND_DB=CP 05/01/2005 00:21:35 33792
Typ SXS_ATTR 08/20/2001 12:23:27 4096
Typ V_EXT_ACT 11/09/2000 14:27:05 2048
Typ SXC_EXIT 11/09/2000 14:23:43 2048
Prg CL_EX_BADI_MATN1==============CP 05/01/2005 00:14:04 22528
Prg IF_EX_BADI_MATN1==============IP 06/13/2004 00:48:55 4096
Typ TMCNV 02/24/1999 03:33:25 3072
Prg SAPLSCNT 02/14/2002 14:22:47 24576
Typ DYCBOX 08/20/1998 11:16:53 2048
Prg SAPLSVSM 01/07/2003 18:35:45 22528
Prg SAPLSGUI 01/09/2003 17:15:12 31744
Prg SAPLSTTM 05/01/2005 00:24:04 75776
Prg SAPLSBDC 05/23/2005 14:05:19 38912
Prg CL_DATAPROVIDER===============CP 02/14/2002 14:22:46 40960
Prg %_CCNTL 02/14/2002 14:22:46 13312
Typ OBJ_RECORD 02/14/1998 08:30:43 2048
Prg SAPLSTUP 05/23/2005 14:03:46 65536
Prg SAPLCNDP 05/23/2005 14:05:47 167936
Prg SAPFGUICNTL 01/09/2003 17:18:52 20480
Prg SAPLOLEA 05/23/2005 14:03:56 79872
Prg SAPLSFES 09/06/2005 22:53:55 191488
Prg SAPLSPLUGIN 02/14/2002 14:22:48 6144
Typ ARFCRDATA 11/09/2000 14:04:16 6144
Prg SAPLGRFC 02/14/2002 14:22:47 13312
Typ SWCBCONT 11/15/2000 17:55:11 3072
Typ OLE_VERBS 04/04/1995 16:02:20 2048
Typ OLE_PA 04/04/1995 16:02:19 2048
Prg SAPSHDTV 03/12/2004 06:40:27 28672
Typ SSCRTEXTS 09/03/1997 03:12:33 3072
Typ SSCRFIELDS 05/13/1997 12:54:26 4096
Prg CL_GUI_PROPS_CONSUMER=========CP 01/07/2003 18:26:56 26624
Prg SAPLTHFB 09/06/2005 22:52:48 306176
Prg CL_DYNAMIC_GUI_EXTENSIONS=====CP 02/14/2002 14:22:46 33792
Prg CL_GUI_DATAMANAGER============CP 05/01/2005 00:20:36 70656
Prg CL_ABAP_CHAR_UTILITIES========CP 05/01/2005 00:14:49 11264
Prg RSDBSPVD 05/01/2005 00:15:44 73728
Typ RVARI 03/30/1998 09:40:50 4096
Typ RSVARIVDAT 04/04/1995 16:12:54 2048
Typ VBEP 01/27/2003 16:50:17 10240
Typ VBAP 09/15/2005 11:15:36 44032
Prg SAPLCEI0 09/22/2005 14:34:40 936960
Typ API_VALUE 02/20/1998 08:46:47 2048
Prg SAPLCUEV 06/07/2001 18:26:56 10240
Prg SAPLSUNI 06/13/2004 00:42:30 131072
Typ TFDIR 07/29/1998 19:49:08 3072
Prg %_CIBCO2 03/13/2004 14:32:13 12288
Typ IBINCOM 06/01/1999 11:56:27 3072
Typ IBINCONF 06/01/1999 11:56:27 2048
Typ IBSTCONF 06/01/1999 11:56:28 1024
Prg SAPLCUCB 05/23/2005 15:20:17 192512
Typ TCUIBSPECIAL 06/07/2001 17:50:37 1024
Prg %_CIBXX 03/13/2004 14:38:45 49152
Typ BAL_S_MSG 12/04/2000 13:04:01 6144
Prg CX_CBASE_ERROR================CP 01/27/2003 16:58:10 10240
Typ SCX_SRCPOS 11/09/2000 14:12:15 2048
Typ BAL_S_CONT 11/02/1998 09:43:07 2048
Typ BAL_S_PARM 12/04/2000 12:45:14 3072
Typ BAL_S_CLBK 11/02/1998 09:43:07 2048
Prg CX_STATIC_CHECK===============CP 02/14/2002 14:22:47 8192
Prg CX_ROOT=======================CP 02/14/2002 14:22:47 9216
Prg CL_CBASE======================CP 05/23/2005 15:19:44 87040
Typ T371G 04/29/1998 10:42:48 2048
Prg SAPLIBCO 03/13/2004 15:32:40 269312
Prg %_CIBCO 03/13/2004 14:38:45 11264
Prg SAPLIBXX 03/13/2004 14:38:46 11264
Prg SAPLIBIBF 03/13/2004 14:38:46 179200
Prg %_CIBIB 03/13/2004 14:38:45 18432
Prg SAPLIBINF 06/12/2004 22:20:22 415744
Prg %_CIBIN 03/13/2004 15:32:40 48128
Prg CL_IBASE_STRUC================CP 06/07/2001 19:59:10 106496
Prg %_CIBST 03/13/2004 14:38:45 37888
Prg CL_IBASE_STRUC_BUF============CP 06/07/2001 19:59:10 89088
Prg CL_IBASE_STRUC_STAT===========CP 06/07/2001 19:59:10 8192
Prg CL_IBASE_STRUC_BUF_IBSTREF====CP 06/07/2001 19:59:10 35840
Prg %_CIBCO1 03/13/2004 14:38:45 14336
Typ IBINVAL 09/18/2001 10:02:52 2048
Prg SAPLIBCU 03/13/2004 14:38:46 12288
Prg SAPLIBCUT 06/07/2001 18:27:19 12288
Typ T371B 05/14/1998 22:58:43 2048
Typ V_IBINR 03/13/2004 15:32:40 5120
Typ V_IBINR_CM 03/13/2004 15:32:40 5120
Prg CL_IBASE_SERVICE==============CP 06/07/2001 19:59:10 13312
Prg CL_IBASE_T371D_BUF============CP 06/07/2001 19:59:10 12288
Typ T371D 08/27/1999 18:19:44 2048
Prg CL_IBASE_R3_MATERIAL==========CP 05/23/2005 15:08:24 59392
Typ MARA 05/23/2005 15:08:18 22528
Typ MAKT 08/28/1997 08:52:19 2048
Typ ICON 01/03/1996 15:34:02 3072
Prg CL_ABAP_TYPEDESCR=============CP 05/01/2005 00:20:10 21504
Prg CL_ABAP_ELEMDESCR=============CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_DATADESCR=============CP 03/12/2004 07:16:33 14336
Prg CL_ABAP_REFDESCR==============CP 03/12/2004 07:17:23 16384
Prg CL_ABAP_STRUCTDESCR===========CP 05/01/2005 00:20:33 20480
Prg CL_ABAP_COMPLEXDESCR==========CP 03/12/2004 07:16:33 13312
Prg CL_ABAP_TABLEDESCR============CP 03/12/2004 07:17:23 17408
Prg CL_ABAP_CLASSDESCR============CP 03/12/2004 07:17:23 23552
Prg CL_ABAP_OBJECTDESCR===========CP 03/12/2004 07:17:23 25600
Prg CL_ABAP_INTFDESCR=============CP 03/12/2004 07:16:33 19456
Prg CL_ABAP_SOFT_REFERENCE========CP 03/29/2001 16:42:12 7168
Prg CL_ABAP_REFERENCE=============CP 02/14/2002 14:22:46 6144
Prg IF_EX_CM_BADI_VERSION=========IP 01/07/2002 16:09:04 3072
Prg %_CABAP 01/07/2003 18:31:23 23552
Typ SXS_INTER 11/30/1998 15:55:16 2048
Prg CL_EX_CM_BADI_VERSION=========CP 05/01/2005 00:14:04 13312
Prg %_CSXRT 06/13/2004 00:40:55 11264
Prg CL_EXIT_MASTER================CP 06/13/2004 00:40:58 13312
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ V_EXT_IMP 11/09/2000 14:27:05 2048
Typ SXC_IMPSWH 11/09/2000 14:23:44 2048
Prg CL_IM_CM_BADI_VERSION_DEF=====CP 04/17/2002 11:01:00 6144
Prg SAPLASTAT_TRIG 02/14/2002 14:22:47 11264
Typ ASTAT_TYP2 11/10/1998 05:35:18 2048
Prg IF_CM_BASELINE================IP 05/23/2005 15:08:24 9216
Prg IF_IBASE_IBOF_TREE_OBJECT=====IP 05/23/2005 15:08:24 5120
Prg IF_IBASE_INSTALL==============IP 06/07/2001 20:08:54 4096
Prg IF_IBASE_MATERIAL=============IP 06/07/2001 20:08:54 3072
Prg IF_IBASE_OBJECT===============IP 06/07/2001 20:08:54 4096
Prg SAPLBOMA 02/14/2002 14:15:40 10240
Typ IONRA 03/12/2004 02:09:40 23552
Typ IBIBCOM 08/30/2001 17:56:57 4096
Typ IBIB 03/13/2004 14:32:13 5120
Prg CL_IBASE_STRUC_SERVICE========CP 06/07/2001 19:59:10 17408
Prg CL_CU_CBASE_ENQUEUE_CORE======CP 06/07/2001 19:58:59 11264
Prg CL_CU_CBASE_ENQUEUE===========CP 06/07/2001 19:58:59 16384
Typ T371F 06/01/1999 12:00:49 2048
Typ V_IBIN_SYVAL 03/13/2004 15:32:41 4096
Typ IBIN 09/18/2001 10:02:52 6144
Typ IBINOWN 02/01/2000 14:56:07 2048
Prg CL_IBASE_T371F_BUF============CP 06/07/2001 19:59:11 8192
Prg CL_IBASE_STRUC_FILT_02========CP 06/07/2001 19:59:10 11264
Prg CL_IBASE_STRUC_FILT===========CP 06/07/2001 19:59:10 10240
Typ IBST 09/18/2001 10:02:52 4096
Typ IBST 09/18/2001 10:02:52 4096
Typ IBSTREF 04/15/1998 00:20:43 2048
Typ IBSTREF 04/15/1998 00:20:43 2048
Prg IF_CBASE_E====================IP 06/07/2001 20:08:25 3072
Prg %_CCXTAB 02/14/2002 14:22:46 6144
Prg SAPLCUCQ 09/15/2005 11:15:38 79872
Typ CUCO 09/18/2001 10:02:34 18432
Typ CUCO_OBJ 09/18/2001 10:02:34 18432
Prg SAPLCLCA 09/06/2005 23:33:29 68608
Typ TCLA 03/13/2004 14:10:20 5120
Typ TCLAO 08/13/1997 13:57:22 4096
Prg SAPLCUOB 05/23/2005 14:31:35 31744
Typ INOB 09/03/1997 03:20:02 4096
Prg SAPLCLSE 05/23/2005 14:32:26 167936
Prg %_CCC01 05/01/2005 00:34:57 53248
Typ TABLEKEY 07/06/1998 21:01:06 2048
Typ KSSK 09/18/2001 10:02:58 3072
Prg SAPLCLEF -
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 = 0x0000000000000000Have 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 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.kHi 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 -
Reg SDCCN and USMM - Abap runtime error
Dear Friends,
Runtime Errors : DBIF_RSQL_SQL_ERROR
Exception : CX_SY_OPEN_SQL_DB
When I run a T.Code SDCCN and USMM, got abap run time error
"SQL error in the database when accessing a table" that errors are below.
Internal Call code is ..........[RSQL/OPEN/TBTCO]
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPLBTCH" or "LBTCHF19"
"EXECUTE_BP_JOB_SELECT"
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.
This kind of errors found.
what can i do ? Pls give me advice
Regards
keshavhi,
please share the solution how you solve the Question.
Because of some times i got the same dump.
Regards,
Ananth -
ABAP Runtime error in FM BBP_VENDOR_GET_DATA2 in R/3
Hi Gurus
We are receiving nearly 1000 ABAP runtime error in the Functional Module BBP_VENDOR_GET_DATA2 in the user ID as RFCPROD in the ST22 and in the dump details as soon below.
Possible error causes:
o The maximum size of an SQL statement was exceeded.
o The statement contains too many input variables.
o The input data requires more space than is available.
And this is happening in this place.
48| IF NOT LRT_ADDRNR[] IS INITIAL. |
|>>>>>| SELECT * APPENDING TABLE ITAB_ADRC FROM ADRC .
We enter the T-code XK01, XK02 and XK03 , then enter the details of vendor , press enter immediately one count is increasing in the ST22.
Please any one can suggest .
Thanks & Regards
SadaHi Sadasivam Soliyappan,
Could you please share the SAP Note number with us urgently?
We have been encountered with the same problem unfortunately.
Thanks in advance.
Dolunay. -
Dear All,
We are setting up Solman 7.1 sp08 for VAR scenario.
As we faced some issues with duplicated ibase components SAP suggested us to implement note 2012029.
After following step by step and running the reporrts mentioned in above note like report AI_CRM_PRODUCT_DELETE we started getting an abap runtime error.
SAP is telling us to re implement the note but it does not resolve our issue.
Now we are unable to create incidents, or to run trx ib_gen.
Because of this, job refresh_admin_data_from_support is getting cancelled.
find attached screenshot showing dump.
all suggestions or comments are welcome!
regards,
GermanHi German,
Looks like your report CL_AI_CRM_OBJECT_LMDB============CP is corrupted. Can you try restoring this program to original version by going to Version management in SE38?
Regards,
Vivek -
ABAP RUNTIME ERROR WHILE DOING MIRO
Runtime Errors MESSAGE_TYPE_X
Date and Time 23.02.2011 17:07:24
Short dump has not been completely stored (too big)
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Error creating the document in Profitability Analysis
Long text of error message:
Diagnosis
An error was found while the system was processing the FI/CO
document in Profitability Analysis.
System Response
The document cannot be processed any further.
Procedure
Contact your system administrator.
Technical information about the message:
Message class....... "KE"
Number.............. 476
Variable 1.......... " "
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
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:
MESSAGE_TYPE_X " "
RK2RF001 or "RKEVRK2R_FIX"
MOVE_VALUE_FIELDS_FI
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 701
Application server... "FPELECCPRD"
Network address...... "192.168.0.24"
Operating system..... "Windows NT"
Release.............. "6.0"
Hardware type........ "16x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "FPELECCPRD\FTP"
Database type..... "MSSQL"
Database name..... "FTP"
Database user ID.. "ftp"
Terminal.......... "PUNE143"
Char.set.... "C"
SAP kernel....... 701
created (date)... "Feb 24 2009 23:27:20"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 32
Patch text.. " "
Database............. "MSSQL 9.00.2047 or higher"
SAP database version. 701
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 16192
EM...... 29328880
Heap.... 0
Page.... 221184
MM Used. 20281392
MM Free. 664288
User and Transaction
Client.............. 900
User................ "FABUPLO"
Language key........ "E"
Transaction......... "MIRO "
Transactions ID..... "1C413FE0E2E7F1C88D54E61F1346F073"
Program............. "RK2RF001"
Screen.............. "SAPLMR1M 6000"
Screen line......... 34
Information on where terminated
Termination occurred in the ABAP program "RK2RF001" - in
"MOVE_VALUE_FIELDS_FI".
The main program was "SAPLMR1M ".
In the source code you have the termination point in line 2749
of the (Include) program "RKEVRK2R_FIX".Hi
Normally what we understand is we should not have a COPA doc in case of MIRO unless and untill one has got the Purchase Price Variance in the entry and for the same the OKB9 setting has been made while the GL account either doesnot have cost element for the period or the PA structure is not complete.
The above can be the probable reason for the dump. I hope if you try to investigate the problem on the above line you will find out the solution to the problem
regards
Debashis -
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
SKKread 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 errors COMPUTE_BCD_OVERFLOW
ABAP runtime errors COMPUTE_BCD_OVERFLOW
Occurred on 12/08/2010 at 06:44:17
>> Short dump has not been completely stored. It is too big.
Error analysis
An overflow has been determined in the current arithmetical operation
containing operands of type P. Possible causes include:
1. The results field of type P is to small and the result does not fit
into it.
places.
2. The result or partial result has more than 31 decimal places.
How to correct the error
You may need to define the result field to be larger, if it is still
possible to do so.
It may be possible to split the current process so that only smaller
values occur.
Eine Vorablösung zu dem aufgetretenen Fehler findet sich vielleicht
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
If you require an interim solution to this error, you can look in the
SAP note system. If you have access to
the SAP notes system yourself, enter the following search strings:
"COMPUTE_BCD_OVERFLOW"
"BCD_FIELD_OVERFLOW" (By release 4.0a, this error has been remedied at this
point)Hi Ganapati,
Check this thread COMPUTE_BCD_OVERFLOW in Database Performance collector.
Note 543749 - ABAP runtime error COMPUTE_BCD_OVERFLOW
It may helps you.
Maybe you are looking for
-
List of modules with ECC 6.0
I am looking for information on different module and engine in SAP from licensing perspective , like Netweaver comes wih ECC 6.0. What about Open Hub ? Can anyone kindly provide list of module and what comes with what and how it is set up?
-
Hi Experts, I have problem in SXMB_MONI when i am sending messages from RWB the messages which have BPM Associated with it are not been visible in SXMB_MONI but the messages which do not involve BPM that which are sent from RWB are visible . what cou
-
Some Language fonts no longer display correctly
I have a few language fonts, specifically Russian and Church Slavonic, which I have been using for years without any problem. They still partially display correctly, but there are some characters which display a different character now. For instance,
-
How to install windows mac book air
Hi, I'm trying to install windows onto my mac book air and bootcamp says I need an external optical drive. What is this and how do I get it? Thanks,
-
Hi, I have a procedure doing paging and returning the count of rows: As you see I used 2 select, one for paging and one for getting total row counts. Is there a way to get rid of "SELECT count(*) into PO_TOTAL FROM TABLE1;"? CREATE OR REPLACE PACKAGE