Providing RFCs in Lobster_data
As you already know, Lobster_data can call RFCs in SAP systems. Here we want to describe how to provide an RFC in Lobster_data that can be called from an SAP system.
An RFC provided by Lobster_data can be provided either asynchronously or synchronously. When working asynchronously, data can only be sent to a profile in Lobster_data, without a response back to the calling SAP system. In synchronous mode, a response from the Lobster_data profile can be sent back to the calling SAP system. The definition of the RFC interface can either be in the form of an XML file, or the interface of an RFC, which exists actively under the same name in the connected SAP in the SAP Dictionary, can be "mirrored". Only the interface of the RFC is copied, not its ABAP implementation in SAP. The advantage of this configuration, called 'copyFromPeer', is that it ensures that all data types used in the interface also actively exist in the SAP Dictionary. This suits the mindset of SAP consultants. See section Providing the RFC (second configuration option).
If several RFCs are to be provided, a separate configuration is required for each RFC. Each RFC is associated with a Lobster_data profile.