Professional Documents
Culture Documents
RFC
RFC
Behavior – Sync/Async
To add ECC system details, we click on paper icon and select connection, a window pops up and
there we select User specified system and click on next.
Description: Dev/Quality/Prod
Logon details will be provided by BASIS team, if not provided please ask them to create and provide
the same.
1. Standard RFC – (Name starts with A-X) – these are inbuilt RFCs that are existing in SAP tool
itself.
2. Custom RFC – (Name starts with Y-Z) – created by ABAP consultant as per our requirement.
3. Extended RFC – Standard RFC with some Modifications as per the requirement.
RFC is used to exchange data between SAP application and Non SAP application.
**************************************
In SAP we use T-Code SE37 to create custom RFC, name starts with Y-Z(it is created by ABAP
consultant).
The Function Builder screen appears when we use T Code SE37 and there we have to give Function
Module name and click on Create.
We can skip the above step when we have to work with standard RFC.
We have to create RFC destination using T-Code SM59 (Basis team needs to do this step)m
We need to give Gateway Host and service details under Gateway options. The Gateway option
details are found under the transaction code SMGW
SMGWGotoParameter Display
For SAP adapters we use AS ABAP technical system to create SLD objects
Once the RFC destination is created, we have to import RFC into ESR.
Goto the name space under which the RFC has to be updated, click on imported objects Import of
SAP objects and in the window (import from SAP system) Application server and System Number
details -> Under logon details give ECC User name and password
Select RFC option and select the required RFC specified by ABAPer/Functional consultant
Adapter: RFC