Runtime Error CONNE_IMPORT_WRONG_COMP_LENG In Method CL_SALV_BS_RUNTIME_INFO=>GET_DATA

Runtime Error CONNE_IMPORT_WRONG_COMP_LENG In Method CL_SALV_BS_RUNTIME_INFO=>GET_DATA

Symptom

While executing the report, you run into runtime error CONNE_IMPORT_WRONG_COMP_LENG (Exception CX_SY_IMPORT_MISMATCH_ERROR) in Method CL_SALV_BS_RUNTIME_INFO=>GET_DATA.

Reason

One of the fields in the ALV data table is defined with of ABAP type C with length greater than 255 characters.
e.g.
field1(1000) TYPE c.
The problem doesn't occur while using type from DDIC (Dictionary).

The dump occurs in case at least one of data table's fields (even fields which aren't available in ALV field catalog) is of type C (CHAR) with length greater than 255.
In such case, when ALV data is imported, corresponding field is created as CHAR 255 instead of actual field's length, what leads to structure inconsistency issues..
The problem results from bug in method CL_SALV_BS_DDIC->DESCRIBE_ELEMENT (which is called by cl_salv_bs_ddic=>create_data_from_components): When field isn't from DDIC, ls_dfies-leng is set as lr_elemdescr->output_length, which is limited to 255 chars (Check note 777826 - "Output length of data elements with more than 255 characters").
The problem doesn't occur when field type is from DDIC (i.e. Data element or table field).


Solution

Replace the definition of the field to DDIC (data element/table field) instead of simple ABAP type.
e.g. 
field1 TYPE text1000.

    • Related Articles

    • Exception LCX_PROGRAM_ERROR In Method LCL_FUNCTIONAL=>ARGNAMES_GET

      Symptom After you have updated the interface of a customer (Z) formula function, any execution of Rainbow variant which makes use of this formula function leads to runtime error due to uncaught exception LCX_PROGRAM_ERROR in ...

    • Exception CNTL_ERROR (Control Framework: Fatal error - GUI cannot be reached)

      Symptom A background job of Publisher terminates with runtime error due to uncaught exception CNTL_ERROR (Error message "Control Framework: Fatal error - GUI cannot be reached" is written in the job log). Reason The original report doesn't support ...

    • Dump (Runtime Error)

      In case of dump (runtime error), please attach the complete dump to the ticket (as described in the OSS note 1896868 – How to save a short dump in text format: When a user receives a short dump at runtime mode, pay attention to the fact that the dump ...

    • Runtime Error SET_HANDLER_FOR_NULL In Transaction FBL3H

      Symptom When you run transaction FBL3H via Publisher/Rainbow, runtime error SET_HANDLER_FOR_NULL occurs in method CL_SALV_TREE_ADAPTER=>CREATE_TREE. Reason By default, transaction FBL3H displays an ALV tree of History. Submit of transaction with ALV ...

    • ME1L / ME1M - Error Message "no ALV table imported from memory"

      Symptom You have created a Insight Creator variant based on original transaction ME1L / ME1M. When you execute the variant error message  "no ALV table imported from memory" is raised and no results are displayed. Reason Transaction ME1L / ME1M has ...