Skip to Content
avatar image
Former Member

Idoc generated with Byte Order Mark

Hello All,

Recently we did an upgrade from Release 731 to 740 (EHP 6 to EHP 7). Prior to the upgrade all outbound Idocs generated to Seeburger did not have the Byte Order Mark ( FF FE) when viewed in Hex in the payload.

After the upgrade it is for some reason adding the BOM at the beginning and Seeburger is failing to read the Idoc. In the partner profile we have set the Segment Release level to 731 and in the Port definition for Seeburger checked the flag to have the control record have a release level determined from the partner profile.

The RFC is via the sapconnector.

Has anyone seen this issue and suggest what the issue might be ?

Thanks in Advance

Shounak

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 24, 2015 at 02:02 PM
    Add comment
    10|10000 characters needed characters exceeded