VNFOR SAP (IS-H: Update structure for NFOR) Structure details
Description: IS-H: Update structure for NFOR
Structure field list including key, data, relationships and ABAP select examples
VNFOR 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 "IS-H: Update structure for NFOR" 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_VNFOR TYPE VNFOR.
The VNFOR table consists of various fields, each holding specific information or linking keys about IS-H: Update structure for NFOR data available in SAP. These include MANDT (Client), PATNR (IS-H: Patient Number), FALNR (IS-H: Case Number), LNRTMN (IS-H: Identification of Appointment).. 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 VNFOR 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 | |||
| PATNR | IS-H: Patient Number | PATNR | CHAR | 10 | Assigned to domain | ALPHA | PATNR | PAT | |
| FALNR | IS-H: Case Number | FALNR | CHAR | 10 | Assigned to domain | ALPHA | FALNR | FAL | |
| LNRTMN | IS-H: Identification of Appointment | ISH_TMNID | CHAR | 10 | ALPHA | ISH_LNRAPP | |||
| LFDNR | Sequence Number of Form Logging | LFDNR_NFOR | NUMC | 5 | LFDNR_NFOR | ||||
| EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| TOMID | IS-H: Work Organizer Key | TOMID | CHAR | 8 | Assigned to domain | ALPHA | N_ORGMID | ||
| LOMID | IS-H: Work Organizer Type Key | LOMID | CHAR | 8 | Assigned to domain | ALPHA | ISH_LOMID | ||
| FBFORM | IS-H: Customer Function Module for Logical Work Organizer | FBFORM_C | CHAR | 30 | Assigned to domain | FUNCNAME | |||
| TDFORM | IS-H: Form name of a SAPscript form | N_TDFORM | CHAR | 16 | TDFORM | ||||
| TDTEXT | IS-H: Description of a Form | ISH_TDTEXT | CHAR | 30 | TDTEXT | ||||
| TDDEST | Spool: Output device | RSPOPNAME | CHAR | 4 | Assigned to domain | SPDEV | RSPOPNAME | ||
| BEDINGUNG | IS-H: Condition for technical work organizer | ISH_BEDING | CHAR | 20 | TEXT20 | ||||
| OMTYP | Category of Work Organizer Type | ISH_OMTYP | CHAR | 1 | ISH_OMTYP | ||||
| FBPRINT | IS-H: User-Defined Print Function Module | ISH_FUBU | CHAR | 30 | CHAR30 | ||||
| PROTTYP | IS-H: Logging Type | N_PROTTYP | CHAR | 2 | N_PROTTYP | ||||
| UPDAT | IS-H: Date of Last Change | RI_UPDAT | DATS | 8 | RI_DATUM | ||||
| UPZT | IS-H: Time of Last Change | RI_UPTIM | TIMS | 6 | UHRZT | ||||
| UPUSR | IS-H: Name of Person who Last Changed Data | RI_UPNAM | CHAR | 12 | USNAM | ||||
| LOEKZ | Deletion Flag/Indicator | RI_LOEKZ | CHAR | 1 | XFELD | ||||
| SFFNAME | Smart Forms: Form Name | TDSFNAME | CHAR | 30 | STXFADM | TDSFNAME | SSFNAME | ||
| SFVARIA | Smart Forms: Variant | TDVARIANT | CHAR | 8 | STXFVAR | TDVARIANT | |||
| SMARTFACT | IS-H: Smart Forms Active | ISH_SMARTFORMS_ACTIVE | CHAR | 1 | XFELD | ||||
| AFNAME | Name of Form Object | ISH_FP_NAME | CHAR | 30 | Assigned to domain | ||||
| AFACT | PDF-Based Forms Active | ISH_FP_ACTIVE | CHAR | 1 | XFELD | ||||
| AFSFCOMP | IS-H: Boolean Data Type for ON (= 'X') and OFF (= ' ') | ISH_ON_OFF | CHAR | 1 | ISH_ON_OFF | ||||
| LFDBEW | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
| KZ | Change Type (U, I, S, D) | CDCHNGIND | CHAR | 1 | CDCHNGIND |
| Key field | Non-key field |
How do I retrieve data from SAP structure VNFOR using ABAP code?
As VNFOR 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 VNFOR as there is no data to select.How to access SAP table VNFOR
Within an ECC or HANA version of SAP you can also view further information about VNFOR 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