Skip to Content

SUP2.2 MBO migration to SMP3.0 OData

Hi all,

I've already followed a lot of SMP3.0 OData development tutorials and all of those tutorials were base on webservices that were easily consumable to match the Query and CRUD OData operations.

At this moment I'm working in a SUP MBO migration to SMP OData model but unfortunately the webservice does not have any matching between the OData entity and the webservice properties from request mapping or response mapping.

Instead the webservice expects a query like "select * from xxxx" but in OData model definition I can't find any way to do it.

Please find some screenshots that might be helpful to illustrate this case (ignore the funny colours from the RDP session wrong configuration):

I suspect that the solution might be through custom code following the logic from the tutorial How to use Composite WSDL in Integration Gateway

@Jitendra Kansal can you help me with this?



1.png (13.1 kB)
2.png (25.5 kB)
Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Oct 12, 2015 at 10:49 AM

    Hi Vicente,

    Request mapping for SOAP is not supported through design tool. Hence you need to write some custom script if you want to get data based on input.

    If you want complete data which is not based on input you need to do only response mapping as mentioned here - How to connect SOAP WebServices with Integration Gateway in SMP3

    (I think the wsdl used in this example throws some issues,hence use another wsdl to test it).

    If you want to know how to pass the input and filter the data you could find an example here - Third Party Security Schemes with SOAP in Integration Gateway (input is passed in the header of request and used custom script in integration gateway to map it).

    You could also have a look at this example - How to Handle Filters in Soap Operations

    Another option, if you are using BAPIs you could use SAP Gateway (free component) to create Odata service hence you could consume it directly in your mobile app without integration gateway.

    Regards, Midhun

    SAP Technology RIG

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Vicente,

      To be clear SOAP has multiple levels of complexities. Hence there is a difficulty in mapping soap with Odata. There are cases which are not supported if we try to map it with Odata.

      1. If your response has values within the attribute definition it will not be supported. Ex.
      2. If the response has repeating complex structure it will not be supported. Ex. (address1 is repeating) . In this case note that if there is a common key exits between the header and child entities it will be supported via relationships (you will be using $expand query) i.e there should be a common key in supplierData and address1.

      Your case is similar to case 1. But the only difference is you have similar structure in a request.

      I haven't tried this case in a request. The way you could try this is as mentioned in my previous replies. If it didn't work means this will not be supported.

      If you have further questions please raise an OSS message the IGW product team would help you.

      Regards, Midhun

      SAP Technology RIG

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.