RNCORDER SAP (IS-HCM Interface structure of ISHCM_ORDER_DISPATCH) Structure details
Description: IS-HCM Interface structure of ISHCM_ORDER_DISPATCH
Structure field list including key, data, relationships and ABAP select examples
RNCORDER 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-HCM Interface structure of ISHCM_ORDER_DISPATCH" 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_RNCORDER TYPE RNCORDER.
The RNCORDER table consists of various fields, each holding specific information or linking keys about IS-HCM Interface structure of ISHCM_ORDER_DISPATCH data available in SAP. These include EVENT (IS-H: Event for Triggering Messages, Forms), EINRI (Institution), PATNR (IS-H: Patient Number), FALNR (IS-H: Case 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 RNCORDER 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 |
| APPLK | Application (Always N for IS-H) | APPKL | CHAR | 1 | APPKL | ||||
| EVENT | IS-H: Event for Triggering Messages, Forms | N_EVENT | CHAR | 6 | Assigned to domain | N_EVENT | |||
| EINRI | Institution | EINRI | CHAR | 4 | Assigned to domain | ALPHA | EINRI | EIN | |
| PATNR | IS-H: Patient Number | PATNR | CHAR | 10 | Assigned to domain | ALPHA | PATNR | PAT | |
| FALNR | IS-H: Case Number | FALNR | CHAR | 10 | Assigned to domain | ALPHA | FALNR | FAL | |
| LFDNR | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
| ORGFA | IS-H: OU with Departmental Responsibility for Case | NZUWFA | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ORGPF | Organizational Unit Assigned to Case | NZUWPF | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| GPART | IS-H: Business Partner | GPARTNER | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | NGP | |
| PRIORPATNR | IS-H: Patient Number | PATNR | CHAR | 10 | Assigned to domain | ALPHA | PATNR | PAT | |
| PRIORPZIFF | Check Digit for Patient | PZIFF_PAT | CHAR | 1 | PZIFF | PZP | |||
| ANFKEY | IS-HCM: Reference for ISH*Med ID Request (Number) | NANFID | NUMC | 8 | VANR | ||||
| ORGFA_OLD | IS-H: OU with Departmental Responsibility for Case | NZUWFA | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| ORGPF_OLD | Organizational Unit Assigned to Case | NZUWPF | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| DOKAR | Document Type | DOKAR | CHAR | 3 | Assigned to domain | DOKAR | CV2 | ||
| DOKNR | Document number | DOKNR | CHAR | 25 | Assigned to domain | ALPHA | DOKNR | CV1 | |
| DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
| DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
| LFDDOK | Sequence Number of Document | LFDDOK | INT4 | 10 | INT4_NOS | ||||
| SUBKEY1 | IS-H: Additional key value for single event processing | SUBKEYARG | CHAR | 20 | TEXT20 | ||||
| SUBKEY2 | IS-H: Additional key value for single event processing | SUBKEYARG | CHAR | 20 | TEXT20 | ||||
| SUBKEY3 | IS-H: Additional key value for single event processing | SUBKEYARG | CHAR | 20 | TEXT20 | ||||
| SUBKEY4 | IS-H: Additional key value for single event processing | SUBKEYARG | CHAR | 20 | TEXT20 | ||||
| SUBKEY5 | IS-H: Additional key value for single event processing | SUBKEYARG | CHAR | 20 | TEXT20 | ||||
| SUBKEY6 | IS-H: Additional key value for single event processing | SUBKEYARG | CHAR | 20 | TEXT20 | ||||
| MEDRECID | IS-H : Identifier for the Medical Record Folder | ISH_MEDRECID | CHAR | 35 | ISH_MEDRECID | ||||
| EXEC_FLAG | IS-H: Boolean Data Type for ON (= 'X') and OFF (= ' ') | ISH_ON_OFF | CHAR | 1 | ISH_ON_OFF |
| Key field | Non-key field |
How do I retrieve data from SAP structure RNCORDER using ABAP code?
As RNCORDER 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 RNCORDER as there is no data to select.How to access SAP table RNCORDER
Within an ECC or HANA version of SAP you can also view further information about RNCORDER 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