SNAST SAP (WFMC: Selected fields for message output) Structure details
Description: WFMC: Selected fields for message output
Structure field list including key, data, relationships and ABAP select examples
SNAST 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 "WFMC: Selected fields for message output" 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_SNAST TYPE SNAST.
The SNAST table consists of various fields, each holding specific information or linking keys about WFMC: Selected fields for message output data available in SAP. These include KSCHL (Message type), SPRAS (Message language), ADRNR (Address number), NACHA (Message transmission medium).. 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 SNAST 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 | |||
| KSCHL | Message type | SNA_KSCHL | CHAR | 4 | CHAR4 | ||||
| SPRAS | Message language | NA_SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | ||
| ADRNR | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| NACHA | Message transmission medium | NA_NACHA | CHAR | 1 | NA_NACHA | ||||
| ANZAL | Number of messages (original + copies) | NA_ANZAL | DEC | 2 | DEC2 | ||||
| VSDAT | Requested date for sending message | NA_VSDAT | DATS | 8 | DATUM | ||||
| VSURA | Requested time for sending message (from) | NA_VSURA | TIMS | 6 | UZEIT | ||||
| TCODE | Communication strategy | CSTRATEGY | CHAR | 4 | Assigned to domain | CSTRATEGY | |||
| USNAM | User name | USNAM | CHAR | 12 | Assigned to domain | XUBNAME | USR | ||
| LDEST | Spool: Output device | RSPOPNAME | CHAR | 4 | TSP03 | SPDEV | RSPOPNAME | ||
| DSNAM | Spool request: Name | RSPO0NAME | CHAR | 6 | CHAR6 | ||||
| DSUF1 | Spool request: Suffix 1 | RSPO1NAME | CHAR | 4 | CHAR4 | ||||
| DSUF2 | Spool request: Suffix 2 | RSPO2NAME | CHAR | 12 | CHAR12 | ||||
| DIMME | Print immediately | TDIMMED | CHAR | 1 | TDBOOL | ||||
| DELET | Release after output | TDDELETE | CHAR | 1 | TDBOOL | ||||
| TELFX | Fax number | NA_TELFX | CHAR | 31 | TEXT31 | ||||
| TELX1 | Telex number | TELX1 | CHAR | 30 | TEXT30 | ||||
| PFLD4 | WFMC: SAPscript form in 30-character field | NA_TDFORM | CHAR | 30 | CHAR30 | ||||
| PFLD5 | WFMC: Function module for print formatting | NA_LABEL | CHAR | 30 | TFDIR | FUNCNAME | |||
| TDNAME | Object key (long) | NA_OBJKY_L | CHAR | 70 | NA_OBJKY_L | ||||
| SNDDR | Send: As disregard | SO_SND_DR | CHAR | 1 | SO_FLAG | ||||
| SNDBC | Address type (1=Organization, 2=Person, 3=Contact person) | AD_ADRTYPE | CHAR | 1 | AD_ADRTYPE | ||||
| FORFB | Requested Status | BCS_RQST | CHAR | 1 | BCS_RQST | ||||
| PRIFB | Setting for Which Statuses Are Reported by Mail | BCS_STML | CHAR | 1 | BCS_STML | ||||
| TDRECEIVER | Spool Recipient Name | SYPRREC | CHAR | 12 | SYCHAR12 | ||||
| TDDIVISION | Spool Department Name | SYPRABT | CHAR | 12 | SYCHAR12K | ||||
| TDOCOVER | Print: SAP cover page | SYPRSAP | CHAR | 1 | SYPRSAP | ||||
| TDCOVTITLE | Spool Description | SYPRTXT | CHAR | 68 | SYCHAR68K | ||||
| TDAUTORITY | Print: Authorization | SYPRBER | CHAR | 12 | SYCHAR12 | SAU | |||
| TDARMOD | Print: Archiving mode | SYARMOD | CHAR | 1 | SYARMOD | ||||
| USRNAM | WFMC: Address number, 12 characters | NA_PERS_12 | CHAR | 12 | CHAR12 | ||||
| EVENT | Event | SWO_EVENT | CHAR | 32 | SWC_ELEM | ||||
| SORT1 | Sort criteria for message status records | NAST_SORTK | CHAR | 20 | CHAR20 | ||||
| SORT2 | Sort criteria for message status records | NAST_SORTK | CHAR | 20 | CHAR20 | ||||
| SORT3 | Sort criteria for message status records | NAST_SORTK | CHAR | 20 | CHAR20 | ||||
| OBJTYPE | Object type | OJ_NAME | CHAR | 10 | TOJTB | OJ_NAME | |||
| TDSCHEDULE | Send time request | SKSCHEDULE | CHAR | 3 | SKSCHEDULE | ||||
| TLAND | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND |
| Key field | Non-key field |
How do I retrieve data from SAP structure SNAST using ABAP code?
As SNAST 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 SNAST as there is no data to select.How to access SAP table SNAST
Within an ECC or HANA version of SAP you can also view further information about SNAST 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