RNB10 SAP (IS-H: Screen fields etc. module pool SAPMNB10/SAPMNB20) Structure details
Description: IS-H: Screen fields etc. module pool SAPMNB10/SAPMNB20
Structure field list including key, data, relationships and ABAP select examples
RNB10 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: Screen fields etc. module pool SAPMNB10/SAPMNB20" 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_RNB10 TYPE RNB10.
The RNB10 table consists of various fields, each holding specific information or linking keys about IS-H: Screen fields etc. module pool SAPMNB10/SAPMNB20 data available in SAP. These include VORNA (First Name / Second Name), EINRI (Institution), EINKB (IS-H: Short Text for Institution), LANDX (Country Name).. 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 RNB10 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 |
PERNR | IS-H: Person Number | RI_PERNR | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | NGP | |
VORNA | First Name / Second Name | GPNAM2 | CHAR | 35 | NAME | ||||
EINRI | Institution | EINRI | CHAR | 4 | TN01 | ALPHA | EINRI | EIN | |
EINKB | IS-H: Short Text for Institution | EINKB | CHAR | 15 | TEXT15 | ||||
LANDX | Country Name | LANDX | CHAR | 15 | TEXT15 | ||||
LOEKZ | Deletion Flag/Indicator | RI_LOEKZ | CHAR | 1 | XFELD | ||||
GESCH | IS-H: Sex Indicator - User-Specific | GSCHLE | CHAR | 1 | Assigned to domain | GSCHLE | |||
ORSW1 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ1 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW2 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ2 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW3 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ3 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW4 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ4 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW5 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ5 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW6 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ6 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW7 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ7 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW8 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ8 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSW9 | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZ9 | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORSWX | IS-H: Key word for organizational units | ORGSW | CHAR | 4 | TEXT4 | ||||
ORKZX | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORGID | Identification Key of Organizational Unit | ORGID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OGE | |
ORGTY | IS-H: Category of Organizational Unit | ORGTYP | CHAR | 2 | TN10A | ORGTYP | OTY | ||
ORGKB | IS-H: Organizational Unit Short Text | ORGKB | CHAR | 12 | TEXT12 | ||||
OTTXT | IS-H: Text Describing Organizational Unit Category | OTTXT | CHAR | 20 | TEXT20 | ||||
ORGNA | IS-H: Organizational Unit Name | ORGNA | CHAR | 30 | TEXT30 | ||||
OKURZ | IS-H: Identifier of Organizational Unit in the Application | OEKURZ | CHAR | 5 | ORGKZ | ||||
ORT2 | District | ORT02 | CHAR | 25 | TEXT25 | ||||
FORID | IS-H: ID of Assigning Department of a Logical Org. Unit | FORID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
FORKZ | IS-H: Identifier of dept. w. inter-dept. bed asgmt authority | FORKZ | CHAR | 5 | ORGKZ | ||||
BEGDT | IS-H: Valid-From Date of Record | RI_BEGDT | DATS | 8 | RI_DATUM | ||||
ENDDT | IS-H: Valid-To Date of Record | RI_ENDDT | DATS | 8 | RI_DATUM | ||||
UNTOR | IS-H: Lower-level organizational unit | UNTOR | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
UEBOR | IS-H: Higher-Level Organizational Unit | UEBOR | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ORGIN | IS-H: OU to which patients Are Assigned from Other Depts | ORGIN | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ORGBE | IS-H: OU with Inter-Departmental Bed Assignment Authority | ORGBE | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
FATXT1 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT2 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT3 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT4 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT5 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT6 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT7 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
FATXT9 | IS-H: Name of Specialty | TEXT_KFA | CHAR | 30 | TEXT30 | ||||
BAUAR | IS-H: Building Unit Type | BAUART | CHAR | 2 | BAUART | ||||
BAUTY | Category of a Building Unit | BAUTYPEX | CHAR | 2 | Assigned to domain | BAUTYPEX | BTY | ||
BAUKB | IS-H: Short Text for Building Unit | BAUKB | CHAR | 12 | TEXT12 | ||||
BAUNA | Building Unit Name | BAUNA | CHAR | 30 | TEXT30 | ||||
BAUID | IS-H: Identification of Building Unit | BAUID | CHAR | 8 | Assigned to domain | ALPHA | BAUID | BAU | |
BTTXT | IS-H: Text Describing Building Unit Category | BAUTYPTXT | CHAR | 20 | TEXT20 | ||||
UNTBE | Is-H: Identification of Lower-Level Building Unit | BAUID_UNT | CHAR | 8 | NBAU | ALPHA | BAUID | ||
UEBBE | IS-H: Indentification of Higher-Level Building Unit | BAUID_UEB | CHAR | 8 | NBAU | ALPHA | BAUID | ||
AUSID | Facilities Key of an Organizational Unit | AUSID | CHAR | 4 | TN11G | AUSID | |||
TARIF | IS-H: Service Catalog Identification Key | TARID | CHAR | 2 | Assigned to domain | ALPHA | TARID | TAK | |
KATBE | Short Description of Catalog | KATKB | CHAR | 10 | TEXT10 | ||||
KATKB | Short Description of Catalog | KATKB | CHAR | 10 | TEXT10 | ||||
TALST | Service in Service Catalog | TARLS | CHAR | 10 | Assigned to domain | ALPHA | TARLS | TAL | |
LGTXT | Screen Field for Displaying Dynamic Icon | ISH_LGTX03 | CHAR | 30 | ISH_ICON | ||||
BMTXT | Screen Field for Displaying Dynamic Icon | ISH_LGTX03 | CHAR | 30 | ISH_ICON | ||||
KTXT1 | IS-H: First Short Text for Service | TARKTXT1 | CHAR | 40 | LEIKTXT | ||||
ZOTYP | IS-H: Type of Service Assignment | ISH_ZUOTYP | CHAR | 3 | Assigned to domain | ALPHA | ISH_ZUOTYP | TZO | |
TTEXT | IS-H: Description of the type of service assignment | TYP_TEXT | CHAR | 20 | TYP_TEXT | ||||
KTEXT | IS-H: First Short Text for Service | TARKTXT1 | CHAR | 40 | LEIKTXT | ||||
TGRKZ | IS-H: Indicator Denoting a Service Group | TGRU_KZ | CHAR | 1 | XFELD | ||||
ORGFA | IS-H: Org. Unit with Departmental Assignment Authority | ISH_ORGFA | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ORGPF | Organizational Unit with Nursing Assignment Authority | ISH_ORGPF | CHAR | 8 | Assigned to domain | ALPHA | ORGID | ||
ORGFAKB | IS-H: Organizational Unit Short Text | ORGKB | CHAR | 12 | TEXT12 | ||||
ORGPFKB | IS-H: Organizational Unit Short Text | ORGKB | CHAR | 12 | TEXT12 | ||||
ORGFABDT | IS-H: Valid-From Date of Record | RI_BEGDT | DATS | 8 | RI_DATUM | ||||
ORGFAEDT | IS-H: Valid-To Date of Record | RI_ENDDT | DATS | 8 | RI_DATUM | ||||
VCODE | IS-H: Processing Mode | ISH_VCODE | CHAR | 3 | ISH_VCODE | ||||
NOGAP | IS-H: Completeness Indicator | ISH_NOGAP | CHAR | 1 | XFELD | ||||
CASE | IS-H: soer criterion item | ISH_POS | NUMC | 1 | NUM01 | ||||
BATXT | IS-H: Building category name | ISH_BATXT | CHAR | 50 | TEXT50 | ||||
ZIMKZ | IS-H: Building unit is Room | ISH_ZIMMKZ | CHAR | 1 | XFELD | ||||
BETKZ | IS-H: Building unit is a bed location | BETTKZ | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure RNB10 using ABAP code?
As RNB10 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 RNB10 as there is no data to select.How to access SAP table RNB10
Within an ECC or HANA version of SAP you can also view further information about RNB10 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