Skip to Content
author's profile photo Former Member
Former Member

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


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: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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Feb 02, 2005 at 03:49 PM

    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".

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.