CONNE_IMPORT_WRONG_COMP_LENG error

[Former Member]

Hi All,

We are at SAP ECC 5.0 SAP_BASIS 640.

we got " CONNE_IMPORT_WRONG_COMP_LENG" dump WITH THE EXCEPTION "CX_SY_IMPORT_MISMATCH_ERROR". Could you please help me to fix this problem?

Here is the error info:

-

---

What happened?

Error in ABAP application program.

The current ABAP program "RMCY9940" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

data was not the same as the length of the data created

in the program.

Error in ABAP application program.

The current ABAP program "RMCY9940" had to be terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

-

---

Error analysis

An exception occurred. This exception is dealt with in more detail below

. The exception, which is assigned to the class 'CX_SY_IMPORT_MISMATCH_ERROR',

was neither

caught nor passed along using a RAISING clause, in the procedure

"%_IMPORT_VARI_CLNT" "(FORM)"

.

Since the caller of the procedure could not have expected this exception

to occur, the running program was terminated.

The reason for the exception is:

When importing the object "SL_0008", the component 3 in the dataset

had a different length from the corresponding component of the

target object in the program "RMCY9940".

The length is 5 in the dataset, but 2 in the program.

-

---

User and Transaction

Client.............. 500

User................ "WKOEIJER"

Language key........ "E"

Transaction......... " "

Program............. "RMCY9940"

Screen.............. "RMCY9940 1000"

Screen line......... 3

-

---

Information on where terminated

The termination occurred in the ABAP program "RMCY9940" in

"%_IMPORT_VARI_CLNT".

The main program was "RMCY9940 ".

The termination occurred in line 82 of the source code of the (Include)

program "RMCY9940"

of the source code of program "RMCY9940" (when calling the editor 820).

The program "RMCY9940" was started as a background job.

Job name........ "RMCY9940"

Job initiator... "WKOEIJER"

Job number...... 06010001

Processing was terminated because the exception "CX_SY_IMPORT_MISMATCH_ERROR"

occurred in the

procedure "%_IMPORT_VARI_CLNT" "(FORM)" but was not handled locally, not

declared in the

RAISING clause of the procedure.

The procedure is in the program "RMCY9940 ". Its source code starts in line 82

of the (Include) program "RMCY9940 ".

-

---

Internal notes

The termination occurred in the function "CheckSimpleComponent" of the SAP

Basis System, specifically in line 1136 of the module

"//bas/640_REL/src/krn/runt/abconne.c#21".

The internal operation just processed is "IMPO".

The internal session was started at 20080915060159.

-

---

Source Code Extract

Line SourceCde

52 SELECT-OPTIONS SL_SPTAG FOR S994-SPTAG MODIF ID PER.

53 SELECT-OPTIONS SL_SPWOC FOR S994-SPWOC MODIF ID PER.

54 SELECT-OPTIONS SL_SPMON FOR S994-SPMON MODIF ID PER.

55 SELECT-OPTIONS SL_SPBUP FOR S994-SPBUP MODIF ID PER.

56 SELECTION-SCREEN END OF BLOCK ZEITRAUM.

57 RANGES: PERIOTAB FOR S994-SPTAG.

58 * Erweiterte Selektion: Abgrenzung 　er Hierarchie *

59 INCLUDE RMCS0ES2.

60

61 * Parameter *

62 SELECTION-SCREEN BEGIN OF BLOCK PARAM WITH FRAME TITLE TXT_PARA.

63 PARAMETERS: SL_WAERS LIKE RMCS0-AWAER1.

64 * Allgemeine Parameter *

65 INCLUDE RMCS00SP.

66 SELECTION-SCREEN END OF BLOCK PARAM.

67

68 * AT SELECTION-SCREEN ON-Verarbeitung f　 allgemeine Parameter *

69 INCLUDE RMCS00SO.

70

71 * Ablauflogik *

72 INCLUDE RMCS00AL .

73

74 * Globale Formroutinen *

75 INCLUDE RMCS0F00 .

76

77 * Applikationsspezifische Formroutinen *

78 INCLUDE RMCV0F00.

79

80 * Formroutinen f　 Analyse 6994 *

81 INCLUDE RMCY994F.

[Former Member]

Have you looked for notes?

Rob

[Former Member]

Rob,

Yes, I looked for the note but cannot find anything which can fix my problem.

Leo

[Former Member]

It's a standard SAP program, so you might want to send it to them via a message.

Rob

[Koen_VL]

programs RSVCHECK and RSVARDOC_610 can help. More info can be found in this SAP note: 153865

http://service.sap.com/sap/support/notes/153865