Proxy problem. INTERFACE_SIGNATURE_ERROR ??

[Former Member]

 
 
  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--   --> 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
  <SAP:Category>XIProxy</SAP:Category> 
  <SAP:Code area="ABAP">INTERFACE_SIGNATURE_ERROR</SAP:Code> 
  <SAP:P1>ZSOW_II_SIIA_MAANDVOLUME_MAX</SAP:P1> 
  <SAP:P2>MT_MaandvolumeMax</SAP:P2> 
  <SAP:P3>urn:xxxxxxxxxx:i_edm_g:meten:verwerkenmeetdata:maandvolumemax</SAP:P3> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>Information über die Methodenparameter fehlt für Schnittstelle ZSOW_II_SIIA_MAANDVOLUME_MAX (ABAP Schnittstelle, Request-Message MT_MaandvolumeMax, Request-Message-Namensraum urn:alliander.com:i_edm_g:meten:verwerkenmeetdata:maandvolumemax)</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>
 Call Inbound Proxy 

Hi,

via SXMB_MONI I am getting this error, translated via google to EN:  Information on methods for interface parameter is missing

Proxy is generated, Interface exist, class exist. What am I missing?

tnx!

[Former Member · Accepted solution]

Hi Adibo,

Please check inside the method in SPROXY.

There might be some problem with the method "EXECUTE_SYNCHRONOUS / EXECUTE_ASYNCHRONOUS" which one in your case i dont't know since you have not mentoined the flow is Sync or Async.

Please consult your ABAP team.

Also, please check the following link for your configuration details:

http://scn.sap.com/thread/1988692

[Former Member · Accepted solution]

Tnx mate! Your answer helped me to search further. So I compared via SPROXY outboud on system X and inbound on system Y.

I found on system X (outbound) tab Internal View section EST Attributes was not released! So PI guys wil release it now and we wil see if that solves the problem.

[marksmyth]

Hello

The error you get: INTERFACE_SIGNATURE_ERROR means that the proxy object has got inconsistent against his definition in the ESR. You can check this in trx SPROXY -> open the corresponding object,
and choose 'check proxy' from the context menu (or Ctrl + F2).

The reported warnings mean that the definition has changed in the ESR, thus regeration of the proxies is needed (directly in the system, via transport).

Regards

Mark

[Former Member]

Hi Adibo,

Open Sproxy tx. then check for the inbound proxy under the namespace.

Double click on the Provider class-->Opens the Methds tab. IN that click on the parameters button. You should be able to view the Associated type( class).

Also check whether the proxy is properly activated.

[Former Member]

Hi,

Whe I click on Provider class it opens a interface methode: ZSOW_II_SIIA_MAANDVOLUME_MAX~SIIA_MAANDVOLUME_MAX

Then when I click on parameter button I see importing parameter INPUT and under Associated type ZSOW_MT_MAANDVOLUME_MAX (Structure). All activated!

[Former Member]

Hi Adibo,

Try to test your proxy from SPROXY transaction by providing the test data and check. Whether it is able to process the message and debug the proxy.

You would be able to find the issue.