Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from hari131 on Feb 12 at 2:00 AM I checked the OSS notes but i didn't found any notes for associated to the error. Can you please let me know if you have any idea about this?
| | | ---------------Original Message---------------
From: BELLAMKONDA HARIKRISHNA
Sent: Tuesday, February 11, 2014 2:55 AM
Subject: CONNE_IMPORT_WRONG_COMP_LENG
Short text
Error when attempting to IMPORT object "IMLCUM".
What happened?
Error in the ABAP Application Program
The current ABAP program "J_1GVL_VL" 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.
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 "UPDATE_ONLINE_WHB_YTD_TOTALS" "(FORM)", 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:
When importing the object "IMLCUM", the component 2 in the dataset
had a different length from the corresponding component of the
target object in the program "J_1GVL_VL".
The length is 4 in the dataset, but 6 in the program.
How to correct the error
Try to find out why the length of the object should be 4.
There are various possible options:
1. The length of the imported field has changed in the Data Dictionary.
Make sure that the length of the imported field matches the length
of the field in the Data Dictionary.
If the data cannot be restored from another source, the data must be
read by the 'old' structure, converted und again eported with the new
structure, so that future IMPORTs will always function with the new
structure.
2. A new program version is active, which no longer fits the dataset.
Try to solve the error generating the program "J_1GVL_VL" again. This
works as follows: Select transaction SE38 in the SAP system. Enter
the program name "J_1GVL_VL". Then activate the function 'Generate'.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CONNE_IMPORT_WRONG_COMP_LENG" "CX_SY_IMPORT_MISMATCH_ERROR"
"J_1GVL_VL" or "J_1GVL_VLI03"
"UPDATE_ONLINE_WHB_YTD_TOTALS"
The exception must either be prevented, caught within proedure
"UPDATE_ONLINE_WHB_YTD_TOTALS" "(FORM)", or its possible occurrence must be
declared in the
RAISING clause of the procedure.
To prevent the exception, note the following: |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
