on 06-09-2008 1:44 PM
Hi Friends,
Ours is ECC 5.0 and DB is Oracle. we are getting 200 dumps for the RFC conversion field, i went thorrugh the OSS notes, but still not successfull.
HEre is the content of the error message:-
Short textConversion error between two character sets.
What happened?
Conversion error "ab_rfccon" from character set 4102 to character set 1100
A conversion error occurred during the execution of a Remote Function
Call. This happened either when the data was received or when it was
sent. The latter case can only occur if the data is sent from a Unicode
system to a non-Unicode system.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
What can you do?
Note which actions and input led to the error.
Thanks
please help friends
> Ours is ECC 5.0 and DB is Oracle. we are getting 200 dumps for the RFC conversion field, i went thorrugh the OSS notes, but still not successfull.
>
> HEre is the content of the error message:-
>
> Short textConversion error between two character sets.
>
> What happened?
> Conversion error "ab_rfccon" from character set 4102 to character set 1100
The problem is related to Unicode/non-Unicode conversion.
Check the affected RFC connection if all settings are correctly done.
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here are the details of the CALLED and the CLient system
User and Transaction |
Client.............. 100 |
User................ "ALEREMOTE" |
Language Key........ "E" |
Transaction......... " " |
Transactions ID..... "484C8D987CDB5EBDE10000000AFA0821" |
Program............. "SAPLNLSK_G" |
Screen.............. "SAPMSSY1 3004" |
Screen Line......... 2 |
Information on caller of Remote Function Call (RFC): |
System.............. "MCQ" |
Database Release.... 700 |
Kernel Release...... 700 |
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.) |
Call Type........... "synchron and transactional (emode 0, imode 0)" |
Inbound TID.........." " |
Inbound Queue Name..." " |
Outbound TID........."0AFA08216A23484D41D74879" |
Outbound Queue Name.." " |
Client.............. 100 |
User................ "ALEREMOTE" |
Transaction......... " " |
Call Program........."SAPLERFC" |
Function Module..... "ARFC_DEST_SHIP" |
Call Destination.... "NONE" |
Source Server....... "wiqa2_MCQ_05" |
Source IP Address... "10.233.8.33" |
Additional information on RFC logon: |
Trusted Relationship " " |
Logon Return Code... 0 |
Trusted Return Code. 0 |
Note: For releases < 4.0, information on the RFC caller are often |
only partially available. |
-
-
Information on where terminated |
Termination occurred in the ABAP program "SAPLNLSK_G" - in |
"NLS_GET_LANGU_CP_TAB". |
The main program was "SAPMSSY1 ". |
In the source code you have the termination point in line 24 |
| of the (Include) program "LNLSK_GU01".
please help what to do now.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.