Skip to Content
Former Member
Apr 18, 2011 at 10:01 PM

CRLF issue



We are gearing up for our integration testing with our 30 odd EDI partners. But we have a small subset who are using Carriage Return Line feed hexa decimal values ( 0D 0A) as delimiters in our inbound documents which might potentially cause our BIC mappings to fails. Since it is a single map for all our partners, I would like to handle it at PI level. I have read the SEEBURGER manuals and came across the following settings in our sender comm. Channels. Would this be a right approach, whereby we keep our BIC mappings intact and accommodate the partner delimiter differences at a communication channel level?

binaryMode true

replaceString "270D0A"

searchString "270A"

Module Name : localejbs/Seeburger/ReplaceString

Module Key : rst

Modulekey Parametername ParameterValue

rst sourceDest MainDocument

rst targetDest MainDocument

rst searchString "Search string"

rst replaceString "replace string"

rst regularExpression true