Proxy generated, but without method definition

[Former Member]

Hello,

Upon generation of a proxy of an RFC on 4.6c, the class definition does not contain the target method.

However the method is visible in the visual studio design front end, but not invokable programatically.

This problem is specific to a particular rfc.

The other RFC's generated contain the method definition.

Is there some setting issue on the SAP server side or on the client side?

I am using VS.net

Microsoft Visual C# .NET 69461-270-0000007-18490

SAP .NET Connector 2.0.

SAP 4.6c

Thank you,

Amit

[Former Member]

I could work around this problem and fix it by selecting True on CreateTRFC on the options tool box. After that, it generated the Source Codes.

[reiner_hille-doering]

This sounds like a "mark dirty" issue: If - for any reason - the designer is not maked dirty and thus not showing a "*" in the title, it could happen that it's not saved and no code is generated. Another possible workarriund would be to move one of the icons a little bit.

[reiner_hille-doering]

To help you on this issue, we need more input:

- Name of the RFC function that doesn't work.

- The .sapwsdl file (or at least a snipped of it).

- The generated .cs or .vb file (the one that contains the proxy) or at least a snipped of it.

Best you open a OSS support ticket and attach the files.

[Former Member]

Hi Reiner,

Thanks for your quick response.

The problem seems to have gone away.

We are not sure what could have caused it,why it went away, and when it could return.

My colleague suggested to apply SAP Note Number: 506603.

Does this have any bearing on the SAP .NET connector runtime (SAP.Connector & SAP.Connector.Rfc assemblies) ?

The RFC is a custom one built by another collegue.

I have a zip file with all the previous screen shots.

Please give me an email address i could mail it to you directly.

Our guess is that it is a server setting that was turned on and off.

We would like to know which one it is.

Thanks,

Amit.

[reiner_hille-doering]

The problem (or it's solution) could have been related to the patch from note 506603. It doesn't have any influence for runtime, but you mentioned that the proxy has not been correctly created. And the fix does have a influence on code generation.

[Former Member]

I got the same problem and could't solve it.

It only happens when calling custom functions.

The SAP Lib doesn't generate the method codes.

Any tips on the directions I should go ?

Thanks !