RN2N0BERI SAP (IS-H*MED: Structure for transfering data from surg. report) Structure details
Description: IS-H*MED: Structure for transfering data from surg. report
Structure field list including key, data, relationships and ABAP select examples
RN2N0BERI 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*MED: Structure for transfering data from surg. report" 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_RN2N0BERI TYPE RN2N0BERI.
The RN2N0BERI table consists of various fields, each holding specific information or linking keys about IS-H*MED: Structure for transfering data from surg. report data available in SAP. These include MANDT (Client), DOKAR (Document Type), DOKNR (Document number), DOKVR (Document Version).. 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 RN2N0BERI 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 | MANDT | ||||
DOKAR | Document Type | DOKAR | CHAR | 3 | DOKAR | CV2 | |||
DOKNR | Document number | DOKNR | CHAR | 25 | ALPHA | DOKNR | CV1 | ||
DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
DWNAM | Name of person responsible | DWNAM | CHAR | 12 | DWNAM | ||||
DOKST | Document Status | DOKST | CHAR | 2 | DOKST | ||||
LABOR | Laboratory/design office | LABOR | CHAR | 3 | LABOR | ||||
AENNR | Change Number | DAENR | CHAR | 12 | AENNR | AENNR | |||
WERKA | Plant | WERKA | CHAR | 4 | WERKS | ||||
LOEDK | Deletion indicator | LOEDK | CHAR | 1 | XFELD | ||||
CADKZ | CAD Indicator | CADKZ | CHAR | 1 | XFELD | ||||
PRENR | Document number of superior document | PRENR | CHAR | 25 | ALPHA | DOKNR | |||
PREVR | Document version of superior document | PREVR | CHAR | 2 | DOKVR | ||||
PRETL | Document Part of Superior Document | PRETL | CHAR | 3 | DOKTL | ||||
PREAR | Document type of the superior document | PREAR | CHAR | 3 | DOKAR | ||||
BEGRU | Authorization Group | BEGRU | CHAR | 4 | BEGRU | ||||
FILEP | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
DTTRG | Name of Data Carrier | DTTRG | CHAR | 10 | DTTRG | CV5 | |||
DAPPL | Application | DAPPL | CHAR | 3 | DAPPL | ||||
FILEP1 | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
DTTRG1 | Name of Data Carrier | DTTRG | CHAR | 10 | DTTRG | CV5 | |||
DAPPL1 | Application | DAPPL | CHAR | 3 | DAPPL | ||||
VRLDAT | Due Date | VRLDAT | DATS | 8 | DATUM | ||||
VPRIOR | Processing priority | VPRIOR | NUMC | 1 | NUMC01 | ||||
RES1 | Reserve field DRAW | RESDRAW | CHAR | 14 | CHAR14 | ||||
RES2 | Reserve field DRAW | RESDRAW | CHAR | 14 | CHAR14 | ||||
RES3 | Reserve field DRAW | RESDRAW | CHAR | 14 | CHAR14 | ||||
RES4 | Reserve field DRAW | RESDRAW | CHAR | 14 | CHAR14 | ||||
MRK_FILEP | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
MRK_DTTRG | Name of Data Carrier | DTTRG | CHAR | 10 | DTTRG | CV5 | |||
MRK_FILEP1 | Original of document | FILEP | CHAR | 255 | TEXT255 | ||||
MRK_DTTRG1 | Name of Data Carrier | DTTRG | CHAR | 10 | DTTRG | CV5 | |||
ADATUM | Output date for document | ADATUM | DATS | 8 | DATUM | ||||
DOKNR_VL | Document Number of Source Document | DOKNR_VL | CHAR | 25 | ALPHA | DOKNR | |||
DOKTL_VL | Document part of source document | DOKTL_VL | CHAR | 3 | DOKTL | ||||
DOKVR_VL | Document version of source document | DOKVR_VL | CHAR | 2 | DOKVR | ||||
FILELEN | File length of original | ORLN | NUMC | 12 | NUM12 | ||||
FILELEN1 | File length of original | ORLN | NUMC | 12 | NUM12 | ||||
CM_RELEVANCE | Relevant for Configuration Management | DE_CM_RELEVANCE_FLAG | CHAR | 1 | DO_CM_RELEVANCE_FLAG | ||||
CM_FIXED | Document fixed | DMS_CM_FIXED | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure RN2N0BERI using ABAP code?
As RN2N0BERI 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 RN2N0BERI as there is no data to select.How to access SAP table RN2N0BERI
Within an ECC or HANA version of SAP you can also view further information about RN2N0BERI 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