RFCFunctionMBS.Constructor(typeDescription as RFCFunctionDescriptionMBS)

The importing parameters can be set using the Value() properties. After the RfcInvoke call returned successfully, the exporting parameters can be read from this data container via the Value() properties.

RFCFunctionMBS.DescribeFunction as RFCFunctionDescriptionMBS

If the function description is already in the repository cache for that system ID, it will be returned immediately (from the cache), otherwise it will be looked up in the system's DDIC using the connection. The result from the DDIC lookup will then be placed in the cache. The RFC Runtime maintains a cache for every SAP System ID, as the meta data may be different depending on the SAP release. This is the main API that should be used.

RFCFunctionMBS.Destructor

RFCFunctionMBS.Invoke

Dim fd As RFCFunctionDescriptionMBS = connection.FunctionDescription("BAPI_COMPANY_GETDETAIL")
Dim f As RFCFunctionMBS = fd.CreateFunction

f.StringValue("COMPANYID") = "000007"
f.Invoke

Dim s As RFCStructureMBS = f.StructureValue("RETURN")
Dim t As String = s.StringValue("MESSAGE")

MsgBox t

RFCFunctionMBS.ParameterActive(Name as String) as Boolean

This is particularly useful for BAPIs which have many large tables, in which you are not interested.
Deactivate those and leave only those tables active, in which you are interested. This reduces network traffic and memory consumption in your application considerably.

This functionality can be used for input and output parameters. If the parameter is an input, no data for that parameter will be sent to the backend. If it's an output, the backend will be informed not to return data for that parameter.
(Read and Write computed property)