Special characters conditions in receiver determination

[Former Member]

hi there,

i have the following problem:

There are conditions in receiver determination to find the proper xsl mapping for different segments in IDocs.

That works fine.

But if there are special characters like &, the interface mappings can't be found, because for the conditions the xml is already corrupt.

So, i've tried to replace all occurrences of & with & in a java mapping that is called before the xsl mappings.

It doesn't work, because in that case conditions are processed before the java and xsl mappings.

Do you have any idea how to replace special characters before conditions in receiver determination are processed?

thx in advance

Stefan

[Shabarish_Nair · Accepted solution]

1. Use the same code in an adapter module so that message itself is converted before it comes into the integration engine.

2. The design should be,

a. get the message

b. use the mapping

c. use a simple BPM, receive and send step (the message is the same)

d. BPM -> target (here you will get the converted XML in the RD)

[Former Member · Accepted solution]

Hi,

thx for the fast reply, but problem persists.

java coding for special characters is not possible in module, because in idoc adapter a module can't be implemented. So before any mapping takes place, conditions in receiver determnation will be evaluated, with a corrupt xml.

Need possibility to map special characters before evaluation of conditions.

Any other ideas?

Thx Stefan

[Shabarish_Nair · Accepted solution]

try the BPM way. Have the mapping done before the message enters the BPM.

its going to be something similar to -

[bhavesh_kantilal]

Hey Stefan,

Can you explain this problem further? Not sure I followed it. Can you provide a example?

Regards

Bhavesh

[Former Member]

hi,

write a module to replace all those special charactars to some '_', which XI accepts. so u r problem can be soved...

Thanks,

Madhav

Points If useful

[former_member183906]

Handling the Special Characters in XI

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

Find out which character encoding the receiver system expects and put the same to the receiver channel.

By default the file adapter would create a file with UTF-8, which might not be useable for the receiver.

check this thread.

check the document :

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79...

Depends upon encoding methods handling will differ,

you can use ISO-8859-1 or ISO-8859-2 instead of UTF-8 for some special characters.

check this blog:

*Suppress Special Character *