Package com.sap.cloud.sdk.s4hana.connectivity.rfc

Class RfmRequest

java.lang.Object
com.sap.cloud.sdk.s4hana.connectivity.Request<RequestT,RequestResultT>
com.sap.cloud.sdk.s4hana.connectivity.rfc.AbstractRemoteFunctionRequest<RfmRequest,RfmRequestResult>
com.sap.cloud.sdk.s4hana.connectivity.rfc.RfmRequest
@Deprecated public class RfmRequest extends AbstractRemoteFunctionRequest<RfmRequest,RfmRequestResult>
Deprecated.
This module will be discontinued, along with its classes and methods.
Class representing a request calling a remote-enabled function module (RFC module or RFM) in an ERP system.

Use the class BapiRequest to call BAPIs in an ERP system.

The signature of an RFM consists of importing, exporting, changing, and tables parameters.

From the perspective of the RFM caller, input data is considered as exporting, output data is considered as importing, tables, and changing parameters can be used for both directions. The methods of this class are named following the caller's perspective.

From the perspective of the RFM, importing means input data, exporting means output data, changing, and tables parameters can be used for both directions.

Example:
Calling a RFM with one importing parameter (from RFM perspective) requires to utilize the method withExporting(String, String). Consider all existing variants of this method depending on the Java data type of the parameter, e.g. use withExporting(String, String, String) to pass a String object.

The data type (i.e. the data dictionary object) of importing and exporting parameters (regardless of the perspective) can either be a data element, a structure, or a table type.

After calling execute(Destination) use the class RfmRequestResult to access the results of the RFM call (e.g. the exporting parameters from the RFM perspective respectively the importing parameters from the caller's perspective).