RN1MLEDATA SAP (IS-H*MED:IS-HCM structure for medical service data) Structure details
Description: IS-H*MED:IS-HCM structure for medical service data
Structure field list including key, data, relationships and ABAP select examples
RN1MLEDATA 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*MED:IS-HCM structure for medical service 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_RN1MLEDATA TYPE RN1MLEDATA.
The RN1MLEDATA table consists of various fields, each holding specific information or linking keys about IS-H*MED:IS-HCM structure for medical service data data available in SAP. These include MANDT (Client), EINRI (Institution), FALNR (IS-H: Case Number), FZIFF (Check Digit for Case).. 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 RN1MLEDATA 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 |
IDENTIFIER | IS-H: Service Sequence Number | LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
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 | |
FZIFF | Check Digit for Case | PZIFF_FALL | CHAR | 1 | PZIFF | PZF | |||
MODULO | IS-H: Coding of Modulo Method for Check Digit | ISH_MODULO | CHAR | 3 | ISH_MODULO | ||||
ORGID | IS-H: Org. Unit (for OU-Related Service Entry Only) | ORGID_LS | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OGE | |
LEIST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
LEITX | IS-H: Service Short Text (May Differ from Service Master) | TEXT_LEI | CHAR | 40 | LEIKTXT | ||||
ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ANPOE | IS-H: Nursing Organizational Unit Requesting the Service | ANPOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ERBOE | IS-H: Organizational Unit that Performs the Service | ERBOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
HAUST | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | Assigned to domain | ALPHA | TARID | TAK | |
TARAS | IS-H: Multiplication Factor | TARAS6 | DEC | 6(3) | ISH_TARAS6 | ||||
ABRKZ | Service Can Be Billed For | ABRKZ | CHAR | 1 | ABRKZ_LS | ||||
IMENG | Service Quantity | I_MENG_LS | NUMC | 4 | LEISMENGE | ||||
IBGDT | IS-H: Date when Service Performance Starts (Actual) | I_BDT_LS | DATS | 8 | RI_DATUM | ||||
IBZT | IS-H: Time when Service Performance Starts (Actual) | I_BZT_LS | TIMS | 6 | UHRZT | ||||
IENDT | IS-H: Date when Service Performance Ends (Actual) | I_EDT_LS | DATS | 8 | RI_DATUM | ||||
IEZT | IS-H: Time Service Performance Ends (Actual) | I_EZT_LS | TIMS | 6 | UHRZT | ||||
ERBTY | Type of Service Performance | TYP_ERBR | CHAR | 1 | TYP_ERBR | ||||
LFDNR | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
ANFID | Identification of a Request (Number) | ANFID | NUMC | 8 | Assigned to domain | ANFID | |||
LNRLS | IS-H: Service Sequence Number | LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
NTRKZ | Indicator for Subsequently Added Service | NTRKZ | CHAR | 1 | XFELD | ||||
LSSTA | Service Status | N1LSSTA_D | CHAR | 3 | N1LSSTA | ||||
LSSTAE | Service Status - User-Specific | N1LSSTAE | CHAR | 3 | Assigned to domain | N1LSSTAE | |||
LSSTTXT | Service Status Text | N1LSSTTXT | CHAR | 10 | N1C010 | ||||
GPART | Employee Responsible | N1MITARB | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | VMA | |
NAME1 | IS-H: Last Name/ 1st Name | GPNAM1 | CHAR | 35 | NAME | NA1 | |||
NAME2 | First Name / Second Name | GPNAM2 | CHAR | 35 | NAME | ||||
WBGDT | Desired Start Date of a Service | W_BDT_LS | DATS | 8 | RI_DATUM | ||||
WBGZT | Desired Start Time of a Service | W_BZT_LS | TIMS | 6 | UHRZT | ||||
ERGTX | Supplementary Text | N1ERGTX | CHAR | 50 | TEXT50 | ||||
OBJTP | Code for document class | SO_OBJ_TP | CHAR | 3 | Assigned to domain | SO_OBJ_TP | |||
STOID | Reason for Canceling Medical Object | N1STOID | CHAR | 3 | Assigned to domain | N1STOID | |||
STOTX | Text for Cancellation Reason | N1STOTX | CHAR | 15 | N1C015 |
Key field | Non-key field |
How do I retrieve data from SAP structure RN1MLEDATA using ABAP code?
As RN1MLEDATA 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 RN1MLEDATA as there is no data to select.How to access SAP table RN1MLEDATA
Within an ECC or HANA version of SAP you can also view further information about RN1MLEDATA 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