RNPP3 SAP (IS-H: Log Payment Distribution Service Level) Structure details
Description: IS-H: Log Payment Distribution Service Level
Structure field list including key, data, relationships and ABAP select examples
RNPP3 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: Log Payment Distribution Service Level" 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_RNPP3 TYPE RNPP3.
The RNPP3 table consists of various fields, each holding specific information or linking keys about IS-H: Log Payment Distribution Service Level data available in SAP. These include FALNR (IS-H: Case Number), LFDNR (Sequence Number), RANGF (IS-H: Ranking Order of Case-Rel. Insurance Relationships), VTRTY (IS-H: Insurance Contract Scheme).. 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 RNPP3 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 | |
| FALNR | IS-H: Case Number | FALNR | CHAR | 10 | Assigned to domain | ALPHA | FALNR | FAL | |
| LFDNR | Sequence Number | LFDNR | CHAR | 3 | LFDNR | ||||
| RANGF | IS-H: Ranking Order of Case-Rel. Insurance Relationships | ISH_RANGF | NUMC | 2 | RANGF | ISH_RANGF | |||
| VTRTY | IS-H: Insurance Contract Scheme | ISH_VTRTY | CHAR | 6 | Assigned to domain | ALPHA | ISH_VTRTY | ||
| POSNO | IS-H: Item Number | ISH_POSNO | NUMC | 4 | NUMC4 | ||||
| LNRLS | IS-H: Service Sequence Number | LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
| SPLIT | Combination Criteria Billing Items | ISH_SPLIT | NUMC | 3 | NUMC3 | ||||
| ABTAR | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | Assigned to domain | ALPHA | TARID | TAK | |
| ABLST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
| ZEITR | IS-H: Indicator for Extended Service | NZEITRLS | CHAR | 1 | NZEITRLS | ||||
| BEGDT | IS-H: Date when Service Performance Starts (Actual) | I_BDT_LS | DATS | 8 | RI_DATUM | ||||
| ENDDT | IS-H: Date when Service Performance Ends (Actual) | I_EDT_LS | DATS | 8 | RI_DATUM | ||||
| MENGE | Service Quantity | I_MENG_LS | NUMC | 4 | LEISMENGE | ||||
| NETWR | IS-H: Net Value of Billing Item in Document Currency | ISH_NETWR | CURR | 11(2) | ISH_WERTV6 | ||||
| BRUWR | IS-H: Gross Value of Billing Item in Document Currency | ISH_BRUWR | CURR | 11(2) | ISH_WERTV6 | ||||
| KTRWR | Insurance Provider-Dependent Price Component of Billing Item | ISH_KTRWR | CURR | 11(2) | ISH_WERTV6 | ||||
| COVER | IS-H: Amount allocated in 'case currency' | ISH_COVER | CURR | 11(2) | ISH_WERTV6 | ||||
| COVAM | IS-H: Allocated amount in target currency | ISH_COVAM | CURR | 11(2) | ISH_WERTV6 | ||||
| WAERS | Currency Key | WAERS | CUKY | 5 | Assigned to domain | WAERS | FWS | ||
| MSGID | Message Class | SYMSGID | CHAR | 20 | Assigned to domain | ARBGB | |||
| MSGTY | Message Type | SYMSGTY | CHAR | 1 | SYCHAR01 | ||||
| MSGNO | Message Number | SYMSGNO | NUMC | 3 | SYMSGNO | ||||
| MSGV1 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV2 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV3 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 | ||||
| MSGV4 | Message Variable | SYMSGV | CHAR | 50 | SYCHAR50 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNPP3 using ABAP code?
As RNPP3 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 RNPP3 as there is no data to select.How to access SAP table RNPP3
Within an ECC or HANA version of SAP you can also view further information about RNPP3 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