RNBQSCTR SAP (BQS: Control Table for QA Requirement) Structure details
Description: BQS: Control Table for QA Requirement
Structure field list including key, data, relationships and ABAP select examples
RNBQSCTR 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 "BQS: Control Table for QA Requirement" 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_RNBQSCTR TYPE RNBQSCTR.
The RNBQSCTR table consists of various fields, each holding specific information or linking keys about BQS: Control Table for QA Requirement data available in SAP. These include EINRI (Institution), FALNR (IS-H: Case Number), MODUL (IS-H: Number of the QA FR/PS Module), LFDBEW (IS-H: Sequence Number of Movement).. 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 RNBQSCTR 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 | 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 | |
MODUL | IS-H: Number of the QA FR/PS Module | ISH_MODNR | CHAR | 5 | ISH_MODNR | ||||
LFDBEW | IS-H: Sequence Number of Movement | LFDBEW | NUMC | 5 | Assigned to domain | LFDBEW | |||
LNRIC0 | IS-H: Sequence Number of Surgical Procedure Code | ISH_LNRIC | CHAR | 10 | ALPHA | ISH_LNRIC | |||
ICPMK | IS-H: Identification of Surgical Procedure Coding Catalog | ICPM_ID | CHAR | 2 | Assigned to domain | ALPHA | TARID | ||
ICPML0 | IS-H: Surgical Procedure Code (Service) | ICPM_LS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | ||
ICPHC0 | IS-H: Main Surgical Procedure Code | ICPM_HCODE | CHAR | 1 | XFELD | ||||
BGDOP0 | IS-H: Date when Surgical Procedure Code Performed | ISH_BEGDT_ICP | DATS | 8 | RI_DATUM | ||||
LNRLS0 | IS-H: Service Sequence Number | LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
ANFOE | Departmental Organizational Unit That Requests the Service | ANFOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ERBOE | IS-H: Organizational Unit that Performs the Service | ERBOE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
FACHR1 | Specialty According to Federal Regulation for Hospitals 1995 | FACHRTY0 | CHAR | 4 | Assigned to domain | ALPHA | ISH_FACHR | ||
LNRIC1 | IS-H: Sequence Number of Surgical Procedure Code | ISH_LNRIC | CHAR | 10 | ALPHA | ISH_LNRIC | |||
ICPML1 | IS-H: Surgical Procedure Code (Service) | ICPM_LS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | ||
LNRIC2 | IS-H: Sequence Number of Surgical Procedure Code | ISH_LNRIC | CHAR | 10 | ALPHA | ISH_LNRIC | |||
ICPML2 | IS-H: Surgical Procedure Code (Service) | ICPM_LS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | ||
LEIST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
LNRLS_LEIST | BQS: Service Number FR/PS | NBQS_LNRLS | CHAR | 10 | ALPHA | LNRLS | |||
OPTLEI | BQS: Service Proposal According to the Option Model | NBQS_OPTLEI | CHAR | 10 | Assigned to domain | ALPHA | TARLS | ||
TARIF | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | Assigned to domain | ALPHA | TARID | TAK | |
TALST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
DKAT1 | IS-H: Identification Key of Diagnosis Coding Catalog | DIAKAT | CHAR | 2 | KATID | ||||
DKEY1 | IS-H: Diagnosis Code | DIAID | CHAR | 30 | DIAID | ||||
DKAT2 | IS-H: Identification Key of Diagnosis Coding Catalog | DIAKAT | CHAR | 2 | KATID | ||||
DKEY2 | IS-H: Diagnosis Code | DIAID | CHAR | 30 | DIAID | ||||
DKAT3 | IS-H: Identification Key of Diagnosis Coding Catalog | DIAKAT | CHAR | 2 | KATID | ||||
DKEY3 | IS-H: Diagnosis Code | DIAID | CHAR | 30 | DIAID | ||||
FTYPE | BQS: Specialty Category of the Assignment | NBQS_FTYPE | CHAR | 1 | CHAR1 | ||||
ICDS | BQS: Assignment Dependent on Diagnoses | NBQS_ICDS | CHAR | 1 | NBQS_ICDS | ||||
FREI | BQS: 'QA Required/Voluntary' Indicator | NBQS_FREI | CHAR | 1 | NBQS_FREIW | ||||
STUFE | BQS: Classification According to BQS | NBQS_STUFE | CHAR | 1 | NBQS_STUFE | ||||
UBOGEN | BQS - Indicator for a Section | NBQS_UBOGEN | CHAR | 1 | CHAR1 | ||||
PFREI | Control of Voluntary Documentation by User Parameter | NBQS_PFREI | CHAR | 1 | NBQS_FREIW | ||||
PORG | Control of Specialty Determination by User Parameter | NBQS_PORG | CHAR | 1 | NBQS_PORG |
Key field | Non-key field |
How do I retrieve data from SAP structure RNBQSCTR using ABAP code?
As RNBQSCTR 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 RNBQSCTR as there is no data to select.How to access SAP table RNBQSCTR
Within an ECC or HANA version of SAP you can also view further information about RNBQSCTR 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