Thanks.
But the question is more about the fact that we may name a type as we want, SAP does not check (VAGResult in the screen capture below, which becomes <complexType name="VAGResult"... in the WSDL). It may be the same name as a type in another Web Service, both types may have completely different structures. It's a problem from a "philosophical" perspective, as these types share the same namespace "urn:sap-com:document:sap:rfc:functions"; the client software doesn't accept that, we have to rename it; I'd like to know whether SAP proposes a way to prevent choosing a name if it's already chosen for another type of different content.