JBIBP_BUS_EI_BUPA_RFC_CON SAP (Ext. Interface: Data for Creating an RFC Destination) Structure details
Description: Ext. Interface: Data for Creating an RFC Destination
Related tables to JBIBP_BUS_EI_BUPA_RFC_CON
Access table JBIBP_BUS_EI_BUPA_RFC_CON
Structure field list including key, data, relationships and ABAP select examples
JBIBP_BUS_EI_BUPA_RFC_CON 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 "Ext. Interface: Data for Creating an RFC Destination" 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_JBIBP_BUS_EI_BUPA_RFC_CON TYPE JBIBP_BUS_EI_BUPA_RFC_CON.
The JBIBP_BUS_EI_BUPA_RFC_CON table consists of various fields, each holding specific information or linking keys about Ext. Interface: Data for Creating an RFC Destination data available in SAP. These include DATA (), STD_NO (Standard Sender Address in this Communication Type), LOG_DEST (RFC logical destination), STD_RECIP (Flag: Recipient is standard recipient for this number).. 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: Not classified
SAP JBIBP_BUS_EI_BUPA_RFC_CON 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 |
| TASK | Ext. Interface: Change Indicator for RFC Destination | JBIBP_BUS_EI_RFC_TASK | CHAR | 1 | JBIBP_BU_EI_RFC_TASK | ||||
| DATA | 0 | ||||||||
| STD_NO | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
| LOG_DEST | RFC logical destination | AD_LOGDEST | CHAR | 32 | RFCDEST | ||||
| STD_RECIP | Flag: Recipient is standard recipient for this number | AD_DFTRCNR | CHAR | 1 | XFELD | ||||
| R_3_USER | Flag: Connected to an SAP System | AD_R3_USER | CHAR | 1 | XFELD | ||||
| HOME_FLAG | Recipient address in this communication type (mail sys.grp) | AD_FLGHOME | CHAR | 1 | XFELD | ||||
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| ERRORFLAG | Flag: Record not processed | AD_ERRBAPI | CHAR | 1 | XFELD | ||||
| FLG_NOUSE | Indicator: This Communication Number is Not Used | JBIBP_AD_FLNOUSE | CHAR | 1 | XFELD | ||||
| DATAX | 0 | ||||||||
| STD_NO | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| LOG_DEST | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| STD_RECIP | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| R_3_USER | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| HOME_FLAG | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| CONSNUMBER | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE | ||||
| UPDATEFLAG | Address transfer structure change flag | AD_UPDFLAG | CHAR | 1 | AD_UPDFLAG | ||||
| FLG_NOUSE | Updated information in related user data field | BAPIUPDATE | CHAR | 1 | BAPIUPDATE |
| Key field | Non-key field |
How do I retrieve data from SAP structure JBIBP_BUS_EI_BUPA_RFC_CON using ABAP code?
As JBIBP_BUS_EI_BUPA_RFC_CON 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 JBIBP_BUS_EI_BUPA_RFC_CON as there is no data to select.How to access SAP table JBIBP_BUS_EI_BUPA_RFC_CON
Within an ECC or HANA version of SAP you can also view further information about JBIBP_BUS_EI_BUPA_RFC_CON 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