How To Fix SPRX063 - Proxy generation terminated: "mixed content" not supported

SAP Error Message - Details

• Message type: E = Error

• Message class: SPRX - Proxy Generation

• Message number: 063

• Message text: Proxy generation terminated: "mixed content" not supported

INCLUDE SPRX_GET_WSDL OBJECT DOKU ID TX

What causes this issue?

You used so-called "mixed content" in the interface description.
This means that the attribute mixed="true" was set for <complexType> or
<complexContent>.
A definition of this type ensures that a mixture of text and tags can
occur in the XML instance.
Example:
<Text>
Dear Mr/Mrs/Ms. <Name>Smith</Name>.
In your letter dated <Date>22.7.2001</Date> ...
</Text>
A feature of this type cannot be mapped by the proxy generation.

System Response

The system produces an error message. A proxy cannot be generated.

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 SPRX063 - Proxy generation terminated: "mixed content" not supported ?

  The SAP error message SPRX063, which states "Proxy generation terminated: 'mixed content' not supported," typically occurs during the generation of a proxy object in SAP when there is a conflict between the content types being used. This usually happens in the context of web services, particularly when the service definition includes both SOAP and RESTful elements or when there are inconsistencies in the data types or structures defined in the WSDL (Web Services Description Language) file.
  Cause:
  
  Mixed Content Types: The error indicates that the proxy generation process has encountered mixed content types, which means that the service definition is trying to use both XML and non-XML data types in a way that is not supported.
  WSDL Issues: There may be issues in the WSDL file, such as incorrect definitions, unsupported data types, or inconsistencies in the schema.
  Service Definition: The service might be defined in a way that does not conform to the expected standards for a single content type.
  
  Solution:
  
  Review WSDL: Check the WSDL file for any inconsistencies or errors. Ensure that all data types are correctly defined and that there are no mixed content types.
  Correct Data Types: Ensure that the data types used in the service are consistent and supported by SAP. Avoid using mixed content types in the service definition.
  Regenerate Proxy: After making the necessary corrections to the WSDL or service definition, try regenerating the proxy in SAP.
  Use Correct Binding: Ensure that the correct binding (SOAP or REST) is being used consistently throughout the service definition.
  Check SAP Notes: Look for any relevant SAP Notes or documentation that may provide additional guidance or updates related to this error.
  
  Related Information:
  
  SAP Documentation: Refer to the official SAP documentation for guidelines on creating and managing web services and proxies.
  SAP Community: Engage with the SAP Community forums to see if others have encountered similar issues and what solutions they have found.
  Debugging Tools: Use SAP's debugging tools to trace the proxy generation process and identify the exact point of failure.
  
  By addressing the issues related to mixed content types and ensuring that the service definition is consistent and compliant with SAP standards, you should be able to resolve the SPRX063 error.