SOESD SAP (SAPoffice: data structure of external send protocol (SOES)) Structure details
Description: SAPoffice: data structure of external send protocol (SOES)
Structure field list including key, data, relationships and ABAP select examples
SOESD 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 "SAPoffice: data structure of external send protocol (SOES)" 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_SOESD TYPE SOESD.
The SOESD table consists of various fields, each holding specific information or linking keys about SAPoffice: data structure of external send protocol (SOES) data available in SAP. These include SNDTIM (Time at Which The Object Was Sent), SNDART (Transmission Method (Fax, Telex, ...)), ADRNR (Addresses: Address Number), LFDNR (Addresses: Sequence Number of 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: Not classified
SAP SOESD 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 |
SNDDAT | Date On Which Object Was Sent | SO_DAT_SD | DATS | 8 | DATUM | ||||
SNDTIM | Time at Which The Object Was Sent | SO_TIM_SD | TIMS | 6 | UZEIT | ||||
SNDART | Transmission Method (Fax, Telex, ...) | SO_SND_ART | CHAR | 6 | SO_SND_ART | ||||
ADRNR | Addresses: Address Number | SO_ADR_NR | CHAR | 10 | Assigned to domain | ALPHA | ADRNR | ||
LFDNR | Addresses: Sequence Number of Address | SO_LFD_NR | CHAR | 3 | LFDNR | ||||
SCOMTP | SAPcomm ID: ID type | SO_SCOM_TP | CHAR | 3 | Assigned to domain | SO_OBJ_TP | |||
SCOMYR | SAPcomm: year of ID | SO_SCOM_YR | CHAR | 2 | SO_OBJ_YR | ||||
SCOMNO | SAPcomm: number of the ID | SO_SCOM_NO | CHAR | 12 | Assigned to domain | SO_OBJ_NO | |||
SCDATE | SAPcomm: Transfer date to SAPcomm | SO_SC_DATE | DATS | 8 | DATUM | ||||
SCTIME | SAPcomm: Transfer time to SAPcomm | SO_SC_TIME | TIMS | 6 | UZEIT | ||||
DELIVER | Acknowledgment of receipt expected | SO_NF_DELI | CHAR | 1 | SO_FLAG | ||||
NOT_DELI | Acknowledgment of receipt expected | SO_NOTDELI | CHAR | 1 | SO_FLAG | ||||
READ | Read acknowledgment expected | SO_NOTREC | CHAR | 1 | SO_TEXT001 | ||||
SAP_BODY | Send externally with SAP data part | SO_SAP_BDY | CHAR | 1 | SO_FLAG | ||||
STATUS | SAPcomm: status of the sent object | SO_REC_STA | CHAR | 12 | SO_TEXT012 | ||||
MAILSTATUS | Status of external send in which a mail was sent | SO_MLSTAT | CHAR | 1 | SYCHAR01 | ||||
MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
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 | ||||
NODE | Name of SAPconnect Node or Telephony Server | SX_NODE_ID | CHAR | 6 | Assigned to domain | SX_NODE_ID | SXN | SX_NODE_ID | |
JOBNAME | Name of Send Process | SO_JOBNAME | CHAR | 32 | CHAR32 | ||||
JOBCOUNT | ID number of send process | SO_JOBCNT | CHAR | 8 | CHAR8 |
Key field | Non-key field |
How do I retrieve data from SAP structure SOESD using ABAP code?
As SOESD 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 SOESD as there is no data to select.How to access SAP table SOESD
Within an ECC or HANA version of SAP you can also view further information about SOESD 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