SN1TER SAP (Appointments) Structure details
Description: Appointments
Structure field list including key, data, relationships and ABAP select examples
SN1TER 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 "Appointments" 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_SN1TER TYPE SN1TER.
The SN1TER table consists of various fields, each holding specific information or linking keys about Appointments data available in SAP. These include TRZ01 (Separator), STATE (Appointment status), TRZ02 (Separator), TERDT (Date of Appointment (Scheduled, Desired Date)).. 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 (character-type)
SAP SN1TER 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 |
ID | Planning Object Identification, Appointment | N1ID | NUMC | 3 | N1ID | ||||
TRZ01 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
STATE | Appointment status | N1STATE | CHAR | 2 | N1STATE | ||||
TRZ02 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
TERDT | Date of Appointment (Scheduled, Desired Date) | N1TERDT | CHAR | 10 | N1TERDT | ||||
TRZ03 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
TERZT | Appointment Time | N1TERZT | CHAR | 5 | N1TERZT | ||||
TRZ04 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
PLDTE | Planned duration of appointment (minutes) | N1PLDTE | NUMC | 3 | N1PLDTE | ||||
TRZ05 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
NFDKZ | Duration can be changed | N1NFDKZ | CHAR | 1 | XFELD | ||||
TRZ06 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
LSTTX | Service Text | N1LSTTX | CHAR | 80 | N1LSTTX | ||||
TRZ07 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
LNRLS | IS-H: Service Sequence Number | LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
TRZ08 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
ANZKZ | Service displayed in appointment field | N1ANZKZ | CHAR | 1 | XFELD | ||||
TRZ09 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
PATNA | Patient name | N1PATNA | CHAR | 80 | N1INFO | ||||
TRZ10 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO1 | Information (user-defined text) | N1INFO | CHAR | 80 | N1INFO | ||||
TRZ11 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO1ID | Object ID which is displayed in the Infotext field | N1INFOID | CHAR | 10 | N1INFOID | ||||
TRZ12 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO1AN | User-defined text info displayed | N1INFOAN | CHAR | 1 | XFELD | ||||
TRZ13 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO2 | Information (user-defined text) | N1INFO | CHAR | 80 | N1INFO | ||||
TRZ14 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO2ID | Object ID which is displayed in the Infotext field | N1INFOID | CHAR | 10 | N1INFOID | ||||
TRZ15 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO2AN | User-defined text info displayed | N1INFOAN | CHAR | 1 | XFELD | ||||
TRZ16 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO3 | Information (user-defined text) | N1INFO | CHAR | 80 | N1INFO | ||||
TRZ17 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO3ID | Object ID which is displayed in the Infotext field | N1INFOID | CHAR | 10 | N1INFOID | ||||
TRZ18 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO3AN | User-defined text info displayed | N1INFOAN | CHAR | 1 | XFELD | ||||
TRZ19 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO4 | Information (user-defined text) | N1INFO | CHAR | 80 | N1INFO | ||||
TRZ20 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO4ID | Object ID which is displayed in the Infotext field | N1INFOID | CHAR | 10 | N1INFOID | ||||
TRZ21 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
INFO4AN | User-defined text info displayed | N1INFOAN | CHAR | 1 | XFELD | ||||
TRZ22 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
UEBLK | Overlap indicator | N1UEBLK | CHAR | 1 | XFELD | ||||
TRZ23 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
DBAKT | Action After Accepting Appointment | N1DBAKT | CHAR | 2 | N1DBAKT | ||||
TRZ24 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
KONSK | Passed consistency check | N1KONSK | CHAR | 1 | N1KONSK | ||||
TRZ25 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
FIXZK | Fixed Time Indicator | N1FIXZK | CHAR | 1 | N1FIXZK | ||||
TRZ26 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
FARBE | Color | N1FARBE | CHAR | 1 | N1FARBE | ||||
TRZ27 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
PATMANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
TRZ28 | Separator | N1TRENZ | CHAR | 1 | N1TRENZ | ||||
PATNR | IS-H: Patient Number | PATNR | CHAR | 10 | Assigned to domain | ALPHA | PATNR | PAT |
Key field | Non-key field |
How do I retrieve data from SAP structure SN1TER using ABAP code?
As SN1TER 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 SN1TER as there is no data to select.How to access SAP table SN1TER
Within an ECC or HANA version of SAP you can also view further information about SN1TER 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