RNPLR_REL SAP (Patient - Legal Representative Relationship Data) Structure details
Description: Patient - Legal Representative Relationship Data
Structure field list including key, data, relationships and ABAP select examples
RNPLR_REL 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 "Patient - Legal Representative Relationship 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_RNPLR_REL TYPE RNPLR_REL.
The RNPLR_REL table consists of various fields, each holding specific information or linking keys about Patient - Legal Representative Relationship Data data available in SAP. These include CLIENT (Client), RELNR (BP Relationship Number), PARTNER1 (Business Partner Number), PARTNER2 (Business Partner 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 RNPLR_REL 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 |
CLIENT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
RELNR | BP Relationship Number | BU_RELNR | CHAR | 12 | Assigned to domain | ALPHA | BU_RELNR | ||
PARTNER1 | Business Partner Number | BU_PARTNER | CHAR | 10 | BUT000 | ALPHA | BU_PARTNER | BPA | BUPA |
PARTNER2 | Business Partner Number | BU_PARTNER | CHAR | 10 | BUT000 | ALPHA | BU_PARTNER | BPA | BUPA |
DATE_TO | Validity Date (Valid To) | BU_DATTO | DATS | 8 | DATUM | ||||
DATE_FROM | Validity Date (Valid From) | BU_DATFROM | DATS | 8 | DATUM | ||||
RELTYP | Business Partner Relationship Category | BU_RELTYP | CHAR | 6 | Assigned to domain | BU_RELTYP | |||
XRF | Business partner role definition instead of BP relationship | BU_XRF | CHAR | 1 | XFELD | ||||
DFTVAL | BP: Differentiation type characteristic (change doc.-rel.) | BU_DFTVAL | CHAR | 20 | CHAR20 | ||||
RLTYP | Business partner role (change doc.-relevant) | BU_RLTYPE | CHAR | 6 | Assigned to domain | BU_ROLE | |||
RELKIND | Business partner relationship type | BU_RELKIND | CHAR | 4 | Assigned to domain | BU_RELKIND | |||
CRUSR | User who created the object | BU_CRUSR | CHAR | 12 | USNAM | ||||
CRDAT | Date on which the object was created | BU_CRDAT | DATS | 8 | DATUM | ||||
CRTIM | Time at which the object was created | BU_CRTIM | TIMS | 6 | UZEIT | ||||
CHUSR | Last user to change object | BU_CHUSR | CHAR | 12 | USNAM | ||||
CHDAT | Date when object was last changed | BU_CHDAT | DATS | 8 | DATUM | ||||
CHTIM | Time at which object was last changed | BU_CHTIM | TIMS | 6 | UZEIT | ||||
XDFREL | Standard Relationship | BU_XDFREL | CHAR | 1 | XFELD | ||||
XDFREL2 | Standard Relationship | BU_XDFREL | CHAR | 1 | XFELD | ||||
DB_KEY | GP: UUID for Identifying the Data Record (SETGUID) | BUP_SETGUID | RAW | 16 | SYSUUID | ||||
DB_KEY_TD | GP: UUID for Identifying the Data Record (SETGUID) | BUP_SETGUID | RAW | 16 | SYSUUID | ||||
XATTR | Indicator: Detail data can be maintained | BU_XCAN | CHAR | 1 | XFELD | ||||
XMUST | Indicator: Detail data must be maintained | BU_XMUST | CHAR | 1 | XFELD | ||||
XDONE | Indicator: Detail data maintained | BU_XDONE | CHAR | 1 | XFELD | ||||
XDIRECTION | One-Way Business Partner Relationship Category | BU_XDIRECT | CHAR | 1 | XFELD | ||||
XENQ_R | Indic.: Object blocked | BU_XENQ | CHAR | 1 | XFELD | ||||
XENQ_P | Indic.: Object blocked | BU_XENQ | CHAR | 1 | XFELD | ||||
XCHNG | Indicator: Data has been changed | BU_XCHNG | CHAR | 1 | XFELD | ||||
XFMOD | Single-Character Indicator | CHAR1 | CHAR | 1 | CHAR1 | ||||
RELSHIP_CHIND | Change category | BU_CHIND | CHAR | 1 | BU_CHIND | ||||
FROM_DATE | Validity Date (Valid From) | BU_DATFROM | DATS | 8 | DATUM | ||||
KIND_PROC | Power of Attorney Type | ISH_KIND_PROC | CHAR | 2 | TNKOP | ISH_KIND_PROC | |||
RANGE_PROC | Scope of Power of Attorney | ISH_RANGE_PROC | CHAR | 2 | TNROP | ISH_RANGE_PROC | |||
DESC_PROC | Description of Power of Attorney | ISH_DESC_PROC | CHAR | 50 | TEXT50 | ||||
DESC_PROC_L | Indicator that Long Text Exists | RI_LGTXT | CHAR | 1 | XFELD | ||||
DESC_PROC_LNUM | Sequence number | LFDNR5 | NUMC | 5 | NUMC5 |
Key field | Non-key field |
How do I retrieve data from SAP structure RNPLR_REL using ABAP code?
As RNPLR_REL 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 RNPLR_REL as there is no data to select.How to access SAP table RNPLR_REL
Within an ECC or HANA version of SAP you can also view further information about RNPLR_REL 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