BTP_SMI_S_RFCDEST SAP (BTP SMSY RFC-Destinations) Structure details
Description: BTP SMSY RFC-Destinations
Related tables to BTP_SMI_S_RFCDEST
Access table BTP_SMI_S_RFCDEST
Structure field list including key, data, relationships and ABAP select examples
BTP_SMI_S_RFCDEST is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "BTP SMSY RFC-Destinations" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BTP_SMI_S_RFCDEST TYPE BTP_SMI_S_RFCDEST.
The BTP_SMI_S_RFCDEST table consists of various fields, each holding specific information or linking keys about BTP SMSY RFC-Destinations data available in SAP. These include MANDT (BTP SMSY System Client), MANDT_DESCR (BTP SMSY System Client Description), RFCDEST (Logical Destination (Specified in Function Call)), RFCTYPE (Type of Entry in RFCDES).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP BTP_SMI_S_RFCDEST structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| SYSTEM | BTP SMSY System Name | BTP_SMI_SMSY_SYSTEMNAME | CHAR | 8 | BTP_SMI_SMSY_SYSTEMNAME | ||||
| MANDT | BTP SMSY System Client | BTP_SMI_SMSY_MANDT | CHAR | 3 | BTP_SMI_SMSY_MANDT | ||||
| MANDT_DESCR | BTP SMSY System Client Description | BTP_SMI_SMSY_MANDT_DESCR | CHAR | 30 | BTP_SMI_SMSY_SHDESCRIPTION | ||||
| RFCDEST | Logical Destination (Specified in Function Call) | RFCDEST | CHAR | 32 | Assigned to domain | RFCDEST | RFC | F4_RFCDESTYPEALL | |
| RFCTYPE | Type of Entry in RFCDES | RFCTYPE_D | CHAR | 1 | RFCTYPE | ||||
| RFCTYPETEXT | RFC connection type | RFCTYTEXT | CHAR | 32 | RFCNAME | ||||
| PURPOSE | BTP SMSY Purpose of a RFC destination | BTP_SMI_SMSY_RFCDEST_PURPOSE | CHAR | 10 | BTP_SMI_SMSY_RFCDEST_PURPOSE | ||||
| RFCDOC1 | Description of RFC connection | RFCDOC_D | CHAR | 72 | RFCDOC | ||||
| RFCDOC2 | Description of RFC connection | RFCDOC_D | CHAR | 72 | RFCDOC | ||||
| RFCDOC3 | Description of RFC connection | RFCDOC_D | CHAR | 72 | RFCDOC |
| Key field | Non-key field |
How do I retrieve data from SAP structure BTP_SMI_S_RFCDEST using ABAP code?
As BTP_SMI_S_RFCDEST is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BTP_SMI_S_RFCDEST as there is no data to select.How to access SAP table BTP_SMI_S_RFCDEST
Within an ECC or HANA version of SAP you can also view further information about BTP_SMI_S_RFCDEST and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects