Hello

we call an abap proxy on a crm backend (same problem might occur on erp) with 731 release from a newly upgraded pi java only system, release 7.40

and we are getting HTTP/500 response after the upgrade in the adapter framework with a deserialization error (soap adapter, xi protocol)


As a result of a program error, one of the fields defined in ABAP is too short, thus preventing you from storing a value longer than 200 characters in this field.


Class CL_XMS_MSGHDR30_DYNAMIC

the following note fixed the problem:

http://search.sap.com/notes?id=2028742
XI runtime: Enhancing the dynamic header for SuccessFactors

don’t be missguided by the successFactor statement in the header, after we implemented the note our scenario worked withouth problems!


related note:

http://search.sap.com/notes?id=2143862

XI Runtime: SOAP:Header:DynamicConfiguration:Record has incorrect value

“SOAP:Header:DynamicConfiguration:Record has incorrect value”

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply