RNDAE SAP (IS-H: Structure for updating NDAE records) Structure details
Description: IS-H: Structure for updating NDAE records
Structure field list including key, data, relationships and ABAP select examples
RNDAE 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: Structure for updating NDAE records" 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_RNDAE TYPE RNDAE.
The RNDAE table consists of various fields, each holding specific information or linking keys about IS-H: Structure for updating NDAE records 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 RNDAE 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 | |||
| DOKAR | Document Type | DOKAR | CHAR | 3 | TDWA | DOKAR | CV2 | ||
| DOKNR | Document number | DOKNR | CHAR | 25 | DRAW | ALPHA | DOKNR | CV1 | |
| DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
| DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
| ENTLEIHER | Borrower for Document Management | ENTLEIHNR | CHAR | 10 | ALPHA | ENTLNR | |||
| ENTLTYP | Borrower Category | ENTLEIHTYP | CHAR | 2 | TND03 | ALPHA | ENTLEIHTYP | ||
| LEIHDAT | IS-H: Date at which a Medical Record Is Borrowed/Requested | ISH_LEIDAT | DATS | 8 | RI_DATUM | ||||
| LEIZEIT | IS-H: Borrowing time | ISH_LEIZEI | TIMS | 6 | UHRZT | ||||
| ORGKR | Organizational Group for Borrowing Authorizations | ORGKREIS | CHAR | 4 | ALPHA | ORG_KR | |||
| ENTZW | IS-H: Reason for Borrowing Medical Record/Document | ISH_ENTLZW | CHAR | 2 | TND01 | ALPHA | ISH_ENTLZW | ||
| RUEKDAT | IS-H: Date Medical Record Returned | ISH_RUEKDT | DATS | 8 | RI_DATUM | ||||
| STATUS | IS-H: Borrowing Status | ISH_LEISTA | CHAR | 1 | ISH_LEISTA | ||||
| ANZMAH | IS-H: Number of Reminders for Medical Records | ISH_ANZMAH | INT2 | 5 | INT2 | ||||
| ERMAHN | IS-H: Date of 1st Reminder for Medical Record | ISH_AKM1DT | DATS | 8 | RI_DATUM | ||||
| LEMAHN | IS-H: Date of Last Reminder | ISH_AKM2DT | DATS | 8 | RI_DATUM | ||||
| ENTTEXT | IS-H: Comment on Borrowing Episode | TEXTENT | CHAR | 50 | TEXT50 | ||||
| LGTXT | IS-H: Indicator that Borrowing Long Text Exists | ENTLGTXT | CHAR | 1 | XFELD | ||||
| ERDAT | IS-H: Date when Record Created | RI_ERDAT | DATS | 8 | RI_DATUM | ||||
| ERUSR | IS-H: Name of Employee who Created Record | RI_ERNAM | CHAR | 12 | USNAM | ||||
| UPDAT | IS-H: Date of Last Change | RI_UPDAT | DATS | 8 | RI_DATUM | ||||
| UPUSR | IS-H: Name of Person who Last Changed Data | RI_UPNAM | CHAR | 12 | USNAM | ||||
| ENTLEND | IS-H: Scheduled Borrowed-To Date | ISH_ENTLEN | DATS | 8 | RI_DATUM | ||||
| VERANTW | IS-H: Person Responsible for Medical Records/Documents | VERANTWORT | CHAR | 10 | ALPHA | ENTLNR | |||
| ERTIM | IS-H: Time Record Created | RI_ERTIM | TIMS | 6 | UHRZT | ||||
| FILEMR | IS-H: Medical Record Has still to Be Stored | ISH_FILE_MR | CHAR | 1 | XFELD | ||||
| UPDKZ | Update indicator | UPDKZ_D | CHAR | 1 | UPDKZ |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNDAE using ABAP code?
As RNDAE 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 RNDAE as there is no data to select.How to access SAP table RNDAE
Within an ECC or HANA version of SAP you can also view further information about RNDAE 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