RN1_DYNP_OE_HIER SAP (i.s.h.med: Screen Structure for OU Hierarchy) Structure details
Description: i.s.h.med: Screen Structure for OU Hierarchy
Related tables to RN1_DYNP_OE_HIER
Access table RN1_DYNP_OE_HIER
Structure field list including key, data, relationships and ABAP select examples
RN1_DYNP_OE_HIER 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 "i.s.h.med: Screen Structure for OU Hierarchy" 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_RN1_DYNP_OE_HIER TYPE RN1_DYNP_OE_HIER.
The RN1_DYNP_OE_HIER table consists of various fields, each holding specific information or linking keys about i.s.h.med: Screen Structure for OU Hierarchy data available in SAP. These include HIER_LEVEL (i.s.h.med: Hierarchy Level), NAME (Name of Organizational or Building Unit), TYPE (i.s.h.med: Organizational Unit or Building Unit), FAZUW (Indicator that Departmental Assignment Is Allowed).. 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 RN1_DYNP_OE_HIER 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 |
| NODE_KEY | ALV Tree Control: Node Key | LVC_NKEY | CHAR | 12 | |||||
| HIER_LEVEL | i.s.h.med: Hierarchy Level | RN1_HIER_LEV | NUMC | 2 | NUMC2 | ||||
| NAME | Name of Organizational or Building Unit | ISH_ORGNA_BAUNA | CHAR | 30 | TEXT30 | ||||
| TYPE | i.s.h.med: Organizational Unit or Building Unit | N1OUBU | CHAR | 2 | N1OUBU | ||||
| FAZUW | Indicator that Departmental Assignment Is Allowed | FAZUW | CHAR | 1 | XFELD | ||||
| PFZUW | Nursing Assignment Is Allowed | ISH_PFZUW | CHAR | 1 | XFELD | ||||
| AMBES | Outpatient Visit Allowed | AMBES | CHAR | 1 | XFELD | ||||
| INTKZ | Interdepartmental Bed Assignment Possible | RI_INTKZ | CHAR | 1 | XFELD | ||||
| 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 | ||||
| ASSIG | Building Unit-to-Organizational Unit Assignment | ISH_OU_BU_ASSIG | CHAR | 1 | ISH_OU_BU_ASSIG | ||||
| ORGID | Identification Key of Organizational Unit | ORGID | CHAR | 8 | Assigned to domain | ALPHA | ORGID | OGE | |
| BAUID | IS-H: Identification of Building Unit | BAUID | CHAR | 8 | Assigned to domain | ALPHA | BAUID | BAU | |
| N1APL | Indicator for Work Station | N1APL | CHAR | 1 | XFELD | ||||
| N1ANFKZ | Can be Requested Indicator | N1ANFKZ | CHAR | 1 | XFELD | ||||
| N1DIKZ | Scheduling Indicator | N1DIKZ | CHAR | 1 | XFELD | ||||
| N1ERBRKZ | Performability Indicator | N1ERBRKZ | CHAR | 1 | XFELD | ||||
| SELECTED | IS-H: Boolean Data Type for ON (= 'X') and OFF (= ' ') | ISH_ON_OFF | CHAR | 1 | ISH_ON_OFF |
| Key field | Non-key field |
How do I retrieve data from SAP structure RN1_DYNP_OE_HIER using ABAP code?
As RN1_DYNP_OE_HIER 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 RN1_DYNP_OE_HIER as there is no data to select.How to access SAP table RN1_DYNP_OE_HIER
Within an ECC or HANA version of SAP you can also view further information about RN1_DYNP_OE_HIER 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