CMD_S_MSG_COMPLETE SAP (Message with All Additional Data) Structure details
Description: Message with All Additional Data
Related tables to CMD_S_MSG_COMPLETE
Access table CMD_S_MSG_COMPLETE
Structure field list including key, data, relationships and ABAP select examples
CMD_S_MSG_COMPLETE 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 "Message with All Additional Data" 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_CMD_S_MSG_COMPLETE TYPE CMD_S_MSG_COMPLETE.
The CMD_S_MSG_COMPLETE table consists of various fields, each holding specific information or linking keys about Message with All Additional Data data available in SAP. These include MDO_NAME (Master Data Object), MDO_KEY (Object Key (Master Data Object)), MDS_NAME (Master Data Segment), MDS_KEY (Object Key (Master Data Segment)).. 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 CMD_S_MSG_COMPLETE 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 |
| MDO_NAME | Master Data Object | CMD_MDOBJECT | CHAR | 30 | |||||
| MDO_KEY | Object Key (Master Data Object) | CMD_MDOKEY | STRG | 0 | |||||
| MDS_NAME | Master Data Segment | CMD_MDSEGMENT | CHAR | 30 | |||||
| MDS_KEY | Object Key (Master Data Segment) | CMD_MDSKEY | STRG | 0 | |||||
| MDS_KEYTYPE | Key Type | CMD_MDS_KEYTYPE | CHAR | 1 | CMD_KEYTYPE | ||||
| MDS_ATTR | Object Attribute (Master Data Segment) | CMD_MDSATTR | STRG | 0 | |||||
| MDS_ATTR_SOURCE | 0 | ||||||||
| MDS_ATTR_TARGET | 0 | ||||||||
| LIFETIME | Lifetime of Message | CMD_MSGLIFETIME | CHAR | 1 | CMD_LIFETIME | ||||
| CATEGORY | Message Category | CMD_LOGMSGCAT | CHAR | 1 | CMD_MSGCAT | ||||
| CONSUMER_ID | Message Generator | CMD_MSGCONSUMER | CHAR | 100 | CMD_CONSUMER | ||||
| MSGKIND | Message Type | CMD_MSGKIND | CHAR | 3 | CMD_MSGKIND | ||||
| SYMPTOM | Message symptom | CMD_SESF_MESSAGE_SYMPTOM | CHAR | 15 | |||||
| IS_RESUMABLE | Yes/No - Field | CMD_LOGFLAGX | CHAR | 1 | CMD_LOGFLAGX | ||||
| MSGHNDL | 0 | ||||||||
| LOG_HANDLE | Application Log: Log Handle | BALLOGHNDL | CHAR | 22 | SYSUUID_22 | ||||
| MSGNUMBER | Sequential Number of Message | CMD_MSGNUMBER | NUMC | 10 | CMD_NUMC10 | ||||
| MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
| MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
| MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV1_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
| MSGV2_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
| MSGV3_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
| MSGV4_SRC | Application Log: Origin of a message variable | BALMSGVSRC | CHAR | 15 | CHAR15 | ||||
| DETLEVEL | Application Log: Level of detail | BALLEVEL | CHAR | 1 | BALLEVEL | ||||
| PROBCLASS | Application log: Message problem class | BALPROBCL | CHAR | 1 | BALPROBCL | ||||
| ALSORT | Application log: Sort criterion/grouping | BALSORT | CHAR | 3 | CHAR3 | ||||
| TIME_STMP | Application Log: Message time stamp | BALTIMSTMP | DEC | 21(7) | TZNTSTMPL | ||||
| MSG_COUNT | Application Log: Cumulated message count | BALCNTCUM | INT4 | 10 | BALCOUNT | ||||
| CONTEXT | 0 | ||||||||
| TABNAME | Application Log: Context: DDIC structure name | BALTABNAME | CHAR | 30 | Assigned to domain | AS4TAB | DTB | ||
| VALUE | Application Log: Context data | BALCVAL | CHAR | 256 | BALCVAL | ||||
| PARAMS | 0 | ||||||||
| T_PAR | 0 | ||||||||
| CALLBACK | 0 | ||||||||
| USEREXITP | Application Log: Callback: Program name | BALUEP | CHAR | 40 | PROGNAME | ||||
| USEREXITF | Application Log: Callback: Routine name | BALUEF | CHAR | 30 | CHAR30 | ||||
| USEREXITT | Application Log: Callback: Type (Ext. Perform, FM, etc.) | BALUET | CHAR | 1 | BALUET | ||||
| ALTEXT | Application log: Standard text | BALTEXT | CHAR | 28 | CHAR28 |
| Key field | Non-key field |
How do I retrieve data from SAP structure CMD_S_MSG_COMPLETE using ABAP code?
As CMD_S_MSG_COMPLETE 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 CMD_S_MSG_COMPLETE as there is no data to select.How to access SAP table CMD_S_MSG_COMPLETE
Within an ECC or HANA version of SAP you can also view further information about CMD_S_MSG_COMPLETE 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