.net connector 2.0 and visual studio 2003 : user alias class

[Former Member]

Hello,

I tried to implement Bapi_User_Get_Detail (Devclass SUSR) in a windows based visual studio 2003 Project.

1. choosed a new windows forms project

2. added a proxy class

3. populated it with Bapi_User_Get_Detail

4. compiled the project

now visual studio returns three errors due to the fact that:

1. in the structure BAPILOGOND resides a Field named "Class".

2. Somewhere is field named "Alias".

I could remove the first error by renaming the member "Class" of the BAPILOGOND Structure to "XClass".

For the other two errors i had no idea, what to do.

Here a look at the SAPProxy1.wsdl Code, where i suppose the cause:

<xsd:element name="ALIAS" minOccurs="0" type="s0:BAPIALIAS" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<xsd:annotation>

<xsd:documentation>User Name Alias</xsd:documentation>

The BAPIALIAS Structure has only one field named "Useralias". A change of the field's name did not eliminate the compile errors.

Has someone a good idea ...?

best regards

[reiner_hille-doering · Accepted solution]

The Function Bapi_User_Get_Detail has a parameter called "Alias". Unfortunately VB has lots of keywords that can conflict with names. Fortunately you can customize any name generated by .NET connector. Don't change the generated code but change the name in .sapwsdl designer. In case of the "Alias" problem, select "Bapi_User_Get_Detail" icon, right-click and select "Edit Parameter" and change the Name property of "Alias".

[Former Member · Accepted solution]

Thank you very much for your quick and helpful answer!

Fortunately and long-sighted the properties of names in the proxy-designer are changeable

best regards