Runtime error when accessing variant of a table whose structure has changed

[Former Member]

Hi Experts,

We have a custom table to which a new field was added recently and moved to Production. Now while trying to access the table variant to retrieve data from the table in SE16, we get runtime error

Runtime Errors CONNE_IMPORT_WRONG_COMP_TYPE

Exception CX_SY_IMPORT_MISMATCH_ERROR

Date and Time 08-04-2011 15:46:36

Short text

Error when attempting to IMPORT object "I15".

What happened?

Error in the ABAP Application Program

The current ABAP program "/1BCDWB/DBZFIGL_SEGHEADER" 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.

We have rebuilt the variant with the same selection parameters and saved it with same name and it works fine now.

Has anyone experienced the same issue?

Thanks,

Leena

[former_member305388]

I tried this scenario in Dev Server and found that is you have a variant with a few fields and if you add a new field in between those, then it cannot fetch the values for variant instead gives an error given below:

Message no. DB634

Diagnosis

You attempted to start report /1BCDWB/DBZRPROJ using variant TEST. Since this variant was generated, the report SELECT-OPTIONS or PARAMETERs have changed considerably, i.e. the type or length no longer match and PARAMETERs have become SELECT-OPTIONS or vice versa. Many of these changes are so serious that even attempting to import the variant results in runtime errors.

Procedure

Adjust or delete the variant.

So, as suggested, you can either Adjust or Delete and recreate the variant.

Hope this helps.

[Former Member]

Hi Srinivas,

But the field added in not in between the fields that hold value in the variant in this case.

Thanks,

Leena

[former_member305388]

It not only depends on where the field is added but also on which fields were selected at the time of variant creation. In other words, the screen on which you are providing variant has now an extra field. You can try by just restricting that field from being displayed ont he screen by through Settings->Fields for selection.

Try hiding the new field or any fields and make sure the structure is the same as before.

For example.. there are 5 fields in your table...

fld1

fld2

fld3

fld4

fld5

You have created variant when the structure was like this:

fld1

fld2

fld4

Now, you have added fld6 at the bottom and the screen is given as:

fld1

fld2

fld3

fld4

fld5

fld6...

Now it gives error for sure... but if you try hiding fld3 and fld5... this solves the problem... fld6 will not affect as it is placed at last...

Hope this solves your problem.

Edited by: Srinivas Kalluri on Aug 5, 2011 3:46 PM

Edited by: Srinivas Kalluri on Aug 5, 2011 3:49 PM

[Former Member]

Hi Leena,

This is a kind of work around only...

Are you able to see the values stored in variant with below process ...

Once you went to second screen of SE16, in MENU go to GOTO->VARIANTS->DISPLAY, then select the variant from the list there you can see the values, and then with those values create a new variant...

Thanks:

RK

[Former Member]

Hi RK,

Thanks for the workaround, but the effort would be cumbersome if we have more number of variants. I would like to know if there is a solution to make sure that this will not happen.

Thanks,

Leena

[Former Member]

Run standard program RSVARDOC_610 (Rescue obsolete variants).

Rob

[Former Member]

*