Hello Bruce,
apparently the template, that generates the WSDL, cuts off the Fieldnames at the Underscore, turning lfdNr_A to A, as seen below.
<Rueckgabe_list>
<Paarung>
<SYSID>value</SYSID>
<lfdNr_A>value</lfdNr_A>
<PZN_A>value</PZN_A>
<Produktname_A>value</Produktname_A>
<lfdNr_B>value</lfdNr_B>
<PZN_B>value</PZN_B>
<Produktname_B>value</Produktname_B>
<Inkompatibilitaetsstatus>value</Inkompatibilitaetsstatus>
<HTMLKommentar>value</HTMLKommentar>
</Paarung>
<xs:complexType name="Rueckgabe">
<xs:sequence>
<xs:element minOccurs="0" name="SYSID" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="A" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="A" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="A" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="B" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="B" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="B" nillable="false" type="xs:string"/>
<xs:element minOccurs="0" name="Inkompatibilitaetsstatus" nillable="false" type="xs:int"/>
<xs:element minOccurs="0" name="HTMLKommentar" nillable="false" type="xs:string"/>
</xs:sequence>
As far as I understood, the NT--templates treat the colonm, being the separator between prefix and label, by converting to an underscore. This WSDL-generator seems to believe, that everything left of the underscore is the prefix and <TSCHACK> chops if off with its eversharp hatchet. maybe I am wrong, this is just how I think its working at the moment.
I will now circumvent this by renaming these fields. It would be nice, if this could be addressed somehow, either by leaving the labelname as it is, cuts off only the prefix, or by mentioning this in the manual, like "Never use an underscore in the fieldnames!".
Thanks
Wolfgang