MSM_COMMUNICATE SAP (Global communication structure) Structure details
Description: Global communication structure
Related tables to MSM_COMMUNICATE
Access table MSM_COMMUNICATE
Structure field list including key, data, relationships and ABAP select examples
MSM_COMMUNICATE 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 "Global communication structure" 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_MSM_COMMUNICATE TYPE MSM_COMMUNICATE.
The MSM_COMMUNICATE table consists of various fields, each holding specific information or linking keys about Global communication structure data available in SAP. These include DEVICE (Communication type (key)), DEVICE_TEXT (Communication type description), REMARK (Communication link notes), RECEIVER (Recipient address).. 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)
SAP MSM_COMMUNICATE 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 |
| MARK | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| DEVICE | Communication type (key) | AD_COMTYPE | CHAR | 3 | Assigned to domain | AD_COMTYPE | |||
| DEVICE_TEXT | Communication type description | AD_COM_TX | CHAR | 20 | TEXT20 | ||||
| REMARK | Communication link notes | AD_REMARK2 | CHAR | 50 | TEXT50 | ||||
| RECEIVER | Recipient address | SO_NAME | CHAR | 241 | SO_STRI241 | ||||
| L_ART | Specification of recipient type | SO_ESCAPE | CHAR | 1 | SO_ESCAPE | ||||
| FLGDEFAULT | Standard Sender Address in this Communication Type | AD_FLGDFNR | CHAR | 1 | XFELD | ||||
| ZAV_ADDRNUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| ZAV_PERSNUMBER | Person number | AD_PERSNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_PERSNUM | CDT | ADDRESS |
| CONSNUMBER | Sequence Number | AD_CONSNUM | NUMC | 3 | NUMC3 | ||||
| PARTNER_ART | Type of partner number | NRART | CHAR | 2 | Assigned to domain | NRART | |||
| PARTNER_NUMBER | Partner | I_PARNR | CHAR | 12 | ALPHA | I_PARNR |
| Key field | Non-key field |
How do I retrieve data from SAP structure MSM_COMMUNICATE using ABAP code?
As MSM_COMMUNICATE 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 MSM_COMMUNICATE as there is no data to select.How to access SAP table MSM_COMMUNICATE
Within an ECC or HANA version of SAP you can also view further information about MSM_COMMUNICATE 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