Can we create inbound Proxy without Datatype and messagetype

[binnari_rampullaiah2]

Hi experts,  My scenario is SOAP to Proxy

Is it possible to create inbound proxy without datatype and message type. my case is i want use datatype and message type as XSD file which is given by Source system. I want to use same structure on receiver side also.

In Source structure some fields are untyped

I facing issue while creating datatype in sap pi for target system to create proxy.  i am not able to create datatype with type ""untyped"

so i want use same xsd for target ECC system to generate proxy

[nitindeshpande · Accepted solution]

Hello Binnari,

Why some of the fields are untyped? PI does not allow to save such XSDs which do not have the datatype assigned, this will lead to an error. This means your XSD is not proper. Edit the XSD and provide the datatype for the fields which are untyped.

Once you do it, import the XSD into the external definitions and use the same in Service interface.

There may be also the case, where the datatype will have external reference and if you do not import the XSD of external reference, it does not recognize the datatype. Hence for this you can try importing the XSDs using the option Import all external definitions by navigating through -

Tools -> Import All External Definitions with Reference

It is not mandatory to have DT and MT for creating a proxy. XSD would work.

Please let me know if you need more help on this. Let me know if you get stuck anywhere.

Regards,

Nitin Deshpande

[binnari_rampullaiah2 · Accepted solution]

Thank you for your quick reply Nitin Deshpande.

My case is totally different. From source webservice system i am getting data in gml format inside xml. so their structure xsd structure is having some fields type as "anytype". i used same structure in receiver service interface.

sample data is like from source system

<assets>

  <id>000000TEST</id>

     <inserts>

            <gml:FeatureCollection xmlns:gml="http://www.opengis.net/gml" xmlns:sw="http://www.gesmallworld.com/sw" xmlns:swgml="http://www.gesmallworld.com/swgml" xmlns:wfs="http://www.opengis.net/wfs" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.gesmallworld.com/sw http://npcl-vm:8080/gss/resource/xsd/electric.pole.xsd?token=-1385992386">

  <gml:boundedBy>

  <gml:Null>This feature collection contains no geometry in the geographic world</gml:Null>

  </gml:boundedBy>

  <gml:featureMembers>

  <sw:electric.pole gml:id="swrefVsbiboVoidZ-0021electric-0021ed_pole-0021644350VtypeZpole">

  <sw:remarks/>

  <sw:asset_id/>

  <sw:material/>

  <sw:number/>

  <sw:usage>Primary</sw:usage>

  <sw:height/>

</sw:electric.pole>

</gml:featureMembers>

               </gml:FeatureCollection>

         </inserts>

         <updates>

              <gml:FeatureCollection xmlns:gml="http://www.opengis.net/gml" xmlns:swgml="http://www.gesmallworld.com/swgml" xmlns:wfs="http://www.opengis.net/wfs" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.gesmallworld.com/sw http://npcl-vm:8080/gss/resource/xsd/xsd8540245809688346915.xsd?token=-1203766449">

                  <gml:boundedBy>

<gml:Null>This feature collection contains no geometry in the geographic world</gml:Null>

             </gml:boundedBy>

                        <gml:featureMembers/>

            </gml:FeatureCollection>

        </updates>

        <deletes>

            <gml:FeatureCollection xmlns:gml="http://www.opengis.net/gml" xmlns:swgml="http://www.gesmallworld.com/swgml" xmlns:wfs="http://www.opengis.net/wfs" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.gesmallworld.com/sw http://npcl-vm:8080/gss/resource/xsd/xsd6365995064037275686.xsd?token=1297061467"><gml:boundedBy><gml:Null>This feature collection contains no geometry in the geographic world</gml:Null>

                </gml:boundedBy>

                      <gml:featureMembers/>

            </gml:FeatureCollection>

        </deletes>

</assets>

If you observe in my first post the structure is

assets

       ID

       inserts

       deletes

       updates

so inserts xml field having gml data. can i pass whole data if i put that element as xsd:string in receiver system.

[nitindeshpande · Accepted solution]

Hello Binnari,

Yes, you can use the datatype as string in the XSD. And there is no maximum length restriction on the string data-type. Hence It can hold any length of data and there is no restriction on the data which it holds too.

Regards,

Nitin

[binnari_rampullaiah2 · Accepted solution]

Thank u Nithin

This thread is closed

[iaki_vila]

Hi Binnari,

The untyped elements can produce issues when you are trying to use it with the ABAP classes generated in the ECC. I always change them manually to xsd:string. If you don't set any additional restriction or XSD validation in PI, you won't have any additional issue.

Regards.

[Former Member]

Hi,

Yes, you can use an xsd or wsdl for proxy. External Type on the Service Interface.

Regards,

Jannus Botha

[pvishnuvardan_reddy]

Hi Binnari,

If you have xsd file, then create a external definition in PI system, and there you can import that xsd file, which forms the message structure. Now, create a Service interface pointing to this external definition.

In ECC, generate proxy for this service interface and the remaining steps are as usual.

Regards

Vishnu