Skip to Content

Using a RFC in BPM as data object

Dear all,

I will use a RFC structure as data object. I imported the the RFC PROCESS_MESS_UPLAOD from SAP system. But it could not be used directly, becaused the WSDL is not well-formed.

<xsd:element name="PROCESS_MESS_UPLOAD" >
  <xsd:complexType>
      <xsd:all>....

I tried to export the WSDL, adding a type to the element and a name to complex type, but it throws an error after reimporting.

<xsd:element name="PROCESS_MESS_UPLOAD" type="PROCESS_MESS_UPLOAD">
    <xsd:complexType name="PROCESS_MESS_UPLOAD">
       <xsd:all>
.....

Error:
for element:
element "<element name>" has both a 'type' attribute and 'anonymous type' child

for complexType:
Name is not allowed in complex type.

I tried to removed the name from complexType without success.
Any hints how to use a RFC here or how to adjust?

regards

Chris

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Dec 12, 2017 at 10:24 AM

    Hi,

    even if this "forum" seems to be dead (am I the only one who is missing the old forum?), I will share my solution.

    It is not enough to use type in Element-Tag and name in ComplexType. We have to separate them.

    From

                <xsd:element name="PROCESS_MESS_UPLOAD" type="PROCESS_MESS_UPLOAD">
                    <xsd:complexType name="PROCESS_MESS_UPLOAD">
                            .....
                    </xsd:complexType>
                </xsd:element>

    To

        <xsd:element name="PROCESS_MESS_UPLOAD" type="PROCESS_MESS_UPLOAD" />
        <xsd:complexType name="PROCESS_MESS_UPLOAD">
            .....
        </xsd:complexType>
    
    

    ComplexType is not a child of element tag anymore, but get refers via type and name attributes.
    After this I was able to import it into NWDS and my message types get listed in datatypes.

    Regards

    Chris

    Add comment
    10|10000 characters needed characters exceeded