Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG

Former Member — Tue, 11 Feb 2014 08:08:35 GMT

Hi Experts,

Recently our APPL system has been upgraded and after this upgrade activity we are getting the dumps "CONNE_IMPORT_WRONG_COMP_LENG" .

Can someone please help me to come out from this issue.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Short text

Error when attempting to IMPORT object "IMLCUM".

What happened?

Error in the ABAP Application Program

The current ABAP program "J_1GVL_VL" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

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 that is explained in detail below.

The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was

not caught in

procedure "UPDATE_ONLINE_WHB_YTD_TOTALS" "(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 "IMLCUM", the component 2 in the dataset

had a different length from the corresponding component of the

target object in the program "J_1GVL_VL".

The length is 4 in the dataset, but 6 in the program.

How to correct the error

Try to find out why the length of the object should be 4.

There are various possible options:

1. The length of the imported field has changed in the Data Dictionary.

Make sure that the length of the imported field matches the length

of the field in the Data Dictionary.

If the data cannot be restored from another source, the data must be

read by the 'old' structure, converted und again eported with the new

structure, so that future IMPORTs will always function with the new

structure.

2. A new program version is active, which no longer fits the dataset.

Try to solve the error generating the program "J_1GVL_VL" again. This

works as follows: Select transaction SE38 in the SAP system. Enter

the program name "J_1GVL_VL". Then activate the function 'Generate'.

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:

"CONNE_IMPORT_WRONG_COMP_LENG" "CX_SY_IMPORT_MISMATCH_ERROR"

"J_1GVL_VL" or "J_1GVL_VLI03"

"UPDATE_ONLINE_WHB_YTD_TOTALS"

The exception must either be prevented, caught within proedure

"UPDATE_ONLINE_WHB_YTD_TOTALS" "(FORM)", or its possible occurrence must be

declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

Line SourceCde

11217 tbl_purch, tbl_pu, tbl_gr,

11218 tbl_prod, tbl_cost, tinx,

11219 tbl_oidt, oidat, asdat,

11220 tbl_anal, tbl_canal, tbl_analp, tbl_anals, tbl_intr,

11221 tbl_rev,

11222 *{ DELETE CZRK021270 1

11223 *\ tbl_trans,

11224 *\ tbl_neg, tbl_neg_pr, tbl_negpc, tbl_coprod, tbl_nocost,

11225 *} DELETE

11226 *{ INSERT CZRK021270 2

11227 tbl_neg, tbl_neg_pr, tbl_negpc, tbl_coprod, tbl_byprod, tbl_nocost,

11228 *} INSERT

11229 tbl_totals.

11230

11231 * ytd aggregation: retrieve buffered COL data of previous months

11232 if gf_ytd_aggr = continuing.

11233 clear ls_bufkey.

11234 ls_bufkey-bukrs = s_bukrs.

11235 ls_bufkey-iaskz = p_ias.

11236 ls_bufkey-dtgrp = col.

11237 loop at gr_dates_prev.

11238 write gr_dates_prev-low to l_dat.

11239 concatenate 'YTD aggregation: Retrieving buffered COL data of'

11240 l_dat '...'

11241 into l_txt separated by space.

11242 perform update_progress using l_txt.

11243 clear lt_mlcum[].

11244 ls_bufkey-budat = gr_dates_prev-low.

11245 case gv_mlbuf_area.

11246 when gc_mlbuf_area1.

>>>>> import imlcum to lt_mlcum

11248 from database j_1gvl_mlbuf(vl) id ls_bufkey.

11249 when gc_mlbuf_area2.

11250	import imlcum to lt_mlcum
11251	from database j_1gvl_mlbuf(v2) id ls_bufkey.
11252	when gc_mlbuf_area3.
11253	import imlcum to lt_mlcum
11254	from database j_1gvl_mlbuf(v3) id ls_bufkey.
11255	endcase.
11256	loop at lt_mlcum into imlcum.
11257 *{ DELETE	CZRK022179	3
11258 *\	collect imlcum into imlcum.

11259 *} DELETE

11260 *{ INSERT	CZRK022179	4
11261	read table imat with key matnr = imlcum-matnr
11262	werks = imlcum-vlwrk
11263	bwtar = imlcum-bwtar
11264	binary search.
11265	check sy-subrc = 0.
11266	imlcum-sptag = l_prev_run_date.

Re: Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG

gouravkumar64 — Tue, 11 Feb 2014 08:29:11 GMT

Hi,

Not sure about your issue,can you please check this 3 notes & correction instructions.

I saw the correction,looking like your issue.

1554790 - Material Valuation: An issue regarding YTD aggregation

1776415 - Material Valuation: Correction for YTD aggregation

1637421 - Short dump CONNE_IMPORT_WRONG_COMP_LENG

Thanks

Gourav.

Re: Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG

Former Member — Tue, 11 Feb 2014 17:17:46 GMT

hi krishna,

as from the dump its given as data length mismatch from source and destination...

you can check this error by keeping a break point on the source code before the error line shown in the dump... and then check for the data assighned between the objects as shown above are with different length or or not... if so then change the data coming inside into the object to legth 4 in debugging mode and execute.. this error may be rectified...

topic Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG in Application Development and Automation Discussions

Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG

Re: Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG

Re: Runtime Errors CONNE_IMPORT_WRONG_COMP_LENG