Cannot generate proxy

[Former Member]

Hi,

We have integrate our E-recruiting system with external JOB site http://hh.ru/services/.

For integration we use SAP PI with SAOP (Axis) driver.

We were able to send a query and get the answer for http://hh.ru/services/AuthenticationService services from ABAP.

But for service http://hh.ru/services/NegotiationService we get an error when generate proxy in trx SPROXY.

Anybody know how to resolve this issue or analysis method this issue?

Cannot generate proxy (object <portType name="SI_Out_NegotiationService"> missing in WSDL, see long text)

Message no. SPRX084

Background

During proxy generation, an interface description in WSDL format is fetched from the Enterprise Services Builder or from another source and interpreted. This WSDL document must describe the whole interface correctly.
==> Display Query
==> Display WSDL Document

Diagnosis

In the WSDL document, the object
   ""
from the namespace
  ""
links to the object
   "<portType name="SI_Out_NegotiationService">"
from the namespace
   "http://hrxml.headhunter.ru/2008-03-18"

However, this last object does not exist in the WSDL document.

System Response

ABAP proxy generation expects that all directly and indirectly referenced objects are in the WSDL document. Therefore, no proxy can be generated for this WSDL and the system displays an error message.

Procedure

This situation can have different causes:

• Object "<portType name="SI_Out_NegotiationService">" not been defined
• Object "<portType name="SI_Out_NegotiationService">" saved in the wrong namespace
• In the reference to object "<portType name="SI_Out_NegotiationService">", the wrong name was specified
• In the reference to object "<portType name="SI_Out_NegotiationService">", the wrong namespace "http://hrxml.headhunter.ru/2008-03-18" was specified
• Internal error in the service that constructs the WSDL document
• Internal error in ABAP proxy generation

[Former Member · Accepted solution]

Hello Mikhail,

have you had a look inside the WSDL? Have you followed the suggested procedure? What were your findings? It is hard to say why this fails without knowing the WSDL. Unless someone experienced the exact same problem before.

Regards,

Jörg

[Former Member · Accepted solution]

Hello Jörg,

We have had a number of tests and determined that the cause of the error has been in use union operation.

For example:

<xsd:simpleType name="PublicationOtherTypes" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

        <xsd:union memberTypes="xStringPatternExtensionType PublicationOtherTypeTypes" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />

    </xsd:simpleType>

Also we find this link and now check all WSDL.

[Sriram2009 · Accepted solution]

Hi Mikhail

Kindly refer the SAP Note 1046046 - Proxy generation problem with external definitions

Regards

Ram

[Former Member · Accepted solution]

Hi Ram,

Thanks for response, but our system has updated to a latest SP.

[Former Member · Accepted solution]

Hi Mikhail,

yes, this is a very likely reason. XSD support is quite poor in PI. You can try to import the WSDL in PI and define an internal representation of the service for your backend system. Maybe PI is more tolerant than the stylesheet generator.

Regards,

Jörg

[Former Member · Accepted solution]

Hi Jörg,

We changed WSDL (excluded union operator) and import it to PI. Now we are generate proxy without any problem.