/BOFU/S_SEND_REQUEST_K SAP (Combined structure for send request) Structure details
Dictionary Type: Structure
Description: Combined structure for send request
Description: Combined structure for send request
ABAP Code to SELECT data from /BOFU/S_SEND_REQUEST_K
Related tables to /BOFU/S_SEND_REQUEST_K
Access table /BOFU/S_SEND_REQUEST_K
Related tables to /BOFU/S_SEND_REQUEST_K
Access table /BOFU/S_SEND_REQUEST_K
Structure field list including key, data, relationships and ABAP select examples
/BOFU/S_SEND_REQUEST_K 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 "Combined structure for send request" 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_/BOFU/S_SEND_REQUEST_K TYPE /BOFU/S_SEND_REQUEST_K.
The /BOFU/S_SEND_REQUEST_K table consists of various fields, each holding specific information or linking keys about Combined structure for send request data available in SAP. These include MANDT (Client), OS_GUID (Globally Unique Identifier), CHG_USER (Changed by), SND_CLS (Globally Unique Identifier).. 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 /BOFU/S_SEND_REQUEST_K 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| OS_GUID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| CHG_USER | Changed by | SO_CHO_NAM | CHAR | 12 | USERNAME | ||||
| SND_CLS | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| SND_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| REP_TO_CLS | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| REP_TO_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| STREC_CLS | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| STREC_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| SIG_WF | GUID in 'CHAR' Format in Uppercase | GUID_32 | CHAR | 32 | SYSUUID_C | ||||
| ASYNC | Boolean | OS_BOOLEAN | CHAR | 1 | OS_BOOLEAN | ||||
| ENCRYPT | Boolean | OS_BOOLEAN | CHAR | 1 | OS_BOOLEAN | ||||
| SIGN | Boolean | OS_BOOLEAN | CHAR | 1 | OS_BOOLEAN | ||||
| STATE | Send Request Status | SR_STATE | CHAR | 1 | SR_STATE | ||||
| PRIORITY | Send: Priority | SO_SND_PRI | CHAR | 1 | SO_OBJ_PRI | ||||
| NOTE_CLS | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| NOTE_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| DOC_CLS | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| DOC_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| OSR_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| MIME_DOC | Logical document | SDOK_LOID | CHAR | 32 | SDOK_DOCID | ||||
| REQ_STAT | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| STATUSMAIL | Setting for Which Statuses Are Reported by Mail | BCS_STML | CHAR | 1 | BCS_STML | ||||
| OUTBOX | Boolean | OS_BOOLEAN | CHAR | 1 | OS_BOOLEAN | ||||
| LAST_STAT | Accumulated Last Recipient Status | BCS_LST_ST | CHAR | 1 | CHAR01 | ||||
| TSND_CLS | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| TSND_OID | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| IN_RPLY_TO | Globally Unique Identifier | OS_GUID | RAW | 16 | SYSUUID | ||||
| SCOM_KEY | SAPoffice: ID of a SAPoffice object | SO_OBJ_ID | CHAR | 17 | SO_OBJ_ID | ||||
| APPL_ID | Application ID | BCS_APPL | CHAR | 4 | BCS_APPL | ||||
| TO_DELETE | Deletion Indicator (Marked for Deletion) | BCS_DEL | CHAR | 1 | SO_FLAG | ||||
| EXPIRES_ON | Expiration Date in UTC | BCS_XPIRE | DEC | 15 | TZNTSTMPS | ||||
| CREATED_ON | Creation Date in UTC | BCS_CREA | DEC | 15 | TZNTSTMPS | ||||
| CHANGED_ON | Change Date in UTC | BCS_CHANG | DEC | 15 | TZNTSTMPS | ||||
| SEND_AT | BCS: Send in the Future: Time Stamp in UTC | BCS_SNDAT | DEC | 15 | TZNTSTMPS | ||||
| MIME_TRANSIENT | Boolean | OS_BOOLEAN | CHAR | 1 | OS_BOOLEAN | ||||
| PCOPY_EXISTS | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
| SUBJECT | Subject (Without Length Restriction) | BCSD_SUBJ | CHAR | 255 | |||||
| DSN_MIME | Logical document | SDOK_LOID | CHAR | 32 | SDOK_DOCID | ||||
| DISCLOSURE | Setting: Insert disclosure? | BCS_DISCL | NUMC | 1 | BCS_DISCL | ||||
| /BOFU/NOTE_TEXT | BCS: Note Text | /BOFU/BCS_NOTE_TEXT | STRG | 0 | |||||
| DOC_IMP | Document Priority | /BOFU/DOC_IMP | CHAR | 1 | /BOFU/DOC_IMP | ||||
| KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
| PARENT_KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY | ||||
| ROOT_KEY | NodeID | /BOBF/CONF_KEY | RAW | 16 | /BOBF/CONF_KEY |
| Key field | Non-key field |
How do I retrieve data from SAP structure /BOFU/S_SEND_REQUEST_K using ABAP code?
As /BOFU/S_SEND_REQUEST_K 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 /BOFU/S_SEND_REQUEST_K as there is no data to select.How to access SAP table /BOFU/S_SEND_REQUEST_K
Within an ECC or HANA version of SAP you can also view further information about /BOFU/S_SEND_REQUEST_K 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