LOAD_TYPE_VERSION_MISMATCH

hie all
im getting this dump type with no clues as to what could have gone wrong, pliz assist. also there is additional text :
"There is no help text for this dump
Either the text was inadvertently deleted or the release of
the kernel differs from that of the database.
Refer to the Note system for further information on            this dump. "
regards
Prince

Please look at SAP Note : 1010590
The ABAP program terminates due to structure components that are too wide (64KB or greater). Depending on the kernel patch and Support Package status:
when you generate the program, it leads to the error DDIC_TYPES_INCONSISTENT, or
when you execute the program, it leads to the error LOAD_TYPE_VERSION_MISMATCH.
Other terms
Runtime object, DBLENGTH, DBLENGTH2, DDIC_TYPES_INCONSISTENT, LOAD_TYPE_VERSION_MISMATCH
Reason and Prerequisites
If a structure (S1) has a total length of more than 65535 bytes and is used as a structure component in another structure (S2), this length can no longer be managed in the runtime object of S2.
This causes an overflow, and then leads to an error.

Similar Messages

Short Dump LOAD_TYPE_VERSION_MISMATCH

Hello,
We have copied the standard form in HRFORMS to a custom one and made changes, Changes only made in the ADOBE interface and layout. Its working in Development environment. Then we moved the transport to the Quality and we activated the HRFORMS and executed to print checks and getting the dump
LOAD_TYPE_VERSION_MISMATCH.
Could anybody tell what's the issue is. Is there any other way of activating HRFORMS apart from going through to menu bar utilities -> Activate forms.
Regards,
Hemanth.
Edited by: keerthipati hemanth on Jan 12, 2010 9:27 AM

Check Note 1338583 and Note 1010590.
Chintan

Need Help Regarding LOAD_TYPE_VERSION_MISMATCH

Dear gurus
While executing T-code vl01n vl02n vl03n
im having this error
LOAD_TYPE_VERSION_MISMATCH
Short text
 Change of a Dictionary structure at runtime of a program.
What happened?
 Runtime error
 The current ABAP program "SAPMV50A" 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.
Please help me
Regards
Saad

Hi Saad,
if i call the vl01 i've got a raise exception with internal error:
 74 FORM CUKRX_GET_STATUS_RELEASED.
 75
 76 * IF CUKRD_KNSTA_RELEASED IS INITIAL.
 77 SELECT * FROM TCUX WHERE KNREL = 'X'.
 78 APPEND TCUX-KNSTA TO CUKRD_KNSTA_RELEASED.
 79 ENDSELECT.
 80 IF SY-SUBRC <> 0.
 81 *..identifier for status 'RELEASED' not found........
 82 RAISE INTERNAL_ERROR.
 83 ENDIF.
 84 SORT CUKRD_KNSTA_RELEASED.
 85 * ENDIF.
And this table is empty, so it raises the internal error.
What show your st22-output about the ABAP code ?
regards
Kay

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

LOAD_TYPE_VERSION_MISMATCH Error in LSMW

Hi,
We have changed some custom fields in BUT000 and imported into PreProduction. And the table is adjusted and its active now.
However, When I run LSMW program (Convert Data), I am getting the following dump.
Error:
LOAD_TYPE_VERSION_MISMATCH.
Error Analysis:
The dictinary type BUT000 is changed during the flow of transaction as the type was already used in the old version, and the new type should be used in the new version.
Can you please help me out, how can I solve this.
Thanks,
Sandeep

Hi
You need to check where that type is used ,problably you need to define the step again in order to use the new definition
Max

How to delete the structure created from Tx: EEWB ?

Hi SAP Gurus
I have an issue at hand. I have added three components in the structure BUS000___I and the components are ZZ1, ZZ2, ZZ3, I was following the EEWB wizard and from there these three components were made, now I cannot delete these components directly from SE11. Because after adding these components the system is not allowing me to do so and is asking for the access code.
I am getting a syntax error in all the tx where Business Partner is used. No old versions for this structure was found in the system. The only structure that has come into this BP structure is ZBSTC0000000000 followed by three data elements of this structure.
I know the Project and the enhancement that was created and I have tried deleting the enhancement from EEWB but when i try deleting it, it always fall into an intermediate stage where it leaves some entries and due to these left over entries these errors are coming.
Another imp thing is that the structure that i have reported is a newly created one I cannot find this anywhere else. looks like this structure was created after executing the EEWB transaction only.
Now when I try activating the enhancement again the magic wand button used to activate an enhancement and the generate button is also inactive in EEWB and now it is not getting activated, even after rt click enhancement then clicking change or by clicking on the edit-change button on the top tool bar. Do you think if I create another enhancement this button might get activated?
Please let me know how do I delete these components.
Kindly reply at the earliest.
Regards,
Amit

Hi, I had the similar problem (and here the solution):
Spezifikation: Deletion of EEWB fields manually, error in middleware bdoc,
Kurztext
Deletion of EEWB fields manually, error in middleware bdoc,
Langtext
BDOC-Error from function module BAPI_CRM_SAVE. no further using of the
middleware for sales activities (sales order) possible.
see steps for reconstruction
Schritte zur Rekonstruktion
what done before:
- added one field via transaction code EEWB to business object
SALES_TRANSACTION (Verkaufsvorgang), "Erweiterungstyp CUSTOMER_I
(Positions-Zusatzextension erweitern) with one existing data element
type Z_, Geschäftsvorgangstypen = Verkauf
no selection of "Datenaustausch mit den Mobile Clients",
"Datenaustausch mit R/3 Supply Chain Execution" or
"Business Information Warehouse".
- deleted the extension manually, deleted the eewb project manually
(successful)
- got an short dump on saving a sales order via transaction code
CRMD_ORDER:
dump type: LOAD_TYPE_VERSION_MISMATCH
Der Abbruch trat im ABAP-Programm "SAPLCRM_UPLOAD" auf, und zwar in
"CRM_UPLOAD_BUS_TRANS_MSG". Das Hauptprogramm war "CRM_1O_FRAME ".
Im Quelltext befindet sich die Abbruchstelle in Zeile 5
des (Include-)Programms "LCRM_UPLOAD$18".
(bei Anwahl des Editors: 50) der ABAP-Source "LCRM_UPLOAD$18".
000040 *********************************************************
FUNCTION $$UNIT$$ CRM_UPLOAD_BUS_TRANS_MSG
000060
000070 IMPORTING
000080 REFERENCE(IV_GUID) TYPE !CRMT_OBJECT_GUID
000090 EXPORTING
000100 REFERENCE(ES_BDOC_HEADER) TYPE !SMW3_FHD
000110 REFERENCE(ES_BDOC_MESSAGE) TYPE !/1CRMG0/BUS_TRANS_MSG
000120 REFERENCE(ES_BUS_TRANS_MSG) TYPE !BAD_BUS_TRANSN_MESSAGE
000130 EXCEPTIONS
000140 !ERROR_OCCURED .
- re-generation of a lot of of function modules
(e.g. CRM_UPLOAD_BUS_TRANS_MSG)
and some corresponding structures (e.g. CRMT_CUSTOMER_I_COM)
- fixed the short dumps with this gereration
Current Errors:
- the crm middleware (mBdoc) cannot copy sales orders from crm to r/3
- via transaction code CRMD_ORDER i copy an existing sales order and
save or try to change just one field and save.
- saving is succesfull (message type s), but on changing again, the
order is locked by middleware
- bdoc in transaction SMW02 is on state yellow "An Empfänger gesendet
(nicht alle haben bestätigt) BUS_TRANS_MSG"
- in transaction code SMW02 occurs:
Mdt Benutzer Funktionsbaustein Queue-Name
100 CPIC_FILO BAPI_CRM_SAVE R3AD_SAL_ERR
Datum Zeit
12.04.2007 17:52:10
Statustext
Inkonsistenz zwischen den DDIC-Typen CRMT_CUSTOMER_I_COMT und ABAP-
genera
SOLUTION:
re-generation of *ALL* code which using structure CRMT_CUSTOMER_I_COMT had solved it.

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.

EhP1 installer error (RFC of "SUBST_START_REPORT_IN_BATCH" failed)

Hi,
we are trying to upgrade our CRM 7.0 to the EhP1 and the EhP1 installer is blocked with the error:
Checks after phase MAIN_SHDRUN/ALTNTAB_FILL were negative!
Last error code set: RFC call to SUBST_START_REPORT_IN_BATCH failed with key RFC_ERROR_SYSTEM_FAILURE (SYSTEM_FAILURE): connection closed without message (CM_NO_DATA_RECEIVED)
Log files report the following errors:
(altntfi.sav)
#---- MASKING file ALTNTFI.LOG from G:\usr\sap\CR7\EHPI\abap\log
#---- TIME: 20111125115607 PHASE: ALTNTAB_FILL
1 ETQ201 Entering upgrade-phase "ALTNTAB_FILL" ("20111125111509")
4 ETQ399 Set environment for standard connect:
2 ETQ367 Connect variables are set for standard instance access
4 ETQ399 System-nr = '02', GwService = 'sapgw02'
4 ETQ399 Environment variables:
4 ETQ399 dbs_ora_schema=SAPSR4
4 ETQ399 auth_shadow_upgrade=0
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/ALTNTAB_FILL'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = '30'
2 ETQ399 Arg[1] = 'ALTNTFI.ELG'
4 ETQ399 Set environment for shadow connect:
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '07', GwService = 'sapgw07'
4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"
4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"
4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"
4 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ399 default TPPARAM: SHADOW.TPP
4 ETQ010 Date & Time: 20111125111509
4 ETQ265 Starting report "RDDNT2MT" with variant "SAP_INIT" in batch
4 ETQ359 RFC Login to: System="CR7", Nr="07", GwHost="SYSKCRMDEV1", GwService="sapgw07"
4 ETQ232 RFC Login succeeded
4 ETQ233 Calling function module "SUBST_START_REPORT_IN_BATCH" by RFC
2EETQ360 RFC of "SUBST_START_REPORT_IN_BATCH" failed:
2EETQ361 code/exception : SYSTEM_FAILURE
2EETQ362 key : RFC_ERROR_SYSTEM_FAILURE
2EETQ364 message :
2EETQ399 connection closed without message (CM_NO_DATA_RECEIVED)
4 ETQ359 RFC Login to: System="CR7", Nr="07", GwHost="SYSKCRMDEV1", GwService="sapgw07"
4 ETQ232 RFC Login succeeded
2EETG894 Exception "SYSTEM_FAILURE" raised, write variant failed with error code -1
2EETG890 Exception "SYSTEM_FAILURE" raised, job scheduling failed with error code -1
2EETQ261 Start of batchjob "RDDNT2MT" failed
4 ETQ010 Date & Time: 20111125111548
We have logged through GUI to the shadow instance but we can't test the function module SUBST_START_REPORT_IN_BATCH: the shadow instance continuously dumps (in SE37, ST22, ST11, SU01... with dumps LOAD_PROGRAM_CLASS_MISMATCH, GETWA_WRONG_LENGTH, LOAD_TYPE_VERSION_MISMATCH...). When I don't have a dump (i.e. I try to activate the function module in SE37 without opening it), the GUI closes with the error: "Work process restarted, session terminated " and in the logfile dev_disp shows me:
Fri Nov 25 11:15:30 2011
*** ERROR => DpHdlDeadWp: W5 (pid 17996) died (severity=0, status=0) [dpxxwp.c 1522]
Any help would be greatly appreciated.
Thanks,
Davide

Hi Davide,
Please try out below mentioned steps
Set the USER Environment Variable u2018auth_shadow_upgradeu2019 to u20181u2019 for the <SID>adm user (set the variable while logged in as that user)
Change the Shadow Instance service to run with the <SID>adm account
Stop the Shadow Instance (you can leave the Central and SCS Instances running)
Start the Shadow Instance
Continue the EHPI process from where it left off
Hope this helps.
Regards,
Deepak Kori

Creation of DR instance problem

Hi,
We created our failover (DR) instance by copying the DB and Kernel from production instance. Distaster recovery instance is up, but almost each and every screen is throwing some or other error like LOAD_PROGRAM_CLASS_MISMATCH, LOAD_TYPE_VERSION_MISMATCH, call_function_conflict_leng and so on.. Please help.
ECC 6.0 / Oralce 10.2.0.4 / NT
Edited by: Dhimbak on May 14, 2010 9:12 PM

Raj,
SICK is clean nad ST11 i can access too. Here is log
ABAP Program SAPLWB_CUSTOMIZING .
A Source LWB_CUSTOMIZINGU01 Line 21.
A Error Code TYPELOAD_NEW_VERSION.
A Module $Id: //bas/700_REL/src/krn/runt/abtypload.c#9 $ SAP.
A Function ab_CheckTypeloadTimestamp Line 2231.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_GOTO_RABAX
A A newer version of data type RSEUMOD was found than one required.
Thanks

Production Issue in Barcoding - Need Help

Hi,
One of our plant reported that there is a serious production
issue and they are not able to dispatch or receive goods. We
understand that the plants are getting 'ABAP Runtime Error' in
the hand held scanner and when we looked at the last transports,
we came across with the following error:
LOAD_TYPE_VERSION_MISMATCH
Please help me what is the issue and what needs to be done to
resolve this barcoding issue.
Thanks,
Sriram

please see OSS Note 713492 & 1010590 to see if this is your problem -
cheers
nandu
====================================================
OSS Note 713492 brief
Symptom
An additional time stamp check has been installed in the internal structure administration of the ABAP VM. This is supposed to ensure improved analysis of errors that may occur as a result of changes to dictionary types at runtime. In addition to the LOAD_TYPE_VERSION_MISMATCH short dump, the TYPELOAD_NEW_VERSION short dump may now also occur.
==========================================================
OSS Note 1010590 brief
Symptom
The ABAP program terminates due to structure components that are too wide (64KB or greater). Depending on the kernel patch and Support Package status:
when you generate the program, it leads to the error DDIC_TYPES_INCONSISTENT, or
when you execute the program, it leads to the error LOAD_TYPE_VERSION_MISMATCH.
Other terms

Object Versions invalid after DB actions (table copy)

Hi all,
recently I have encountered some weird issues during a little archiving run I'm doing on MM_MATBEL.
Tables involved:
IMEXT
MKPF
MSEG
MSEGO1
MSEGO2
NAST
OIAQB
After the archiving was done I logically went for an online reorg of these tables. This worked for all tables, except for MSEG. The reason was the following:
BR1962W Table SAPSR3.MSEG has more than 255 columns
BR1967W Table SAPSR3.MSEG would be implicitly decompressed during reorganization
BR1111I Reorganization of table SAPSR3.MSEG will be skipped
So apparently the table had been compressed in the past (when it had less than 255 columns) and now cannot be rebuilt anymore with compression.
In the following note they mention a workaround/solution:
http://service.sap.com/sap/support/notes/1872983
The solution consists of copying the compressed table into a newly created table. After some problems with the script (which will be fixed) and consulting SAP Support I finally succeeded in rebuilding the tables.
After this rebuild there are numerous dumps (LOAD_FORMAT_ERROR, DDIC_TYPE_INCONSISTENCY, LOAD_TYPE_VERSION_MISMATCH, etc...) in SAP itself, rendering the system practically unusable.
One workaround is to manually re-activate the object generating the shortdump, this does solve the issue on that object, but that's it.
I can hear you think: "Run SGEN, you stupid". Well, I did, and it did not help, or at least not much. It did regenerate some objects, but apparently it's not sufficient.
To me it seems like some inconsistency in the Dictionary, caused by the tables that were rebuilt. Is there a way that we can regenerate the Data Dictionary of SAP? Or at least fix the DDL inconsistencies?
The tables that I have recreated using note 1872983 are:
LIPS
MSEG
VBAP
VBRP
ZEKPO
N2CA02
N2CA03
N2CA04
N2CA05
N2CA09
PA0008
PA0146
PA0701
PA0706
PA0764
PA0897
PB0008
T5ITT7
RSEUMOD
COMPMOVE
WDFR_POS
N3BGF1008
OIUH_RV_JE
OIUH_RV_RJE
TTONFTVZZBEPP
TLVC_DFT_ASSGN
If you have any suggestions, I'd love to hear them.
Thanks in advance
Dieter Waelkens
Ps:
I've found notes
http://service.sap.com/sap/support/notes/1567187
http://service.sap.com/sap/support/notes/162991
I'll analyze them and come back with an update
Message was edited by: Dieter Waelkens (added notes in the end)

Hello Dieter,
Looks like your errors are more related to DDIC problems than program problems, this might be why SGEN could not help.
Report RUTMSJOB could help, at least to identify if there are inconsistencies, that could be fixed by re-activating the tables.
Check note 1538932 - RUTMSJOB error with check DDTYPES
You could also use report RSNTABCONSISTENCY from note 1167784 - Runtime error DDIC_TYPE_INCONSISTENCY
Regards
Options for RUTMSJOB in expert mode.

LOAD_TYPE_VERSION_MISMATCH

Similar Messages

Maybe you are looking for