How To Fix SPRX044 - Proxy generation terminated: WSDL error (method "&1" without in/output)

SAP Error Message - Details

• Message type: E = Error

• Message class: SPRX - Proxy Generation

• Message number: 044

• Message text: Proxy generation terminated: WSDL error (method "&1" without in/output)

INCLUDE SPRX_GET_WSDL OBJECT DOKU ID TX

What causes this issue?

In the WSDL document,
either <input> or <output> or both
must be in <zh><operation name="&V1&"></>
(method must communicate with external systems).
In this instance, neither <input> nor <output> have been used.

System Response

Proxy generation is terminated.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SPRX044 - Proxy generation terminated: WSDL error (method "&1" without in/output) ?

  The SAP error message SPRX044 indicates that there is an issue with the Web Service Definition Language (WSDL) file generated for a proxy service. Specifically, the error states that a method is defined in the WSDL without any input or output parameters, which is not valid.
  Cause:
  
  Missing Parameters: The method in the WSDL does not have any defined input or output parameters. This can happen if the method is incorrectly defined in the underlying ABAP class or function module.
  Incorrect Method Signature: The method signature in the ABAP code may not match the expected format for a web service, leading to the generation of a WSDL that lacks the necessary parameters.
  Proxy Generation Issues: There may be issues during the proxy generation process that prevent the correct WSDL from being created.
  Changes in the ABAP Code: If the ABAP code was modified after the last successful proxy generation, it may lead to inconsistencies in the WSDL.
  
  Solution:
  
  
  Check Method Definition: Review the ABAP method that corresponds to the WSDL method. Ensure that it has the correct input and output parameters defined.
  
  If the method is supposed to have parameters, make sure they are correctly declared in the ABAP code.
  If the method is not supposed to have parameters, consider whether it should be a web service at all.
  
  
  
  Regenerate the Proxy: After correcting the method definition, regenerate the proxy.
  
  Use transaction SPROXY to regenerate the proxy and ensure that the WSDL is correctly generated.
  
  
  
  Check for Syntax Errors: Ensure that there are no syntax errors in the ABAP code that could prevent the proxy from being generated correctly.
  
  
  Review WSDL: If you have access to the WSDL, manually inspect it to see if the method is indeed defined without parameters. This can help confirm the issue.
  
  
  Test the Web Service: After making changes and regenerating the proxy, test the web service to ensure that it functions as expected.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SPROXY: Used for managing and generating proxies.
  SE80: Object Navigator, where you can check the ABAP class or function module.
  
  
  
  Documentation: Refer to SAP documentation on web services and proxy generation for more detailed guidelines on defining methods and parameters.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address known issues with proxy generation or WSDL errors.
  
  
  By following these steps, you should be able to resolve the SPRX044 error and successfully generate the proxy with the correct WSDL.