This functionality is obsolete and will not be supported by ERPConnect starting by version 4.5.
In each of the examples previously discussed, we referred to functional modules or BAPIs with the “RFC-enabled” attribute. But that’s only one subset of all the modules available in an SAP system. With ERPConnect, it is also possible to execute modules that are not explicitly labeled as RFC enabled. For this purpose, a sort of wrapper is internally built around the module, executing it indirectly instead of directly. As a developer though, you’ll hardly notice this. The only thing you have to do is to set the attribute UseRFCWraper of the RFCFunction object to true.
The following example shows the call of the module READ_TEXT. It is used by ABAP programs to read text objects (such as e.g. a sales memo to a customer). By default it is not RFC enabled, yet it still works with ERPConnect.
Important!!! Unfortunately, the tactic with the wrapper only works if the modification flag in the SAP system is set (see transaction SE03, administration). To find out if this flag is set, the attribute IsEditable of the R3Connection object can be queried, as shown in the following.
Click to open C# example.