RN1ANF_DAT SAP (IS-H*MED: N1ANF structure enhanced by planned date) Structure details
Dictionary Type: Structure
Description: IS-H*MED: N1ANF structure enhanced by planned date
Description: IS-H*MED: N1ANF structure enhanced by planned date
Structure field list including key, data, relationships and ABAP select examples
RN1ANF_DAT 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: N1ANF structure enhanced by planned date" 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_RN1ANF_DAT TYPE RN1ANF_DAT.
The RN1ANF_DAT table consists of various fields, each holding specific information or linking keys about IS-H*MED: N1ANF structure enhanced by planned date data available in SAP. These include MANDT (Client), EINRI (Institution), ANFID (Identification of a Request (Number)), ORGID (Identification Key of Organizational Unit).. 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 RN1ANF_DAT 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 |
| MANDT | Client | MANDT | CLNT | 3 | T000 | MANDT | |||
| 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 | |
| ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | NORG | ALPHA | ORGID | ||
| ANPOE | IS-H: Nursing Organizational Unit Requesting the Service | ANPOE | CHAR | 8 | NORG | ALPHA | ORGID | ||
| ANFTY | Request Type | ANFTY | CHAR | 6 | N1ANFTYP | ANFTY | |||
| 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 | |||
| APRI | Prioritization for Request/Movement (Internal) | N1APRI_D | NUMC | 3 | N1APRI | ||||
| 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 | |||
| 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 | |||
| 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 | ||||
| STORN | IS-H: Cancellation Indicator | RI_STORN | CHAR | 1 | XFELD | ||||
| STUSR | IS-H: Name of User who Canceled Data Record | STORN_USER | CHAR | 12 | USNAM | ||||
| STDAT | Date of Cancellation | STORN_DAT | DATS | 8 | RI_DATUM | ||||
| BHANF | Request Remarks | N1BHANF | CHAR | 50 | TEXT50 | ||||
| BHATX | Indicator that Long Text Exists | RI_LGTXT | CHAR | 1 | XFELD | ||||
| PATNR | IS-H: Patient Number | PATNR | CHAR | 10 | NPAT | ALPHA | PATNR | PAT | |
| DITXT | Diagnosis for a Preregistration | N1VKDIAG | CHAR | 50 | CHAR50 | ||||
| DILTX | Indicator that Long Text Exists | RI_LGTXT | CHAR | 1 | XFELD | ||||
| VBUND | N1ANFVBD | CHAR | 1 | XFELD | |||||
| 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 | ||||
| ORGFD | OU of the Patient Transport Service | N1ORGFD | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
| PAPID | IS-H: Provisional Patient Number | ISH_PAPID | CHAR | 10 | NPAP | ALPHA | ISH_PAPID | ||
| PBGDT | IS-H: Planned Date of Preregistration | N1VKPDT | DATS | 8 | DATS |
| Key field | Non-key field |
How do I retrieve data from SAP structure RN1ANF_DAT using ABAP code?
As RN1ANF_DAT 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 RN1ANF_DAT as there is no data to select.How to access SAP table RN1ANF_DAT
Within an ECC or HANA version of SAP you can also view further information about RN1ANF_DAT 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