RNFN101 SAP (IS-H*MED: Structure for request) Structure details
Description: IS-H*MED: Structure for request
Structure field list including key, data, relationships and ABAP select examples
RNFN101 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: Structure for request" 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_RNFN101 TYPE RNFN101.
The RNFN101 table consists of various fields, each holding specific information or linking keys about IS-H*MED: Structure for request data available in SAP. These include ANFID (Identification of a Request (Number)), ORGID (Identification Key of Organizational Unit), ORGNA (IS-H: Organizational Unit Name), ANFOE (Departmental Organizational Unit That Requests the Service).. 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 RNFN101 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 |
EINRI | Institution | EINRI | CHAR | 4 | TN01 | ALPHA | EINRI | EIN | |
ANFID | Identification of a Request (Number) | ANFID | NUMC | 8 | Assigned to domain | ANFID | |||
ORGID | Identification Key of Organizational Unit | ORGID | CHAR | 8 | NORG | ALPHA | ORGID | OGE | |
ORGNA | IS-H: Organizational Unit Name | ORGNA | CHAR | 30 | TEXT30 | ||||
ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | NORG | ALPHA | ORGID | ||
ANFNA | IS-H: Organizational Unit Name | ORGNA | CHAR | 30 | TEXT30 | ||||
ANPOE | IS-H: Nursing Organizational Unit Requesting the Service | ANPOE | CHAR | 8 | NORG | ALPHA | ORGID | ||
ANPNA | IS-H: Organizational Unit Name | ORGNA | CHAR | 30 | TEXT30 | ||||
ANFTY | Request Type | ANFTY | CHAR | 6 | N1ANFTYP | ANFTY | |||
ANFNATYP | Request Type Name | ANFNA | CHAR | 30 | TEXT30 | ||||
ANFNR | Request Number | N1ANFNR | CHAR | 8 | N1ANFNR | ||||
FALNR | IS-H: Case Number | FALNR | CHAR | 10 | NFAL | ALPHA | FALNR | FAL | |
ANSTAE | Status of a Request | N1ANSTAE | CHAR | 3 | N1AST | N1ANSTAE | |||
ANSTATXT | Service Status Text | N1ANSTTXT | CHAR | 10 | N1C010 | ||||
APRI | Prioritization for Request/Movement (Internal) | N1APRI_D | NUMC | 3 | N1APRI | ||||
APRITXT | Text for Priority | N1APRITXT | CHAR | 15 | TEXT15 | ||||
KANAM | Short Anamnesis | KANAM | CHAR | 50 | TEXT50 | ||||
KALTX | Indicator that Long Text Exists | RI_LGTXT | CHAR | 1 | XFELD | ||||
FALDIA | IS-H: Case Number | FALNR | CHAR | 10 | NFAL | ALPHA | FALNR | FAL | |
LFDDIA | IS-H: Sequence Number of Diagnosis | LFDDIA | NUMC | 3 | LFDDIA | ||||
FRAGE | Request - Questions | ANFFRAGE | CHAR | 50 | TEXT50 | ||||
FRLTX | Indicator that Long Text Exists | RI_LGTXT | CHAR | 1 | XFELD | ||||
SCHWKZ | Indicator that Patient Is Pregnant | SCHWANGER | CHAR | 1 | XFELD | ||||
SCHWO | Week of Pregnancy | SCHWOCHE | NUMC | 2 | NUMC02 | ||||
LFDMEHR | Sequence Number of a Multiple Birth | LFDMEHR | NUMC | 5 | LFDMEHR | ||||
TPAE | Transport Type | N1TPAE | CHAR | 2 | N1TA | N1TPAE | |||
TPATXT | Text for Transport Type | N1TPATXT | CHAR | 15 | N1TPATXT | ||||
RCKRUF | Callback Number for Request | N1RCKRUF | CHAR | 10 | TEXT10 | ||||
DOKAR | Document Type | DOKAR | CHAR | 3 | TDWA | DOKAR | CV2 | ||
DOKNR | Document number | DOKNR | CHAR | 25 | DRAW | ALPHA | DOKNR | CV1 | |
DOKVR | Document Version | DOKVR | CHAR | 2 | DOKVR | CV3 | |||
DOKTL | Document Part | DOKTL_D | CHAR | 3 | DOKTL | CV4 | |||
GPART | Employee Responsible | N1MITARB | CHAR | 10 | NGPA | ALPHA | RI_KUNNR | VMA | |
GPART1 | Employee Responsible | N1MITARB | CHAR | 10 | NGPA | 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 | ||||
NAME3 | Third Name | GPNAM3 | CHAR | 35 | NAME | ||||
KNAME | IS-H: Short Name of Business Partner | KZNAME | CHAR | 12 | ISH_C12 | ||||
TEXT | 30 Characters | CHAR30 | CHAR | 30 | CHAR30 | ||||
ERDAT | IS-H: Date when Record Created | RI_ERDAT | DATS | 8 | RI_DATUM | ||||
ERUSR | IS-H: Name of Employee who Created Record | RI_ERNAM | CHAR | 12 | USNAM | ||||
UPDAT | IS-H: Date of Last Change | RI_UPDAT | DATS | 8 | RI_DATUM | ||||
UPUSR | IS-H: Name of Person who Last Changed Data | RI_UPNAM | CHAR | 12 | USNAM | ||||
MI | Metal Implants | N1METIMP | CHAR | 1 | XFELD | ||||
SM | Pacemaker | N1SM | CHAR | 1 | XFELD | ||||
KM | Contrast Medium Application | N1KM | CHAR | 1 | N1KM | ||||
JOD | Allergy to Iodine-Containing Contrast Medium | N1KM_JOD | CHAR | 1 | XFELD | ||||
ANDERE | Allergy to Other Contrast Medium | N1KM_ANDERE | CHAR | 1 | XFELD | ||||
KGR | Height in Cm | N1KGR | NUMC | 3 | N1N003 | ||||
KGEW | Body Weight in Kg | N1KGEW | NUMC | 3 | N1N003 | ||||
RP | X-Ray Log Exists | N1RP | CHAR | 1 | N1RP | ||||
RPID | X-Ray Log ID | N1RPID | CHAR | 40 | N1C040 |
Key field | Non-key field |
How do I retrieve data from SAP structure RNFN101 using ABAP code?
As RNFN101 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 RNFN101 as there is no data to select.How to access SAP table RNFN101
Within an ECC or HANA version of SAP you can also view further information about RNFN101 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