Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Dump RFC_CONVERSION_FIELD

Former Member
0 Likes
2,545

Hi Experts,

We have upgraded from R/3 4.7 to ECC 6.0.

The BW system ( Non-unicode ) while extracting data from ECC 6.0 (Unicode) system gives an error :-

Error occurred in the source system. Conversion error between two character sets.

At the same time, a dump is generated in ECC 6.0 system (Unicode ) :- RFC_CONVERSION_FIELD.

Conversion error "ab_rfcImplode" from character set 4102 to character set 1100.

The problems seems to be because of a Non-Unicode system trying to access data from a Unicode system. We only have English language.

Any pointers towards resoluton of the above issue would be highly appreciated.

Thanks,

Best regards,

Prashant

7 REPLIES 7
Read only

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Likes
1,154

Hi Prashant,

please have a look at SAP note 814707, maybe this one solves your problem ?

Best regards,

Nils Buerckel

SAP AG

Read only

Former Member
0 Likes
1,154

Hi Nils,

As per the note we have identified the record because of which we get the error.

Material no. VAITMX0 is converted as VAITM X#.

Seems that anything after X is treated as a binary code the way it was used in R/3 4.7, 4.6c etc..

Solution mentioned in the note is to update code page but since we are using only English language not sure whether we need to update code page etc.

Thanks,

Best regards,

Prashant

Read only

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Likes
1,154

Hi Prashant,

as far as I see it, a proper view is only possible with detailed analysis of the data (source and target).

But I think this is already ongoing via SAP development support.

Best regards,

Nils Buerckel

SAP AG

Read only

Former Member
0 Likes
1,154

Hi,

Yes thats right, OSS message has been raised. Will update the solution as soon as we find it.

Thanks,

Best regards,

Prashant

Read only

0 Likes
1,154

Hi Prashant,

Do you remember what was the solution?

Thanks

Eddy.

Read only

0 Likes
1,154

Hi Eddy,

Yes. The problem was due to special character => Hyphen(-). For few material nos. we had hyphen in between. Those hyphen were created using Microsoft Word i.e. User had prepared the list of material nos. in MS Word & then pasted those in SAP. The hyphen on our keypad is different as compared to the one which is in MS Word & hence the issue as SAP wasnt able to recognize it.

We replaced those hyphen with keypad hyphen & issue was resolved.

Thanks,

Best regards,

Prashant

Read only

nils_buerckel
Product and Topic Expert
Product and Topic Expert
0 Likes
1,154

Hi all,

yes, this is a general problem when transfering data from Unicode-Systems to Non-Unicode systems (could be also vice-versa, if unsupported characters are inserted).

One of these problematic characters is the hyphen (I think it is rather a dash, but hard to distinguish).

Another example would be the symbols €,â„¢ or MS word exclamation marks  ...

This is one of the reasons why SAP recommends to minimize mixed connections between non-Unicode and Unicode. In the long run, all systems in the landscape should be based on Unicode.

Best regards,

Nils Buerckel