sap-rfc-wrapper-class

Exposing an ABAP class method as an RFC callable function module requires generating a wrapper function module that mirrors the method's interface and internally dispatches the call to the class. This allows external SAP clients to invoke the logic via RFC.

Yes, you can call both static and instance ABAP class methods externally via RFC. The generated wrapper function module handles the interface mapping and internal dispatching, supporting both method types for external integration without exposing underlying class details.

The wrapper handles IMPORTING, EXPORTING, and CHANGING parameters by reading the class method interface from SEOCOMPODF and SEOSUBCODF tables. It generates an ABAP function module that accurately maps these parameters alongside TABLES and EXCEPTIONS to ensure proper RFC integration.

Yes, you need SAP login and active RFC connectivity to generate RFC wrappers for class methods. These prerequisites allow the system to read class interfaces via RFC_READ_TABLE and deploy the generated function module to SE37 using TR deployment rules.

The best way to integrate external .NET or Java clients with internal ABAP class logic is using a generated RFC wrapper. This approach deploys a function module that acts as an entry point, invoking the encapsulated ABAP class method through RFC without exposing the class itself.

Source-based ABAP classes are handled using an RTTI-based fallback when generating an RFC wrapper. This ensures the function module accurately captures and maps the method interface even when standard table reads via SEOCOMPODF are insufficient.