RNLPA SAP (IS-H: Structure for Service Requirement Pairs) Structure details
Description: IS-H: Structure for Service Requirement Pairs
Structure field list including key, data, relationships and ABAP select examples
RNLPA 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 Service Requirement Pairs" 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_RNLPA TYPE RNLPA.
The RNLPA table consists of various fields, each holding specific information or linking keys about IS-H: Structure for Service Requirement Pairs data available in SAP. These include MANDT (Client), EINRI (Institution), RGART (IS-H: Rule Type), TAR_1 (IS-H: Service Catalog Identification Key).. 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 RNLPA 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 | |||
| EINRI | Institution | EINRI | CHAR | 4 | TN01 | ALPHA | EINRI | EIN | |
| RGART | IS-H: Rule Type | ISH_RGART | CHAR | 10 | TNT3 | ALPHA | ISH_RGART | ||
| TAR_1 | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | TNK01 | ALPHA | TARID | TAK | |
| LST_1 | Service in Service Catalog | TARLS | CHAR | 10 | NTPK | ALPHA | TARLS | TAL | |
| TAR_2 | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | TNK01 | ALPHA | TARID | TAK | |
| LST_2 | Service in Service Catalog | TARLS | CHAR | 10 | NTPK | ALPHA | TARLS | TAL | |
| ENDDT | IS-H: Valid-To Date of Record | RI_ENDDT | DATS | 8 | RI_DATUM | ||||
| INCLD | IS-H: Service Inclusion Indicator | INCLD | CHAR | 1 | INCLD | ||||
| MSGTY | Message type (E, I, W, ...) | MSGTY_CO | CHAR | 1 | MSGTY_CO | ||||
| DATUM | IS-H: Check Date for Service Rules | ISH_PA_DAT | CHAR | 1 | XFELD | ||||
| MENGE | IS-H: Check Quantity for Service Pair Rules | ISH_PA_MNG | CHAR | 1 | XFELD | ||||
| UNIDI | IS-H: Check Service Inclusion in one Direction Only | ISH_PA_UNI | CHAR | 1 | XFELD | ||||
| BEGDT | IS-H: Valid-From Date of Record | RI_BEGDT | DATS | 8 | RI_DATUM | ||||
| REVRS | IS-H: Boolean Data Type for ON (= 'X') and OFF (= ' ') | ISH_ON_OFF | CHAR | 1 | ISH_ON_OFF |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNLPA using ABAP code?
As RNLPA 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 RNLPA as there is no data to select.How to access SAP table RNLPA
Within an ECC or HANA version of SAP you can also view further information about RNLPA 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