How To Fix SPRX269 - Proxy generation terminated: xsd:anyType as base type is not supported

SAP Error Message - Details

• Message type: E = Error

• Message class: SPRX - Proxy Generation

• Message number: 269

• Message text: Proxy generation terminated: xsd:anyType as base type is not supported

What causes this issue?

Xsd:anyType is used as base type of an extension or restriction .
Extensions and restrictions of xsd:anyType cannot be handled by proxy
generation.

System Response

Proxy generation terminated.

How to fix this error?

Use of xsd:anyType as base type must be avoided. Please use xsd:anyType
directly instead of using a type with base type xsd:anyType.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SPRX269 - Proxy generation terminated: xsd:anyType as base type is not supported ?

  The SAP error message SPRX269 indicates that there is an issue with the proxy generation process, specifically related to the use of xsd:anyType as a base type. This error typically occurs when the system encounters a data type in the WSDL (Web Services Description Language) that it cannot handle, which in this case is xsd:anyType. 
  Cause:
  
  Unsupported Data Type: The xsd:anyType is a generic type that can represent any XML data type. However, it is too broad and does not provide enough specificity for the proxy generation process in SAP.
  WSDL Definition Issues: The WSDL file may have been incorrectly defined, leading to the inclusion of xsd:anyType where a more specific type should be used.
  Incompatibility with SAP Proxy: SAP's proxy generation tools require specific data types to create the necessary structures and classes. The presence of xsd:anyType can lead to ambiguity and confusion during this process.
  
  Solution:
  
  Modify the WSDL: Review the WSDL file and replace instances of xsd:anyType with more specific data types. For example, if the data is expected to be a string, use xsd:string instead. If it is a complex type, define a specific complex type.
  Regenerate the Proxy: After modifying the WSDL, regenerate the proxy in SAP to see if the error persists.
  Check for Other Errors: Ensure that there are no other issues in the WSDL that could lead to similar problems. Validate the WSDL using tools like XML validators or WSDL validators.
  Consult Documentation: Refer to SAP documentation or community forums for any specific guidelines related to proxy generation and WSDL definitions.
  
  Related Information:
  
  SAP PI/PO: If you are using SAP Process Integration (PI) or Process Orchestration (PO), ensure that the integration scenarios are correctly defined and that the WSDL is compatible with the expected data types.
  WSDL Validation Tools: Use tools like SoapUI or WSDL validators to check the correctness of your WSDL file.
  SAP Notes: Check SAP Notes for any known issues or patches related to proxy generation and WSDL handling.
  
  By addressing the root cause of the xsd:anyType usage in the WSDL, you should be able to resolve the SPRX269 error and successfully generate the proxy.