This extract allows the retrieval of data from RFC or BAPI function in an SAP System. Logically, only those RFCs that read data from SAP should be used here. RFC functions that commit data or require user interaction (pop-up dialogs for user input) will lead to an error.
Note: RFC stands for Remote Function Call. A SAP Function Module has to be defined as “Remote enabled" in the SAP system to be a RFC.
Settings
| Connection | Name of the SAP connection. |
| Function module | Name of the RFC function module. |
| Import parameters | The parameter name and its value. |
| Import structures | The structure name, the field name, and its value. |
| Import tables | The table name, the line number, the field name of the table structure, and its value. |
| Export structure type | The output of the extract is given by one table or one structure of the RFC. |
| Export structure name | The name of the table/structure has to be defined. |
| Export data fields | The columns of extract output are defined as follows:
|
| Use return message of function module | Many RFCs and all BAPIs use a specific exporting structure or table for return messages that occurred during the RFC processing. It is possible to use this information for the Integrator message log. The name and the type (exporting structure or table) differ between different RFCs, so it has to be specified in the extract. For BAPIs, the structure is mostly called “RETURN”. |
| Structure name | Name of the RFC structure or table with the return messages. |
| Use caching | Memory, disk, or none (default). See Caching in Extracts. |
Note: it is not possible to read multiple exporting tables of one RFC in one extract. In case of a structure, the output will only contain one single row.
Updated March 15, 2024