RN2GL_BADI_REQ_IMP SAP (Base Items: Result of Request) Structure details
Dictionary Type: Structure
Description: Base Items: Result of Request
Description: Base Items: Result of Request
ABAP Code to SELECT data from RN2GL_BADI_REQ_IMP
Related tables to RN2GL_BADI_REQ_IMP
Access table RN2GL_BADI_REQ_IMP
Related tables to RN2GL_BADI_REQ_IMP
Access table RN2GL_BADI_REQ_IMP
Structure field list including key, data, relationships and ABAP select examples
RN2GL_BADI_REQ_IMP 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 "Base Items: Result of 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_RN2GL_BADI_REQ_IMP TYPE RN2GL_BADI_REQ_IMP.
The RN2GL_BADI_REQ_IMP table consists of various fields, each holding specific information or linking keys about Base Items: Result of Request 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 (Deep)
SAP RN2GL_BADI_REQ_IMP 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 |
| N1ANF | 0 | ||||||||
| MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
| EINRI | Institution | EINRI | CHAR | 4 | ALPHA | EINRI | EIN | ||
| ANFID | Identification of a Request (Number) | ANFID | NUMC | 8 | ANFID | ||||
| ORGID | Identification Key of Organizational Unit | ORGID | CHAR | 8 | ALPHA | ORGID | OGE | ||
| ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | ALPHA | ORGID | |||
| ANPOE | IS-H: Nursing Organizational Unit Requesting the Service | ANPOE | CHAR | 8 | ALPHA | ORGID | |||
| ANFTY | Request Type | ANFTY | CHAR | 6 | ANFTY | ||||
| ANFNR | Request Number | N1ANFNR | CHAR | 8 | N1ANFNR | ||||
| FALNR | IS-H: Case Number | FALNR | CHAR | 10 | ALPHA | FALNR | FAL | ||
| ANSTAE | Status of a Request | N1ANSTAE | CHAR | 3 | 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 | 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 | N1TPAE | ||||
| RCKRUF | Callback Number for Request | N1RCKRUF | CHAR | 10 | TEXT10 | ||||
| DOKAR | Document Type | DOKAR | CHAR | 3 | DOKAR | CV2 | |||
| DOKNR | Document number | DOKNR | CHAR | 25 | 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 | 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 | ALPHA | ORGID | |||
| PAPID | IS-H: Provisional Patient Number | ISH_PAPID | CHAR | 10 | ALPHA | ISH_PAPID | |||
| T_NLEI | 0 | ||||||||
| T_NLEM | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure RN2GL_BADI_REQ_IMP using ABAP code?
As RN2GL_BADI_REQ_IMP 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 RN2GL_BADI_REQ_IMP as there is no data to select.How to access SAP table RN2GL_BADI_REQ_IMP
Within an ECC or HANA version of SAP you can also view further information about RN2GL_BADI_REQ_IMP 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