BUS_EI_COM_BUPA_TLX SAP (Com. Interface: Data for Creating a Telex Number) Structure details
Description: Com. Interface: Data for Creating a Telex Number
Related tables to BUS_EI_COM_BUPA_TLX
Access table BUS_EI_COM_BUPA_TLX
Structure field list including key, data, relationships and ABAP select examples
BUS_EI_COM_BUPA_TLX 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 "Com. Interface: Data for Creating a Telex Number" 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_BUS_EI_COM_BUPA_TLX TYPE BUS_EI_COM_BUPA_TLX.
The BUS_EI_COM_BUPA_TLX table consists of various fields, each holding specific information or linking keys about Com. Interface: Data for Creating a Telex Number data available in SAP. These include TASK (Com. Interface: Change Indicator), DATA (), COUNTRY (R3A BP: Country Key), COUNTRYISO (R3A BP: ISO Code of Country).. 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: Can Be Enhanced (Deep)
SAP BUS_EI_COM_BUPA_TLX 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 |
| CONTACT | 0 | ||||||||
| TASK | Com. Interface: Change Indicator | GC_TASK | CHAR | 1 | CHAR1 | ||||
| DATA | 0 | ||||||||
| COUNTRY | R3A BP: Country Key | GB_LAND1 | CHAR | 3 | CHAR3 | ||||
| COUNTRYISO | R3A BP: ISO Code of Country | GB_INTCA | CHAR | 2 | CHAR2 | ||||
| STD_NO | R3A BP: Standard Sender Address in This Method of Communic. | GB_FLGDFNR | CHAR | 1 | CHAR1 | ||||
| TELEX_NO | R3A BP: Telex Number | GB_TLXNMBR | CHAR | 30 | CHAR30 | ||||
| STD_RECIP | R3A BP: Indic.: Recipient is Standard Recipient for this No. | GB_DFTRCNR | CHAR | 1 | CHAR1 | ||||
| R_3_USER | R3A BP: Indicator: Connected to R/3 | GB_R3_USER | CHAR | 1 | CHAR1 | ||||
| HOME_FLAG | R3A BP:Recipient Addr. in This Meth. of Comm (Mail Syst Grp) | GB_FLGHOME | CHAR | 1 | CHAR1 | ||||
| CONSNUMBER | R3A BP: Sequence Number | GB_CONSNUM | NUMC | 3 | NUMC3 | ||||
| ERRORFLAG | R3A BP: Indicator: Record not Processed | GB_ERRBAPI | CHAR | 1 | CHAR1 | ||||
| FLG_NOUSE | R3A BP: Indicator: Do Not Use this Communication Number | GB_FLNOUSE | CHAR | 1 | CHAR1 | ||||
| VALID_FROM | Valid from (YYYYMMDDHHMMSS) | GB_VALFROM | CHAR | 14 | TIMESTMP | ||||
| VALID_TO | Valid to (YYYYMMDDHHMMSS) | GB_VALTO | CHAR | 14 | TIMESTMP | ||||
| DATAX | 0 | ||||||||
| COUNTRY | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| COUNTRYISO | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| STD_NO | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| TELEX_NO | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| STD_RECIP | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| R_3_USER | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| HOME_FLAG | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| CONSNUMBER | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| UPDATEFLAG | R3A BP: Change Indicator for BAI Structures at BP | GB_UPDFLAG | CHAR | 1 | CHAR1 | ||||
| FLG_NOUSE | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| VALID_FROM | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| VALID_TO | R3A BP: Change Information for Relevant User Data Field | GB_BAPIUPD | CHAR | 1 | CHAR1 | ||||
| REMARK | 0 | ||||||||
| CURRENT_STATE | Com. Interface: Curent State Flag | GC_C_STATE | CHAR | 1 | CHAR1 | ||||
| REMARKS | 0 | ||||||||
| CURRENTLY_VALID | External Interface: Data Currently Valid | BUS_EI_CURRENTLY_VALID | CHAR | 1 | BU_EI_CURRENTLY_VALID | ||||
| COMM_USAGE | 0 | ||||||||
| CURRENT_STATE | External Interface: Indicator for Complete Data | BUS_EI_CURRENT_STATE | CHAR | 1 | XFELD | ||||
| COMM_USAGES | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure BUS_EI_COM_BUPA_TLX using ABAP code?
As BUS_EI_COM_BUPA_TLX 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 BUS_EI_COM_BUPA_TLX as there is no data to select.How to access SAP table BUS_EI_COM_BUPA_TLX
Within an ECC or HANA version of SAP you can also view further information about BUS_EI_COM_BUPA_TLX 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