on 05-06-2014 10:17 AM
Hello Experts,
I am trying to run the initialization for the Billing conditions 2lis_13_vdkon datasource.
Job is getting cancelled and the following error messages are coming when i check the job log in source system
Job started
Step 001 started (program SBIE0001, variant &0000000006238, user ID BASIS
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_13_VDKON
RLOGSYS = BWDCLNT900
REQUNR = REQU_DHKONXGA1B82HZ49O94KQ03C4
UPDMODE = C
LANGUAGES = *
*************************************************************************
* Current Values for Selected Profile Parameters *
*************************************************************************
* abap/heap_area_nondia......... 2000683008
* abap/heap_area_total.......... 2000683008
* abap/heaplimit................ 40894464
* zcsa/installed_languages...... ED
* zcsa/system_language.......... E
* ztta/max_memreq_MB............ 2047
* ztta/roll_area................ 3000320
* ztta/roll_extension........... 2000683008
*************************************************************************
Function module /BI0/QI2LIS_13_VDKON does not exist
You can only use LIKE and TYPE to specify types in RFC
Internal session terminated with a runtime error (see ST22)
Job cancelled
even when i check in ST22
Category | ABAP Programming Error |
Runtime Errors | IMPORT_ALIGNMENT_MISMATCH |
Except. | CX_SY_IMPORT_MISMATCH_ERROR |
ABAP Program | SAPLMCEX |
Application Component LO-LIS
Date and Time | 06.05.2014 12:30:28 |
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 "MCEX_BW_LO_API" "(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 importing object "MC13VD0KON_TAB", the structure did not match the | |
structure of the target object. The error occurred in component | |
no. 21. | |
This may be due to one of the following reasons: | |
- the structure is actually different (the next field has, for | |
example, a different data type) or | |
- the same sequence of components were exported and imported, | |
but the fields were from other include units. |
How to correct the error
There is a probably a new version of the program active that does | |||
not match the dataset. The data may not have been converted. | |||
It is also possible that the field type of the imported field has been changed in the Data Dictionary. Try to eliminate the error by regenerating the program "SAPLMCEX". To do this, proceed as follows: Call Transaction SE38 in the R/3 System, enter the program name "SAPLMCEX" and then choose "Generate". If the error occurred in your own ABAP program or in an SAP program you modified, try to remove 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: "IMPORT_ALIGNMENT_MISMATCH" "CX_SY_IMPORT_MISMATCH_ERROR" "SAPLMCEX" or "LMCEXU06" "MCEX_BW_LO_API" If you cannot solve the problem yourself and want to send an error please help me in this regards Quick response will be appreciated. Thanks in advance |
Hi,
Any upgrades were happen recently?
Are you able to run your data source extraction at RSA3(source side)?
Can you run full load info pack and see.
Where your facing this issue. At dev or prod?
Reactivate your data source structure, data source and all settings LBWE.
Try to load full load once with small selections and lets see whether its its working or not.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ram,
no upgrades recently
they have taken backup from production server.
now i am facing this prob in development server.
when i am trying to check in RSA3 it is throwing same short dump
as u said i did all the re activations still i am facing the same issue.
please give me some other sol...
thanks,
srikanth Putta'
Hi,
Can you share LBWE screen shot of your data source settings.
If you have done all steps again at dev, it should work.
If not then any your dev and prod may not be in synch. some patches or updates were missing at dev system.
Check table RSLOGSYSMAP at ecc dev and bw dev. need to have same technical names of source and target names.
Thanks
SAPLMCEX - means you are using "user exit" coding next to the standard DataSource... your problem lies there most likely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.