RNCHCM1 SAP (IS-HCM HCM precustomizing screen fields) Structure details
Description: IS-HCM HCM precustomizing screen fields
Structure field list including key, data, relationships and ABAP select examples
RNCHCM1 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-HCM HCM precustomizing screen fields" 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_RNCHCM1 TYPE RNCHCM1.
The RNCHCM1 table consists of various fields, each holding specific information or linking keys about IS-HCM HCM precustomizing screen fields data available in SAP. These include EINRI (Institution), SYSTID (IS-H: Unique system identification (logical name)), SYSTYP (IS-H: System Type Specification), ISHREL (IS-H: Release).. 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 RNCHCM1 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 | TN01 | ALPHA | EINRI | EIN | |
SYSTID | IS-H: Unique system identification (logical name) | ISH_SYSTEM | CHAR | 8 | TN02S | ALPHA | ISH_SYSTEM | ||
SYSTYP | IS-H: System Type Specification | SYSTYP | CHAR | 2 | ALPHA | SYSTYP | |||
ISHREL | IS-H: Release | ISHREL | CHAR | 4 | ALPHA | ISHREL | |||
DBREM | IS-H: Identification of External System | DBREM | CHAR | 1 | XFELD | ||||
XCOMNAME | IS-HCM: Name of the Communication Partner in Table TXCOM | XCOMNAME | CHAR | 8 | XUHDEST | ||||
STAND | IS-HCM: Communications Standard | CMSTD | CHAR | 8 | TNCST | NTSTD | |||
STVER | IS-HCM: Version of Communication Standard | STDVER | CHAR | 3 | TNCST | NTVER | |||
SPECHARS | IS-HCM: Special Characters Agreed (Standard-Dependent) | SPECHARS | CHAR | 6 | CHAR6 | ||||
ALLINONE | IS-HCM: Write all messages to file NTISH.dat | NALLINONE | CHAR | 1 | XFELD | ||||
SPERRKZ | Blocking Indicator | RI_SPERR | CHAR | 1 | XFELD | ||||
SDEST | Symbolic destination | SDEST | CHAR | 8 | XUHDEST | ||||
LU | Logical Unit | LU | CHAR | 8 | LU | ||||
TP | Transaction program | TP | CHAR | 8 | TP | ||||
TPPUT | Long TP name | LONGTP | CHAR | 64 | LONGTP | ||||
TPGET | Long TP name | LONGTP | CHAR | 64 | LONGTP | ||||
TPRESP | Long TP name | LONGTP | CHAR | 64 | LONGTP | ||||
CTYPE | Communications type | CTYPE | CHAR | 1 | CTYPE | ||||
GWHOST | Gateway host | GWHOST | CHAR | 20 | GWHOST | ||||
GWSERV | Gateway service | GWSERV | CHAR | 20 | GWSERV | ||||
APPLK | Application (Always N for IS-H) | APPKL | CHAR | 1 | APPKL | ||||
EVENT | IS-H: Event for Triggering Messages, Forms | N_EVENT | CHAR | 6 | Assigned to domain | N_EVENT | |||
NTNR | IS-HCM: Message Type Number Supported by SAP INBOUND | N_SUPPNTNO | CHAR | 3 | Assigned to domain | N_SUPPNTNO | |||
KZORGABH | Indicator for Org. Unit-Dependent Dispatch Control | KZORGABH | CHAR | 1 | XFELD | ||||
EK | IS-HCM: Message Type Owner Code | NTOWNERCDE | CHAR | 2 | NTOWNERCDE | ||||
RFCDEST | IS-HCM: Logical Destination for Remote Function Call | ISHRFCDEST | CHAR | 32 | RFCDES | RFCDEST | RFC | ||
FUNAM | IS-H: Remote Function (Module) Name (Target Computer) | RFNAME | CHAR | 30 | Assigned to domain | FUNCNAME | |||
IFFUB | IS-HCM: Cust. interface FM for Express dispatch | N_CIFUB | CHAR | 30 | TFDIR | FUNCNAME | |||
CODEPAGE | SAP Character Set ID | CPCODEPAGE | NUMC | 4 | TCP00 | CPCODEPAGE |
Key field | Non-key field |
How do I retrieve data from SAP structure RNCHCM1 using ABAP code?
As RNCHCM1 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 RNCHCM1 as there is no data to select.How to access SAP table RNCHCM1
Within an ECC or HANA version of SAP you can also view further information about RNCHCM1 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