RNPNT_VNDOC SAP (Fields Related to View N_VNDOC (SAP BP point of view)) Structure details
Dictionary Type: Structure
Description: Fields Related to View N_VNDOC (SAP BP point of view)
Description: Fields Related to View N_VNDOC (SAP BP point of view)
Structure field list including key, data, relationships and ABAP select examples
RNPNT_VNDOC 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 "Fields Related to View N_VNDOC (SAP BP point of view)" 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_RNPNT_VNDOC TYPE RNPNT_VNDOC.
The RNPNT_VNDOC table consists of various fields, each holding specific information or linking keys about Fields Related to View N_VNDOC (SAP BP point of view) data available in SAP. These include DOKAR (Document Type), DOKNR (Document number), DOKVR (Document Version), DOKTL (Document Part).. 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 or numeric)
SAP RNPNT_VNDOC 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 | |||
| DOKAR | Document Type | DOKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
| DOKNR | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
| DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
| DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
| LFDDOK | Sequence Number of Document | LFDDOK | INT4 | 10 | INT4_NOS | ||||
| ORGFORM | IS-H: Organization Form for Medical Record Management | ORGFORM | CHAR | 1 | ORGFORM | ||||
| EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| 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 | |
| FALAR | IS-H: Case Type | FALLART | CHAR | 1 | FALLART | ||||
| ORGFA | IS-H: OU with Departmental Responsibility for Case | NZUWFA | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ORGPF | Organizational Unit Assigned to Case | NZUWPF | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ORGDO | Documenting Organizational Unit | ORGDO | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OED | |
| LFDBEW | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
| STORN | IS-H: Cancellation Indicator | RI_STORN | CHAR | 1 | XFELD | ||||
| MEDOK | Indicator for a Medical Document | MEDOK | CHAR | 1 | XFELD | ||||
| ARCHIV | IS-H: Organizational ID of the medical record archive | ARCHIV_ID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| STANDORT | IS-H: Building ID of building unit in the 'archive' OU | ISH_ARCHST | CHAR | 8 | Assigned to domain | ALPHA | BAUID | ||
| ROLLNO | IS-H: Roll Number of a Micro Film | ISH_ROLLNO | CHAR | 10 | CHAR10 | ||||
| MICROF | IS-H: Patient's medical record is microfilmed | ISH_MICROF | CHAR | 1 | XFELD | ||||
| EXTNR | IS-H: External Medical Record/Document ID | ISH_DOCEXT | CHAR | 15 | CHAR15 | ||||
| INFOMR | IS-H: Informational Text for Medical Record | ISH_INFOMR | CHAR | 50 | TEXT50 | ||||
| TEMPMR | IS-H: Flags a Medical Record as Temporary Medical Record | ISH_TEMPMR | CHAR | 1 | XFELD | ||||
| ALBUM | IS-H: Album Id for microfilm | ISH_ALBUM | CHAR | 10 | CHAR10 | ||||
| MFYEAR | IS-H: Year Until when Data Archived on Microfilm | ISH_MFYEAR | NUMC | 4 | NUMC4 | ||||
| REDO_KZ | Indicator for Renewable Document Management | ISH_REDO_KZ | CHAR | 1 | XFELD | ||||
| XSEXM | Selection: Business partner is male | BU_XSEXM | CHAR | 1 | XFELD | ||||
| XSEXF | Selection: Business partner is female | BU_XSEXF | CHAR | 1 | XFELD | ||||
| XSEXU | Selection: Sex of business partner is not known | BU_XSEXU | CHAR | 1 | XFELD | ||||
| NAME_LAST | Last name of business partner (person) | BU_NAMEP_L | CHAR | 40 | BU_NAME | ||||
| STD_LN | IS-H: Standardized Last Name | NNAMES_PAT | CHAR | 30 | CHAR30 | ||||
| NAME_FIRST | First name of business partner (person) | BU_NAMEP_F | CHAR | 40 | BU_NAME | ||||
| STD_FN | Standardized First Name | VNAMES_PAT | CHAR | 30 | CHAR30 | ||||
| BIRTHDT | Date of Birth of Business Partner | BU_BIRTHDT | DATS | 8 | DATUM | ||||
| PNT_CD | Check Digit for Patient | PZIFF_PAT | CHAR | 1 | PZIFF | PZP | |||
| TITLE_ACA1 | Academic Title: Key | AD_TITLE1 | CHAR | 4 | Assigned to domain | AD_TITLE1 | AD_TITLE1 | ||
| PREFIX1 | Name Prefix (Key) | AD_PREFIX | CHAR | 4 | Assigned to domain | AD_PREFIX | |||
| PREFIX2 | 2nd name prefix (key) | AD_PREFIX2 | CHAR | 4 | Assigned to domain | AD_PREFIX | |||
| PNT_EXTNR | IS-H: External Patient Identification | EXT_PATNR | CHAR | 20 | EXT_PATNR | ||||
| TITLE_ROYL | Name supplement, e.g. noble title (key) | AD_TITLES | CHAR | 4 | Assigned to domain | AD_TITLES |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNPNT_VNDOC using ABAP code?
As RNPNT_VNDOC 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 RNPNT_VNDOC as there is no data to select.How to access SAP table RNPNT_VNDOC
Within an ECC or HANA version of SAP you can also view further information about RNPNT_VNDOC 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