REBP_PARTNER_COMMUNICATION SAP (Communication Data for Partner) Structure details
Description: Communication Data for Partner
Related tables to REBP_PARTNER_COMMUNICATION
Access table REBP_PARTNER_COMMUNICATION
Structure field list including key, data, relationships and ABAP select examples
REBP_PARTNER_COMMUNICATION 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 "Communication Data for Partner" 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_REBP_PARTNER_COMMUNICATION TYPE REBP_PARTNER_COMMUNICATION.
The REBP_PARTNER_COMMUNICATION table consists of various fields, each holding specific information or linking keys about Communication Data for Partner data available in SAP. These include SMTP_ADDR (E-Mail Address), TEL_COUNTRY (Country for telephone/fax number), TEL_NUMBER (Telephone no.: dialling code+number), TEL_EXTENS (Telephone no.: Extension).. 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 (character-type or numeric)
SAP REBP_PARTNER_COMMUNICATION 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 |
| DEFAULTCOMM | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | Assigned to domain | AD_COMM | |||
| SMTP_ADDR | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
| TEL_COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| TEL_NUMBER | Telephone no.: dialling code+number | AD_TLNMBR | CHAR | 30 | CHAR30 | ||||
| TEL_EXTENS | Telephone no.: Extension | AD_TLXTNS | CHAR | 10 | CHAR10 | ||||
| TEL_NUMBER_LONG | Complete number: dialling code+number+extension | AD_TELNRLG | CHAR | 30 | CHAR30 | ||||
| FAX_COUNTRY | Country for telephone/fax number | AD_COMCTRY | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
| FAX_NUMBER | Fax number: dialling code+number | AD_FXNMBR | CHAR | 30 | CHAR30 | ||||
| FAX_EXTENS | Fax no.: Extension | AD_FXXTNS | CHAR | 10 | CHAR10 | ||||
| FAX_NUMBER_LONG | Complete number: dialling code+number+extension | AD_FXNRLNG | CHAR | 30 | CHAR30 |
| Key field | Non-key field |
How do I retrieve data from SAP structure REBP_PARTNER_COMMUNICATION using ABAP code?
As REBP_PARTNER_COMMUNICATION 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 REBP_PARTNER_COMMUNICATION as there is no data to select.How to access SAP table REBP_PARTNER_COMMUNICATION
Within an ECC or HANA version of SAP you can also view further information about REBP_PARTNER_COMMUNICATION 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