Seeburger Mapping See_E2X_ORDERS_UN_D96A

[shweta_walaskar2]

Hello,

I was using See_E2X_ORDERS_UN_D96A mapping in our scenario but then we had a problem with special characters where the message used to fail at Seeburger level whenever it contained Special characters(Russian)

Then I created my own mapping E2X_ORDERS_UN_D96A where I set an option setDestinationEncoding= UTF-8.

Now,message is not failing at Seeburger,but I cant see any special characters.

I cannot see the original file sent by the partner ,but looking at the result available in XI message ,I believe ,Seeburger mapping is cutting down these special characters,they are not even reaching XI.

Has anybody observed this behavior?

Is there any way,I can get special characters in XI?

Thanks in advance.

Regards,

Shweta

[prateek]

Have you tried setting setSourceEncoding instead of setDestinationEncoding?

Regards,

Prateek

[shweta_walaskar2]

Hello Prateek,

Thanks.

Currently,we have no option of deploying new mappings in production.

But my problem is,I asked them to send such files via mail and when I test these files locally using BIC MD,I get no error and I can see special characters in the converted file.

So ,it doesnt make any difference if I set source encoding to UTF-8 in BIC converter and test it as anyway,it is working locally.

But if they send the same file via AS2,it fails.

I always get the same error message in BIC converter what I can see in CC log.

What could be different if I test it locally?

Thanks.

Regards,

Shweta

[Former Member]

Hi Shewta,

you need to add one more module in adapter.

module name is localejbs/Seeburger/CharsetConversion

Type- Local Enterprise Bean

Parameter name--targetEnc

paramter Value-ISO-8859-1

Note : make sure you add this module before bic.

Give me a shout if still problem persist.

Cheers,

/Hidayat.

[shweta_walaskar2]

Hello Hidayat,

Thanks for the reply.

I am sorry to say,even this didn't work for me.

Are you sure,it should be ISO-8859-1 ,charset for Russian is Cyrillic(Windows)?

Regards,

Shweta

[shweta_walaskar2]

Hello,

In the worst case, if we assume that Seeburger deletes these special characters ,the problem gets severe when we receive data as:

ABCXYZ hvcdjjfvhgfvfdvjfgvb НАУШН/ПРОВОД СЕРБР:ATLANTA SEEBURGER123

in such cases,it produces output as:

ABCXYZ hvcdjjfvhgfvfdvjfgvb НАATLANTA SEEBURGER123

i.e.It deletes : which separates two fields along with special characters like СЕРБР

Now,this field can have a specified maximum length,but as it is merging next field as well (ATLANTA SEEBURGER123)

length goes beyond maximum value and it fails at Seeburger even though they are sending data of correct length

We need to handle this somehow .

Kindly suggest.

Thanks.

Regards,

Shweta

[shweta_walaskar2]

Hello ,

I have set this option in BIC Converter and tried to test the file ,as always,it got converted to XML without any error and this time generated XML has proper Russian characters even though original file has corrupted characters.

Same mapping is deployed on XI.(without source encoding setting)

I cannot understand why same mapping works in BIC converter but not in XI.

can anyone please help?

Thanks a lot in advance

Regards,

Shweta

[Former Member]

Hello,

i hope this can help you with characters in XI

this blog explains How to handle the Special Characters in XI

https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/9420 [original link is broken] [original link is broken] [original link is broken]

this explains how to work with character encoding in sap PI 7.0

https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42&overrid...

also check this thread

Regards,

lpbuff

[shweta_walaskar2]

Hello,

Thanks for the information.

These links explain how can we handle special characters in XI.

But my problem is ,these special characters are not even reaching XI, as message fails at Seeburger level itself.

Thanks.

Regards,

Shweta

[Former Member]

Hi Shweta,

If you say that in seeburger tool work correctly but deployed not. Maybe some updates are not ok or maybe the deploy have to be done again. maybe some update of seeburger is not in your server.

because with the

setSourceEncodung() and setDestinationEncoding() it will works......

regards,

lpbuff

[Former Member]

one thing you can do is just add log messages in mappings and test the same in BIC mapping designer and deploy the same to XI box and check the logs there too

traceln("log message in BIC mapping");

if something is wrong then it will help to point out the error

HTH

Rajesh

[shweta_walaskar2]

Hello,

Thanks for the reply.

I used the same module configuration but with File adapter instead of AS2 adapter and it works fine .

This means that there is no problem in bic mapping.

These characters are cut by AS2 adapter itself and they are not even reaching XI.

Is this AS2 adapter behavior?How can we handle this?

Please let me know.

Thanks .

Regards,

Shweta

[Former Member]

Hi Shweta,

I had the same issue

Please let me know if you found the necessary settings for this issue.Thanks...