Runtime Error due To ABAP Dump LOAD_TYPE_VERSION_MISMATCH

Hi,
We had a requirement were were asked to add some customer specific fields to Material Master Table MARA.
We did that by appending a z structure to Material master Table. After some while we had made a change in the Data type of a fields in the structure, while activating it was giving a warning message that other dependent structure of Mara table would be affected & activation needs to be done for that dependent structures also. the activation was done but still with warning message.
When this transport request was moved to Production, all those users which were using T-codes related to Material master MM01/02/03 & other T-codes were receiving ABAP dump LOAD_TYPE_VERSION_MISMATCH.
What could be the reason for such ABAP dump ?
Again it is observed that after running it 2-3 times, it is not throwingany runtime errors. We have also tried to regenerate objects related to transport request.
Edited by: priyeshosi on Jul 2, 2011 2:42 PM

Hi priyeshosi,
thats normal.
If a user starts a transaction, the system knows that something has changed and will automatically trigger compilation of the object.
If a user starts a transaction and does not close it - just not to have to start it again too many times -, and then you import the transport, you will probably get the load type mismatch dump as soon as the users uses the already loaded transaction.
The best way to avoid this is importing significant changes in the night when nobody or only few users are working. If this is not possible, the administrator can insert a warning message that pops up when the users takes any action.
You can also start report for mass generation after importing the transport, this will avoid the re-generation triggering but it will not help transactions already loaded into memory.
Regards,
Clemens

Similar Messages

Catch CONVT_NO_NUMBER runtime error in OO ABAP Program

Hi all,
       In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump. I noticed that this error cannot be caught by CX_ROOT exception class.
       Some told me I can use the CATCH SYSTEM-EXCEPTIONS sentence to catch this runtime error, but it is a old-way syntax and cannot be used with the "try" and "catch".
       So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
You are not checking for conversion.
You are checking ofr logical expression.
Try below code, it works
DATA error_ref TYPE REF TO cx_sy_conversion_no_number.
DATA err_text TYPE string.
DATA a TYPE i.
TRY.
    MOVE 'A' TO a.
CATCH cx_sy_conversion_no_number INTO error_ref.
    err_text = error_ref->get_text( ).
    WRITE err_text.
ENDTRY.
Regards,
Atish

How to troubleshoot runtime error (termination with short dump)

hi all,
i'm new comer on crm. and i got a problem when i accessed tx: segment builder (runtime error: termination with short dump).
i've tried to troubleshoot this problem by set the java2 SDK GUI path on the client side.but it still didn't work.then i tried to activate the automation trace (just perform the procedure which wrote down on error analysis), but i confused when tried to read the trace file and still didn't get the point. FYI, i 'm using sap logon 710 and SAP crm 5.0.
what i've should to do?
should i have to re install my sap logon?
i really need ur assistance!
best regards,
agung

Hi Agung,
Please refer the following SAP Note for your information:
<b>SAP Note: 990263</b>
Best Regards,
Johnny.
Reward with points if it helps.

Delivery Can not Delete Delivery due to ABAP Dump

I have a strange situation on a delviery that is in our production client. We rec;d an APAB dump whenposting goods issue in delivery (successfully posted but still ABAP'd out) this was due to the sales unit field calculated to high of a qty due to a material master setting in the price unit qty, This has been fixed in the material master but we can not get to the delivery to delete it. I have succefully reversed goods issue and successfully cancelled TO confirmation. I can not get to the delivery to delete it. I can not reject line items on the sales order due to it having subsequent documents. Does anyone know how this can be accomplished? Please advise/comment experiences. It would be GREATLY appreciated. See Below ABAP dump if it helps....
Kim
Runtime Errors         DYNPRO_FIELD_CONVERSION
Date and Time          05/16/2011 11:05:21
                   Screen name.............. "SAPMV50A"
                   Screen number............ 1102
                   Screen field............. "LIPSD-PIKMG"
                   Error text............... "FX015: Sign lost."
     Other data:
     If you cannot solve the problem yourself and want to send an error
     notification to SAP, include the following information:
     1. The description of the current problem (short dump)
        To save the description, choose "System->List->Save->Local File
     (Unconverted)".
     2. Corresponding system log
        Display the system log by calling transaction SM21.
        Restrict the time interval to 10 minutes before and five minutes
     after the short dump. Then choose "System->List->Save->Local File
     (Unconverted)".
     3. If the problem occurs in a problem of your own or a modified SAP
     program: The source code of the program
        In the editor, choose "Utilities->More
     Utilities->Upload/Download->Download".
     4. Details about the conditions under which the error occurred or which
     actions and input led to the error.

Symptom
A Warehouse Management-relevant (WM-relevant) delivery item is picked, and then the WM transfer order is canceled again using LT0G.
If the storage location for the delivery is changed to a non-WM-relevant storage location and a pick quantity is entered in the delivery, this pick quantity is assigned to the document flow record for the cancellation of the WM transfer order. This is incorrect.
The incorrect document flow record is stored in the database when you save the delivery.
This results in the ABAP runtime error "DYNPRO_FIELD_CONVERSION" when the delivery is processed again with VL02 or VL02N.
Other terms
PIKMG, WM-TA, Warehouse Management (WM) transfer order (TO), VBFA, RFMNG, SAPMV50A, MV50AO0F, FELDAUSWAHL, MV50AO0F, LIPSD-PIKMG
Reason and Prerequisites
This problem is caused by a program error.
Solution
Implement the specified correction to prevent this inconsistency in the table VBFA from occurring again.
Correction report Z_CORRECT_VBFA_FROM_LTAP:
Implement the correction report specified below with transaction SE38 using the attributes:
Title            Correction report for note 435274
Type            1 Executable program
Status                T    Test program
Application              V     Sales
Input parameters for execution of the report:
P_VBELN: Document number of the delivery that has document flows
         for the WM transfer order that are to be corrected.
        While the report is running, make sure that
        no changes are made to the relevant
        document.
P_TEST = 'X': Analysis:   Analysis of the missing document flow records;
                        no changes in the document.
P_TEST = ' ': Correction: Document flow records between delivery and
                        WM transfer order are corrected.
refer SAP Note 435274 - Negative pick quantity in the delivery

LSO Follow Up (WBT) - Runtime error due to ceased employees

We have just created a custom program which confirms participation for learners (web-based training). In Production we will create a nightly job that confirms participation if the learner forgets to click on this link.
This is done by using ABAP program SAPLLSO_FOLLOWUP.
It's working fine, however we've come across one issue. We are getting runtime errors when executing the program. After some investigation we found out this is because we have Ceased employees enrolled in the courses.
As as example, in our Test Environment we have a WBT course which has three people enrolled. One of those people is now ceased. When you right click on the course (via the dynamic menu) and click on Follow Up, you get the runtime error.
We can't cancel the ceased employee since he/she has already completed the course. So as a work around, we changed the Course Type "Completion Specifications" infotype so learners can be "canceled at any time". We then cancelled the ceased employee from the course. We then right clicked on the course>follow up, this time it worked.
Obviously this work around won't be suitable for Produciton. We don't want to cancel ceased employees from a course as we still want to keep a record of their training. So is there a way around this???
Any help would be greatly appreciated!!!!
Cheers
Shaun

Figured it out - data issue

Portal Runtime Error due to use of string buffer

Hi All,
Whenever I run a portal component in which i have used srting buffer i am getting portal runtime error like
java.lang.StringBuffer.append(Ljava/lang/String;)Ljava/lang/AbstractStringBuilder;.
but same code run fine from my colleague's system/ NWDS .I reinstalled my NWDS but still same problem .What could be reson for this strange behaviour?
Provide your inputs to solve this problem.
Regards,
Madhvika

Hi,
Check the JDK version for compiling, it should be 1.4.
To check this in NWDS goto menu: windows --> preference --> Java --> Compiler.
Here check tab Compliance and Classfiles.
If this does not solve, check if you installed JDK 1.5, if so uninstall it.
Also check this, may be a NWDS upgrade can help:
Re: Modify or field-symbol statement
Regards,
Praveen Gudapati

Runtime Error for WD ABAP Application in Portal

Hello Everyone,
I developed a WD ABAP Application and then created an iview in portal for this WD ABAP application and then assigned this iview to a role.
Now, when I click on this WD ABAP iview it is working fine for the first time. If I click on the iview "again" it is throughing the following error message. Please let me know why I am getting this error.
The following error text was processed in the system DV1 : User session (HTTP/SMTP/..) closed after timeout
The error occurred on the application server sapdv5_DV1_00 and in the work process 0 .
The termination type was: ERROR_MESSAGE_STATE
The ABAP call stack was:
Method: PREPROCESS_REQUEST of program CL_WDR_CLIENT_ABSTRACT_HTTP===CP
Method: IF_HTTP_EXTENSION~HANDLE_REQUEST of program CL_WDR_MAIN_TASK==============CP
Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP
Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME
Module: %_HTTP_START of program SAPMHTTP
I greatly appreciate your help.
Regards,
Gopal.
Edited by: Gopal on Sep 17, 2009 7:09 PM

Hi Gopal,
I m not sure enough regarding this error but on searching i came accros a thread in wjhich some solution is provided which might help you.
User session (HTTP/SMTP/..) closed after timeout
just go thru this ..
regards,
anand

Runtime error in xi abap stack -while getting AE logon details

Hi XI gurus
We are getting a error in abap stack , transaction SMQ2 in XI box - whose details in sxmb_moni are as follows
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">CLIENT_RECEIVE_FAILED</SAP:Code>
<SAP:P1>400</SAP:P1>
<SAP:P2>ICM_HTTP_CONNECTION_FAILED</SAP:P2>
<SAP:P3 />
<SAP:P4 />
When we look at the error trace in sxmb_moni, I see the following :
<Trace level="2" type="T">return fresh values from cache</Trace>
<Trace level="2" type="T">Get logon data for adapter engine (SAI_AE_DETAILS_GET):</Trace>
<Trace level="1" type="T">HTTP Multipart document length: 30971</Trace>
<Trace level="2" type="System_Error">HTTP-Client: exception during receive: HTTP_COMMUNICATION_FAILURE</Trace>
</Trace>
</Trace>
Is there a RFC destination to adapter engine from ABAP stack that is failing here ? What should we check ?

Hi
Please perform below tasks
1. Please check INTEGRATION_SERVER_HMI rfc is working fine using SM59 transaction
2. If you are using RFC detination to connect to Proxy system, then i suggest you to check the connection
3. Have a look at SAP Note 755372, 634006 and 773830 for the solution.
4. refer to this blog - /people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi
5. If still problem persist please post us the ICM trace file
Regards
Sekhar

Runtime Error due to activating Fund Management

Hi,
I had activated Funds Management in SAP. I started getting Run Time Errors. I deactivated the Fund Management. But still the Run Time Error is there. I am attaching the file for your reference.
I enquired with the Basis consultant who is telling this is a Functional problem, hence I need to solve this. I checked all the configurations, but could not find the exact problem.
Can anybody tell me how this can be resolved.
Note: This error is showing in Quality Server. There was a copying from Production to Quality.

In the error I see the statement before the dump comes is PERFORM exit--entry_from_table | | 1039| IN PROGRAM (-callback_report)
That sounds like an user exit from a table that is not there.
You say you had a copy from production. It could be that a user exit which was not implemented yet in production and therefore not in the exit table. is now also not present anymore in your Q system after the copy. Were there any changes about to go to production ?
Also in the dump I read the comment:
| 1063|* version and guid are used by strategy -> further params for generated | | 1064|* routines. guid is only used for reference purposes and not returned at | | 1065|* the moment
That could possibly mean that this is a generated program. Maybe you need to regenerate it.
I also see: STEP--METHOD_DRULE
That could mean that these have something to do with rules that have not been maintained.
You could ask a programmer to debug the program and see where SAP tries to get the rules and exit information from (which table) .
Maybe that give you a clue what is going wrong.
If you have a table name start SM30 and click customizing. If it opens a customizing transaction then that is where you need to maintain entries.

FB03 transaction gives runtime error due to time out!

Hi All,
In the transaction FB03, I entered a reference number that has not yet been created and then a company code of 2130 and fiscal year 2010 and hit enter. It takes a lot of time to show the error message that "No documents exists which fulfills the selection criteria".
I debugged and found that a FETCH NEW CURSOR statement takes time and hence the delay in showing the o/p.
The exact ABAP statement is :- FETCH NEW CURSOR dbcursor INTO CORRESPONDING FIELDS OF ex_result.
Please suggest me if there is some note to be implemented or any other solution for the same!
Thanks,
Safeer.

I entered a reference number that has not yet been created and then a company code of 2130 and fiscal year 2010 and hit enter. It takes a lot of time to show the error message that "No documents exists which fulfills the selection criteria".
Trace the process to determine if there is a bad index being used. Is the search using BKPF~1 or another index? Are your DB stats up to date? As for notes, you're unlikely to find one but don't ask for them here, search for them on OSS.

ABAP runtime errors "DYNPRO_MSG_IN_HELP"

Hello Friends,
Help me to solve the ABAP runtime errors "DYNPRO_MSG_IN_HELP"
The ABAP dump occurred executing transaction "ZQ01".
The dump occurs in standard program "SAPMZQ01 " of transaction "ZQ01" .
Error Comes during "F4" processing, the program tried to send a " " message.
This is not allowed at this point in processing.The program had to be terminated.
search criteria of error is shown below:
Program Name:   "SAPMZQ01 "
Include Name:    "MZQ01F01 "
Form Name:       "KTAAR_SIMPLE_F4"
Error in Source code:
024030               INVALID_ABAPWORKAREA = 1
024040               INVALID_DYNPROFIELD = 2
024050               INVALID_DYNPRONAME   = 3
024060               INVALID_DYNPRONUMMER = 4
024070               INVALID_REQUEST      = 5
024080               NO_FIELDDESCRIPTION = 6
024090               INVALID_PARAMETER    = 7
024100               UNDEFIND_ERROR       = 8
024110               OTHERS               = 9.
024120
024130     CLEAR V_IDX.
024140     CALL FUNCTION 'HELP_VALUES_GET_WITH_DD_NAME'
024150          EXPORTING
024160               SELECTFIELD                   = 'KTAAR'
024170               TABLENAME                     = 'ZTQ_KTAAR'
024180               TITEL                         = TEXT-P04
024190               SHOW_ALL_VALUES_AT_FIRST_TIME = 'X'
024200          IMPORTING
024210               IND                           = V_IDX
024220          TABLES
024230               FULL_TABLE                    = T_KTAAR
024240          EXCEPTIONS
024250               NO_TABLEFIELDS_IN_DICTIONARY = 1
024260               NO_TABLESTRUCTURE_GIVEN       = 2
024270               MORE_THEN_ONE_SELECTFIELD     = 3
024280               NO_SELECTFIELD                = 4
024290               OTHERS                        = 5.
024300     IF SY-SUBRC NE 0. MESSAGE W044. EXIT. ENDIF.
024310     READ TABLE T_KTAAR INDEX V_IDX.
>     IF SY-SUBRC NE 0. MESSAGE W045. EXIT. ENDIF.
024330     READ TABLE LT_DYN WITH KEY FIELDNAME = 'ZTQ_FLDS-KTAAR'.
024340     CHECK SY-SUBRC = 0.
Thanking You,
Rahul Asthana

Hi
The problem is a Warning message is triggered in a process for F4 (I suppose you're in PROCESS ON VALUE-REQUEST)
This kind of message isn't supported there, you can use a message type S
Max

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

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

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

ABAP RunTime Error for tcode : TS01

Hi Friends,
Actually we are getting the run time error while creating the standard security transaction using TS01.
After entering the data in the first screen -- click on the enter -- enter the details inside & click on save button--then it will go run time error.
Here while calling the method, we are getting the run time error.
call method cl_class_position_op_trs=>trs_flows_calculate_tax
      exporting
        im_tab_flow         = L_TAB_FLOWS
        im_company_code     = l_company_code
        im_security_account = l_security_account
        im_security_id      = l_security_id
      receiving
        re_tab_flow         = RE_TAB_FLOWS
      exceptions
        failed = 1
        others = 2.
if sy-subrc <> 0.
     MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
              RAISING FAILED.
endif.
Actuallly here the problem with the class becuase the class cl_class_position_op_trs itself has error.
In the class , in the local classes they are calling again the class cl_class_position_op_trs. becasue of this reason it was going to run time error.
So we are getting the run time error.
We have OSS note for the same problem.But i am unable to implement that.
Please guide me how to implement the OSS note 751947.(Note 751947 - TRS: Syntax error due to ABAP Compiler)
please find the error details:
Runtime Errors         SYNTAX_ERROR
       Occurred on     03/12/2008 at 00:26:57
Syntax error in program "CL_CLASS_POSITION_OP_TRS======CP ".
What happened?
The following syntax error occurred in the program
CL_CLASS_POSITION_OP_TRS======CP :
"Components of classes declared using "CLASS CL_CLASS_POSITION_OP_TRS D"
Error in ABAP application program.
The current ABAP program "CL_CLASS_POSITION_TRS=========CP" 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?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "CL_CLASS_POSITION_OP_TRS======CP
You can also perform the syntax check from the ABAP/4 Editor.
If the problem persists, proceed as follows:
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
The following syntax error was found in the program
CL_CLASS_POSITION_OP_TRS======CP :
"Components of classes declared using "CLASS CL_CLASS_POSITION_OP_TRS D"
Regards.
Lakshmi
Edited by: lakshmi podile on Mar 14, 2008 8:08 AM

Did you go through the steps in the note?
Use transaction SE24 to distribute the local classes into new include structures as follows:
Call transaction SE24 for the class CL_CLASS_POSITION_OP_TRS.
Select the following menu option:
Goto --> Class-local types --> Local Class Definitions/Types
Confirm the message that proposes conversion into the new structures.
Choose Utilities --> Regenerate sections from the menu.
Activate the class and all changed objects.
Try and do this, and see what happens.
Good luck.

How to catch CONVT_NO_NUMBER runtime error in ABAP Proxy

Hi all,
In our abap proxy program, sometimes the CONVT_NO_NUMBER will happen and cause the program dump and then stuck the whole queue. I noticed that this error cannot be caught by CX_ROOT exception class. So, how can I catch this runtime error and avoid the dump of our program?
Thanks,
YiNing

Hi,
While Executing the proxy,first give \h TC and then execute the proxy then it will automatically got to debugging mode.
I think ur data is worng,if it is wrong then only u will get this type of errors.
Regards,
Phani

UNCAUGHT_EXCEPTION is the ABAP Runtime error

Hi all,
Our Production System BI7.0 with oracle 10g running on Unix . The UNCAUGHT_EXCEPTION is the ABAP Runtime error exists in ST22.
Please find the Error analysis from ABAP Dump of UNCAUGHT_EXCEPTION.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_SDB_ORA_PROGRAM_ERROR', was not
     caught and
    therefore caused a runtime error.
    The reason for the exception is:
    An error occurred in the program:
    The occurrence of the exception is closely related to the occurrence of
    a previous exception "CX_SQL_EXCEPTION", which was raised in the program
     "CL_SQL_STATEMENT==============CP",
    specifically in line 31 of the (include) program
     "CL_SQL_STATEMENT==============CM002".
    The cause of the exception was:
    ORA-04031: unable to allocate 62208 bytes of shared memory ("shared
    pool","DBMS_STATS","PL/SQL MPCODE","BAMIMA: Bam Buffer")#ORA-06508: PL/SQL:
    could not find program unit being called: "SYS.DBMS_STATS"#ORA-06512: at line 1
Thanx,
Peter

Hi Peter,
You shared pool might be too small
Read,
SAP Note 869006 - Composite SAP note: ORA-04031
Regards
Juan

Runtime Error due To ABAP Dump LOAD_TYPE_VERSION_MISMATCH

Similar Messages

Maybe you are looking for