Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Idoc generated with Byte Order Mark

shounakm
Explorer
0 Kudos

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

1 REPLY 1

michael_kozlowski
Active Contributor
0 Kudos