VNAST SAP (Output status (update structure)) Structure details
Description: Output status (update structure)
Structure field list including key, data, relationships and ABAP select examples
VNAST 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 "Output status (update structure)" 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_VNAST TYPE VNAST.
The VNAST table consists of various fields, each holding specific information or linking keys about Output status (update structure) data available in SAP. These include MANDT (Client), KAPPL (Application for message conditions), OBJKY (Object key), KSCHL (Message type).. 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 VNAST 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 | T000 | MANDT | |||
KAPPL | Application for message conditions | SNA_KAPPL | CHAR | 2 | CHAR2 | ||||
OBJKY | Object key | NA_OBJKEY | CHAR | 30 | NA_OBJKEY | ||||
KSCHL | Message type | SNA_KSCHL | CHAR | 4 | CHAR4 | ||||
SPRAS | Message language | NA_SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | ||
PARNR | Message partner | NA_PARNR | CHAR | 10 | ALPHA | NA_PARNR | |||
PARVW | Partner function (for example SH for ship-to party) | SNA_PARVW | CHAR | 2 | CHAR2 | ||||
ERDAT | Date on which status record was created | NA_ERDAT | DATS | 8 | DATUM | ||||
ERUHR | Time at which status record was created | NA_ERUHR | TIMS | 6 | UZEIT | ||||
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 | ||||
VSZTP | Dispatch time | NA_VSZTP | CHAR | 1 | NA_VSZTP | ||||
VSDAT | Requested date for sending message | NA_VSDAT | DATS | 8 | DATUM | ||||
VSURA | Requested time for sending message (from) | NA_VSURA | TIMS | 6 | UZEIT | ||||
VSURB | Requested time for sending message (to) | NA_VSURB | TIMS | 6 | UZEIT | ||||
MANUE | Message processed manually | NA_MANUE | CHAR | 1 | NA_MANUE | ||||
DATVR | Processing date | NA_DATVR | DATS | 8 | DATUM | ||||
UHRVR | Processing time | NA_UHRVR | TIMS | 6 | UZEIT | ||||
DATRE | Date of the expected response to a message | NA_DATRE | DATS | 8 | DATUM | ||||
USNAM | User name | USNAM | CHAR | 12 | Assigned to domain | XUBNAME | USR | ||
VSTAT | Processing status of message | NA_VSTAT | CHAR | 1 | NA_VSTAT | ||||
AKTIV | Active | NA_AKTIV | CHAR | 1 | CHAR1 | ||||
TCODE | Communication strategy | CSTRATEGY | CHAR | 4 | Assigned to domain | CSTRATEGY | |||
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 | ||||
TELTX | Teletex number | TELTX | CHAR | 30 | TEXT30 | ||||
AENDE | Change message flag | NA_AENDE | CHAR | 1 | NA_AENDE | ||||
REPET | Repeatability of message | NA_REPET | CHAR | 1 | NA_REPET | ||||
REPID | Unused field | NA_OBS008 | CHAR | 8 | CHAR8 | ||||
PFLD1 | Unused field | NA_OBS030 | CHAR | 30 | CHAR30 | ||||
PFLD2 | Unused field | NA_OBS030 | CHAR | 30 | CHAR30 | ||||
PFLD3 | Unused field | NA_OBS030 | CHAR | 30 | CHAR30 | ||||
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 | |||
PMID1 | Unused field | NA_OBS003 | CHAR | 3 | Assigned to domain | CHAR03 | |||
PMID2 | Unused field | NA_OBS003 | CHAR | 3 | Assigned to domain | CHAR03 | |||
PMID3 | Unused field | NA_OBS003 | CHAR | 3 | Assigned to domain | CHAR03 | |||
PMID4 | Unused field | NA_OBS003 | CHAR | 3 | Assigned to domain | CHAR03 | |||
PMID5 | Unused field | NA_OBS003 | CHAR | 3 | Assigned to domain | CHAR03 | |||
TDNAME | Object key (long) | NA_OBJKY_L | CHAR | 70 | NA_OBJKY_L | ||||
TDID | Text ID | TDID | CHAR | 4 | TTXID | TDID | |||
TDSPRAS | Language Key | SPRAS | LANG | 1 | T002 | ISOLA | SPRAS | SPR | H_T002 |
EDIKEY | Dunning Date (Used in Retail) | NA_DUNNING_DATE | CHAR | 8 | CHAR8 | ||||
EDITRANS | Dunning Time (Used in Retail) | NA_DUNNING_TIME | CHAR | 6 | CHAR6 | ||||
SNDDR | Send: As disregard | SO_SND_DR | CHAR | 1 | SO_FLAG | ||||
SNDEX | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
SNDCP | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
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 | ||||
ACALL | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OBJAC | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OBJRR | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OBJRN | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OUTFL | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OBJSNS | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OBJPRI | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
OBJCP | Unused field | NA_OBS001 | CHAR | 1 | CHAR1 | ||||
NAUTO | Message determined via conditions | NA_NAUTO | CHAR | 1 | XFELD | ||||
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 | ||||
OPTARCNR | Archive number for optical archives | NA_OPTAR | NUMC | 10 | NA_OPTAR | ||||
CMFPNR | Error management number | NA_CMF_NR | NUMC | 12 | NUMC12 | ||||
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 | ||
SELKZ | Selection indicator for list screens | SELKZ_LIST | CHAR | 1 | SELKZ | ||||
PNAME | Name 1 | NAME1_GP | CHAR | 35 | NAME | ||||
MSGNA | Output description | NA_MSGNA | CHAR | 30 | NA_MSGNA | ||||
UPDAT | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
NBEAR | Output cannot be changed manually | NA_NBEAR | CHAR | 1 | NA_NBEAR | ||||
DBASE | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 |
Key field | Non-key field |
How do I retrieve data from SAP structure VNAST using ABAP code?
As VNAST 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 VNAST as there is no data to select.How to access SAP table VNAST
Within an ECC or HANA version of SAP you can also view further information about VNAST 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