RNINSI SAP (IS-H: Institution-Dependent Ins. Provider Data - Change Str.) Structure details
Description: IS-H: Institution-Dependent Ins. Provider Data - Change Str.
Structure field list including key, data, relationships and ABAP select examples
RNINSI 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: Institution-Dependent Ins. Provider Data - Change Str." 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_RNINSI TYPE RNINSI.
The RNINSI table consists of various fields, each holding specific information or linking keys about IS-H: Institution-Dependent Ins. Provider Data - Change Str. data available in SAP. These include ACTION (IS-H: Action Type), GPART (IS-H: Business Partner), EINRI (Institution), COPAY_PROC (IS-H: Copayment Procedure for Billing).. 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 RNINSI 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 | Assigned to domain | MANDT | |||
ACTION | IS-H: Action Type | ISH_AKTTYP | CHAR | 1 | ISH_AKTTYP | ||||
GPART | IS-H: Business Partner | GPARTNER | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | NGP | |
EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
COPAY_PROC | IS-H: Copayment Procedure for Billing | VERFZUZ | CHAR | 1 | VERFZUZ | ||||
COPAY_PROC_X | IS-H: Assigned Field Content Relevant for CHANGE-API (BAPI) | ISH_RELEVANT | CHAR | 1 | XFELD | ||||
ERUSR | IS-H: Name of Employee who Created Record | RI_ERNAM | CHAR | 12 | USNAM | ||||
ERDAT | IS-H: Date when Record Created | RI_ERDAT | DATS | 8 | RI_DATUM | ||||
ERTIM | IS-H: Time Record Created | RI_ERTIM | TIMS | 6 | UHRZT | ||||
UPUSR | IS-H: Name of Person who Last Changed Data | RI_UPNAM | CHAR | 12 | USNAM | ||||
UPDAT | IS-H: Date of Last Change | RI_UPDAT | DATS | 8 | RI_DATUM | ||||
UPTIM | IS-H: Time of Last Change | RI_UPTIM | TIMS | 6 | UHRZT |
Key field | Non-key field |
How do I retrieve data from SAP structure RNINSI using ABAP code?
As RNINSI 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 RNINSI as there is no data to select.How to access SAP table RNINSI
Within an ECC or HANA version of SAP you can also view further information about RNINSI 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