RNNL1 SAP (IS-H NL: Structure for activity context data) Structure details
Description: IS-H NL: Structure for activity context data
Structure field list including key, data, relationships and ABAP select examples
RNNL1 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 NL: Structure for activity context data" 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_RNNL1 TYPE RNNL1.
The RNNL1 table consists of various fields, each holding specific information or linking keys about IS-H NL: Structure for activity context data data available in SAP. These include LEIST (Service in Service Catalog), LEVON (Date when Service Performance Starts), LEBIS (IS-H: Date when Service Performance Ends), MENGE (Service Quantity).. 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 RNNL1 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 |
| EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| LEIST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
| LEVON | Date when Service Performance Starts | BEGDTLEI | DATS | 8 | RI_DATUM | ||||
| LEBIS | IS-H: Date when Service Performance Ends | ENDDTLEI | DATS | 8 | RI_DATUM | ||||
| MENGE | Service Quantity | I_MENG_LS | NUMC | 4 | LEISMENGE | ||||
| LEITX | IS-H: Service Short Text (May Differ from Service Master) | TEXT_LEI | CHAR | 40 | LEIKTXT | ||||
| SESNR | _ | ISH_SESNR | CHAR | 10 | ALPHA | ISH_SESNR | |||
| WNDNR | IS-H: Wound Number | ISH_WNDNR | CHAR | 10 | ALPHA | ISH_WNDNR | |||
| ASSTP | _ | ISH_ASSTP | CHAR | 2 | ALPHA | ISH_ASSTP | |||
| KZEAH | _ | ISH_KZEAH | CHAR | 1 | ALPHA | ISH_KZEAH | |||
| KZPRF | _ | ISH_KZPRF | CHAR | 1 | ALPHA | ISH_KZPRF | |||
| REMRK | IS-H: User's Comment on Service | ISH_REMRK | CHAR | 40 | ISH_REMRK |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNNL1 using ABAP code?
As RNNL1 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 RNNL1 as there is no data to select.How to access SAP table RNNL1
Within an ECC or HANA version of SAP you can also view further information about RNNL1 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