Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Dump IMPORT_WRONG_END_POS after NW 7.3 upgrade and unicode conversion

Hi All,

We are getting the below dump while calling t-code SCUA after upgrading the BI system from NW 7.0 to NW 7.3 and doing the unicode conversion.

Please advise

IMPORT_WRONG_END_POS

Category               ABAP Programming Error

Runtime Errors         IMPORT_WRONG_END_POS

Except.                CX_SY_IMPORT_MISMATCH_ERROR

ABAP Program           SAPLSUU6

Application Component  BC-SEC-USR-ADM

Date and Time          04.07.2013 09:59:17

Short text

     Length error in the IMPORT statement.

What happened?

     Error in the ABAP application program.

     The current ABAP program "SAPLSUU6" had to be interrupted because it contains

     a statement that cannot be executed.

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 "SUSR_ZBV_CHECK_IF_TEMP_OFF" "(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:

     During the import it was discovered that the target object has a

     different length to the object that is to be imported.

Missing RAISING Clause in Interface

     Program                                 SAPLSUU6

     Include                                 LSUU6U24

     Row                                     1

     Module type                             (FUNCTION)

Source Code Extract

Line  SourceCde

    5 *"     REFERENCE(TEMP_OFF) TYPE  CUA_TEMP_OFF

    6 *"     REFERENCE(CENTRAL_SYSTEM_LOGSYS) TYPE  USZBVLNDSC-SENDSYSTEM

    7 *"     REFERENCE(CENTRAL_SYSTEM_RFC_DEST) TYPE  RFCDES-RFCDEST

    8 *"     REFERENCE(BAPILINK) TYPE  CUSTMODEL

    9 *"  EXCEPTIONS

   10 *"      INVALID_MODEL

   11 *"      CHECK_ERROR

   12 *"----------------------------------------------------------------------

   13

   14 *&---------------------------------------------------------------------*

   15 *& LOCAL DATA DEFINITION

   16 *&---------------------------------------------------------------------*

   17   DATA:

   18     ls_usbapilink TYPE usbapilink,

   19     ls_cent_conn  TYPE ty_conn.

   20

   21 *&---------------------------------------------------------------------*

   22 *& START OF PROCESSING

   23 *&---------------------------------------------------------------------*

   24   CALL FUNCTION 'SUSR_ZBV_CHECK_IF_ACTIVE'

   25     EXCEPTIONS

   26       active         = 1

   27       not_active     = 2

   28       invalid_model  = 3

   29       OTHERS         = 4.

   30   CASE sy-subrc.

   31     WHEN 1.

   32       temp_off = ' '.

   33     WHEN 2.

   34 *     read saved date from indx

>>>>>       IMPORT usbl_data TO ls_usbapilink

   36              conn_data TO ls_cent_conn

   37       FROM DATABASE indx(cu) ID gc_indxkey.

   38       IF sy-subrc = 0.

   39 *       check imported data

   40         IF ls_cent_conn-logsys    IS INITIAL

   41         OR ls_cent_conn-rfcdest   IS INITIAL

   42         OR ls_usbapilink-bapilink IS INITIAL.

   43           MESSAGE e722(01) RAISING check_error.

   44         ENDIF.

   45 *       export status and imported data

   46         temp_off = 'X'.

   47         central_system_logsys   = ls_cent_conn-logsys.

   48         central_system_rfc_dest = ls_cent_conn-rfcdest.

   49         bapilink                = ls_usbapilink-bapilink.

   50       ELSE.

   51         temp_off = ' '.

   52       ENDIF.

   53     WHEN 3.

   54       MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno

Regards,

Pankaj Pabreja

replied

Hi All,

The SAP has released a new note 1887254 with corrections to be implemented in the system after 7.3 upgrade. This is applicable if you have temporarily disabled the CUA before upgrade.

Regards,

Pankaj

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question