Runtime error in transaction ME31L

Hi Experts,
I am facing the problem with tranasaction code ME31L ,its showing the runtime error..
here i am writting the whole error discription which occurs at runtime.
Short text
    Dynpro does not exist
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLXM06" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    The system attempted to use dynpro 0201 in program "SAPLXM06".
    This dynpro does not exist.
Trigger Location of Runtime Error
    Program                                 SAPLXM06
    Include                                 MM06EO0C_CUSTSCR1_HEAD_SET_DAT
    Row                                     10
    Module type                             (FUNCTION)
    Module Name                             EXIT_SAPLEINM_013
Source Code Extract
Line SourceCde
     1 ----
     2 *       MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT                          *
     3 ----
     4 *       ........                                                      *
     5 ----
     6 MODULE CUSTSCR1_HEAD_SET_DATA OUTPUT.
     7
     8   PERFORM CUSTSCR1_HEAD_SET_DATA_PBO using fc_call.
     9
>>>>> ENDMODULE.

Hi,
This means that the exit is not implemented yet. Infact what you are seeing is a warning message(ZX...).
Is your system recently upgraded? Wrong OSS note implementation is also a possibility.
Just debug and see at what point you are getting the error. Also did you check the program whether it has the required screen or not? If not available then you can raise an OSS note to SAP if you are not able to find any.
Thanks,
Vinod.

Similar Messages

Runtime error in transaction MFBF

Hi,
In MFBF, am giving the following details:
Material No.
Plant
Storage location
Batch
After this when i click on select post with correction, select lines and delete them all and save then its giving a dump saying ,
No status object available for INL 0.
Can anyone help me that why is this happening?

Hi Inder
Check the following link
Re: No system status shown in the inspection lot and cannot UD
Regards

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC in t-code KO02

Hi Guru,
I got runtime error in transaction KO02, below i given all the details.
Runtime Errors         SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
    Use an ABAP/4 Open SQL array insert only if you are sure that none of
    the records passed already exists in the database.
    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:
    "SAPSQL_ARRAY_INSERT_DUPREC" "CX_SY_OPEN_SQL_DB"
    "SAPLA02S" or "LA02SF00"
    "INSERT_ENTRIES"
    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.
The exception must either be prevented, caught within proedure
"INSERT_ENTRIES" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
Information on where terminated
    Termination occurred in the ABAP program "SAPLA02S" - in "INSERT_ENTRIES".
    The main program was "RSM13000 ".
    In the source code you have the termination point in line 132
    of the (Include) program "LA02SF00".
    The program "SAPLA02S" was started in the update system.
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "INSERT_ENTRIES" "(FORM)", but it was neither handled locally nor
     declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLA02S "; its source code begins in line
    85 of the (Include program "LA02SF00 ".
Plz tell me if some one have idea to solve this problem,
Thanks,
Namdev

Hi,
check in the OSS and see if there is any note available:
e.g.
Note 78466 - RA_ASSET_MODIFIKATION - SAPSQL_ARRAY_INSERT_DUPREC
https://service.sap.com/sap/support/notes/78466
Best regards.

Runtime error in KEFC Transaction while uploading CSV format file

Hi Experts,
This is regarding Runtime Error while executing the KEFC transaction in R3D.
It is working successfully while uploading the file in Text format. But there is run time error while uploading in CSV format.
It showing "The transfer was terminated.However,content errors occured" .
Please provide the solution.
Thanks in advance.
Regards,
Priya.

Hi,
To upload a CSV file it is used FM:
CALL FUNCTION 'TEXT_CONVERT_CSV_TO_SAP'
EXPORTING
i_field_seperator = ';'
I_LINE_HEADER =
i_tab_raw_data = lt_file
i_filename = p_filename
TABLES
i_tab_converted_data = p_table
EXCEPTIONS
conversion_failed = 1
OTHERS = 2
Please check what separetor this fm and your file are using. It should be the same.
Regards,
Fernando

Runtime Error in BW, in RSA1 transaction

Hello Boss,
Iam getting runtime error while activating the info object in RSA1 transaction.
I got OSS notes also from our basis consultant, plz give suggestion how to rectify this one.
Even while executing the program iam getting runtime error.
In this OSS notes they mentioned while u activating DSO u get this runtime error & solutions r given. iam not activating any DSO, activating info object. plz give ur suggestion.

Hi,
check in ST22 what exactly is message.. Ask basis to check server space and bg process.
Abhi

Runtime error in CRMD_SALES_MASS transaction

Hi Gurus,
I have to enhance the transaction CRMD_SALES_MASS to add few custom fields to it.
I am trying to execute the transaction but I keep getting a runtime error in a standard Function Module CRM_SALESORDER_MASS_SELECT that is meant for the MASS Transaction. I have gone through many notes but I could not find anything which is relevant. Please help me with this! Please find the below dump if it can help.
Runtime Errors         CREATE_DATA_UNKNOWN_TYPE
Except.                CX_SY_CREATE_DATA_ERROR
Date and Time          09.12.2010 05:11:12
Short text
    CREATE DATA: The specified type "CRMT_SALESORD_MASSUPDATE_ITEM
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLCRM_SALES_MASS_UPDATE" had to be terminated
     because it has
    come across a statement that unfortunately cannot be executed.

Hi Nisha,
Thanks for the reply.
I got to know the issue with the function module before I saw the reply. It has something to do with the type that is used in CREATE DATA statement. The statement at line 51 should have been as below
CREATE DATA ls_selecttable_ref type (tabname-name).
but the type mentioned tabname in standard FM is a structure of type MASSTABLESTAB.
Now I have another question. If we are to implement MASS transaction for Service contracts in CRM how are we supposed to do it? I am talking about SAP GUI and not the WebUI here.
Regards,
Mahesh

Portal Runtime Error while checking the Transaction in Portal

Hi all,
We r in the phase of setting the configuration of Portal. We did the the template installer but when iam checking the transactions in Portal ( System Administration--> Support--->SAP Apllication) , it is throwing me the following error.
Portal Runtime Error
An exception occurred while processing a request for :
iView : N/A
Component Name : N/A
Missing Property 'ClassName' in property file for layer'Transaction/WinguiSSOLayer'..
See the details for the exception ID in the log file
Can anybody help me in this regard.
Thank in Advance.

Hi Niyati,
I guess check through -->
Under "Personalize > User Profile" the checkbox "Activate Accessibility Feature" must be unchecked!
as, people earlier also faced this issue and SAP provided this solution.
Also an alternative solution for this is like --
Go to:
<Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\portal\portalapps\com.sap.portal.appintegrator.sap\property\Transaction
and see the content of the 'WebGuiSSOLayer.properties' file.
One of the entries is ''ClassName'. The value on a 'valid' portal is: com.sapportals.portal.sapapplication.itsdetection.ITSDetectionLayer
If it's not the case, then go to:
<Drive>\usr\sap\<SID>\JC<Instance No.>\j2ee\cluster\server<Server No.>\apps\sap.com\irj\servlet_jsp\irj\root\WEB-INF\deployment\pcd
rename the file 'com.sap.portal.appintegrator.sap.par.bak' to 'com.sap.portal.appintegrator.sap.par' open the par file and edit the file ''WebGuiSSOLayer.properties' (add the relevant entry for ClassName).
Save the file (still with the par extension)
Restart the portal (if everything is OK then the bak extension will be added to the filename).
Just try this, hope it works.
Reward points if helpful
Regards,
Shailesh Nagar
Edited by: Shailesh Kumar Nagar on Jan 22, 2008 7:16 AM

While trying to change a BOM with transaction CS02, a runtime error appears

While trying to change a BOM with transaction CS02, a runtime error appears.
In intial screen he entered material ,plant BOM usage and date valid from after executed then id displayed item list in that he wantu2019s delete one item, he has been deleted selected item after that when he was saving he is getting runtime error
Developer trace
ABAP Program SAPLKED1_WRITE_CE4_BPS1                 .
Source LKED1_WRITE_CE4_BPS1U01                  Line 30.
Error Code SAPSQL_ARRAY_INSERT_DUPREC.
Module $Id: //bas/640_REL/src/krn/runt/absapsql.c#17 $ SAP.
Function HandleRsqlErrors Line 775.
RABAX: level LEV_RX_STDERR completed.
RABAX: level LEV_RX_RFC_ERROR entered.
RABAX: level LEV_RX_RFC_ERROR completed.
RABAX: level LEV_RX_RFC_CLOSE entered.
RABAX: level LEV_RX_RFC_CLOSE completed.
RABAX: level LEV_RX_IMC_ERROR entered.
RABAX: level LEV_RX_IMC_ERROR completed.
RABAX: level LEV_RX_DATASET_CLOSE entered.
RABAX: level LEV_RX_DATASET_CLOSE completed.
RABAX: level LEV_RX_RESET_SHMLOCKS entered.
RABAX: level LEV_RX_RESET_SHMLOCKS completed.
RABAX: level LEV_RX_ERROR_SAVE entered.
RABAX: level LEV_RX_ERROR_SAVE completed.
RABAX: level LEV_RX_ERROR_TPDA entered.
RABAX: level LEV_RX_ERROR_TPDA completed.
RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
RABAX: level LEV_RX_END entered.
RABAX: level LEV_RX_END completed.
RABAX: end RX_RFC
In sm21
Perform rollback
Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
     Short dump "090618 110101 donalda 11557 " generated
Runtime Error          SAPSQL_ARRAY_INSERT_DUPREC
Exception              CX_SY_OPEN_SQL_DB
       Occurred on     18.06.2009 at   11:01:01
The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLKED1_WRITE_CE4_BPS1" 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 is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"RKE_WRITE_CE4__BPS1" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
If you use an ABAP/4 Open SQL array insert to insert a record in
the database and that record already exists with the same key,
this results in a termination.
(With an ABAP/4 Open SQL single record insert in the same error
situation, processing does not terminate, but SY-SUBRC is set to 4.)
How to correct the error
The exception must either be prevented, caught within the procedure
"RKE_WRITE_CE4__BPS1"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Use an ABAP/4 Open SQL array insert only if you are sure that none of
the records passed already exists in the database.
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:
"SAPSQL_ARRAY_INSERT_DUPREC" CX_SY_OPEN_SQL_DBC
"SAPLKED1_WRITE_CE4_BPS1" or "LKED1_WRITE_CE4_BPS1U01"
"RKE_WRITE_CE4__BPS1"
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.

Hi ,
you are getting beacuse u are trying to do mass update to database.
Please check that below note are applicable to your system.
Note 453313 - DBIF_RSQL_ERROR_INTERNAL for mass insert
Note 869534 - AFS MRP doesn't work properly with all BOM item categories
Thanks Rishi Abrol

Runtime Error while opening the transaction ME22N

Hi,
when am trying to open the transaction ME22Nin Ecc6.0 its showing the runtime error like Assign with Length 0 in the pgm SAPLTAX1 in the Module FIND_TAX_SPREADSHEET.
than you in advance.

post your Dump information with
Short text
What happened?

Runtime error while executing transaction BDLS

Hello,
While executing BDLS transaction for converting logical system names I am getting following error
Runtime Errors         CONVT_NO_NUMBER
Except.                CX_SY_CONVERSION_NO_NUMBER
Short text
     Unable to interpret "7,160 " as a number.
How to resolve the above problem?

Hi Rachel,
BDLS creates an ABAP program SBDLS* which includes all the tables possibly including logical system names as of the domain behind the table fields. This program firstly
lives in runtime only and is checked by syntax checker.
Now, sometimes tables have inconsistencies associated with them and you
will get this dump when a syntax check is performed on them.
So please check this and regenerate the culprit tables.
So please redo the steps for BDLS and check. There are
probably some tables which could be determined by you (syntax
check - in case program has already been saved only)
An easy way to check this is to run RBDLS2LS program (old BDLS) and
afterwards performing a syntax check on generated RBDLS*** (RBDLS<(>
<<)>(>
<<(><<)>)>ClientName>) program.
Known tables which caused such dumps in the past are:
DFKKCOLFILE_P_W
DFKKKO
DFKKMKO
DFKKREP06
DFKKREP06_S
DFKKREP07
DFKKREV06
DFKKREV07
Simply reactivate the tables you find out in SE11.
Another thing which has lead to this dump in the past is
in your R/3-System the value ' x ' is
additionally added to the value of your current release in the basis
release table SVERS.
The table RSBASIDOC takes the release value from the table SVERS.
If you change value 'x' to your release in both tables (SVERS and
RSBASIDOC) and
and activate again your source system connection. This could solve the
dump too.
I hope, this helps-if not, pls open a message with SAP.(component: BC-MID-ALE)
b.rgds, Bernhard

Runtime error in the transaction S_ALR_*

Hi SDN-ers,
I have a problem with the transaction S_ALR_8******2 in my PROD system.
Although I can open it, then instantly a page with ABAP runtime error occurs.
I ran SE16 and entered the Table Name TSTCT and entered S_ALR* to find out all the Tcodes which starts with S_ALR with Description too.
1) Is there any other way / T-Code availbale in viewing S_ALR_8******2.
2) What are all the User Parameters that need to be changed for this and where can we find them?
Please help me in resolving this issue.
Thanks,
Anguraj M.

Hi Michael,
Thanks for your reply.
Could you please let me know where can we change/modify the below User Parameter for this T-Code S_ALR_8******2?
User Parameter is GRWE = X?XXXXXX XEX.
What is the trouble shooting method when the user faces ABAP Runtime error while executing the above mentioned T-Code (S_ALR_8******2)?
Please help me on this.
Thanks,
Anguraj M.

ABAP runtime error in ME2N Transaction

Hi All,
I am getting an ABAP runtime error when i run transaction ME2N and then click on th Account Assignment Button.
This is the error i get.
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          06/01/2009 16:35:59
Short text
Field symbol has not yet been assigned.
The section of the code which is creating problem is
2326|*... ... find the row that holds the first requested cell                                   |
2327
loop at ct_stin assigning <ls_stin>
2328
where start_indx le i_start.
2329
l_start = sy-tabix.
2330
endloop.                       "Y6DK065306
>>>>>
if <ls_stin>-filled eq abap_false.
2332
lt_delete_row-low    = <ls_stin>-row_pos.
2333
lt_delete_row-sign   = 'I'.
2334
lt_delete_row-option = 'EQ'.
2335
insert lt_delete_row into table lt_delete_row.
2336
endif.
| 2337|
the internal table ct_stin is not gettin any data in Runtime.
Can anybody help me out in analysing this.
Saurabh

As I understand you have modify the standard SAP program. The problem is when the internal table
ct_stin does not have data the field symbol <ls_stin> does not have any assign. to correct this
LOOPAT CT_STIN ASSIGNING <LS_STIN>
WHERE START_INDX LE I_START.
L_START = SY-TABIX.
ENDLOOP.                                                    "Y6DK065306
Check <LS_STIN> IS Assigned.
IF <LS_STIN>-FILLED EQ ABAP_FALSE.
LT_DELETE_ROW-LOW = <LS_STIN>-ROW_POS.
LT_DELETE_ROW-SIGN = 'I'.
LT_DELETE_ROW-OPTION = 'EQ'.
INSERT LT_DELETE_ROW INTO TABLE LT_DELETE_ROW.
ENDIF.

Runtime error when trying to execute transaction OB58

Hi all,
We have upgraded from SAP system 4.6c to ECC 6.0 . We are facing one error in the FI transaction OB58.
When trying to delete any finanicial version or trying to create any new financial version , we are getting a runtime error which
states that " Error when attempting to IMPORT object "X011F". and its giving short dump at this point .The description of the error is :
Short text
    Error when attempting to IMPORT object "X011F".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLFAGL_FSV" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
     not caught in
    procedure "FSV_POSITIONS_CONVERT" "(FORM)", 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:
    When importing the object "X011F", the component 1 in the dataset
    had a different length from the corresponding component of the
    target object in the program "SAPLFAGL_FSV".
    The length is 4 in the dataset, but 32 in the program.
Thanks,
Sumit

Hi Sumit,
We Upgraded our system from 4.6C to ECC 6.0 and
I am facing same error. We applied note 1544367. After applying not also we are facing issue during
import x011p to lt_x011p
         i011z to lt_x011z
         x011v to lt_x011v
         x011s to lt_x011s
         x011f to lt_x011f
from database rfdt(bs) client p_mandt
                               id p_versn
                        accepting padding
                         ignoring conversion errors.
You faced same issue after applying note or if you have any solution please let me know.
Regards,
Mahesh

Transaction IA12:ABAP runtime errors:TIME_OUT

Hi,
We are executing transaction IA12.We are getting ABAP runtime errors:Time_Out.
We have searched for a SAP note to sort the issue:SAP Note 607086 - Functional location: Problems when displaying structure list.
Please suggest what will be the option to solve the issue.
Thanks.

Hi,
searching for the FORM routine where the timeout occurs ("mara_predecessor_f50") and excluding SAP notes that are modification notes or based on the implementation of modification notes, there is only one remaining note
Note 658930 - Structure list: Configuration not considered with BOM
for 46C up to Support Package SAPKH46C46.
If this is still not in your system, the note may be a solution.
If not, I'm running out of good ideas. Then also the SAP modification notes can be your last option.
Regards,
Klaus

Runtime Errors: CONVT_OVERFLOW while executing transaction sm66

Hello Everyone,
There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
Please suggest
Runtime Errors         CONVT_OVERFLOW
Exception              CX_SY_CONVERSION_OVERFLOW
Date and Time          02.04.2011 00:41:01
Short text
     Overflow when converting from "2.90113e+09"
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
      caught in
     procedure "TH_WP_DETAIL_INFO" "(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:
     When attempting to convert the value "2.90113e+09",
     an overflow occurred.
     There is probably an error in the program
     "SAPLTHFB".
How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     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,
     please use the following search criteria:
     "SAPLTHFB" "CONVT_OVERFLOW"
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.
The exception must either be prevented, caught within proedure
"TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
tem environment
SAP-Release 700
Application server... "POSDMCI"
Network address...... ""
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "POSDMDB"
Database type..... "ORACLE"
Database name..... "BP2"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 16192
EM...... 8379696
Heap.... 0
Page.... 40960
MM Used. 720912
MM Free. 3466336
Information on where terminated
    Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
    The main program was "SAPMSM66 ".
    In the source code you have the termination point in line 82
    of the (Include) program "LTHFBU26".
    The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
     occurred in
    procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLTHFB "; its source code begins in line
    1 of the (Include program "LTHFBU26 ".

Hello Everyone,
There are two Application serevrs out of which I am getting the following error while executing transaction SM66 only in one i.eCI server but if i remote login to other system and try SM66 its working fine.
Please suggest
Runtime Errors         CONVT_OVERFLOW
Exception              CX_SY_CONVERSION_OVERFLOW
Date and Time          02.04.2011 00:41:01
Short text
     Overflow when converting from "2.90113e+09"
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_CONVERSION_OVERFLOW', was not
      caught in
     procedure "TH_WP_DETAIL_INFO" "(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:
     When attempting to convert the value "2.90113e+09",
     an overflow occurred.
     There is probably an error in the program
     "SAPLTHFB".
How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     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,
     please use the following search criteria:
     "SAPLTHFB" "CONVT_OVERFLOW"
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.
The exception must either be prevented, caught within proedure
"TH_WP_DETAIL_INFO" "(FUNCTION)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
To prevent the exception, note the following:
tem environment
SAP-Release 700
Application server... "POSDMCI"
Network address...... ""
Operating system..... "SunOS"
Release.............. "5.10"
Hardware type........ "sun4u"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "POSDMDB"
Database type..... "ORACLE"
Database name..... "BP2"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 21:14:52"
create on........ "SunOS 5.9 Generic_117171-13
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE
SAP database version. 700
Operating system..... "SunOS 5.9, SunOS 5.10"
Memory consumption
Roll.... 16192
EM...... 8379696
Heap.... 0
Page.... 40960
MM Used. 720912
MM Free. 3466336
Information on where terminated
    Termination occurred in the ABAP program "SAPLTHFB" - in "TH_WP_DETAIL_INFO".
    The main program was "SAPMSM66 ".
    In the source code you have the termination point in line 82
    of the (Include) program "LTHFBU26".
    The termination is caused because exception "CX_SY_CONVERSION_OVERFLOW"
     occurred in
    procedure "TH_WP_DETAIL_INFO" "(FUNCTION)", but it was neither handled locally
     nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLTHFB "; its source code begins in line
    1 of the (Include program "LTHFBU26 ".

Runtime error in transaction ME31L

Similar Messages

Maybe you are looking for