RNEXL SAP (IS-H: Structure exporting variables for service entry) Structure details
Description: IS-H: Structure exporting variables for service entry
Structure field list including key, data, relationships and ABAP select examples
RNEXL 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 exporting variables for service entry" 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_RNEXL TYPE RNEXL.
The RNEXL table consists of various fields, each holding specific information or linking keys about IS-H: Structure exporting variables for service entry data available in SAP. These include AUFSW (IS-H: Date of First Contact), AUFZT (IS-H: Time of Movement), ABRKZ (IS-H: Billing Indicator for Case), BUKRS (Company Code).. 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 RNEXL 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 |
| AUFDT | IS-H: Date of First Contact | ISH_AUFDT | DATS | 8 | RI_DATUM | ||||
| AUFSW | IS-H: Date of First Contact | AUFSW | CHAR | 40 | TEXT40 | ||||
| AUFZT | IS-H: Time of Movement | BWIZT | TIMS | 6 | UHRZT | ||||
| ABRKZ | IS-H: Billing Indicator for Case | ABRKZ_FALL | CHAR | 1 | ABRKZ_FALL | ||||
| BUKRS | Company Code | BUKRS | CHAR | 4 | Assigned to domain | BUKRS | BUK | C_T001 | |
| BWART | IS-H: Movement Type | RI_BWART | CHAR | 2 | Assigned to domain | RI_BWART | |||
| EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| ENTDT | Date of Last Contact | ENTDT | DATS | 8 | RI_DATUM | ||||
| ENTSW | IS-H: Date of Last Contact | ENTSW | CHAR | 40 | TEXT40 | ||||
| ENTZT | IS-H: Time of Movement | BWIZT | TIMS | 6 | UHRZT | ||||
| FALAR | IS-H: Case Type | FALLART | CHAR | 1 | FALLART | ||||
| FALNR | IS-H: Case Number | FALNR | CHAR | 10 | Assigned to domain | ALPHA | FALNR | FAL | |
| FZIFF | Check Digit for Case | PZIFF_FALL | CHAR | 1 | PZIFF | PZF | |||
| GBDAT | IS-H: Birthdate | RI_GBDAT | DATS | 8 | RI_DATUM | ||||
| GSCHL | IS-H: Sex Indicator - User-Specific | GSCHLE | CHAR | 1 | Assigned to domain | GSCHLE | |||
| KOSTR | IS-H: Insurance Provider | KH_KOSTR | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | KOT | |
| LFDNR | IS-H: Sequence Number of Insurance Relationship | LFDVV | NUMC | 3 | LFDVV | ||||
| NNAME | Patient Last Name | NNAME_PAT | CHAR | 30 | TEXT30 | ||||
| PATNR | IS-H: Patient Number | PATNR | CHAR | 10 | Assigned to domain | ALPHA | PATNR | PAT | |
| PLANAUF | Planned/Actual Admission Indicator | PLANAUF | CHAR | 1 | ISH_PLAN | ||||
| PLANENT | Planned/Actual Discharge Indicator | PLANENT | CHAR | 1 | ISH_PLAN | ||||
| PNAME | IS-H: Patient Name | RI_NAME | CHAR | 30 | TEXT30 | ||||
| SNBEW | IS-H: Indicator whether the user selected a movement | SEL_NBEW | CHAR | 1 | XFELD | ||||
| STATU | IS-H: Case Status | FALLSTATUS | CHAR | 1 | FALLSTATUS | ||||
| STORN | IS-H: Cancellation Indicator | RI_STORN | CHAR | 1 | XFELD | ||||
| OKURZ1 | Organizational Unit Identifier | ISH_OKURZ | CHAR | 38 | TEXT38 | ||||
| OKURZ2 | Organizational Unit Identifier | ISH_OKURZ | CHAR | 38 | TEXT38 | ||||
| BELNR | IS-H: Document Number of IV Document/Treatment Certificate | KS_BELNR | CHAR | 10 | Assigned to domain | ALPHA | KS_BELNR | ||
| LAND | IS-H: Country of patient's place of residence | LAND_PAT | CHAR | 3 | Assigned to domain | LAND1 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNEXL using ABAP code?
As RNEXL 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 RNEXL as there is no data to select.How to access SAP table RNEXL
Within an ECC or HANA version of SAP you can also view further information about RNEXL 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