12-30-2008 8:06 PM
Hi,
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_CONVERSION_CODEPAGE', was no
caught in
procedure "OPEN_INPUT_FILE" "(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:
Characters are always displayed in only a certain codepage. Many
codepages only define a limited set of characters. If a text from a
codepage should be converted into another codepage, and if this text
contains characters that are not defined in one of the two codepages, a
conversion error occurs.
Moreover, a conversion error can occur if one of the needed codepages
'4110' or '4102' is not known to the system.
Example: µ is creating problems.
I have a problem in uploading the file with below format
F091US122580164 PECOSPHERE C18,3µm,33X4.6MM
1. I am using a custom program to read the file and then updating internal table
2. Unicode code system
Please help to resolve this issue.
Thanks and Regards,
Raveendra
01-06-2009 3:28 AM
Hi Raveendra,
Similar problem is faced by me in my current project. The solutions I have suggested are as below. I have not received any confirmation as to which solution to be applied.
To avoid the dump:
1. Read the file as a NON UNICODE file.
-- For this we use open dataset statement as OPEN DATASET <name> IN TEXT MODE FOR INPUT ENCODING NON-UNICODE. The file is read as a non-Unicode file. This avoids the dump but it uploads also the non Unicode data in the system. We need to analyse if this will cause any other effect on the system.
2. Upload file after removing the special characters
-- We need to upload the file again in the application server after removing the special characters in it.
3. Bypass the dump by displaying error message
-- By using OPEN DATASET........IGNORING CONVERSION ERROR, we can suppress the dump. Here the file is not read but only the dump is suppressed.
regards,
Gaurav
02-07-2009 11:26 AM
HI,
Try
OPEN DATASET p_file in LEGACY TEXT MODE for INPUT.
or
OPEN DATASET p_file in TEXT MODE for INPUT ENCODING NON-UNICODE.