Skip to Content

I thought this might be worth documenting to maybe save someone’s time getting a resolution to web service Serialization / Deserialization issues.  Recently I was asked to consume a 3rd party WSDL. This meant I had to create a consumer proxy in SAP for the abap to use at runtime.  Everything went well with the proxy generation (at least no errors were reported).  However, once I tried to consume the proxy, an exception was thrown when executing the call to the web service method. 

The exception is seen below:

“SOAP:1,027 SRT: Serialization / Deserialization Failed”

/wp-content/uploads/2013/10/p_299963.jpg

After digging a little deeper (SRT_UTIL) and checking the logs in the “Web Service Utilities: Error Log”, I found the following information:

/wp-content/uploads/2013/10/p_299963.jpg

This led me to take a look at the WSDL and found that the date format of these fields looks as follows:

<SubmissionTime>2001-12-31T12:00:00</SubmissionTime>

<CompletionTime>2001-12-31T12:00:00</CompletionTime>

Obviously SAP was having an issue with the date format.  I then went to the Proxy Service and took at look at the external view:

/wp-content/uploads/2013/10/p_299963.jpg

Inspecting the “SubmissionTime” and “CompletionTime” Technical Type, I noticed that they has been set to the following:   XSDDATETIME_Z

/wp-content/uploads/2013/10/p_299963.jpg

From the dictionary, you can see the type corresponds to:

/wp-content/uploads/2013/10/p_299963.jpg

Since the data being returned from the web service does not conform to a decimal format, a change was needed.  We needed something that could handle this format:

<SubmissionTime>2001-12-31T12:00:00</SubmissionTime>

<CompletionTime>2001-12-31T12:00:00</CompletionTime>

There is another format which is more appropriate:  XSDDATETIME_ISO

/wp-content/uploads/2013/10/p_299963.jpg

So for each of the external view fields in the proxy defined as XSDDATETIME_Z, I switched them to:

/wp-content/uploads/2013/10/p_299963.jpg

After the change, everything worked like a charm..

Bottom line; don’t expect the proxy generator to get everything correct.  It’s pretty good, but it’s not perfect.

To report this post you need to login first.

6 Comments

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

  1. amina alavi

    Great Blog! Thanks for writing this. I am having the exact same issue. When you say go to the proxy service and look at the external view, what transaction is this. Are you doing this is PI? You response will be super helpful!

    (0) 
  2. Rubén Quero

    Hi. I have the next error: System expected a value for the type g

    How can i solve it? i tried the solution of this post, but nothing change.

    (0) 
  3. nagesh kumar sirigineedi

    thankyou so much Philip Johnston    for your solution..  really appreciate your effort to share the solution .

    however we have an issue which we are not sure how to go ahead,  we have consumed an opentext webservice , but the structure of the metadata does not have the values field due to which we are unable to get the data.. is there a way to add an extra field to the system created proxy structure

    (0) 
  4. Nic Teunckens

    Excellent BlogPost, even helped me now in 2017 …

    I feel this could have made it to a “How To …” SAP-KBA, would be way easier to get this type of useful information to a broader community instead of just ‘stumbling upon to it’.

    Thanks anyway

    Nic T.

    (0) 

Leave a Reply