cancel
Showing results for 
Search instead for 
Did you mean: 

JMS Receiver Channel sending Special characters from SAP PI!!

Former Member
0 Kudos

Hello Experts,

     Greetings for the day!!!!

I have scenario from ECC to Legacy system with PI as a middle ware. The data structure would be IDoc--> PI-->JMS(Queue). Unfortunately, during testing special characters are added with flat data. I have added the setting in the communication channel with 819 as CCSID and ISO-8859-1 parameter in the additional parameters section but ended in the same situation.Here are the below screen shots of the same.

CCSID setting:

ISO-8859-1Setting:


Output received in the Legacy system after flat data with special characters:




Would request you to kindly help on the same so that i can proceed further with same.

Thanks in advance!!!


Many Thanks,

Best Regards,

Prashanth Bharadwaj Ch.


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Vila/Hi Harish/Hello All,

I have tried all the above settings as per your earlier blog but ended in error situation of Unsupported encoding Exception.Here are the below screenshots for your reference.

Trial 1 without adding call sap adapter:

Error in PI with Unsupported encoding exception:

Trial 2 adding call sap adapter:

Error in PI with Unsupported encoding exception:


Trial 3 with parameter JMS.XIMessage.charset:

PI result after the above trial 3:

Harish
Active Contributor
0 Kudos

Hi Prashanth,

your module configuration has the following issues

1. you need to define two module key for Message transform bean

     a. One for Code page

     b. One for XML2Plain conversion

The codepage module should be before the code page conversion bean.

NumberModule NameTypeModule Key
1AF_Modules/MessageTransformBeanLocal Enterprise BeanCodepage
2AF_Modules/TextCodepageConversionBeanLocal Enterprise BeanConvert
3AF_Modules/MessageTransformBeanLocal Enterprise BeanXML2Plain

regards,

Harish

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi Harish/ Hi All,

Thank you so much for your help. Finally my above setting in earlier post worked.  Here is the below output.

Thanks again for the help.

Many Thanks,

Best Regards,

Prashanth Bharadwaj Ch.

Former Member
0 Kudos

Hi Harish/ Hello All,

I have tried the below setting in the communication channel. Please confirm the same in case of any other changes. Will update the result soon.

Thanks in advance!!

Many Thanks,

Best Regards,

Prashanth Bharadwaj Ch.

Former Member
0 Kudos

Hi Vila/Hi Harish,

Thank you so much for your replies. I will try it and update as soon as possible.

Thanks alot again.

Many Thanks,

Best Regards,

Prashanth Bharadwaj Ch.

Harish
Active Contributor
0 Kudos

Hi Prashanth,

Did you try with message transform bean?

NumberModule NameTypeModule Key
1AF_Modules/MessageTransformBeanLocal Enterprise BeanCodepage
2AF_Modules/TextCodepageConversionBeanLocal Enterprise BeanConvert
3localejbs/CallSapAdapterLocal Enterprise Beanentry

Module KeyParameter NameParameter Value
CodepageTransform.ContentTypetext/plain;utf-8
ConvertConversion.charsetcharset=ISO-8859-1

Please try the above module in the channel.

regards,

Harish

iaki_vila
Active Contributor
0 Kudos

Hi Prashanth,

Have you tried with the parameter JMS.XIMessage.charset ?

Regards.