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.
the following note fixed the problem:
don’t be missguided by the successFactor statement in the header, after we implemented the note our scenario worked withouth problems!
XI Runtime: SOAP:Header:DynamicConfiguration:Record has incorrect value
“SOAP:Header:DynamicConfiguration:Record has incorrect value”