RNPP4 SAP (IS-H: User Exits, Services for Case) Structure details
Description: IS-H: User Exits, Services for Case
Structure field list including key, data, relationships and ABAP select examples
RNPP4 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: User Exits, Services for Case" 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_RNPP4 TYPE RNPP4.
The RNPP4 table consists of various fields, each holding specific information or linking keys about IS-H: User Exits, Services for Case data available in SAP. These include FALNR (IS-H: Case Number), LFDNR (IS-H: Sequence Number of Insurance Relationship), KOSTR (IS-H: Insurance Provider), LNRLS (IS-H: Service Sequence Number).. 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 RNPP4 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 | IS-H: Sequence Number of Insurance Relationship | LFDVV | NUMC | 3 | LFDVV | ||||
KOSTR | IS-H: Insurance Provider | KH_KOSTR | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | KOT | |
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 | |
LFDBEW | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
ZEITR | IS-H: Indicator for Extended Service | NZEITRLS | CHAR | 1 | NZEITRLS | ||||
DAYNO | IS-H: Sequential number of day | ISH_DAYNO | NUMC | 4 | NUMC4 | ||||
MENGE | Service Quantity | I_MENG_LS | NUMC | 4 | LEISMENGE | ||||
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 | ||||
BWART | IS-H: Movement Type for Determining the Billing Type | SPF_BWART | CHAR | 2 | Assigned to domain | RI_BWART | |||
EXCAT | IS-H: External Charge Type | ISH_EXCAT | CHAR | 6 | ISH_EXCAT | ||||
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 |
Key field | Non-key field |
How do I retrieve data from SAP structure RNPP4 using ABAP code?
As RNPP4 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 RNPP4 as there is no data to select.How to access SAP table RNPP4
Within an ECC or HANA version of SAP you can also view further information about RNPP4 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