CPA dynamic error occurs UC_OBJECTS_NOT_CONVERTIBLE.

[Former Member]

Hello dear SAP CRM specialist!

There was a problem while trying to BW system to receive data from CRM. I quote the following scenarios for their reproduction.

When calling extractor 0BPARTNER_ATTR mode delta downloads landscape CPA dynamic error occurs UC_OBJECTS_NOT_CONVERTIBLE.

Quick Overview about the dump in attached file:

Termination occurred in the ABAP program "SAPLRSC1" - in "HANDLE_COMP_DATA".
    The main program was "RSFHGEN2 ".

    In the source code you have the termination point in line 421
    of the (Include) program "LRSC1F01".

Source code fragment:

      IF dc_buflen < tleng.
        DO.
          dc_newrest = dc_buflen.
          PERFORM read_next_decomp_data USING dc_newrest
                                        CHANGING subrc.
          IF subrc <> 0. EXIT. ENDIF.
          IF dc_buflen >= tleng. EXIT. ENDIF.
        ENDDO.
        IF subrc <> 0. EXIT. ENDIF.
        dc_actlen = 0.
      ENDIF.
    ENDIF.

    ASSIGN dc_buffer+dc_actlen(tleng) TO <f> TYPE 'X'.
    dc_actlen = dc_actlen + tleng.
    value = <f>.

    ASSIGN value TO <l_f> TYPE 'C'.
    >>>MOVE <l_f> TO e_t_data.    APPEND e_t_data.

Was tested in extractor mode delta downloads landscapes CDA and CQA, and extractor works nominally: data are uploaded.

When we call the extractor in a full load mode in the CPA - extractor worked normally.

Another scenario reproduce the error:

in CPA: transaction RSA3 → Source: 0BPARTNER_attr → change update mode from F to D

In the extraction the error occurred.

error message: RJ012.

Please help to solve this problem.

Regards,

Pavel.

[Former Member]

Hi Colleagues,

Note was created for avois this type of issue:

2214356 - Shortdump "DATA_LENGTH_TOO_LARGE" "HANDLE_COMP_DATA" when trying to extract data

Regards,

Janaina

[Former Member]

Hello Pavel,

I'm facing the same problem.

Please let me know whether you have found the solution. It will be helpful for me.

Thanks in advance.

Regards,

Vignesh

[Former Member]

Hello Kumar!

We have solved this problem as follows:

Was filled SQL stack on 2uh instances, after cleaning it all worked.

I hope this will help you!

BR,

Pavel.

[former_member182421]

Hello Pavel,

Seeing your error I would suggest to raise a OSS message.

Cheers!

Luis