SOXER SAP (SAPoffice: external recipients of an object) Structure details
Description: SAPoffice: external recipients of an object
Structure field list including key, data, relationships and ABAP select examples
SOXER 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: external recipients of an object" 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_SOXER TYPE SOXER.
The SOXER table consists of various fields, each holding specific information or linking keys about SAPoffice: external recipients of an object data available in SAP. These include DELIVERY (SAPoffice: Deliver to recipient anyway?), SNDEX (Send express), SNDCP (Send: As copy), SNDBC (Send as a blind copy).. 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 SOXER 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 |
| RECEIVER | Recipient address for the SAP communications server | SO_REC_ADR | CHAR | 1244 | SO_ADDRESS | ||||
| DELIVERY | SAPoffice: Deliver to recipient anyway? | SO_DELI | CHAR | 1 | SO_FLAG | ||||
| SNDEX | Send express | SO_SND_EX | CHAR | 1 | SO_FLAG | ||||
| SNDCP | Send: As copy | SO_SND_CP | CHAR | 1 | SO_FLAG | ||||
| SNDBC | Send as a blind copy | SO_SND_BC | CHAR | 1 | SO_FLAG | ||||
| FORFB | You cannot forward this message | SO_FORFB | CHAR | 1 | SO_FLAG | ||||
| PRIFB | Object cannot be printed | SO_PRIFB | CHAR | 1 | SO_FLAG | ||||
| SNDPRI | Send: Priority | SO_SND_PRI | CHAR | 1 | SO_OBJ_PRI | ||||
| ACDAT | Date by which action is to be taken on the received document | SO_DAT_AC | DATS | 8 | DATUM | ||||
| ACTIM | Time by which the received object must be acted upon | SO_TIM_AC | TIMS | 6 | UZEIT | ||||
| ACALL | ToDo by all recipients | SO_ACALL | CHAR | 1 | SO_FLAG | ||||
| ACONE | ToDo by one of the recipients in the group | SO_ACONE | RAW | 1 | SO_CNT1 | ||||
| RRDAT | A reply to the document must be sent by the specified date | SO_DAT_RR | DATS | 8 | DATUM | ||||
| RRTIM | A reply must be sent by the specified time | SO_TIM_RR | TIMS | 6 | UZEIT | ||||
| OBJRR | A reply must be sent for this object | SO_OBJ_RR | CHAR | 1 | SO_FLAG | ||||
| NOTIF_DELI | SAPoffice: Is a delivery confirmation required? | SO_NOT_DEL | CHAR | 1 | SO_FLAG | ||||
| NOTIF_REC | SAPoffice: Is a receipt confirmation required? | SO_NOT_REC | CHAR | 1 | SO_FLAG |
| Key field | Non-key field |
How do I retrieve data from SAP structure SOXER using ABAP code?
As SOXER 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 SOXER as there is no data to select.How to access SAP table SOXER
Within an ECC or HANA version of SAP you can also view further information about SOXER 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