B2B Integration

SI 5.2.6 - Help with Extended Hex Characters

  • 1.  SI 5.2.6 - Help with Extended Hex Characters

    Posted 4 days ago

    We are having an issue with SI translating extended hex characters and are currently using keyword replace to handle.  However, I'd like to find a more permanent solution.

    Data coming from our ERP system sometimes has extended hex characters that Sterling does not translate properly.  I've tried adding the extended hex characters to the map which works fine until the process hits the Enveloping service.  Here is an example:

    Data before Envelope Service: León (This is how it looks in source ERP system)

    Data during Envelope Service: Le�n (This is how it looks once it hits the Envelope service)

    Data translated as: Le�n (This is how it translated to EDI)

    For this particular customer, we need to send the EDI data using US English only - 'León' should translate as 'Leon'.

    Does anyone have any suggestions?

    Thank you,


    Karen Gallello